Hi
my Zigbee2MQTT Addon is every 2h down. I have to (“hardware”)-restart the Proxmox VM to solve the problem for the next 2 hours.
I insatlled it like this guy https://smart-live.net/sonoff-3-0-usb-dongle-plus-e-flashen-fuer-thread-und-matter/
Zigbee and Thread Channel 15
Zigbee2MQTT Log:
Zigbee2MQTT:info 2023-12-08 11:44:30: MQTT publish: topic 'zigbee2mqtt/Anwesenheitssensor Badezimmer', payload '{"detection_delay":0.1,"fading_time":2,"illuminance_lux":4,"linkquality":255,"maximum_range":9.5,"minimum_range":0.6,"presence":false,"radar_sensitivity":5,"target_distance":0}'
Zigbee2MQTT:info 2023-12-08 11:44:32: MQTT publish: topic 'zigbee2mqtt/Anwesenheitssensor Badezimmer', payload '{"detection_delay":0.1,"fading_time":2,"illuminance_lux":4,"linkquality":255,"maximum_range":9.5,"minimum_range":0.6,"presence":false,"radar_sensitivity":5,"target_distance":0}'
Zigbee2MQTT:info 2023-12-08 11:44:33: MQTT publish: topic 'zigbee2mqtt/Anwesenheitssensor Badezimmer', payload '{"detection_delay":0.1,"fading_time":2,"illuminance_lux":4,"linkquality":255,"maximum_range":9.5,"minimum_range":0.6,"presence":false,"radar_sensitivity":5,"target_distance":0}'
Zigbee2MQTT:info 2023-12-08 11:44:35: MQTT publish: topic 'zigbee2mqtt/Anwesenheitssensor Badezimmer', payload '{"detection_delay":0.1,"fading_time":2,"illuminance_lux":4,"linkquality":255,"maximum_range":9.5,"minimum_range":0.6,"presence":false,"radar_sensitivity":5,"target_distance":0}'
Zigbee2MQTT:info 2023-12-08 11:44:36: MQTT publish: topic 'zigbee2mqtt/Anwesenheitssensor Badezimmer', payload '{"detection_delay":0.1,"fading_time":2,"illuminance_lux":4,"linkquality":255,"maximum_range":9.5,"minimum_range":0.6,"presence":false,"radar_sensitivity":5,"target_distance":0}'
Zigbee2MQTT:info 2023-12-08 11:44:38: MQTT publish: topic 'zigbee2mqtt/Anwesenheitssensor Badezimmer', payload '{"detection_delay":0.1,"fading_time":2,"illuminance_lux":4,"linkquality":255,"maximum_range":9.5,"minimum_range":0.6,"presence":false,"radar_sensitivity":5,"target_distance":0}'
Zigbee2MQTT:info 2023-12-08 11:44:40: MQTT publish: topic 'zigbee2mqtt/Anwesenheitssensor Badezimmer', payload '{"detection_delay":0.1,"fading_time":2,"illuminance_lux":4,"linkquality":255,"maximum_range":9.5,"minimum_range":0.6,"presence":false,"radar_sensitivity":5,"target_distance":0}'
Zigbee2MQTT:info 2023-12-08 11:44:41: MQTT publish: topic 'zigbee2mqtt/Anwesenheitssensor Badezimmer', payload '{"detection_delay":0.1,"fading_time":2,"illuminance_lux":4,"linkquality":255,"maximum_range":9.5,"minimum_range":0.6,"presence":false,"radar_sensitivity":5,"target_distance":0}'
Zigbee2MQTT:info 2023-12-08 11:44:43: MQTT publish: topic 'zigbee2mqtt/Anwesenheitssensor Badezimmer', payload '{"detection_delay":0.1,"fading_time":2,"illuminance_lux":4,"linkquality":255,"maximum_range":9.5,"minimum_range":0.6,"presence":false,"radar_sensitivity":5,"target_distance":0}'
Zigbee2MQTT:info 2023-12-08 11:44:44: MQTT publish: topic 'zigbee2mqtt/Anwesenheitssensor Badezimmer', payload '{"detection_delay":0.1,"fading_time":2,"illuminance_lux":4,"linkquality":255,"maximum_range":9.5,"minimum_range":0.6,"presence":false,"radar_sensitivity":5,"target_distance":0}'
Zigbee2MQTT:info 2023-12-08 11:44:46: MQTT publish: topic 'zigbee2mqtt/Anwesenheitssensor Badezimmer', payload '{"detection_delay":0.1,"fading_time":2,"illuminance_lux":4,"linkquality":255,"maximum_range":9.5,"minimum_range":0.6,"presence":false,"radar_sensitivity":5,"target_distance":0}'
Zigbee2MQTT:info 2023-12-08 11:44:47: MQTT publish: topic 'zigbee2mqtt/Anwesenheitssensor Badezimmer', payload '{"detection_delay":0.1,"fading_time":2,"illuminance_lux":4,"linkquality":247,"maximum_range":9.5,"minimum_range":0.6,"presence":false,"radar_sensitivity":5,"target_distance":0}'
Zigbee2MQTT:info 2023-12-08 11:44:49: MQTT publish: topic 'zigbee2mqtt/Anwesenheitssensor Badezimmer', payload '{"detection_delay":0.1,"fading_time":2,"illuminance_lux":4,"linkquality":255,"maximum_range":9.5,"minimum_range":0.6,"presence":false,"radar_sensitivity":5,"target_distance":0}'
Zigbee2MQTT:info 2023-12-08 11:44:51: MQTT publish: topic 'zigbee2mqtt/Anwesenheitssensor Badezimmer', payload '{"detection_delay":0.1,"fading_time":2,"illuminance_lux":4,"linkquality":255,"maximum_range":9.5,"minimum_range":0.6,"presence":false,"radar_sensitivity":5,"target_distance":0}'
Zigbee2MQTT:info 2023-12-08 11:44:52: MQTT publish: topic 'zigbee2mqtt/Anwesenheitssensor Badezimmer', payload '{"detection_delay":0.1,"fading_time":2,"illuminance_lux":4,"linkquality":255,"maximum_range":9.5,"minimum_range":0.6,"presence":false,"radar_sensitivity":5,"target_distance":0}'
Zigbee2MQTT:info 2023-12-08 11:44:54: MQTT publish: topic 'zigbee2mqtt/Anwesenheitssensor Badezimmer', payload '{"detection_delay":0.1,"fading_time":2,"illuminance_lux":4,"linkquality":255,"maximum_range":9.5,"minimum_range":0.6,"presence":false,"radar_sensitivity":5,"target_distance":0}'
Zigbee2MQTT:info 2023-12-08 11:44:55: MQTT publish: topic 'zigbee2mqtt/Anwesenheitssensor Badezimmer', payload '{"detection_delay":0.1,"fading_time":2,"illuminance_lux":4,"linkquality":255,"maximum_range":9.5,"minimum_range":0.6,"presence":false,"radar_sensitivity":5,"target_distance":0}'
Zigbee2MQTT:info 2023-12-08 11:44:57: MQTT publish: topic 'zigbee2mqtt/Anwesenheitssensor Badezimmer', payload '{"detection_delay":0.1,"fading_time":2,"illuminance_lux":4,"linkquality":255,"maximum_range":9.5,"minimum_range":0.6,"presence":false,"radar_sensitivity":5,"target_distance":0}'
Zigbee2MQTT:info 2023-12-08 11:44:59: MQTT publish: topic 'zigbee2mqtt/Anwesenheitssensor Badezimmer', payload '{"detection_delay":0.1,"fading_time":2,"illuminance_lux":4,"linkquality":255,"maximum_range":9.5,"minimum_range":0.6,"presence":false,"radar_sensitivity":5,"target_distance":0}'
Zigbee2MQTT:info 2023-12-08 11:45:00: MQTT publish: topic 'zigbee2mqtt/Anwesenheitssensor Badezimmer', payload '{"detection_delay":0.1,"fading_time":2,"illuminance_lux":4,"linkquality":255,"maximum_range":9.5,"minimum_range":0.6,"presence":false,"radar_sensitivity":5,"target_distance":0}'
Zigbee2MQTT:info 2023-12-08 11:45:02: MQTT publish: topic 'zigbee2mqtt/Anwesenheitssensor Badezimmer', payload '{"detection_delay":0.1,"fading_time":2,"illuminance_lux":4,"linkquality":255,"maximum_range":9.5,"minimum_range":0.6,"presence":false,"radar_sensitivity":5,"target_distance":0}'
Zigbee2MQTT:info 2023-12-08 11:45:03: MQTT publish: topic 'zigbee2mqtt/Anwesenheitssensor Badezimmer', payload '{"detection_delay":0.1,"fading_time":2,"illuminance_lux":4,"linkquality":255,"maximum_range":9.5,"minimum_range":0.6,"presence":false,"radar_sensitivity":5,"target_distance":0}'
Zigbee2MQTT:info 2023-12-08 11:45:05: MQTT publish: topic 'zigbee2mqtt/Anwesenheitssensor Badezimmer', payload '{"detection_delay":0.1,"fading_time":2,"illuminance_lux":4,"linkquality":255,"maximum_range":9.5,"minimum_range":0.6,"presence":false,"radar_sensitivity":5,"target_distance":0}'
Zigbee2MQTT:info 2023-12-08 11:45:07: MQTT publish: topic 'zigbee2mqtt/Anwesenheitssensor Badezimmer', payload '{"detection_delay":0.1,"fading_time":2,"illuminance_lux":4,"linkquality":255,"maximum_range":9.5,"minimum_range":0.6,"presence":false,"radar_sensitivity":5,"target_distance":0}'
Zigbee2MQTT:info 2023-12-08 11:45:08: MQTT publish: topic 'zigbee2mqtt/Anwesenheitssensor Badezimmer', payload '{"detection_delay":0.1,"fading_time":2,"illuminance_lux":4,"linkquality":255,"maximum_range":9.5,"minimum_range":0.6,"presence":false,"radar_sensitivity":5,"target_distance":0}'
Zigbee2MQTT:info 2023-12-08 11:45:10: MQTT publish: topic 'zigbee2mqtt/Anwesenheitssensor Badezimmer', payload '{"detection_delay":0.1,"fading_time":2,"illuminance_lux":4,"linkquality":255,"maximum_range":9.5,"minimum_range":0.6,"presence":false,"radar_sensitivity":5,"target_distance":0}'
Zigbee2MQTT:info 2023-12-08 11:45:11: MQTT publish: topic 'zigbee2mqtt/Anwesenheitssensor Badezimmer', payload '{"detection_delay":0.1,"fading_time":2,"illuminance_lux":4,"linkquality":255,"maximum_range":9.5,"minimum_range":0.6,"presence":false,"radar_sensitivity":5,"target_distance":0}'
Zigbee2MQTT:info 2023-12-08 11:45:13: MQTT publish: topic 'zigbee2mqtt/Anwesenheitssensor Badezimmer', payload '{"detection_delay":0.1,"fading_time":2,"illuminance_lux":4,"linkquality":255,"maximum_range":9.5,"minimum_range":0.6,"presence":false,"radar_sensitivity":5,"target_distance":0}'
Zigbee2MQTT:info 2023-12-08 11:45:15: MQTT publish: topic 'zigbee2mqtt/Anwesenheitssensor Badezimmer', payload '{"detection_delay":0.1,"fading_time":2,"illuminance_lux":4,"linkquality":255,"maximum_range":9.5,"minimum_range":0.6,"presence":false,"radar_sensitivity":5,"target_distance":0}'
Zigbee2MQTT:info 2023-12-08 11:45:16: MQTT publish: topic 'zigbee2mqtt/Anwesenheitssensor Badezimmer', payload '{"detection_delay":0.1,"fading_time":2,"illuminance_lux":4,"linkquality":255,"maximum_range":9.5,"minimum_range":0.6,"presence":false,"radar_sensitivity":5,"target_distance":0}'
Zigbee2MQTT:info 2023-12-08 11:45:18: MQTT publish: topic 'zigbee2mqtt/Anwesenheitssensor Badezimmer', payload '{"detection_delay":0.1,"fading_time":2,"illuminance_lux":4,"linkquality":255,"maximum_range":9.5,"minimum_range":0.6,"presence":false,"radar_sensitivity":5,"target_distance":0}'
Zigbee2MQTT:info 2023-12-08 11:45:19: MQTT publish: topic 'zigbee2mqtt/Anwesenheitssensor Badezimmer', payload '{"detection_delay":0.1,"fading_time":2,"illuminance_lux":4,"linkquality":255,"maximum_range":9.5,"minimum_range":0.6,"presence":false,"radar_sensitivity":5,"target_distance":0}'
Zigbee2MQTT:info 2023-12-08 11:45:21: MQTT publish: topic 'zigbee2mqtt/Anwesenheitssensor Badezimmer', payload '{"detection_delay":0.1,"fading_time":2,"illuminance_lux":4,"linkquality":255,"maximum_range":9.5,"minimum_range":0.6,"presence":false,"radar_sensitivity":5,"target_distance":0}'
Zigbee2MQTT:info 2023-12-08 11:45:23: MQTT publish: topic 'zigbee2mqtt/Anwesenheitssensor Badezimmer', payload '{"detection_delay":0.1,"fading_time":2,"illuminance_lux":4,"linkquality":255,"maximum_range":9.5,"minimum_range":0.6,"presence":false,"radar_sensitivity":5,"target_distance":0}'
Zigbee2MQTT:info 2023-12-08 11:45:24: MQTT publish: topic 'zigbee2mqtt/Anwesenheitssensor Badezimmer', payload '{"detection_delay":0.1,"fading_time":2,"illuminance_lux":4,"linkquality":255,"maximum_range":9.5,"minimum_range":0.6,"presence":false,"radar_sensitivity":5,"target_distance":0}'
Zigbee2MQTT:info 2023-12-08 11:45:26: MQTT publish: topic 'zigbee2mqtt/Anwesenheitssensor Badezimmer', payload '{"detection_delay":0.1,"fading_time":2,"illuminance_lux":4,"linkquality":255,"maximum_range":9.5,"minimum_range":0.6,"presence":false,"radar_sensitivity":5,"target_distance":0}'
Zigbee2MQTT:info 2023-12-08 11:45:27: MQTT publish: topic 'zigbee2mqtt/Anwesenheitssensor Badezimmer', payload '{"detection_delay":0.1,"fading_time":2,"illuminance_lux":4,"linkquality":255,"maximum_range":9.5,"minimum_range":0.6,"presence":false,"radar_sensitivity":5,"target_distance":0}'
Zigbee2MQTT:info 2023-12-08 11:45:29: MQTT publish: topic 'zigbee2mqtt/Luftsensor Kühlschrank ', payload '{"battery":83,"humidity":61.71,"linkquality":255,"power_outage_count":38,"pressure":943.5,"temperature":9.9,"voltage":2975}'
Zigbee2MQTT:info 2023-12-08 11:45:29: MQTT publish: topic 'zigbee2mqtt/Luftsensor Kühlschrank ', payload '{"battery":83,"humidity":67.73,"linkquality":255,"power_outage_count":38,"pressure":943.5,"temperature":9.9,"voltage":2975}'
Silicon Labs Multiprotocol Log:
[11:24:27:310476] Info : fu_recovery_pins_enabled = false
[11:24:27:310476] Info : fu_connect_to_bootloader = false
[11:24:27:310477] Info : fu_enter_bootloader = false
[11:24:27:310478] Info : restart_cpcd = false
[11:24:27:310479] Info : application_version_validation = false
[11:24:27:310479] Info : print_secondary_versions_and_exit = false
[11:24:27:310480] Info : use_noop_keep_alive = false
[11:24:27:310481] Info : reset_sequence = true
[11:24:27:310481] Info : stats_interval = 0
[11:24:27:310482] Info : rlimit_nofile = 2000
[11:24:27:310483] Info : ENCRYPTION IS DISABLED
[11:24:27:310493] Info : Starting daemon in normal mode
[11:24:27:323665] Info : Connecting to Secondary...
[11:24:27:397790] Info : RX capability is 256 bytes
[11:24:27:397853] Info : Connected to Secondary
[11:24:27:399468] Info : Secondary Protocol v4
[11:24:27:403356] Info : Secondary CPC v4.3.1
[11:24:27:405165] Info : Secondary bus bitrate is 460800
[11:24:27:408721] Info : Secondary APP vUNDEFINED
[11:24:27:408785] Info : Daemon startup was successful. Waiting for client connections
[11:24:28] INFO: Starting otbr-agent...
otbr-agent[301]: [NOTE]-AGENT---: Running 0.3.0
otbr-agent[301]: [NOTE]-AGENT---: Thread version: 1.3.0
otbr-agent[301]: [NOTE]-AGENT---: Thread interface: wpan0
otbr-agent[301]: [NOTE]-AGENT---: Radio URL: spinel+cpc://cpcd_0?iid=2&iid-list=0
otbr-agent[301]: [NOTE]-ILS-----: Infra link selected: enp0s18
otbr-agent[301]: 49d.17:03:25.466 [C] Platform------: mCpcBusSpeed = 115200
[11:24:28:366189] Info : New client connection using library v4.3.1.0
[11:24:28:368971] Info : Opened connection socket for ep#12
[11:24:28:369197] Info : Endpoint socket #12: Client connected. 1 connections
[11:24:28:998351] Info : New client connection using library v4.3.1.0
[11:24:29:000732] Info : Endpoint socket #12: Client connected. 2 connections
otbr-agent[301]: 00:00:00.067 [N] RoutingManager: BR ULA prefix: fdf8:d0ef:d9f2::/48 (loaded)
otbr-agent[301]: 00:00:00.067 [N] RoutingManager: Local on-link prefix: fdfd:669d:5971:59d3::/64
ipset v7.10: The set with the given name does not exist
otbr-agent[301]: 00:00:00.090 [W] Platform------: Failed to update ipsets: Failed
otbr-agent[301]: 00:00:00.098 [N] Mle-----------: Role disabled -> detached
otbr-agent[301]: 00:00:00.107 [N] Platform------: [netif] Changing interface state to up.
s6-rc: info: service otbr-agent successfully started
s6-rc: info: service otbr-agent-rest-discovery: starting
[11:24:31] INFO: Successfully sent discovery information to Home Assistant.
s6-rc: info: service otbr-agent-rest-discovery successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
Listening on port 9999 for connection...
Accepting connection.
otbr-agent[301]: 00:00:27.359 [N] Mle-----------: RLOC16 1c00 -> fffe
otbr-agent[301]: 00:00:27.361 [W] Platform------: [netif] Failed to process request#5: Unknown error -95
otbr-agent[301]: 00:00:27.375 [N] Mle-----------: Attach attempt 1, AnyPartition reattaching with Active Dataset
otbr-agent[301]: 00:00:33.875 [N] RouterTable---: Allocate router id 7
otbr-agent[301]: 00:00:33.875 [N] Mle-----------: RLOC16 fffe -> 1c00
otbr-agent[301]: 00:00:33.877 [N] Mle-----------: Role detached -> leader
otbr-agent[301]: 00:00:33.878 [N] Mle-----------: Partition ID 0x6f93baea
ipset v7.10: The set with the given name does not exist
otbr-agent[301]: 00:00:33.886 [W] Platform------: Failed to update ipsets: Failed
otbr-agent[301]: 00:00:33.887 [W] Platform------: [netif] Failed to process request#6: Unknown error -17
ipset v7.10: The set with the given name does not exist
otbr-agent[301]: 00:00:34.388 [W] Platform------: Failed to update ipsets: Failed
otbr-agent[301]: [NOTE]-BBA-----: BackboneAgent: Backbone Router becomes Primary!
ipset v7.10: The set with the given name does not exist
otbr-agent[301]: 00:00:34.751 [W] Platform------: Failed to update ipsets: Failed
ipset v7.10: The set with the given name does not exist
otbr-agent[301]: 00:00:37.037 [W] Platform------: Failed to update ipsets: Failed
ipset v7.10: The set with the given name does not exist
otbr-agent[301]: 00:00:43.834 [W] Platform------: Failed to update ipsets: Failed
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::f467:c6ff:fef4:59c4/veth8dbdde1/27
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::f467:c6ff:fef4:59c4/veth8dbdde1/27
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::f467:c6ff:fef4:59c4/veth8dbdde1/27
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::f467:c6ff:fef4:59c4/veth8dbdde1/27
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::f467:c6ff:fef4:59c4/veth8dbdde1/27
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::5044:4aff:fee5:9984/veth4bb232c/29
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::f467:c6ff:fef4:59c4/veth8dbdde1/27
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::5044:4aff:fee5:9984/veth4bb232c/29
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::5044:4aff:fee5:9984/veth4bb232c/29
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::5044:4aff:fee5:9984/veth4bb232c/29
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::5044:4aff:fee5:9984/veth4bb232c/29
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::5044:4aff:fee5:9984/veth4bb232c/29
Accepted connection 7.
Restarting
[11:25:31:052283] Info : Endpoint socket #12: Client disconnected. 1 connections
[11:25:31:052311] Info : Client disconnected
[11:25:32:053745] Info : New client connection using library v4.3.1.0
[11:25:32:056365] Info : Endpoint socket #12: Client connected. 2 connections
Reusing socket from previous instance.
Socket connection has been closed, restarting...
Listening on port 9999 for connection...
Accepting connection.
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::b494:4cff:fe74:1b81/veth3c3ebc2/31
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::b494:4cff:fe74:1b81/veth3c3ebc2/31
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::b494:4cff:fe74:1b81/veth3c3ebc2/31
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::b494:4cff:fe74:1b81/veth3c3ebc2/31
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::b494:4cff:fe74:1b81/veth3c3ebc2/31
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::b494:4cff:fe74:1b81/veth3c3ebc2/31
Accepted connection 8.
Restarting
[11:25:49:465854] Info : Endpoint socket #12: Client disconnected. 1 connections
[11:25:49:465878] Info : Client disconnected
[11:25:50:467615] Info : New client connection using library v4.3.1.0
[11:25:50:470305] Info : Endpoint socket #12: Client connected. 2 connections
Reusing socket from previous instance.
Mosquitto broker Log:
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/mosquitto.sh
[11:24:16] INFO: Setting up user mqtt-ha
[11:24:16] INFO: SSL is not enabled
cont-init: info: /etc/cont-init.d/mosquitto.sh exited 0
cont-init: info: running /etc/cont-init.d/nginx.sh
cont-init: info: /etc/cont-init.d/nginx.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun mosquitto (no readiness notification)
services-up: info: copying legacy longrun nginx (no readiness notification)
[11:24:17] INFO: Starting NGINX for authentication handling...
s6-rc: info: service legacy-services successfully started
[11:24:17] INFO: Starting mosquitto MQTT broker...
2023-12-08 11:24:17: Warning: Mosquitto should not be run as root/administrator.
2023-12-08 11:24:17: mosquitto version 2.0.18 starting
2023-12-08 11:24:17: Config loaded from /etc/mosquitto/mosquitto.conf.
2023-12-08 11:24:17: Loading plugin: /usr/share/mosquitto/go-auth.so
2023-12-08 11:24:17: ├── Username/password checking enabled.
2023-12-08 11:24:17: ├── TLS-PSK checking enabled.
2023-12-08 11:24:17: └── Extended authentication not enabled.
2023-12-08 11:24:17: Opening ipv4 listen socket on port 1883.
2023-12-08 11:24:17: Opening ipv6 listen socket on port 1883.
2023-12-08 11:24:17: Opening websockets listen socket on port 1884.
2023-12-08 11:24:17: mosquitto version 2.0.18 running
2023-12-08 11:24:18: New connection from 127.0.0.1:57058 on port 1883.
2023-12-08 11:24:18: Client <unknown> disconnected due to protocol error.
[11:24:18] INFO: Successfully send discovery information to Home Assistant.
[11:24:18] INFO: Successfully send service information to the Supervisor.
2023-12-08 11:25:01: New connection from 172.30.32.1:54599 on port 1883.
2023-12-08 11:25:01: New client connected from 172.30.32.1:54599 as 3yY4iTtJH1BTr3EBcUOnDO (p2, c1, k60, u'mqtt-ha').
2023-12-08 11:25:54: New connection from 172.30.33.5:42154 on port 1883.
2023-12-08 11:25:55: New client connected from 172.30.33.5:42154 as mqttjs_26673294 (p2, c1, k60, u'mqtt-ha').
2023-12-08 11:27:29: New connection from 172.30.32.2:47352 on port 1883.
2023-12-08 11:27:29: Client <unknown> closed its connection.
2023-12-08 11:29:29: New connection from 172.30.32.2:40218 on port 1883.
2023-12-08 11:29:29: Client <unknown> closed its connection.
2023-12-08 11:35:29: New connection from 172.30.32.2:37730 on port 1883.
2023-12-08 11:35:29: Client <unknown> closed its connection.
2023-12-08 11:37:29: New connection from 172.30.32.2:42526 on port 1883.
2023-12-08 11:37:29: Client <unknown> closed its connection.
2023-12-08 11:39:29: New connection from 172.30.32.2:50952 on port 1883.
2023-12-08 11:39:29: Client <unknown> closed its connection.
2023-12-08 11:41:29: New connection from 172.30.32.2:56130 on port 1883.
2023-12-08 11:41:29: Client <unknown> closed its connection.
2023-12-08 11:43:29: New connection from 172.30.32.2:35028 on port 1883.
2023-12-08 11:43:29: Client <unknown> closed its connection.
2023-12-08 11:45:29: New connection from 172.30.32.2:35750 on port 1883.
2023-12-08 11:45:29: Client <unknown> closed its connection.
2023-12-08 11:47:29: New connection from 172.30.32.2:60568 on port 1883.
2023-12-08 11:47:29: Client <unknown> closed its connection.
2023-12-08 11:49:29: New connection from 172.30.32.2:54532 on port 1883.
2023-12-08 11:49:29: Client <unknown> closed its connection.
HA-Core Log:
Home Assistant Core
Retrying (Retry(total=5, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x7fc1e7c6cb90>, 'Connection to 192.168.2.108 timed out. (connect timeout=3.0)')': /upnp/control/basicevent1
11:50:33 – (WARNUNG) /usr/local/lib/python3.11/site-packages/urllib3/connectionpool.py - Die Nachricht ist zum ersten Mal am 11:29:08 aufgetreten und erscheint 88 mal
Error communicating with Wemo Steckdose at 192.168.2.108:49153, HTTPException(MaxRetryError("HTTPConnectionPool(host='192.168.2.108', port=49153): Max retries exceeded with url: /upnp/control/basicevent1 (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x7fc1e7cdeb90>, 'Connection to 192.168.2.108 timed out. (connect timeout=3.0)'))")) retry 0
11:50:00 – (WARNUNG) /usr/local/lib/python3.11/site-packages/pywemo/ouimeaux_device/api/service.py - Die Nachricht ist zum ersten Mal am 11:30:59 aufgetreten und erscheint 8 mal
Unable to re-probe wemo <WeMo Switch "Wemo Steckdose"> at 192.168.2.108
11:49:57 – (FEHLER) /usr/local/lib/python3.11/site-packages/pywemo/ouimeaux_device/__init__.py - Die Nachricht ist zum ersten Mal am 11:31:16 aufgetreten und erscheint 9 mal
Resubscribe error for <Subscription basicevent "Wemo Steckdose"> (HTTPConnectionPool(host='192.168.2.108', port=49153): Read timed out. (read timeout=10)), will retry in 60s
11:49:47 – (WARNUNG) /usr/local/lib/python3.11/site-packages/pywemo/subscribe.py - Die Nachricht ist zum ersten Mal am 11:29:00 aufgetreten und erscheint 8 mal
Error doing job: Unclosed client session
11:45:03 – (FEHLER) runner.py - Die Nachricht ist zum ersten Mal am 11:25:21 aufgetreten und erscheint 5 mal
Error fetching Wemo Steckdose data: WeMo update failed
11:44:05 – (FEHLER) Belkin WeMo
Error communicating with Wemo Steckdose after 3 attempts. Giving up.
11:44:05 – (FEHLER) /usr/local/lib/python3.11/site-packages/pywemo/ouimeaux_device/api/service.py
Unable to reconnect with Wemo Steckdose
11:44:05 – (FEHLER) /usr/local/lib/python3.11/site-packages/pywemo/ouimeaux_device/__init__.py - Die Nachricht ist zum ersten Mal am 11:39:17 aufgetreten und erscheint 3 mal
Device setup failed uuid:Socket-1_0-221409K1100C41 http://192.168.2.108:49153/setup.xml
11:31:03 – (FEHLER) /usr/local/lib/python3.11/site-packages/pywemo/discovery.py
Bewegung Flur EG Licht aus: Already running
11:28:09 – (WARNUNG) Automatisierung
Referenced entities light.lampe_3_flur_ug, light.lampe_heizungsraum are missing or not currently available
11:27:29 – (WARNUNG) helpers/service.py - Die Nachricht ist zum ersten Mal am 11:25:56 aufgetreten und erscheint 3 mal
Invalid color mode 'xy' received for entity light.lampe_3_schlafzimmer
11:27:26 – (WARNUNG) MQTT - Die Nachricht ist zum ersten Mal am 11:25:56 aufgetreten und erscheint 14 mal
Error evaluating condition in 'Bewegung Badezimmer an': In 'condition' (item 2 of 2): In 'state': In 'state' condition: unknown entity light.lampe_badezimmer_hk
11:26:03 – (WARNUNG) Automatisierung - Die Nachricht ist zum ersten Mal am 11:25:56 aufgetreten und erscheint 4 mal
The bridge HASS Bridge has entity lock.nuki_haustur_lock_hk. For best performance, and to prevent unexpected unavailability, create and pair a separate HomeKit instance in accessory mode for this entity
11:25:22 – (WARNUNG) HomeKit Bridge
TemplateError('ValueError: Template error: float got invalid input 'unknown' when rendering template '{% if 5000 > states('sensor.tasmota_sml_export_total_kwh') | float | round(3) > -300 %} {{states('sensor.tasmota_sml_export_total_kwh') | float | round(3)}} {% else %} {% endif %}' but no default was specified') while processing template 'Template<template=({% if 5000 > states('sensor.tasmota_sml_export_total_kwh') | float | round(3) > -300 %} {{states('sensor.tasmota_sml_export_total_kwh') | float | round(3)}} {% else %} {% endif %}) renders=4>' for attribute '_attr_native_value' in entity 'sensor.stromzahler_erzeugung'
11:25:20 – (FEHLER) Template - Die Nachricht ist zum ersten Mal am 11:25:20 aufgetreten und erscheint 2 mal
Error while processing template: Template<template=({% if 5000 > states('sensor.tasmota_sml_export_total_kwh') | float | round(3) > -300 %} {{states('sensor.tasmota_sml_export_total_kwh') | float | round(3)}} {% else %} {% endif %}) renders=2>
11:25:20 – (FEHLER) helpers/template.py - Die Nachricht ist zum ersten Mal am 11:25:20 aufgetreten und erscheint 2 mal
Can't connect to ESPHome API for esp32-bluetooth-proxy-e7fdb8 @ 192.168.2.154: Error connecting to ('192.168.2.154', 6053): [Errno 113] Connect call failed ('192.168.2.154', 6053) (SocketAPIError)
11:25:08 – (WARNUNG) runner.py - Die Nachricht ist zum ersten Mal am 11:25:08 aufgetreten und erscheint 2 mal
Connection pool is full, discarding connection: p58-caldav.icloud.com. Connection pool size: 10
11:25:06 – (WARNUNG) /usr/local/lib/python3.11/site-packages/urllib3/connectionpool.py - Die Nachricht ist zum ersten Mal am 11:25:06 aufgetreten und erscheint 7 mal
Error while setting up command_line platform for sensor
11:25:05 – (FEHLER) Sensor
Error adding entities for domain sensor with platform command_line
11:25:05 – (FEHLER) Sensor
Entity sensor.solar_erzeugung_aktuell (<class 'homeassistant.components.command_line.sensor.CommandSensor'>) is using native unit of measurement 'W' which is not a valid unit for the device class ('energy') it is using; expected one of ['GJ', 'MJ', 'MWh', 'kWh', 'Wh']; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+command_line%22
11:25:05 – (WARNUNG) Sensor
Dashboard unavailable; skipping reauth: Cannot connect to host 127.0.0.1:64692 ssl:default [Connect call failed ('127.0.0.1', 64692)]
11:25:03 – (FEHLER) ESPHome
Error requesting ESPHome Dashboard data: Cannot connect to host 127.0.0.1:64692 ssl:default [Connect call failed ('127.0.0.1', 64692)]
11:25:03 – (FEHLER) ESPHome
(Status Code 501)
11:25:02 – (FEHLER) icloud3 (benutzerdefinierte Integration)
(Status Code 501)
11:25:02 – (FEHLER) icloud3 (benutzerdefinierte Integration)
Automation with alias 'Licht Garage an wenn Tor wird geöffnet ' failed to setup actions and has been disabled: Unknown device '5390274f8522f73d93de82205dc269db'
11:24:59 – (FEHLER) Automatisierung - Die Nachricht ist zum ersten Mal am 11:24:59 aufgetreten und erscheint 2 mal
-I changed the Sonoff USB cable and Port on the Server
-I use a 2m USB3 cable in front of the dongle
-reinstall the Addon without Backup and reconnect all devices
-tried to use only 1 Zigbee Device
-Wifi Channel 1 max. away of Zigbee Channel 15
Can Anyone Help me?
