Closed florianmulatz closed 3 years ago
Logs please :)
I assume the unit shows up during scan, and as it's not handled, the add-on logs a Unrecognized device type
- is that correct?
Hey,
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing...
-----------------------------------------------------------
Add-on: Warema Bridge
Control your Warema WMS system
-----------------------------------------------------------
Add-on version: dev
You are running the latest version of this add-on.
System: Home Assistant OS 5.12 (amd64 / qemux86-64)
Home Assistant Core: 2021.3.2
Home Assistant Supervisor: 2021.03.6
-----------------------------------------------------------
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing...
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[09:56:31] INFO: Starting the Warema bridge...
[09:56:31] INFO: Setting WMS_KEY to XXXXXXXXXXXXXXXXXXXXXXXXXXXX
[09:56:31] INFO: Setting WMS_PAN_ID to XXXX
[09:56:31] INFO: Setting WMS_CHANNEL to 17
[09:56:31] INFO: Setting WMS_SERIAL_PORT to /dev/ttyUSB1
[09:56:31] INFO: MQTT available, fetching server detail ...
[09:56:31] INFO: MQTT server settings not configured, attempting auto-discovery...
[09:56:31] INFO: Configuring 'mqtt://core-mosquitto:1883' mqtt server
[09:56:31] INFO: MQTT credentials not configured, attempting auto-discovery...
[09:56:31] INFO: Configuring 'addons' mqtt user
Warema init completed
Scanning...
21 09:56:32.299 I Interval for position update: 30 seconds.
21 09:56:32.346 I /dev/ttyUSB1 Scanned device: F6C011 Type 09 <unknown>
21 09:56:32.403 I /dev/ttyUSB1 Scanned device: F6C011 Type 09 <unknown>
21 09:56:32.403 I /dev/ttyUSB1 Scanned device: 973B0F Type 20 Actuator UP
21 09:56:32.418 I /dev/ttyUSB1 Scanned device: 953B0F Type 20 Actuator UP
21 09:56:32.446 I /dev/ttyUSB1 Scanned device: E70510 Type 20 Actuator UP
21 09:56:32.476 I /dev/ttyUSB1 Scanned device: F6C011 Type 09 <unknown>
21 09:56:32.476 I /dev/ttyUSB1 Scanned device: E70510 Type 20 Actuator UP
21 09:56:32.538 I /dev/ttyUSB1 Scanned device: 973B0F Type 20 Actuator UP
21 09:56:32.564 I /dev/ttyUSB1 Scanned device: 953B0F Type 20 Actuator UP
Connected to MQTT
21 09:56:32.593 I /dev/ttyUSB1 Scanned device: 973B0F Type 20 Actuator UP
21 09:56:32.639 I /dev/ttyUSB1 Scanned device: 953B0F Type 20 Actuator UP
21 09:56:32.665 I /dev/ttyUSB1 Scanned device: E70510 Type 20 Actuator UP
21 09:56:33.060 I wmsTimeout 750 scanRequest 000000 "{R04FFFFFF7020DA0402}".
21 09:56:33.111 I /dev/ttyUSB1 Scanned device: F6C011 Type 09 <unknown>
21 09:56:33.182 I /dev/ttyUSB1 Scanned device: 973B0F Type 20 Actuator UP
21 09:56:33.183 I /dev/ttyUSB1 Scanned device: 953B0F Type 20 Actuator UP
21 09:56:33.198 I /dev/ttyUSB1 Scanned device: F6C011 Type 09 <unknown>
21 09:56:33.220 I /dev/ttyUSB1 Scanned device: E70510 Type 20 Actuator UP
21 09:56:33.262 I /dev/ttyUSB1 Scanned device: 973B0F Type 20 Actuator UP
21 09:56:33.294 I /dev/ttyUSB1 Scanned device: E70510 Type 20 Actuator UP
21 09:56:33.310 I /dev/ttyUSB1 Scanned device: F6C011 Type 09 <unknown>
21 09:56:33.327 I /dev/ttyUSB1 Scanned device: 953B0F Type 20 Actuator UP
21 09:56:33.368 I /dev/ttyUSB1 Scanned device: 953B0F Type 20 Actuator UP
21 09:56:33.395 I /dev/ttyUSB1 Scanned device: 973B0F Type 20 Actuator UP
21 09:56:33.429 I /dev/ttyUSB1 Scanned device: E70510 Type 20 Actuator UP
21 09:56:33.821 I wmsTimeout 750 scanRequest 000000 "{R04FFFFFF7020DA0402}".
21 09:56:33.855 I /dev/ttyUSB1 Scanned device: F6C011 Type 09 <unknown>
21 09:56:33.887 I /dev/ttyUSB1 Scanned device: F6C011 Type 09 <unknown>
21 09:56:33.917 I /dev/ttyUSB1 Scanned device: E70510 Type 20 Actuator UP
21 09:56:33.954 I /dev/ttyUSB1 Scanned device: 973B0F Type 20 Actuator UP
21 09:56:33.954 I /dev/ttyUSB1 Scanned device: 953B0F Type 20 Actuator UP
21 09:56:34.022 I /dev/ttyUSB1 Scanned device: 973B0F Type 20 Actuator UP
21 09:56:34.022 I /dev/ttyUSB1 Scanned device: E70510 Type 20 Actuator UP
21 09:56:34.022 I /dev/ttyUSB1 Scanned device: F6C011 Type 09 <unknown>
21 09:56:34.070 I /dev/ttyUSB1 Scanned device: 953B0F Type 20 Actuator UP
21 09:56:34.116 I /dev/ttyUSB1 Scanned device: E70510 Type 20 Actuator UP
21 09:56:34.116 I /dev/ttyUSB1 Scanned device: 953B0F Type 20 Actuator UP
21 09:56:34.177 I /dev/ttyUSB1 Scanned device: 973B0F Type 20 Actuator UP
21 09:56:34.582 I wmsTimeout 750 scanRequest 000000 "{R04FFFFFF7020DA0402}".
Scanned devices.
Registering 1163510
Unrecognized device type: 09
Adding device 1163510 (type 09)
Registering 998293
Adding device 998293 (type 20)
Registering 998295
Adding device 998295 (type 20)
Registering 1050087
Adding device 1050087 (type 20)
[
{ snr: 1163510, snrHex: 'F6C011', name: '1163510' },
{ snr: 998293, snrHex: '953B0F', name: '998293' },
{ snr: 998295, snrHex: '973B0F', name: '998295' },
{ snr: 1050087, snrHex: 'E70510', name: '1050087' }
]
21 09:57:02.811 I wmsRetry blindGetPos F6C011 "{R06F6C011801001000005}".
21 09:57:03.766 I wmsRetry blindGetPos F6C011 "{R06F6C011801001000005}".
21 09:57:04.277 I wmsRetry blindGetPos F6C011 "{R06F6C011801001000005}".
21 09:57:04.789 I wmsRetry blindGetPos F6C011 "{R06F6C011801001000005}".
21 09:57:05.301 I wmsRetry blindGetPos F6C011 "{R06F6C011801001000005}".
21 09:57:05.813 I wmsRetry blindGetPos F6C011 "{R06F6C011801001000005}".
21 09:57:06.325 I wmsTimeout 500 blindGetPos F6C011 "{R06F6C011801001000005}".
Yes that's correct - anyhow I can "fix" this annoyance with simply put this unrecognized device to the configuration option "ignored devices". Then it's not shown in the logs anymore
Warema Type 09 is the WebControl-Pro Unit which does not report Blind-States of course. This makes the log quite confusing.