Bosch Smart Home

Feature Requests
287

Hey there,
I’m using the HACS integration of Bosch Smart Home Controller (SHC) for some months now and im still impressed by it. I don’t regret having bought the Bosch components.

The only thing i’m missing is triggering scenarios in combination with presence controll. I wanted to solve this with an automation from Home Assistant.

I tried to use the service “Bosch SHC: tigger_scenario” to trigger the scenario i wanted but I can’t get it to work. What do i have to type into the service data field to select the right scenario?

service: bosch_shc.trigger_scenario
data:
  name: Haus verlassen
288

Hi
anything in the log when you trigger the scenario?

I do not use the scenarios yet, but I created a new scenario named “Test1” in Bosch-App on my phone and called the service from the DEV-Tools with (YAML-Mode)

service: bosch_shc.trigger_scenario
data:
  name: Test1

switched on a lamp as configured in the scenario.
Had to restart HA to pick up the new scenario in the integration, prior to that Error was

[homeassistant.components.websocket_api.http.connection] [2851611960] Error handling message: value must be one of [] for dictionary value @ data['name']. Got None

Did you create the “Haus verlassen”-Scenario in the App and configure the actions? The scenarios are listed as preconfigured, but I believe they do not exist as scenario until you went through the configuration and stored it as a new scenario.

Armin

1 Like
289

Hey Armin,
thanks for the quick reply. Yes, I tried it first with the 2 preconfigured scenarios. After this i createad a new scenario named “Test” but i didn’t restart HA after this.

Now after the reboot it works. Thanks a lot!

Edit: I also got the same Error message when i was trying with a different syntax to select the scenario.

290

Hi @tschamm

not sure if this is already supported or not - are there plans to expose the Scenarios from the Controller as scene entities? I saw that there is an API for scenarios
https://apidocs.bosch-smarthome.com/local/#/Scenarios/get_scenarios

and e.g. the hue integration also exposes all hue scenes as Entity with name scene.<room>_<scene_name>

That would be a nice enhancement.

Thanks, Andre

291

Scenarios can be triggered via events currently. I‘ll have a look next week if it makes sense to integrate it the way hue does it.

1 Like
292

Hello everyone,

I’m wondering if someone has an YAML (or via GUI) example, how to configure an automation, that is listening for an event, if the alarm has been fired. I’m currently listening on the state of the smoke detectors, but I experienced, that this now has a 5-6 seconds delay.

Also, I would be interested in what device has triggered the event, if possible.

Thanks for your help, everyone!

Best,
Philip

293 
  - alias: Turn on lights on smoke alarm
    trigger:
      - platform: event
        event_type: bosch_shc.event
        event_data:
          id: "smokeDetectionSystem"
          event_type: "ALARM"
    action:
      - service: homeassistant.turn_on
        entity_id:
          - switch.livingroom_light1
etc, etc

This does have a slight delay and does not tell you which fired.
However, you can do the same on individual alarms and you get instant firing of the event and you can tell which one it is. The downside being that if you have 5 smoke alarms you would need 5 automations.

294

Is it possible to trigger the siren of all smoke detectors simultaniously based on an HA automation? If yes, how?

1 Like
295

Did I miss something or are the water sensors not supported (yet) ?

I can get information about battery level, but I don’t get a hint on wet / dry or on / off?

296

What component are you using? The custom one or the one shipped with HA? The water sensor is supported in the custom component version.
Best, Thomas

297

Till now I am only using the sipped version. So I should install the custom version I guess.

298

Correct, with the custom component platform support is much better. I am working on getting the shipped component on the same level, but this takes time.

299

Hi, I’m new to Home Assistant and slowly building my Dashboard. I use BSH for windows, doors and other things. What I also use is the Alarm Szenario. I have a Shortcut where I activate the Alarm Scenario from the BSH System. I’d like to do this from within HA - but I figured out that I cannot trigger any BSH Scernarios, only sensors are available.

I understood that there are two BSH integrations for SA - the official one (I’m using) and this for HACS. Will this version bring the supported feature I’m looking for? Can I use both entities on my HA, or do I have to uninstall one?

