FlicTeam

@pico right now that particular code only acts as a client.

@pico I think this should be possible. You just need the javascript code that implements it. The underlying tcp/udp support we have should make it possible.

@kerry-thacher I sent you instructions on 5 feb how to enable logging for Apple TV as well, privately. That is what james-2 is referring to I assume. However, you responded that you have never run Homekit on your AppleTV.

@james-2 please file a case at https://flic.io/support and I will continue from there. Press "none of the above" when asked, in order to create an actual support ticket. Please include a link to this forum thread.

@pico I get your point. Maybe we should add a global datastore as well...

Did you know by the way that Govee lights support Matter? That way you should be able to control them using their static node id, so that you don't need to keep track of the IP address.

Could you try to log out from the Flic app and then log in again, to see if it works better then?

@james-2 No worries, I just saw that your question safely arrived to our support inbox. The support team handling the orders will be checking your case and reach back to you as soon as they have processed your issue.

@pico You can adjust the brightness even when it is off, so that it will remember the configured brightness the next time it is turned on. Execute the command I wrote under "setting brightness", adjusting node id and level as you wish.

The "options" is a bit map with currently only having one defined bit "ExecuteIfOff": "If this bit is set, commands in this cluster are executed and potentially change the CurrentLevel attribute when the OnOff attribute of the On/Off cluster is FALSE".

So, if you change OptionsOverride to 0 in the command, the command will be discarded in case the light is off. But if you leave it as 1, then the brightness will be modified in case the light is off.

You cannot write to the CurrentLevel attribute directly using a raw write since it is read only. You need to use one of the commands to adjust the level.

@picomitchell wrapping a subscription using await works fine. Just make sure you remember to cancel it when done. The data is cached by the hub so no extra round trip will be necessary to the device. Out of curiosity, what is your use case for that functionality instead of listening to event updates? You can save the latest value in some variable which would be accessible by the rest of the code.

Writing attributes is not that common to do in an automation setup, since most things can be done by sending commands, but often settings that are to be stored for some time are modelled as attributes that you write to.

@dajudge can you try to go in to the flic app and, without connecting to the hub, add a normal Internet request action targering https://api.flic.io, save the action and then try to execute it? Then tell me if you get any error message in a notification?