Ikea On/Off button turns off all groups/lights

[vandalon]

The Ikea On/Off button that comes with the new ikea tradfri plug seems to turn on/off all groups/lights in phoscon after connecting, without any configuration.

[manup]

Yes, see #846

We need to extend the setup process, so that the group binding happens automatically.

[ebaauw]

We need something similar for the innr RC 110 as well, but probably different commands to setup the groups, see #635. Would that be in the REST API plugin or in Phoscon?

[vandalon]

I've tried the binding dropbox but that did not work for me, and after trying all my lights where unreachable, don't know why :) It would be good to have a way to ignore the "to all" broadcast. I use the switches, without binding them to groups, within home assistant. So I don't "need" to bind them to any groups.

[manup]

We need something similar for the innr RC 110 as well, but probably different commands to setup the groups, see #635. Would that be in the REST API plugin or in Phoscon?

Should be done in the REST-API, for the Bush Jaeger switches it is done in functions:

checkSensorBindingsForClientClusters()
checkSensorGroup()

I've tried the binding dropbox but that did not work for me, and after trying all my lights where unreachable, don't know why :) It would be good to have a way to ignore the "to all" broadcast. I use the switches, without binding them to groups, within home assistant. So I don't "need" to bind them to any groups.

A group cast to all can't be ignored :) the only way to workaround this is to create a binding.

[Kendobendo]

Any update on when deconz will officially support the new IKEA on/off remote?

[cappadanna]

Is it possible to use the Deconz app to create a binding between the on/off switch and a light? I’m new at this and don’t understand the group thing.

[Thomas-Vos]

I tried to bind the on/off switch to a group, it shows successful, but the API and Phoscon still shows it toggles all the lights. Is there anything I can do to get these switches supported in deCONZ?

[ebaauw]

You probably need to use the dimmer after binding it. The REST API plugin only sets config.group when it sees the dimmer issues a group command.

[manup]

Per default the dimmer just broadcasts to the whole network, hence all lights react.
When a group binding is created the dimmer will only use that group.

Currently this isn't done automatically, I hope to get access to one switch in the next days and will add
the automatic binding so the dimmer is working more usable.

[Thomas-Vos]

Thanks for the quick replies. I pressed the buttons while it was binding, and a few times when the binding was complete, but the REST API still shows group 0 for the sensor:

{
	"config": {
		"alert": "none",
		"battery": 87,
		"group": "0",
		"on": true,
		"reachable": true
	},
	"ep": 1,
	"etag": "7341a3579ba5348584aea3d1da718e0c",
	"manufacturername": "IKEA of Sweden",
	"mode": 1,
	"modelid": "TRADFRI on/off switch",
	"name": "TRADFRI on/off switch ",
	"state": {
		"buttonevent": 1002,
		"lastupdated": "2019-01-20T18:06:43"
	},
	"swversion": "1.4.018",
	"type": "ZHASwitch",
	"uniqueid": "d0:cf:5e:ff:fe:d6:f3:33-01-1000"
}

It might be that I am doing this wrong. I'm trying to bind the sensor to a group with id 17 I created using the API.

Does this look correct to you?

[ebaauw]

Looks good to me. Did you also bind the Level Control cluster?

[Thomas-Vos]

Just did that as well. Again it shows "success" in the binding dropbox but the REST API still shows group 0. Are there any more clusters that need to be bound to the group? I just bound the On/Off and Level Control clusters.

[ebaauw]

Are there any more clusters that need to be bound to the group? I just bound the On/Off and Level Control clusters.

Not that I can think of.