-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
home assistant mqtt sensor doesn't update #23
Comments
My former topic for this state was
With MQTTExplorer I noticed that the states
Do you know why? |
Hi, At first, I was thinking about a change in the gigaset json format... but it looks the same. By looking at the code (it has been a while I havent touched it), you should see something in the log gigaset-elements-proxy/src/mqtt.ts Line 104 in 0277627
Then, an event named gigaset-elements-proxy/src/mqtt.ts Line 105 in 0277627
|
I checked my basestation name in the App and it is still the same as before. When I delete all the entities in my MQTT broker regarding Gigaset, the Proxy will open the topic with the basestation name again but also one with „undefined“. |
There are two modes for reading the intrusion settings:
[edit] I don't see the second point in the code... we might have speak about it but never implemented it So it might be the "change intrusion settings mode" event structure that has changed. |
And that would be the reason why it opens that undefined topic? |
Well, if you have the |
Ok, strange I checked my config and I have allow_unknown_events set to false. |
I noticed that my automation did not work again. Without doing anything I get the right state in the old topic again. So I changed back my automation. Still strange that it used that undefined topic for a few days. Hope it stays like this. |
I have to reopen this, my automation failed again today. So it seems like it is switching the topics for some reason. |
I am also seeing this:
|
After having had a look at the event it became clear that the cause of this issue is that the API is no longer submitting the friendlyName with the event. The hex baseStationId is still provided, so I'm considering using that instead. This would be an incompatible change, though. @ycardon Any thoughts? |
No strong opinions, I'm not using this feature :) I can make the change but I don't have access to my Gigaset instance: could you post me a sample event and point me the field that will be used as the basestation friendly-name replacement ? (maybe we can also use a prefix like |
This is what I goto in the logs when I changed from home to away:
Would be great if that helps to fix it somehow. Note: I have allow_unknown_events set to false. |
My automation still doesn’t work because of this issue. Do you have an idea how to fix this? |
The version in my fork at https://github.com/ginkel/gigaset-elements-proxy seems to work for now. There is still some cleanup I'd like to perform before opening a MR, though. |
I just had a look on your fixes, I'll be glad to merge ! |
I still have this issue. I just randomly get the right state, most times "unknown". |
Hi @ginkel, are you happy with your changes ? If so I'm merging them. |
Thanks for merging my changes and sorry for not getting back to you earlier, @ycardon! There is one thing that's currently still broken, which prevented me from opening a PR: I used to do a refresh when starting Home Assistant via |
Ah ok, I reopen this issue until we find some time to investigate ! |
Would be great if you find time. I'm still on 1.3 because of the issue @ginkel mentioned above (force refresh) and one of my automations doesn't work because the state isn't reliable any more. Offtopic: @ycardon I don't want to open an issue for that. |
I have an experimental fix in https://github.com/ginkel/gigaset-elements-proxy, but I don't see why it's not working (the code in line 106 does not seem to get executed ginkel@52a32e5#diff-70fba6368d3fcd389b435446e2177ea0R106). |
Lately I'm facing some issues. All worked fine before for months.
The thing is the app does change the mode and I can also see current mode in "basestations". It seems like there some issue with mqtt (mind that all other things using mqtt work fine).
I don't see anything strange in the logs.
Edit: When I hit "Force refresh" the sensor updates correctly.
The text was updated successfully, but these errors were encountered: