My efforts to put all my #GitHub Action Workflows into a centralized repository and make where to run configurable on the ones for private projects is paying off. Most things can now run on my home cluster, but scaling is still somewhat slow:
Been going through my photos to find the photos I need to for the 3 blog posts I wrote about it yesterday. Came across some random photos, starting with the first node getting set up, with GUI for some reason:
Wrote 3 blog posts today 🫣 . Finishing off the 4th, and doing GitHub sponsors update after. Will be previewing two of those blog posts in there as one is a bit short: https://github.com/sponsors/WyriHaximus
Loving #PhilipsHue's long press to turn all the lights off. With some node-red and #HomeAssistant, I just extended that to our #lego light kits and display lights.
It was slightly infuriating to do because I had to figure out which event it was and to do that I had to look at all events coming from HA just to find "hue_event" among all "state_changed" events. It was simple after that to find the "long_release" event type for the "hue_event".
@benoit_badrignans True, but that is not exactly the same as the event type in the event object. The UI shows "Long release" while the value of event.type was "long_release". They are almost the same, but not guaranteed the same translation happens for each event.
@secupriv@benoit_badrignans Yeah it applies, thanks both found them in both locations. Will go there first next time because the "hue_event" is listed. (Not that in matters much but not using Zigbee directly but the official Hue bridge.)
Using node-red in such a way that I get all events, filter all that are of the long_release type, and then trigger the service calls.
