-
Notifications
You must be signed in to change notification settings - Fork 42
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
How to add multiple lights? #29
Comments
When capturing data from the ZhiJia app, it shouldn't matter whether the actual light is powered or not, the app simply broadcasts the messages. So try to keep all the lights on, and toggle each of them via the app to verify that they toggle correctly - while sniffing the data coming through the app. If that works, I think that setting the ble_adv_controller:
- id: living_room_light_controller
encoding: zhijia
variant: v2
forced_id: 0xE8E075
index: 1
- id: kitchen_light_controller
encoding: zhijia
variant: v2
forced_id: 0xE8E075
index: 2
- id: bar_light_controller
encoding: zhijia
variant: v2
forced_id: 0xE8E075
index: 3 If that doesn't work, try changing the |
I'll try to sniff again, but that is pretty much what I have now. But still each controller affects all 3 lights.
The issue is not if they work. All of them pair and work. But they aren't controlled separately. Every controller does the same thing, and affects all 3 light. I've even tried pairing/unpairing. It all seems to be the same thing. e.g. I pair the living room light with it's pair button, but then I unpair it by calling the kitchen controller unpair method. |
Try setting different IDs for each controller. Any six-digit hex number
should work.
…On Fri, 6 Dec 2024, 9:52 Zoran Ivancevic, ***@***.***> wrote:
I'll try to sniff again, but that is pretty much what I have now. But
still each controller affects all 3 lights.
ble_adv_controller:
- id: living_room_light_controller
encoding: zhijia
forced_id: 0xE8E075
index: 1
show_config: true
- id: bar_light_controller
encoding: zhijia
forced_id: 0xE8E075
index: 2
show_config: true
reversed: true
- id: kitchen_light_controller
encoding: zhijia
forced_id: 0xE8E075
index: 3
show_config: true
The issue is not if they work. All of them pair and work. But they aren't
controlled separately. Every controller does the same thing, and affects
all 3 light. I've even tried pairing/unpairing. It all seems to be the same
thing. e.g. I pair the living room light with it's pair button, but then I
unpair it by calling the kitchen unpair method.
—
Reply to this email directly, view it on GitHub
<#29 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABD52DD4QSP6LD27WQKP7RL2EFJURAVCNFSM6AAAAABTDCZ46WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMRSGQYDQMJQHA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Sorry if this is a stupid question, but I can't figure it out. I see different examples.
I have 3 lights controlled by the Zhi Jia app. What is the proper way to configure that?
I tried adding 3 of everything (controller, light, button), and I can pair all the devices.
But whatever I change on any of them, it changes on all of them.
Here is my current config:
It seems like it's all the same controller. I tried unpairing everything through the service command. It all behaves like the same controller. I can unpair any light with any controllers unpair action.
I've also tried adding
index
to each controller, but it didn't help.Do I need to set a different
force_id
to each controller? How do I find these?I tried sniffing the force_ids, but I'm finding that confusing as well. I see multiple messages when I turn on/off individual lights from the ZhiJia app.
When I just toggle the 1st (living room light), I get this:
Then I turn that light off (completely cut off power via a relay), and just toggle the 2nd light (bar light). I get this:
Then same with the last light (kitchen light). Cut off power to the previous 2, and just toggle the 3rd one. I get this:
I don't know, but for me this makes no sense. Overlapping ids for different indexes...
The text was updated successfully, but these errors were encountered: