homebridge-hue: warning: ignoring unknown ZHASwitch sensor
Hi Erik,
I have again a question for you. I get this message when starting homebridge-hue from my Xiaomi sensors is this a bug in the plugin or in the config?
Its a Aqara contact sensor and a 2 mi temperaturesensor
[Zigbeebridge Abstellkammer] Zigbeebridge Abs: /sensors/4: warning: ignoring unknown ZHASwitch sensor {"config":{"on":true,"reachable":true},"ep":2,"etag":"75fe41f1a41090d2ee9fc4470d77d7e4","manufacturername":"LUMI","mode":1,"modelid":"lumi.sensor_ht","name":"Thermostat Eisschrank Küche","state":{"buttonevent":0,"lastupdated":"1969-12-31T23:00:00"},"type":"ZHASwitch","uniqueid":"00:15:8d:00:02:02:64:51-02-0012"} Dez 31 06:11:33 server homebridge[3327]: [2017-12-31 06:11:33] [Zigbeebridge Abstellkammer] Zigbeebridge Abs: /sensors/5: warning: ignoring unknown ZHASwitch sensor {"config":{"on":true,"reachable":true},"ep":3,"etag":"75fe41f1a41090d2ee9fc4470d77d7e4","manufacturername":"LUMI","mode":1,"modelid":"lumi.sensor_ht","name":"Thermostat Eisschrank Küche","state":{"buttonevent":0,"lastupdated":"1969-12-31T23:00:00"},"type":"ZHASwitch","uniqueid":"00:15:8d:00:02:02:64:51-03-000c"} Dez 31 06:11:33 server homebridge[3327]: [2017-12-31 06:11:33] [Zigbeebridge Abstellkammer] Zigbeebridge Abs: /sensors/9: warning: ignoring unknown ZHASwitch sensor {"config":{"on":true,"reachable":true},"ep":2,"etag":"635751883cae9db186f4488be733a426","manufacturername":"LUMI","mode":1,"modelid":"lumi.sensor_ht","name":"Thermostat Kühlschrank Küche","state":{"buttonevent":0,"lastupdated":"1969-12-31T23:00:00"},"type":"ZHASwitch","uniqueid":"00:15:8d:00:02:02:64:5c-02-0012"}
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Comments: 19 (9 by maintainers)
The dump looks OK to me, or at least in line with the screenshot. I’m thinking the hardware and/or firmware is different for the Xiaomi temperature/humudity sensor showing the additional endpoints. Anyway, I created a PR for deCONZ to expose ZHASwitch resources for these only for the Xiaomi Smart Cube. You probably need to delete/re-pair the sensor once more, after a new deCONZ version with this change is available.
If the node re-appears after deleting it, It’s probably still in the RaspBee’s neighbour table. Reset the RaspBee (power-cycle the Raspberry or shutdown deCONZ and issue
sudo GCFFlasher_internal -r.Looks like you’re running only one instance of homebridge (named homebridge-hue), as a service from systemctl. Typically, the service is defined in
/etc/systemd/system/homebridge-hue.service. You should be able to edit that file and change theExecStartline to include-D. Then aftersudo systemctl daemon-reloadandsudo systemctl restart homebridge-hue, the debug messages should be included in the journal.Looks like you’ve specified the
Hueplatform three times in config.json?! I’m surprised this works - it definitely won’t when moving to dynamic accessories, issue #4. You should specify the platform only once, and specify your bridges using"hosts": ["host1", "host2", "host3"]in config.json.homebridge-hue found all your accessories: the two Mi temperature/humidity sensors (Thermostat Eisschrank Küche and Thermostat Kühlschrank Küche), the Aqara door sensor (Schranktürsensor Abstellkammer) and the Trådfri remote (Schalter 4 Badezimmer), which you probably paired previously, but is now missing (I suspect it shows
reachablefalse).homebridge-hue is receiving updates for the Mi and Aqara sensors from deCONZ and exposing them to HomeKit. You should be able to see these in Apple’s Home app. You’d probably see a Switch for the Trådfri as well, but marked with a Status Fault.
Looking at the screenshot, indeed there’s superfluous endpoints listed for the Mi sensors. I don’t recognise these - the endpoints are similar to those from the Xiaomi Smart Cube, but the clusters are very un-Xiaomi. The unknown node is a Hue dimmer switch, but it hasn’t been read in full by deCONZ either.
As I suspected, these are superfluous resources deCONZ created because of the additional endpoints. Note the matching MAC address - endpoint - cluster in
uniqueid. I don’t know why there’s only one additional endpoint for the second Mi sensor, maybe the 0x000c cluster is missing from the fingerprint?Concluding, it would seem like your deCONZ configuration is broken, somehow. Since you only have a couple of devices paired, I would recommend to discard the current configuration and restart from scratch. Shutdown deCONZ, move
~/.local/share/dresden-elektronik/deCONZtodeCONZ.old(as a backup, just in case), and start deCONZ. It should create a new configuration in~/.local/share/dresden-elektronik/deCONZ.Alternatively, you might try and delete the broken nodes from the deCONZ GUI (select the node and press delete) and delete the corresponding resources through the REST API. Then, shutdown deCONZ, and physically delete the Deleted sensor records from the deCONZ database, located in
~/.local/share/dresden-elektronik/deCONZ/zll.db(I usesqlitebrowserfor that). This step is needed, otherwise deCONZ would revive the Deleted record when the device is paired again.Then, reset each (deleted) device and re-pair them to deCONZ. Make sure the devices remain awake during pairing, by continuously short pressing/releasing the reset button on the temperature/humidity sensors, moving the magnet of the door sensor, pressing a button on the Hue dimmer or Trådfri remote, or, if applicable, waving in front of any motion sensor.