warning: ignoring unknown ZHASwitch sensor #245
Comments
|
Looks like the sensors haven’t been recognised by deCONZ correctly. deCONZ should expose the Xiaomi Mi Temperature/Humidity sensor as a ZHATemperature and a ZHAHumidity sensor, not as ZHASwitches. The log above doesn’t show the Aqara contact sensor. Could you please post the full log running Looking at the |
|
Unfortunately, debuugin does not work for me with homebridge -D. I have you the log at the start completely inserted I hope it tells you more? ` |
|
@server:~ $ sudo journalctl -f -au homebridge-hue |
Looks like you're running only one instance of homebridge (named homebridge-hue), as a service from systemctl. Typically, the service is defined in Looks like you've specified the 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 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 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 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. |
|
Thank you for your prompt reply.
I knew the debug mode only init.d I was not aware that this can be activated under systemd. Thanks for the note. I have already tried it even if it is no longer necessary for this problem.
Can you give me an example of the config? Have looked into your wiki but do not understand how it is meant exactly. This is my current config.json "platforms": [ At deconz I'll try it the way you recommended. Do you already know when you have solved the problem with the accessibility of the lamps at the start of homebridge? I have currently bypassed it with a service.timer that homebridge launches 5 minutes after deconz. |
It should look something like: {
"platforms": [
{
"platform": "Hue",
"hosts": ["xxxx", "yyyy", "zzzz"],
"users": {
"XXXX": "XXXX",
"YYYY": "YYYY",
"ZZZZ": "ZZZZ"
},
"sensors": true,
"excludeSensorTypes": ["CLIPGenericStatus", "CLIPGenericFlag", "Daylight", "Geofence"],
"lights": true,
"nativeHomeKit": true,
"resource": false
}
]
}Because you specify
Yeah, this sucks. I start the homebridge service manually because of this. Luckily you can restart deCONZ while keeping homebridge/homebridge-hue running, so it's only an issue when you reboot the Raspberry. |
I did not know that, but good to know.
I have set up a timer.service for this only the reboot of the pi for 10 min the homebridge-hue.service in the sleep mode until deconz has built the network. I'm not sure if you know this possibility, but maybe it will help you? I wrote instructions here but in German. That with the new config worked. Thank you! The deconz problem I'll try right now to fix. |
|
Thanks. I didn’t know about the Timer service. It seems more useful than the PreExecStart, since you only want the delay after boot, not each time you restart homebridge. |
|
This is the advantage that HomeBridge only sleeps when restarting the Pi. Thanks again for the great plugin and a happy new year 2018 Greeting Nastra |
@Nastras did you manage to fix this? Did you re-initialise the deCONZ database and re-pair the sensors? Could you please post a screenshot from the deCONZ GUI what the sensor now looks like? |
|
Hello Erik, I did not get the bugs fixed. I have the sensor on and off several times, unfortunately, it still looks like the beginning. The error message is still in the log: Zigbeebridge Abs: /sensors/6: warning: ignoring unknown ZHASwitch sensor {"config":{"on":true,"reachable":true},"ep":2,"etag":"8df32f5986e8ec0a7040fa26697bbf5d","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"}
Even after deleting the config from deconz nothing else appears. Also the device 0x422a does not disappear after deleting the node and the config. |
|
I also have another question for you, the Ikea Remote Switch is this because when keys always have a three occupancy or only a double occupancy? Currently I have only one click and long click to select. In some HK apps I am offered the keys additionally with double click to occupy. But this does not work and is not displayed in the log. Is it correct that way? |
|
The IKEA Trådfri remote doesn't support double-click (neither does the Hue dimmer switch): in case you double-click it, it just issues two clicks in short succession. homebridge-hue cannot detect this reliably when polling the Hue bridge (it only sees the last change since at each polling cycle). Maybe it could with deCONZ websocket notifications, but I never got around testing that. |
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 |
|
Then I'll wait until there is a new deconz version where the error has been fixed. If I execute flash command then all devices are gone? |
No, that will just reset the RaspBee - like when powering down the Raspberry. Devices will still be in the network and will be discovered when deCONZ is restarted. |
Only create ZHASwitch resources for _Analog Input_ (0x000c) and _Multistate Input_ (0x0012) clusters for the Xiaomi Smart Cube. See ebaauw/homebridge-hue#245 and ebaauw/homebridge-hue#203.
|
worked thank you for the tip now it is waiting for the deconz update .-) |
|
Manuel did merge my PR, but he’s traveling, so the update won’t be released until end of January. |
|
He has a good life, traveling. Then we wait for him to come back .-) |
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"}The text was updated successfully, but these errors were encountered: