#Hello everyone,
1 messages · Page 1 of 1 (latest)
The problem is that Z2M thinks the light is still on, so that's what HA is told
Probably the problem is that the message to turn off is getting lost
You may be able to solve that by moving to a Zigbee group - in Z2M - and turning that group off
That brings other challenges, but may help here
Would you recommend creating a group containing all my lights?
Worth a shot
I'm going to read the documentation as I'm not at all familiar with this feature. Will it still allow me to control each light independently? What are the advantages of a group? And you mentioned potential problems, what could that entail?
For your information, I have 14 lights
But how can I link my homekit scene to this Z2M group?
Read the group docs above 😉
Being a group leaves everything else alone, you can still control them separately
You can however also control the group as one - but it's a broadcast that can increase traffic on the mesh. Sometimes it causes more problems than it solves
As for HomeKit... no idea, don't use it, but you'll have another light to expose, just add that to the scene and remove the others
okay thanks I'll read all about it,but I'd like to avoid having an extra light in homekit that would manage all the lights.
isn't there another solution to avoid losing mqtt messages?
For information, here's my mosquitto config:
persistence true
persistence_location /mosquitto/data/
log_type all
listener 1883
# Auth
allow_anonymous false
password_file /mosquitto/config/password.txt
and Z2M :
homeassistant:
status_topic: homeassistant/status
mqtt:
base_topic: zigbee2mqtt
server: mqtt://192.168.10.2
user: ****
password: ****
frontend:
port: 9442
serial:
port: /dev/ttyACM0
adapter: deconz
availability:
active:
timeout: 15
passive:
timeout: 360
advanced:
last_seen: ISO_8601
channel: 25
timestamp_format: DD-MM-YYYY HH:mm:ss