Phoscon Groups not working with Home Assistant

deCONZ 3rd Party Integrations
1

I’ve just updated to v2.19.01 / 19/09/2022 and firmware26780700. Previously, Phoscon groups were working fine from HA but that’s no longer the case.

If I set up a new group in Phoscon, the HA integration pulls it through and I can assign , for example, a switch to it and send turn on/turn off events but nothing happens at the bulb. If, in HA, I assign switches to individual bulbs they work perfectly.
The group controls in the Phoscon app are working perfectly so it seems something is getting lost/broken between HA and deconz but only for groups.

Is there a way to see the inputs from HA an the deconz side?

2

@Robban perhaps you can be of help :)?

3

Some things are not clear. Can you control the group light-entity directly in hass? You only say that you assign a switch some way to control the group; is it through an automation or how?

4

It’s through a card in Lovelace. Just a simple “light” card. I set the entity to the phoscon group name that’s been pushed through the deconz integration. The light/entity doesn’t show as “unavailable” so it should work when turning off/on but nothing happens at the physical bulbs. If I change the entity on the card to a single bulb, it works perfectly, but just for that one bulb.

5

Do you mean that when you switch out the referenced “deconz group” entity on the Lovelace card to a “deconz light” entity the control works?

If so, can you enable debug logging for the deconz integration in home assistant and we can see what is being sent once you trigger it from HA gui.

6

Exactly that, yes.

Logs below. Here’s with the lovelace card configured to control a deconz group (Test Group), commands sent, “turn on” then “turn off”:

2023-05-03 09:25:52.787 DEBUG (MainThread) [pydeconz.gateway] Sending “put” “{‘on’: False}” to “http://192.168.0.64:80/api/57B7847560/groups/13/action”

2023-05-03 09:25:52.797 DEBUG (MainThread) [pydeconz.gateway] HTTP request response: [{‘success’: {’/groups/13/action/on’: False}}]

2023-05-03 09:25:52.798 DEBUG (MainThread) [pydeconz.websocket] {“e”:“changed”,“id”:“1”,“r”:“lights”,“state”:{“alert”:null,“bri”:254,“colormode”:“ct”,“ct”:250,“on”:false,“reachable”:true},“t”:“event”,“uniqueid”:“00:0b:57:ff:fe:d2:fa:50-01”}

2023-05-03 09:25:52.799 DEBUG (MainThread) [pydeconz.websocket] {“e”:“changed”,“id”:“8”,“r”:“groups”,“state”:{“all_on”:false,“any_on”:false},“t”:“event”}

2023-05-03 09:25:52.811 DEBUG (MainThread) [pydeconz.websocket] {“e”:“changed”,“id”:“13”,“r”:“groups”,“state”:{“all_on”:false,“any_on”:false},“t”:“event”}

And again with the same card configured to control a deconz light, same commands sent:

2023-05-03 09:33:49.664 DEBUG (MainThread) [pydeconz.gateway] Sending “put” “{‘bri’: 252, ‘on’: True, ‘transitiontime’: 0}” to “http://192.168.0.64:80/api/57B7847560/lights/1/state”

2023-05-03 09:33:49.676 DEBUG (MainThread) [pydeconz.gateway] HTTP request response: [{‘success’: {’/lights/1/state/on’: True}},

{‘success’: {’/lights/1/state/bri’: 252}}]

2023-05-03 09:33:49.676 DEBUG (MainThread) [pydeconz.websocket] {“e”:“changed”,“id”:“1”,“r”:“lights”,“state”:{“alert”:null,“bri”:252,“colormode”:“ct”,“ct”:250,“on”:true,“reachable”:true},“t”:“event”,“uniqueid”:“00:0b:57:ff:fe:d2:fa:50-01”}

2023-05-03 09:33:51.870 DEBUG (MainThread) [pydeconz.websocket] {“attr”:{“colorcapabilities”:16,“ctmax”:454,“ctmin”:250,“id”:“4”,“lastannounced”:null,“lastseen”:“2023-05-03T08:33Z”,“manufacturername”:“IKEA of Sweden”,“modelid”:“TRADFRI bulb GU10 WS 400lm”,“name”:“Bathroom 4”,“swversion”:“1.2.221”,“type”:“Color temperature light”,“uniqueid”:“00:0b:57:ff:fe:d2:35:48-01”},“e”:“changed”,“id”:“4”,“r”:“lights”,“t”:“event”,“uniqueid”:“00:0b:57:ff:fe:d2:35:48-01”}

2023-05-03 09:33:52.669 DEBUG (MainThread) [pydeconz.gateway] Sending “put” “{‘on’: False}” to “http://192.168.0.64:80/api/57B7847560/lights/1/state”

2023-05-03 09:33:52.675 DEBUG (MainThread) [pydeconz.gateway] HTTP request response: [{‘success’: {’/lights/1/state/on’: False}}]

2023-05-03 09:33:52.678 DEBUG (MainThread) [pydeconz.websocket] {“e”:“changed”,“id”:“1”,“r”:“lights”,“state”:{“alert”:null,“bri”:252,“colormode”:“ct”,“ct”:250,“on”:false,“reachable”:true},“t”:“event”,“uniqueid”:“00:0b:57:ff:fe:d2:fa:50-01”}

2023-05-03 09:33:52.678 DEBUG (MainThread) [pydeconz.websocket] {“e”:“changed”,“id”:“8”,“r”:“groups”,“state”:{“all_on”:false,“any_on”:false},“t”:“event”}

2023-05-03 09:33:52.678 DEBUG (MainThread) [pydeconz.websocket] {“e”:“changed”,“id”:“13”,“r”:“groups”,“state”:{“all_on”:false,“any_on”:false},“t”:“event”}

7

It looks to me like the group commands are being sent and received fine. Am I right?

8

According to the logs it seems to be working as expected, the states are updated in hass but not in the real light?

Next thing would be to see what happens on deCONZ side. Maybe @Mimiix can be helpful in how to debug that.

This says that toggling the group makes deconz signal the state change of the light

Two groups states are updated based on the light being turned off (the one toggled as well as another group which probably contains the same light).

9

The on: False makes me believe its turned off? Or am i reading it wrongly?

Best way to test here is using the rest api, a getting started you can find here: Getting Started - deCONZ REST-API