-
-
Notifications
You must be signed in to change notification settings - Fork 20
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
V1.24.3 stucks on actualtemperature #591
Comments
The adapter normally gets data via Websocket connection. Thats means that when data are no longer updated then something is wrong there. What does the log state? Is there any issue or information about reconnects? |
The log does not say anything unfortunately. But if websockets will have the incorrect value why does hmip get the correct one after adapter restart of hmip? |
If there is a Websocket error it should say something. Maybe try to enable debug log and let it run a bit until it happens again |
There are no errors in the log. When I restart websocket the "old" temperature remains. If I restart hmip adapter it will be actualized to the correct data. Seems to be clear that hmip adapter causes the problem |
Obviously post #554 shows same problem! |
BTW in my IOBroker installation a websocket and a socket.io adapter is installed. Do I need both? Maybe they cause the confusion? |
Workaround: ActualTemperature will be saved in variable Temp each 120 minutes. If actualTemperature does not change by comparison to variable Temp within 120 minutes hmip adapter fails to synchronize. In that case hmip adapter will be forced to stop an restartet after 5 seconds delay. You have to switch to expert mode to access alive datapoints!! |
@Tom54497 Please set loglevel to debug and let it run until it happens Post then log from 1h before it starts to happen and 1h afterwards |
@Tom54497 hmip adapter has it's own Websocket connection so the websocket or socketio adapter has nothing to do with this at all |
Installed two instances of hmip. In the second one from time to time the actualtemperature value will not be refreshed. It stucks on the same value although looking at the temperature of the HM app it has changed. After restarting the adapter the correct value will show up. Made a workaround that when the value does not change for 24 hours I will get a notification to restart the adapter.
Any ideas to solve that?
The text was updated successfully, but these errors were encountered: