Problem with separate messages for a color change

[foorschtbar]

Hi,
unfortunately I haven't found anything via the search. I have been using homekit-bridged for a long time and assume the following things:

• When the color changes, only the values that have changed are sent, right?
• And what changes is sent in a separate message, right?

For example, have a lamp with Hue, saturation and brightness characteristics. Color is set to H:100, S:100 and changes now to H:0, S:200, then i got H:0 from the node while S:200 is still set and the lamp briefly shows H:100, S:200. Then S:200 comes from the node the the color is now correct.

Is there any workaround? I try to wait until i get a valid H/S pair with context.get/set, but some color changes only change H or S.

Do you know what I mean?

(The values for H and S are fictitious)

[crxporter]

This is one of the most common homekit problems - lights flashing to one state before quickly going to another. It's caused by how homekit sends messages... It was even an issue in some of my first "homekit official" hardware ever.

Try the following...

Step one:
Put a "debounce" to the right of the light node. This will be a trigger node set to send nothing, wait 250 ms, then send the latest message object.

Step two:
Use the data in msg.hap.allChars (which will always have the homekit H, S, and B values) to send a message to your device.

Hopefully that makes sense. Show me your flow if not.

[foorschtbar]

I'm pleased to see that I haven't done anything wrong :)

That works! Thank u.

Funfact: At the first attempt Node-Red had a bug: My function node (right after the light/debounce node) sends still multiple messages..also without a connected input, but after a complete redeployment this was gone.