Is "Websocket Last Update" no longer available when "Enable polling for changes" disabled in System Options? #365
Replies: 1 comment
-
|
Well, I was going to reproduce this issue and "Reload Failed" issue I were seeing in the last few revision, however both issues are no longer happening. I don't know if it has anything to do with enabling polling for changes. Everything seems to be working fine now. I can reload the integration fine with polling disabled. Websocket Last Updated is being updated periodically as well. The only thing I am seeing now is this error in my HA logs: Log details (ERROR) ws heartbeat error Anyone have been seeing similar issues? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Is "Websocket Last Update" no longer available when "Enable polling for changes" disabled in System Options? In version 2.20.0, I noticed that "Websocket Last Update" seems to be "Unavailable". I personally use this to determine if my connection to the Carrier Cloud is good or not in my climate control automation. Instead of enabling the "Enable polling for changes" in System Options, in my automation, I just call Update entity every 5 minutes. This is done to reduce the number of Api call to the Carrier Cloud.
Please let me know if there was a code change in this version. Thanks!
Beta Was this translation helpful? Give feedback.
All reactions