Gigaset Elements - Discontinues its services as of 29 March 2024

I would exclude a signal problem. The detectors are only a few meters from the base and trigger the Hue lamps reliably.

I have now checked the total logs again via your script (pm).
I see there numerous HUE events that are triggered by the motion detector. But the motion detectors and also the door sensors report their status only when the base station triggers a homecoming event.

`[-] 01/03/22 14:09:27 | um01     | close Wohnungstür
[-] 01/03/22 14:09:24 | ps02     | homecoming Bewegungsmelder
[-] 01/03/22 14:09:23 | ps02     | movement Bewegungsmelder
[-] 01/03/22 14:09:20 | um01     | open Wohnungstür`

Perhaps privacy mode is enabled? Can you check in the app under: Configuration / Alarm mode - Home

1 Like

That was the solution! Thank you, I would not have thought of it. I deactivated the privacy mode and now it works as it should. Perfect!

I still have one small question:
Can I also query the homecoming event via an automation? Or do I have to build it myself?

@Loki81 Inspired by your questions I will do a small release soon. I will add a warning to the logs if privacy mode is enabled moreover add as attribute to sensor.gigaset_elements_base_xxxxxxxx

While I am at it will also add an attribute to the same sensor showing the last home coming / leaving which you can than use as trigger for your automation.

1 Like

Sounds great, thank you :+1:t2:

@Loki81 New version released. Please let me know if it works as expected.

Hi, @dynasticorpheus

thanks, I will test it right away.
Would the query be correct?

platform: state
entity_id: sensor.gigaset_elements_base_1234566789123456789
to: homecoming

Important to take the recent_homecoming attribute as trigger. I read in the app this might have a delay up to 5 min so if this is too long than perhaps replicate functionality in hass using door + motion sensor.

platform: state
entity_id: sensor.gigaset_elements_base_f42a76c4cdc1b770a0e0d74efd3275b5
attribute: recent_homecoming

Have a look at the blueprint shared in this forum, there are some that might fit your use case.

Is there anywhere an overview of which attributes can assume which states? I haven’t found anything about this, not even blueprints.Do you have a hint for me? I’m trying to figure out which state I have to query in case of an intrusion.

Trigger =

platform: state
entity_id: alarm_control_panel.gigaset_elements
to: triggered

or if needed as condition:

condition: state
entity_id: alarm_control_panel.gigaset_elements
state: triggered

Hi @dynasticorpheus,

the integration works very well for me… and also within a few seconds. So no problems with it so far.
I only had to define a condition for the status of the alarm system. Otherwise, it recognizes a homecoming everytime the door is opened.

Looks like this for me now:

trigger:
  - platform: state
    entity_id: sensor.gigaset_elements_base_123456789abcdefg
    attribute: recent_homecoming
condition:
  - condition: state
    entity_id: alarm_control_panel.gigaset_elements
    state: armed_away

Hi @dynasticorpheus

unfortunately this does not work for me yet.
The automation is not triggered. I also don’t see any entries of the entity in the logs.

I set the trigger exactly as you said:

platform: state
entity_id: alarm_control_panel.gigaset_elements
to: triggered

But the only thing I see in the logs is the status of the siren. It changes to on.

[-] 01/25/22 12:38:22 | um01     | open Wohnungstür
[-] 01/25/22 12:38:22 | is01     | sirenon Sirene
[-] 01/25/22 12:38:22 | um01     | intrusion Wohnungstür
[-] 01/25/22 12:38:17 | um01     | prealert Wohnungstür

Do you have another idea?

@Loki81 Hmmm thats actually a regression I introduced, will release a new version soon to fix this. For now you can use the alarm_mode attribute of base sensor which will have triggered status also in case of alarm.

edit: Kindly update to version 2022.2.0 and let me know if triggered status works again

Hi @dynasticorpheus

I have set it exactly like this, but unfortunately it still does not work. Do you have any idea or can I test something else?

trigger:
  - platform: state
    entity_id: alarm_control_panel.gigaset_elements
    to: triggered
condition: []

I don’t see a corresponding entry in the logbook either. For example, I also do not see that the siren activates - only that it deactivates.

grafik

grafik

@Loki81 Can you update to latest version to see if this helps somehow? version 2022.5.1

Hi @dynasticorpheus

My Gigaset entity is duplicated in HA since the update:

However, the intrusion alarm now works properly.

Hi all,
First of all, thanks for creating this awesome integration.
I have one question. In my environment, the motion sensor only reports data when the alarm is active.
Is there any way to make use of that sensor even when the alarm is disarmed?

Thanks in advance

@atdownes Do you perhaps have privacy mode enabled? See Gigaset Elements - #43 by dynasticorpheus

@Loki81 Good to hear it’s working again for you also :slight_smile:

Good catch on the duplicate sensor. I actually had the same but assumed it was a local hick up on my machine. I released version 2022.5.2 to fix this.

After you have upgraded you can safely remove the one with the red exclamation mark. In case the base sensor unique id has _2 at the end you can manually remove that by renaming without.

Hi

i would like to put automatically the alarm on when i leave home. what is the command to put the alarm on ? i do not find it in the documentation

Thanks
Laurent