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

Xiaomi Wall switch group message support question #1515

Closed
pkedvessy opened this issue May 9, 2019 · 12 comments
Closed

Xiaomi Wall switch group message support question #1515

pkedvessy opened this issue May 9, 2019 · 12 comments
Labels
stale Stale issues

Comments

@pkedvessy
Copy link

Hi All,

I'm really interested in the zigbee groups feature to control multiple Xiaomi Wall Switches by a single MQTT command.

I can see that how we can send messages to a group, but sending control messages to these switches is a bit different because they are using separated topics for left and right relays.

Is it possible to apply the group functionality for these switches? If so, how we can set up them?

Thanks,
Peter

@Koenkk
Copy link
Owner

Koenkk commented May 10, 2019

First we have to check if this device support groups. Could you try to add it to a group the way it is now? Then either the left or right button should be in a group.

@pkedvessy
Copy link
Author

Sorry for the late response.
Finally I was able to have a try with a "Xiaomi Aqara Neutral Line Type Remote Control Switch": it got added to a really new group (lets say 'test'), but when I have tried to send '{"state": "ON"}' message to '/bridge/group/test/set' I got the following error: '{"type":"entity_not_found","message":"bridge/group/test"}'

@Koenkk
Copy link
Owner

Koenkk commented May 29, 2019

You should send the message to zigbee2mqtt/test/set {"state": "ON"}

@pkedvessy
Copy link
Author

Ahh, thanks, it is working now: left is in the group. Can we add right as well or can we configure somehow which one is in the group?

Koenkk added a commit that referenced this issue May 29, 2019
Koenkk added a commit to Koenkk/zigbee2mqtt.io that referenced this issue May 29, 2019
@Koenkk
Copy link
Owner

Koenkk commented May 29, 2019

@pkedvessy
Copy link
Author

pkedvessy commented May 29, 2019

Should I update my coordinator's firmware? I'm experiencing issues when starting zigbee2mqtt but I have no issue with the master branch...

@pkedvessy
Copy link
Author

I missed to say thank you for the quick turnaround on having support on my request! It's going to be more than brilliant to controll both channels by group messages!

@pkedvessy
Copy link
Author

I have updated my coordinator to Z-Stack_Home_1.2 version 20190425 and dev branch is working as expected. But when I'm trying to add a specific endpoint to a group, I get this error:

Jun 01 14:08:22 peetserver npm[17732]: zigbee2mqtt:debug 6/1/2019, 2:08:22 PM Received MQTT message on 'zigbee2mqtt/ground_floor/bridge/group/wall_switches/add' with data 'kitchen/wall_switch/2/right' Jun 01 14:08:22 peetserver npm[17732]: zigbee2mqtt:error 6/1/2019, 2:08:22 PM Failed to find device with entity ID 'kitchen/wall_switch/2' Jun 01 14:08:22 peetserver npm[17732]: /opt/zigbee2mqtt/lib/extension/groups.js:150 Jun 01 14:08:22 peetserver npm[17732]: const {entityID, endpointID} = this.parseID(ID); Jun 01 14:08:22 peetserver npm[17732]: ^ Jun 01 14:08:22 peetserver npm[17732]: TypeError: Cannot destructure property entityIDof 'undefined' or 'null'. Jun 01 14:08:22 peetserver npm[17732]: at Groups.updateDeviceGroup (/opt/zigbee2mqtt/lib/extension/groups.js:150:45) Jun 01 14:08:22 peetserver npm[17732]: at Groups.onMQTTMessage (/opt/zigbee2mqtt/lib/extension/groups.js:221:14) Jun 01 14:08:22 peetserver npm[17732]: at results.extensions.filter.map (/opt/zigbee2mqtt/lib/controller.js:152:27) Jun 01 14:08:22 peetserver npm[17732]: at Array.map (<anonymous>) Jun 01 14:08:22 peetserver npm[17732]: at Controller.onMQTTMessage (/opt/zigbee2mqtt/lib/controller.js:152:14) Jun 01 14:08:22 peetserver npm[17732]: at MQTT.onMessage (/opt/zigbee2mqtt/lib/mqtt.js:81:18) Jun 01 14:08:22 peetserver npm[17732]: at MqttClient.emit (events.js:189:13) Jun 01 14:08:22 peetserver npm[17732]: at MqttClient._handlePublish (/opt/zigbee2mqtt/node_modules/mqtt/lib/client.js:1162:12) Jun 01 14:08:22 peetserver npm[17732]: at MqttClient._handlePacket (/opt/zigbee2mqtt/node_modules/mqtt/lib/client.js:351:12) Jun 01 14:08:22 peetserver npm[17732]: at work (/opt/zigbee2mqtt/node_modules/mqtt/lib/client.js:283:12) Jun 01 14:08:23 peetserver npm[17732]: npm ERR! code ELIFECYCLE Jun 01 14:08:23 peetserver npm[17732]: npm ERR! errno 1 Jun 01 14:08:23 peetserver npm[17732]: npm ERR! zigbee2mqtt@1.4.0 start:node index.jsJun 01 14:08:23 peetserver npm[17732]: npm ERR! Exit status 1
and Z2M is terminating.

@Koenkk
Copy link
Owner

Koenkk commented Jun 3, 2019

Did you configure a base_topic in configuration.yaml?

@pkedvessy
Copy link
Author

Yes I did: zigbee2mqtt/ground_floor

@Koenkk
Copy link
Owner

Koenkk commented Jun 3, 2019

Can you post your configuration.yaml?

@stale
Copy link

stale bot commented Aug 2, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale Stale issues label Aug 2, 2019
@stale stale bot closed this as completed Aug 9, 2019
wilmardo pushed a commit to wilmardo/zigbee2mqtt that referenced this issue Sep 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Stale issues
Projects
None yet
Development

No branches or pull requests

2 participants