Ralf Krüger
Ralf Krüger
Das gleiche Problem tritt auch bei dem Adapter ioBroker.unifi auf. Hier werden die MAC-Adressen im Statenamen verwendet. Beispiel: {unifi.0.default.devices.11:22:33:44:55:66.num_sta} liefert immer 0. Soehe auch https://forum.iobroker.net/topic/4514/adapter-iobroker-unifi/466
Bestätigung für stale bot: Die Einschränkung besteht auch noch in vis V1.2.11
I think using an escape character would be the most intuitive method: `{unifi.0.default.devices.11\:22\:33\:44\:55\:66.num_sta}` for the state `unifi.0.default.devices.11:22:33:44:55:66.num_sta`
Thanks for the tip. Unfortunately, the links do not give any information about the status of the individual monitors. even if I evaluate the time series, paused monitors continue with...
+1 with this issue.
Yes, please update!
I get the same error message with different containers and some calls break with error 500. I think, it needs a delay between the calls. This could be configured with...
Same on my system. When the remote docker_proxy restarts, the integration will lost the connection and I have to restart Home Assistant to renable ist: ``` 2024-07-06 10:19:15.279 ERROR (MainThread)...
@ualex73 Yes, I installed & try it today with... - Custom Monitor Docker component for Home Assistant v1.19 - ghcr.io/tecnativa/docker-socket-proxy:0.1.2 - HA-Core 2024.7.1
I get the UptimeKuma-Statistics with the following Javascript using the /metrics subpage. It creates 4 states containing the number of checks per status. Maybe it will help you as long...