Vertex Integration

Sub stream works, but the resolution is so small (640x480) compared to the 4K feed it can produce. One thing I did realize is that I had to restart HA...

I believe this is the official site: https://gitlab.com/Shinobi-Systems/ShinobiDocker

https://codepen.io/vertex-github/pen/ZEwYeZd actually works worse than in my app - nothing is showing inside the viewport here.

Related - how about a smart retention policy like this: https://forum.duplicati.com/t/new-retention-policy-deletes-old-backups-in-a-smart-way/2195 This keeps 1d for 7d, 1/wk for 4wks, and then keeps 1/mth for 12 months. - that would be...

ntfy support is super simple to implement via their web POST hook (config is host,port), and then other external clients could be listening to those notifications to trigger emails etc....

Logs from NR: 21 Aug 14:39:48 - [error] [api-call-service:Garage On] InputError: Invalid action format: on-press 21 Aug 14:39:52 - [error] [api-call-service:Garage On] InputError: Invalid action format: on-press 21 Aug 14:39:54...

I rolled everything back to 0.65.1 and I'm back to normal operation. I only saw errors from nodered - the service call didn't seem to be making it to HA....

I wasn't hiatorically caring about the msg Payload or msg.actiom values. I just used the messages as a trigger to the node and the call service node.did it's thing, like...

All my flows have something in the msg.payload that's always seemingly been ignored - they certainly didnt error out. The flow is simple : Inject a message with a payload...

Im also receiving the following errors from Github when posting here: Remove 'waiting-for-response' label on issue comment by author / remove-label Failed in 3 seconds