Ruslan Sayfutdinov

This happens for camera-streamer precompiled for libcamera0.1. When I manually compile it for libcamera0.2, I get this: ``` [1:04:13.626468831] [16703] INFO Camera camera_manager.cpp:284 libcamera v0.2.0+46-075b54d5 [1:04:13.761606569] [16716] WARN RPiSdn sdn.cpp:39...

To add more details: this error appears as soon as I open stream or request snapshot from raspberry pi v3 camera. I have 64 bit OS: ``` > uname -a...

Ok, basically crash is expected when version of `libcamera-ipa` doesn't match `libcamera-dev` with which `camera-streamer` was built. And precompiled version was built with `libcamera-dev 0.1.0`. And compatibility issue with libcamera0.2...

Have you tried using full address as a login?

Can you try this script and add `print(res)` after line 26? https://gist.github.com/rithvikvibhu/952f83ea656c6782fbd0f1645059055d

It could be related to list of used cyphers: https://github.com/simon-weber/gpsoauth/blob/master/gpsoauth/__init__.py#L30-L45 Maybe something is wrong with ssl on your system.

It should be able to find 1.0.0 if you have python3.8+ https://pypi.org/project/gpsoauth/ Home Assistant minimum required python is [3.8](https://github.com/home-assistant/core/blob/dev/homeassistant/const.py#L13).

1. This will break existing automations. 2. Most likely this will break UI as well. Please follow discussion in https://github.com/home-assistant/architecture/discussions/635

I don't like "Unknown" state because it's misleading as we know the state of alarms. I agree that "Unavailable" isn't much better but I don't think we should introduce a...

I guess the first thing we should do is detect b&b when split is involved and abort as unsupported case. Until someone figure out how to calculate this cases properly.