You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After some days of uptime some values are no longer read/updated.
For example it hits always:
ctlv2/hwcstoragetemp and ctlv2/Hc1FlowTemp
Other values are still being read and provided to home assistant
Rebooting the adapter shield ie. via the webinterface of the adapter fixes the issues.
I am using Home Assistant with the ebusd and Mosquitto broker addons.
The adapter is plugged-in via USB and uses ens:/dev/ttyACM0 as device id.
Is there any way to regularly schedule a reboot (ie. nightly) or trigger via API? This would not fix the issue but would be a fair workaround for me for the time being.
The text was updated successfully, but these errors were encountered:
Hi John, this is something i thought would be more complicated as i
could not directly see which command is being executed. But thinking
about it i was able to figure it out with the network analysis and could
create a curl command.
Am 26.01.2025 20:09, schrieb John:
you can simply issue the same request that is executed when pressing
the reboot button in the ui
--
Reply to this email directly, view it on GitHub [1], or unsubscribe
[2].
You are receiving this because you authored the thread.Message ID:
***@***.***>
After some days of uptime some values are no longer read/updated.
For example it hits always:
ctlv2/hwcstoragetemp and ctlv2/Hc1FlowTemp
Other values are still being read and provided to home assistant
Rebooting the adapter shield ie. via the webinterface of the adapter fixes the issues.
I am using Home Assistant with the ebusd and Mosquitto broker addons.
The adapter is plugged-in via USB and uses ens:/dev/ttyACM0 as device id.
Is there any way to regularly schedule a reboot (ie. nightly) or trigger via API? This would not fix the issue but would be a fair workaround for me for the time being.
The text was updated successfully, but these errors were encountered: