Skip to content
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

Open
Tom54497 opened this issue Sep 24, 2024 · 11 comments
Open

V1.24.3 stucks on actualtemperature #591

Tom54497 opened this issue Sep 24, 2024 · 11 comments
Labels
duplicate This issue or pull request already exists

Comments

@Tom54497
Copy link

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?

@Apollon77
Copy link
Member

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?

@Apollon77 Apollon77 added the question Further information is requested label Sep 24, 2024
@Tom54497
Copy link
Author

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?

@Apollon77
Copy link
Member

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

@Tom54497
Copy link
Author

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

@Tom54497 Tom54497 changed the title V1.23.3 stucks on actualtemperature V1.24.3 stucks on actualtemperature Sep 28, 2024
@Tom54497
Copy link
Author

Obviously post #554 shows same problem!

@Tom54497
Copy link
Author

Tom54497 commented Sep 28, 2024

BTW in my IOBroker installation a websocket and a socket.io adapter is installed. Do I need both? Maybe they cause the confusion?

@Tom54497
Copy link
Author

Tom54497 commented Sep 28, 2024

Screenshot (188)

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!!

@mcm1957
Copy link
Member

mcm1957 commented Sep 28, 2024

Obviously post #554 shows same problem!

So lets close here as duplicate of #554. Problem will be tracked with earlier issue.

@mcm1957 mcm1957 closed this as not planned Won't fix, can't repro, duplicate, stale Sep 28, 2024
@mcm1957 mcm1957 added duplicate This issue or pull request already exists and removed question Further information is requested labels Sep 28, 2024
@mcm1957
Copy link
Member

mcm1957 commented Sep 28, 2024

Obviously post #554 shows same problem!

duplicate #554

@mcm1957 mcm1957 closed this as completed Sep 28, 2024
@Apollon77 Apollon77 reopened this Oct 1, 2024
@Apollon77
Copy link
Member

@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

@Apollon77
Copy link
Member

@Tom54497 hmip adapter has it's own Websocket connection so the websocket or socketio adapter has nothing to do with this at all

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

3 participants