nickrout

Home assistant seems to have constrained pycountry to >23.12.11 two weeks ago. https://github.com/home-assistant/core/commit/f3984a9d3ee94b92fd5a1a8902532d436ca52353 This custom integration constrains pycountry to pycountry=22.1.10 You can't be >23.12.11 and

pycountry>23.0.0,>=22.1.10 Pointless. If it satisfies >23.0.0 it also satisfies >=22.1.10. The latter is unneeded

Mine keeps going unavailable. Restarting HA fixed it this time. Next time I'll try restarting the integration.

I have an automation now that runs where the device goes unavailable, and reloads the integration. Seems to work well. According to my traces, it runs roughly once or twice...

Yes it is the sensor's device_id. I made the automation via the HA UI, so I didn't need to know, it was inserted by the UI editor on choosing "device"...

Does anyone know if this has been fixed? I am keen to try frigate, but the only corals I can find are dev boards. **GRRR global chip shortage**

Thanks.

What appears there does seem to depend on how the entity is chosen (which IMHO is undesirably inconsistent) Option 1: search for the entity at the top of the page...

Me too. For months now.

Adding a bit of debug log after figuring out how ```text 2021-10-17 17:48:11 DEBUG (SyncWorker_11) [custom_components.openhasp.image] image_to_rgb565 out_image: /tmp/tmprqj8cuy4 2021-10-17 17:48:11 DEBUG (MainThread) [custom_components.openhasp] Push hasp/plate50/command/p3b1.src with http://192.168.20.254:8123/api/openhasp/serve/573c838f57c7ad4548f2ea662a815962 2021-10-17 17:48:11...