autoExpose.groups

[Nastras]

Hi Erik, I need your advice again. I can't get it to display the groups.

When I send the command to the getaway I get {} as response. But when I call the gateway afterwards I can't find the setting autoexpose.groups.

I think my command is wrong or?

curl -s -X PUT -d '{"autoExpose.groups": true}' http://127.0.0.1:40865/gateways/00212EFFFXXXXXXXXX/settings | json

Thanks!

[ebaauw]

That setting no longer exists. See https://github.com/ebaauw/homebridge-deconz/wiki/Dynamic-Configuration.

[Nastras]

I don't find it what you mean. 🫣. Have looked through the page so many times now. Please give me a hint what I need to do to view the groups 😅.

[Nastras]

This was all somehow easier with ph and homebridge-hue 😁.

[ebaauw]

You need to change the expose setting on each group device you want to expose. You can use the ui utility, see bottom of the Wiki page.

[Nastras]

For real now 😅 I will try it tomorrow morning and let you know if it works 👍.

[Nastras]

Mission successful 😅🎉🤪 Thanks for the hint 👌

[ebaauw]

Hm, the default gamut and ct range warnings are a bit superfluous, as there's no way to specify these for a group.

[Nastras]

I have this message for other devices/lamps as well. There it is ok?

[ebaauw]

deCONZ should expose the gamut and ct range for these lights, which can now be done quite easily through DDFs. Without these, the colours might be off, or Homebridge deCONZ might try and set a colour (temperature) that the light doesn’t support.

[Nastras]

So it's a deconz problem. When I have inserted the lamp in HK I will test it and if necessary open an issue at deconz. Thanks for the explanation.

[ebaauw]

The DDFs for LEDVANCE and OSRAM lights still need to be made, I think. See also https://github.com/dresden-elektronik/deconz-rest-plugin/issues/6591#issuecomment-1492947737.

[Nastras]

I just noticed something else. I am not sure if it is a bug. I have discovered a spelling mistake in the name of a device. I have corrected this via phoscon. Afterwards I restarted homebridge-deconz. The name of the device is displayed in the journalctl right. In the warning directly below the old and wrong name is still displayed.

[ebaauw]

Note that the first message displays the accessory name; the second message the service name.

That's a "feature": Homebridge deCONZ doesn't sync the resource name with the service name. You would need to change the service name in HomeKit as well. Alternatively, if you were to un-expose/re-expose the device, the new name would be picked up.

[Nastras]

Good to know. Thx!