homebridge-z2m: [Bug] The BIG scene in Homekit doesn't work completely.

Is there an existing issue for this?

I have searched the existing issues

Describe the bug

I noticed that if in a homekit scene, for example good nignt, where many (25-30+, I won’t say the exact number now) devices are switched off at the same time, some of them are switched off in homekit, but the information about it doesn’t get to the mqtt broker, its log doesn’t contain any information about the requested action from the homekit side. as a result, some of the lights remain switched on. Individually these devices are controlled without any problems, small scenes have no such problems. what can it be? where to dig? Is there some restriction in the plugin?

Related devices

Some bilbs and relays

Related Devices

Some bilbs and relays

Steps To Reproduce

Just create big scene

Expected behavior

Works good

Device entry

No answer

Status update

No answer

Messages from this plugin

No errors

This plugin

v1.11.0-beta.3

Homebridge

Latest

Zigbee2MQTT

Latest DEV

Homebridge Config UI X (if applicable)

Latest

About this issue

Original URL
State: closed
Created 5 months ago
Comments: 23 (5 by maintainers)

Most upvoted comments

@mrmaximas are you using Mosquitto (like myself)? I went on a scavenger hunt in the docs and found this:

max_inflight_messages count The maximum number of outgoing QoS 1 or 2 messages that can be in the process of being transmitted simultaneously. This includes messages currently going through handshakes and messages that are being retried. Defaults to 20. Set to 0 for no maximum. If set to 1, this will guarantee in-order delivery of messages.

Notice the default of 20. I just changed this on my mosquitto instance and it already makes a major difference. Not perfect, but much better.

@GrimmiMeloni Looks like you made my day! Thank you so much!

mrmaximas on Mar 17, 2024