Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lumi Sensor Smoke labled as unknown ZHAFire sensor #425

Closed
peer69 opened this issue Jan 10, 2019 · 2 comments
Closed

Lumi Sensor Smoke labled as unknown ZHAFire sensor #425

peer69 opened this issue Jan 10, 2019 · 2 comments
Labels

Comments

@peer69
Copy link

peer69 commented Jan 10, 2019

I have paired a Xiaomi/Honeywell Smoke Sensor to deCONZ Gateway. It works fine with homebridge-hue in terms of creating the device and reporting an alarm via HomeKit.
Even though this seems to be working I see a message in the log which might indicate otherwise:

[1/10/2019, 10:47:06 AM] [Hue] zigbee-gateway: /sensors/31: warning: unknown ZHAFire sensor {"config":{"battery":100,"on":true,"reachable":true,"temperature":2800},"ep":1,"etag":"baca327d6fee5b33869874710dd89825","manufacturername":"LUMI","modelid":"lumi.sensor_smoke","name":"lumi.sensor_smoke","state":{"fire":false,"lastupdated":"2019-01-10T09:46:33","lowbattery":false,"tampered":false},"type":"ZHAFire","uniqueid":"00:15:8d:00:02:ad:0b:4f-01-0500"}

Using ph I receive the following from the API:

"31": { "config": { "battery": 100, "on": true, "reachable": true, "temperature": 2600 }, "ep": 1, "etag": "52e75aa0dc43bcd7447d9172cace95b7", "manufacturername": "LUMI", "modelid": "lumi.sensor_smoke", "name": "lumi.sensor_smoke", "state": { "fire": false, "lastupdated": "2019-01-10T09:39:15", "lowbattery": false, "tampered": false }, "type": "ZHAFire", "uniqueid": "00:15:8d:00:02:ad:0b:4f-01-0500" },

Is there anything that has to be done or should I just ignore the log-message?

@ebaauw
Copy link
Owner

ebaauw commented Jan 10, 2019

Just ignore the message. The warning indicates this model hasn’t been whitelisted explicitly in homebridge-hue. I heven’t seen much variation in the IAS Zone sensors, so there doesn’t seem to be a need for a model-specific configuration. Unlike e.g. for switches, where the possible buttonevent values need to be specified per switch.

@peer69
Copy link
Author

peer69 commented Jan 10, 2019

Thanks for the info. I’ll ignore the message then.

@peer69 peer69 closed this as completed Jan 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants