-
-
Notifications
You must be signed in to change notification settings - Fork 126
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
Implement zigbee2mqtt protocol #1024
base: master
Are you sure you want to change the base?
Conversation
e603bab
to
13f9c51
Compare
Hi, i use now this build https://github.com/awawa-dev/HyperHDR/actions/runs/12522954359
it stays connected
|
You must run zigbee2mqtt wizard in the LED hardware. I will add a tutorial later in the wiki. |
No, it searches for devices only when you run the wizard. Could you check HyperHDR logs when the app says it havent found zigbee devices? Are you able to view the communication in the mosquito? The z2m has the default topic |
@schwatter For discovery topic |
Mh, the topic gets only updated when i restart zigbee2mqtt. Otherwise it is quiet. Maybe i must update z2m or something Topic:
Value:
|
This ZigBee2mqtt topic is retain type: every time you subscribe it you should receive a response. Unless for some reason mqtt broker doesn't support it. |
I think qmqtt library can check mqtt broker capabilities. I'll try to test it and warn the user in logs if the retain messages are not supported. |
13f9b3f
to
3730819
Compare
c49b1ef
to
2ed4cd4
Compare
…hed to our zigbee2mqtt fork for better performance
Currently changing dynamic brightness causes to generete 2 frames to be send (waste of communication): I think I remove dynamic brightness from HyperHDR to zigbee communication. |
Ok, when i set Background effect to RGB(0,0,0), the gu10 went off and yeah black. Because off is off. |
I edit my answer again up |
Probably gamma 1.5 trims this range to RGB(0,0,0). This is how constant brightness works: all-in or off for RGB(0,0,0). Previously, dynamic brightness was implemented in HyperHDR and you saw what happened: delays because instead of one frame (color XY), two had to be sent each time (color XY + current brightness level). |
Ok, i understand the dilemma. Does your Philips Play Lightbar calculate brightnes over rgb? |
No, the brightness needs to be sent separately from XY (or Hue/Saturation) color. Probably Zigbee protocol limitation (there is no RGB command) or Hue bridge is using some undocumented method. |
Alternatively we can go back to dynamic brightness with refresh time of 1Hz and transition time of 1 second. But I'm not sure about the results. |
I would say yes. Maybe you can add some on/off option. Easyer for compareing both. |
@awawa-dev, @schwatter Hello, I've had time again for my Sonoff dongle.
It works very well and is stable. The Philips Hue lights switch to white when the scenes are black. I still have to adjust something. Otherwise, barely noticeable delay. 2025-01-06T14:46:53.787Z [IMAGETOLED_MNG0] Total index number is: 24192 (memory: 24192). User sparse processing is: disabled, image size: 1280 x 720, area number: 1 |
sudo systemctl enable mosquitto and then sudo systemctl start mosquitto |
Strange, in my system it starts automatically. Maybe something is wrong with the configuration file or rights. Did you create config using the tutorial? https://github.com/awawa-dev/HyperHDR/wiki/Zigbee2MQTT-lights |
@awawa-dev, https://www.zigbee2mqtt.io/guide/installation/01_linux.html#optional-running-as-a-daemon-with-systemctl |
@awawa-dev,
|
You mix up mosquitto with zigbee2mqtt! |
Here is z2m. You have to add it manual. Edit: |
I think you mean zigbee2mqtt. Try my servicefile. It is a bit different. Like User and ExecStart.
|
This is what the config looks like. |
Thanks, but it doesn't work. No idea why! |
SSH/system user |
@awawa-dev, |
Just received ZBDongle-E (cp2102N) It works better that ZBDongle-P and cp2530 at standard baudrate. Testing: 43 frames / 2 lamps = 21.5FPS
|
OK, now I see that on the stack ezsp it completely fills the queue. Later even if we turn off the lamps when we play the effect it turns off after a few seconds. It's probably the missing guard for this stack that I didn't implement earlier without having EFR32MG21. |
So you use ezsp instead emper. Which firmware? |
@schwatter yes, I just flashed the default firmware from the browser on this page https://darkxst.github.io/silabs-firmware-builder/ I am currently busy with a very interesting functionality here: awawa-dev/P010_for_V4L2#6 but it should be finished soon and I should start doing some serious re-arranging in Zigbee2MQTT in its communication layer. By the way, MyFriend sent me another 4 adapters 😄 I don't know yet which ones will stay with me and which ones I will sell, but I will try to test them all. |
@satgit62 @schwatter |
This adapter has WORKING touchlink: https://aliexpress.com/item/1005006155691159.html (cc2652p/CH9102X)
|
EFR32MG21 may not support touchlink in standard firmware, probably custom build is neccesery: |
Another cc2531 from https://aliexpress.com/item/1005006177315496.html (cc2531 + antenna) |
|
Does anyone have a lamp that should support touchlink (different than mine 915005733701) but it doesnt work on ember/ezps like ZBDongle-E and could help us testing in the above thread? |
1 Add option to disable lamps in Home Assistant wizard
2 Zigbee2mqtt driver is implemented. MQTT must be enabled and active in the HyperHDR->Advanced->Network section.
Manual (work still in progress can be changed):
https://github.com/awawa-dev/HyperHDR/wiki/Zigbee2MQTT-lights