Hi @maxym
You’re right, I definitely didn’t express myself clearly. I certainly don’t want to speak ill of HACS. I think it’s a way of constantly introducing new integrations, which will eventually be incorporated into Home Assistant in a future update. That’s how I see it, anyway. Of course, there are also developers who want to remain independent so they can fix bugs more quickly or launch new products.
Nevertheless, particularly with regard to Bosch Smart Home, I’d like to point out that the system has been on the market for several years now and has changed very little since then (partly because I consider it to be stable and free from any failures). That’s why I thought it was worth mentioning that the system could one day be officially incorporated into Home Assistant. In a way, this is also a marketing strategy for Bosch Smart Home itself.
Thanks for the kind words and the detailed explanation, much appreciated. And a big thank you to everyone who has been testing, reporting issues, and leaving feedback over the years, that kind of support makes a real difference.
I have been ramping up my involvement in the broader Bosch Smart Home ecosystem and am now actively contributing to @tschamm upstream Bosch Smart Home integration as well. The two projects are connected, and bringing them closer together is part of the plan going forward.
On the path to HA core: the Bosch Smart Home integration is heading in that direction, but realistically that is a long process. The HA core review queue is slow and the requirements are strict, so I would not expect it any time soon.
For the camera integration specifically, the next concrete step is getting it into the official HACS default repository. I already have an open PR for that (hacs/default#8181, currently in the review queue). Once that lands, users can install it directly through the HACS UI without adding a custom repository.
If anyone runs into bugs or has feedback on the camera integration in the meantime, I would really appreciate reports on GitHub. That is the easiest way for me to track issues and make sure nothing gets lost.
BWTH/BWTH24 temperature offset — Fixed in boschshc-hass 0.7.19 + boschshcpy 0.3.16. The Wall Thermostat II (BWTH, BWTH24) now exposes a temperature offset entity in HA (±3.5 °C for BWTH, ±5.0 °C for BWTH24). Update via HACS.
SWD2 / SWD2_PLUS button presses — Not fixable via the local REST API. The Bosch SHC does not expose a Keypad service for this device over the local API; button actions are handled entirely in firmware. No solution available in the integration.
TRV Gen2 Dual (TRV_GEN2_DUAL) — Already recognized by the integration (it appears as a thermostat device). Per-TRV individual entities are an architectural decision deferred for a future release.
Not sure if it is a bug or missing configuration on my end. Has someone the motion detectors in use? Meanwhile the illuminance is shown as well but if i look for e.g. the last 7 days it is constantly showing the same lux value. I would like to configure it like if it is below a certain value light turns on as long as motion is detected.
Does it need to be triggerd to check the latest illuminance, any other feedback?