Da ich nicht weiß, wer der Verursacher des Problems ist, lege ich hierzu auch einen Bug Report im IOT-Adapter an.
Siehe ioBroker.hm-rpc.
Nach längerem Testen scheint in meinen Augen aber der hm-rpc Adapter nicht das Problem zu sein,
da er mit gestoppten iot-Adapter keine Probleme macht. Erst wenn ich im iot-Adapter unter Alexa V3 Geräte mehr als 7 Geräte definiere, bekomme ich diese Fehlermeldungen.
2026-01-28 02:11:17.184 - �[32minfo�[39m: host.iobroker instance system.adapter.weatherunderground.0 having pid 1943673 terminated with code 0 (NO_ERROR)
2026-01-28 03:11:13.008 - �[32minfo�[39m: host.iobroker instance system.adapter.weatherunderground.0 in version "3.7.0" started with pid 1949310
2026-01-28 03:11:17.139 - �[32minfo�[39m: host.iobroker instance system.adapter.weatherunderground.0 having pid 1949310 terminated with code 0 (NO_ERROR)
2026-01-28 04:11:13.007 - �[32minfo�[39m: host.iobroker instance system.adapter.weatherunderground.0 in version "3.7.0" started with pid 1954962
2026-01-28 04:11:17.071 - �[32minfo�[39m: host.iobroker instance system.adapter.weatherunderground.0 having pid 1954962 terminated with code 0 (NO_ERROR)
2026-01-28 05:11:13.010 - �[32minfo�[39m: host.iobroker instance system.adapter.weatherunderground.0 in version "3.7.0" started with pid 1960127
2026-01-28 05:11:17.183 - �[32minfo�[39m: host.iobroker instance system.adapter.weatherunderground.0 having pid 1960127 terminated with code 0 (NO_ERROR)
2026-01-28 06:00:00.008 - �[32minfo�[39m: host.iobroker instance system.adapter.ical.0 in version "1.19.2" started with pid 1964812
2026-01-28 06:00:06.657 - �[32minfo�[39m: host.iobroker instance system.adapter.ical.0 having pid 1964812 terminated with code 0 (NO_ERROR)
2026-01-28 06:11:13.008 - �[32minfo�[39m: host.iobroker instance system.adapter.weatherunderground.0 in version "3.7.0" started with pid 1965748
2026-01-28 06:11:17.043 - �[32minfo�[39m: host.iobroker instance system.adapter.weatherunderground.0 having pid 1965748 terminated with code 0 (NO_ERROR)
2026-01-28 07:11:13.173 - �[32minfo�[39m: host.iobroker instance system.adapter.weatherunderground.0 in version "3.7.0" started with pid 1971496
2026-01-28 07:11:17.301 - �[32minfo�[39m: host.iobroker instance system.adapter.weatherunderground.0 having pid 1971496 terminated with code 0 (NO_ERROR)
2026-01-28 08:11:13.009 - �[32minfo�[39m: host.iobroker instance system.adapter.weatherunderground.0 in version "3.7.0" started with pid 1977096
2026-01-28 08:11:17.169 - �[32minfo�[39m: host.iobroker instance system.adapter.weatherunderground.0 having pid 1977096 terminated with code 0 (NO_ERROR)
2026-01-28 09:11:13.009 - �[32minfo�[39m: host.iobroker instance system.adapter.weatherunderground.0 in version "3.7.0" started with pid 1982704
2026-01-28 09:11:17.168 - �[32minfo�[39m: host.iobroker instance system.adapter.weatherunderground.0 having pid 1982704 terminated with code 0 (NO_ERROR)
2026-01-28 10:11:13.008 - �[32minfo�[39m: host.iobroker instance system.adapter.weatherunderground.0 in version "3.7.0" started with pid 1988806
2026-01-28 10:11:17.173 - �[32minfo�[39m: host.iobroker instance system.adapter.weatherunderground.0 having pid 1988806 terminated with code 0 (NO_ERROR)
2026-01-28 11:11:13.007 - �[32minfo�[39m: host.iobroker instance system.adapter.weatherunderground.0 in version "3.7.0" started with pid 1994430
2026-01-28 11:11:17.318 - �[32minfo�[39m: host.iobroker instance system.adapter.weatherunderground.0 having pid 1994430 terminated with code 0 (NO_ERROR)
2026-01-28 12:11:13.009 - �[32minfo�[39m: host.iobroker instance system.adapter.weatherunderground.0 in version "3.7.0" started with pid 2000553
2026-01-28 12:11:17.212 - �[32minfo�[39m: host.iobroker instance system.adapter.weatherunderground.0 having pid 2000553 terminated with code 0 (NO_ERROR)
2026-01-28 12:19:25.661 - �[33mwarn�[39m: hm-rpc.2 (560702) State "hm-rpc.2.003B6269909D61.0.CONFIG_PENDING" has no existing object, this might lead to an error in future versions
2026-01-28 12:19:25.664 - �[33mwarn�[39m: hm-rpc.2 (560702) State "hm-rpc.2.003B6269909D61.0.UNREACH" has no existing object, this might lead to an error in future versions
2026-01-28 12:19:25.664 - �[33mwarn�[39m: hm-rpc.2 (560702) State "hm-rpc.2.003B6269909D61.0.IP_ADDRESS" has no existing object, this might lead to an error in future versions
2026-01-28 12:19:25.664 - �[33mwarn�[39m: hm-rpc.2 (560702) State "hm-rpc.2.0003DD899A3AC9.0.CONFIG_PENDING" has no existing object, this might lead to an error in future versions
2026-01-28 12:19:25.664 - �[33mwarn�[39m: hm-rpc.2 (560702) State "hm-rpc.2.0003DD899A3AC9.0.UNREACH" has no existing object, this might lead to an error in future versions
2026-01-28 12:19:25.664 - �[33mwarn�[39m: hm-rpc.2 (560702) State "hm-rpc.2.0003DD899A3AC9.0.IP_ADDRESS" has no existing object, this might lead to an error in future versions
2026-01-28 12:19:25.665 - �[33mwarn�[39m: hm-rpc.2 (560702) State "hm-rpc.2.0003DD899A3AC9.0.CONFIG_PENDING" has no existing object, this might lead to an error in future versions
2026-01-28 12:19:25.665 - �[33mwarn�[39m: hm-rpc.2 (560702) State "hm-rpc.2.0003DD899A3AC9.0.UNREACH" has no existing object, this might lead to an error in future versions
2026-01-28 12:19:25.665 - �[33mwarn�[39m: hm-rpc.2 (560702) State "hm-rpc.2.0003DD899A3AC9.0.IP_ADDRESS" has no existing object, this might lead to an error in future versions
2026-01-28 12:19:25.665 - �[33mwarn�[39m: hm-rpc.2 (560702) State "hm-rpc.2.0003DD899A3AC9.0.CONFIG_PENDING" has no existing object, this might lead to an error in future versions
2026-01-28 12:19:25.665 - �[33mwarn�[39m: hm-rpc.2 (560702) State "hm-rpc.2.0003DD899A3AC9.0.UNREACH" has no existing object, this might lead to an error in future versions
2026-01-28 12:19:25.665 - �[33mwarn�[39m: hm-rpc.2 (560702) State "hm-rpc.2.0003DD899A3AC9.0.IP_ADDRESS" has no existing object, this might lead to an error in future versions
2026-01-28 12:19:25.671 - �[33mwarn�[39m: hm-rpc.2 (560702) State "hm-rpc.2.0003DD899A3AC9.0.CONFIG_PENDING" has no existing object, this might lead to an error in future versions
2026-01-28 12:19:25.671 - �[33mwarn�[39m: hm-rpc.2 (560702) State "hm-rpc.2.0003DD899A3AC9.0.UNREACH" has no existing object, this might lead to an error in future versions
Versions:
iot version: 5.0.12
hm-rpc version: 3.0.1
hm-rega version: 5.1.0
admin version: 7.7.22
JS-Controller version: 7.1.0
Node version: 22.22.0
Operating system: Ubuntu 24.04.3 LTS
CCU model: OpenCCU
CCU firmware: 3.85.7.20251129
Da ich nicht weiß, wer der Verursacher des Problems ist, lege ich hierzu auch einen Bug Report im IOT-Adapter an.
Siehe ioBroker.hm-rpc.
Nach längerem Testen scheint in meinen Augen aber der hm-rpc Adapter nicht das Problem zu sein,
da er mit gestoppten iot-Adapter keine Probleme macht. Erst wenn ich im iot-Adapter unter Alexa V3 Geräte mehr als 7 Geräte definiere, bekomme ich diese Fehlermeldungen.
Versions:
iot version: 5.0.12
hm-rpc version: 3.0.1
hm-rega version: 5.1.0
admin version: 7.7.22
JS-Controller version: 7.1.0
Node version: 22.22.0
Operating system: Ubuntu 24.04.3 LTS
CCU model: OpenCCU
CCU firmware: 3.85.7.20251129