Excellent! Did you test it at home?
Awesome!
If you ever need help with that, I’m always available to talk! What’s blocking you?
Yes it works, but since I had to make a small change to the bridge construction and to all HomeKit devices it would be nice to have some additional feedback
After switching to 1.x I can no longer initialize the HomeKit–Gladys connection. When the two are already linked it seems to work but the first connection does not occur correctly. I saw that there were changes to the mDNS library used by default but even when forcing the use of bonjour the error appears. I’ll let you know if I need help, I need to investigate a bit more, but it might take time — I’ll probably make the version change in a second PR.
1 Like
This development made it into Gladys Assistant 4.47! Thanks for the work @bertrandda 
I just opened a PR updating the main dependency of this service hap-nodejs. We’ve moved to a stable version of the library, including major optimizations to prevent congestion on your local network.
The Docker image bertrandda/gladys:homekit is up to date for those who want to test
1 Like
Thanks for the PR @bertrandda, I noticed in my logs that I occasionally had messages coming from HomeKit saying there were slowdowns, so this will help a lot, I think!
By the way, I often see this log:
[Gladys E2CA@Bande LED chambre@Bande LED chambre@Color Temperature] characteristic was supplied illegal value: number 525 exceeded maximum of 500
Do you think this update will fix the issue?
Another question, did you see the CHANGELOG with the breaking changes since our version?
1 Like
We can check, but I don’t think that will fix this problem. It seems to be a normalization issue before sending the info to HomeKit. Could you give me the model of the associated device?
Yes, I’ve checked everything, it’s all good
It’s a Livarno Lidl Zigbee LED strip (Lidl HG06104A control via MQTT | Zigbee2MQTT)
Strangely, indeed I see that on the Zigbee2mqtt side, the feature looks like this:
"external_id": "zigbee2mqtt:bande_led_chambre:light:temperature:color_temp",
"category": "light",
"type": "temperature",
"read_only": false,
"keep_history": true,
"has_feedback": true,
"unit": null,
"min": 150,
"max": 500,
"last_value": 524,
The value is outside the min/max!
Ok perfect, and did you test it on a real existing installation? That doesn’t break already-configured installations, the user won’t have to re-pair HomeKit with the QR Code?
In that case, I imagine the problem is either on the Zigbee2MQTT side or on the device side.
Yes, everything works correctly on my setup, but I’d welcome more feedback to be sure since it deeply affects the network side.
1 Like