Thanks for any support!

300

Hi Nils,
welcome to this Forum. The HACS version does support BSH scenarios. You can trigger them via Events.
Just install the HACS version in addition to the official one, and you will have full support.
Best, Thomas

1 Like
301

Thanks for this integration. Unfortunately, I get the following error every few days. Then it works again for several days without any problems. I control multiple covers in an automation and use delays of several seconds to work around the problem. It’s not really successful. Are there better workarounds?
Iam using the HACS integration.

boschshcpy.exceptions.SHCSessionError: SHC Error (message: API call returned non-OK result (code 503)!: b'{"@type":"JsonRestExceptionResponseEntity","errorCode":"SERVICE_INVOCATION_FAILED","statusCode":503}')

302

Hi guys,

Thanks for this great integration, but it seems it is missing a device type.
I recently purchased a Bosch SHC + 2 Smoke Detectors (version 2) and installed the integration. The Smoke Detection System is discovered, but the detectors do not show up in HA as separate entities.

Going over the code and after inspection of the SHC API using postman, i discovered that the version 2 of the smoke detector uses a different deviceModel: SMOKE_DETECTOR2

    {
        "@type": "device",
        "rootDeviceId": "XXXXXXXXXXXXXX",
        "id": "hdm:ZigBee:XXXXXXXXXXXXXX",
        "deviceServiceIds": [
            "CommunicationQuality",
            "BatteryLevel",
            "Alarm",
            "SmokeDetectorCheck"
        ],
        "manufacturer": "BOSCH",
        "roomId": "hz_1",
        "deviceModel": "SMOKE_DETECTOR2",
        "serial": "XXXXXXXXXXXXXX",
        "profile": "GENERIC",
        "name": "smoke_detector",
        "status": "AVAILABLE",
        "childDeviceIds": []
    }

But in the boschshcpy library, this deviceModel is not mapped to a device implementation

MODEL_MAPPING = {
    "SD": SHCSmokeDetector,
    "SMOKE_DETECTION_SYSTEM": SHCSmokeDetectionSystem,
    .... more device models here ....
}

Should the SMOKE_DETECTOR2 device model be added to the boschshcpy library to make this work?
Your help is much appreciated!

Best regards,
Erik

303

Hey Erik,
I just released a new version of the 3rd party library boschshcpy which now adds support for the SMOKE_DETECTOR2 as well as the TRV_GEN2.
If you are using the custom component, you can update it via HACS. If you are using the official integration, you have to be patient, I have not yet opened a PR which delivers the new functionality.
Best, Thomas

304

Hi Thomas,

Thanks for the update. I updated through HACS and it works as expected, the detectors show up in the integration.
I have another question on the smoke detectors which you might be able to answer for me.

My assumption was that triggering a selftest on the detector would trigger an event through the API, and i would be able to test if any automation triggered by a smoke alarm event could be verified. But this does not seem to be the case. I know this is more a question for the Bosch team that maintains the SHC api, but do you know if the Alarm and SmokeDetectorCheck state can be long-polled and if that will trigger an event through the HACS integration?

Kind regards,
Erik

305

Hi Erik,
I assumed that also but if you look at the events on the bus you see that they are different and they are a test version so if you want your actions to happen you have to call then when you see the test event on the bus.
EG

  - alias: Turn on lights on smoke alarm test
    trigger:
      - platform: state
        entity_id:
          - binary_sensor.hall_smokealarm
          - binary_sensor.landing_smokealarm
          - binary_sensor.loft_smokealarm
          - binary_sensor.garage1_smokealarm
        attribute: smokedetectorcheck_state
        to: "SMOKE_TEST_OK"

Hope that helps.
Ben

306

Hi Ben,

Thanks, that certainly helps!
But the big question then remains: how do i test a real smoke alarm?
Do i have to burn a newspaper underneath the detector :joy: That feels kinda dumb for a ‘smart’ device

subquestion: where did you get the value SMOKE_TEST_OK from? I could not find it in the Bosch API specs on Bosch Smart Home Local API

Best regards,
Erik