Z2m and hue_native_control

Configuration Zigbee
1

With the latest release of z2m we now have native hue controls available, which gives us more efficient network utilization plus more features.
See this pull request for more information:

I’ve enabled it for my around 60 hue bulbs and it seems to work. As a test I’ve tried to activate an effect and then change it’s colour.

Thing is, I mostly control my bulbs via zigbee groups, and it seemse the native hue controls doesn’t apply when I control lights through groups.

Have anyone else tried this out, and maybe made it work with groups?

2

Just set this up this past week and was searching for others - hence the old reply here.

Absolutely they work with groups. You can't create mixed non hue groups, and you either have to use mqtt or your zigbee2mqtt configuration.yaml to turn the same hue native flag on the group. I think there was a regression where they had the group flag enabled in the UI and pulled it off because of the mixed group problem. So just make sure you don't have a mixed group or things may go fubar.

I ping every room / zigbee room group every 90 seconds with updated adaptive lighting configurations including brightness and color. Hue native control slotted in seamlessly and reduced RF traffic significantly.

I'm actually planning an adaptive lighting design that further reduces RF by creating one master light group for the whole house, and just removing dynamically individual lights on the fly so they don't get adapted, eg if someone uses a dimmer paddle or sets a scene, and then adds them back when the scene is done. Need to validate reliability of dynamic zigbee groups though.

3

Like this?

devices:
  '0x00178801038c5e19':
    friendly_name: tvstue_tak
    icon: device_icons/547eb0da2c9c9be1b23cc2a5793f2669.png
    hue_native_control: true
  '0x8c8b48fffe43cd31':
    friendly_name: bad_speilys
    icon: device_icons/c480d23a17c59eeccd516b7d1d3ba5cb.png
  '0x54ef441000c42425':
    friendly_name: gang_bevegelse_n
    icon: device_icons/e3cf8f26cf8676dbe6b7cafc07a77acf.png
    hue_native_control: true
  '0x001788010e5946cf':
    friendly_name: gang_s_2
    icon: device_icons/c39b243908eaaa69b12ea14cf3321750.png
    hue_native_control: true
  '0x001788010e593f1f':
    friendly_name: gang_s_1
    icon: device_icons/c39b243908eaaa69b12ea14cf3321750.png
    hue_native_control: true
  '0xbc026efffe225412':
    friendly_name: soverom_avfukter
    icon: device_icons/e5f1fe49de608bc2593d5e44610a508c.png
    voltage_precision: 0
    current_precision: 0
groups:
  '2':
    friendly_name: z-soverom
    hue_native_control: true
  '3':
    friendly_name: z-soverom_u_seng
    hue_native_control: true
  '4':
    friendly_name: z-kjeller
  '5':
    friendly_name: z-murvegg
    hue_native_control: true
  '6':
    friendly_name: z-høyttalere
    hue_native_control: true
  '7':
    friendly_name: z-gulvlist
    hue_native_control: true
  '8':
    friendly_name: z-gulvlist_og_murvegg
    hue_native_control: true
  '9':
    friendly_name: z-huset_u_seng_og_nattlys
4

This looks correct to me based on mine. I set it via mqtt directly which saved it to the config file and avoided syntax. mqtt.publish action in developer tools is my goto but a few ways to do this.

  Topic: zigbee2mqtt/bridge/request/group/options
  Payload:
  { "id": "z-soverom", "options": { "hue_native_control": true } }
5

This works great, thank you so much!