@Loki81 Your json file looks perfectly fine, does below command yield any results? If not the only thing I can recommend is to remove the motion sensors via the app and re-add them and see what happens.
gigasetelements-cli --username [email protected] --password secret --events 10 --filter motion
Yes, but that’s not the result I would have expected, since we walk past the motion detectors at least 50 times a day.
@Loki81 Perhaps the motion sensors distance or thick walls are blocking signal towards base station hence only few motions end up registered? Perhaps try and test with one sensor close to base?
What is the result of below command?
gigasetelements-cli --username [email protected] --password secret -ss
Gigaset Elements - Command-line Interface v1.6.0b1
[-] Identity | VERIFIED | User logged in successfully.
[-] Authentication | SUCCESS |
[-] Basestation | ONLINE | 9A485F34D0678DD08B9FD6BF1D89586D
[-] Status | RED | ENDNODE_OFFLINE | Modus HOME
[-] Basis Home | ONLINE | firmware UP_TO_DATE
[-] Annikalampe | ONLINE | firmware UP_TO_DATE
[-] Regallampe | ONLINE | firmware UP_TO_DATE
[-] Stehlampe 1 | ONLINE | firmware UP_TO_DATE
[-] Weihnachtsstern Klein | ONLINE | firmware UP_TO_DATE
[-] Esszimmerlampe Oben | ONLINE | firmware UP_TO_DATE
[-] Rauchmelder | ONLINE | firmware UP_TO_DATE | battery OK | 0347199093
[-] Rauchmelder | OFFLINE | firmware UP_TO_DATE | battery OK | 0347198D87
[-] Schlafzimmerlampe | ONLINE | firmware UP_TO_DATE
[-] Flurlampe | ONLINE | firmware UP_TO_DATE
[-] Rauchmelder | ONLINE | firmware UP_TO_DATE | battery OK | 0335D180DE
[-] Fenstersensor | ONLINE | firmware UP_TO_DATE | battery OK | 0335A97EE6
[-] Bewegungsmelder | ONLINE | firmware UP_TO_DATE | battery OK | 031C1797D3
[-] Fenstersensor | ONLINE | firmware UP_TO_DATE | battery OK | 033E1776D8
[-] Alarmschalter | ONLINE | firmware UP_TO_DATE | battery OK | 033E3CABFA
[-] Küchenlampe | ONLINE | firmware UP_TO_DATE
[-] TV Licht | ONLINE | firmware UP_TO_DATE
[-] Philips hue | ONLINE | firmware UP_TO_DATE
[-] Stehlampe 3 | ONLINE | firmware UP_TO_DATE
[-] Sirene | ONLINE | firmware UP_TO_DATE | 031C01D7A6
[-] Stehlampe 2 | ONLINE | firmware UP_TO_DATE
[-] Mikalampe | ONLINE | firmware UP_TO_DATE
[-] Bürolampe | ONLINE | firmware UP_TO_DATE
[-] Weihnachtsstern Groß | ONLINE | firmware UP_TO_DATE
[-] Bewegungsmelder | ONLINE | firmware UP_TO_DATE | battery OK | 0324EFC0D8
[-] Rauchmelder | ONLINE | firmware UP_TO_DATE | battery OK | 0335D181DA
[-] Rauchmelder | ONLINE | firmware UP_TO_DATE | battery OK | 0335D183B9
[-] Rauchmelder | ONLINE | firmware UP_TO_DATE | battery OK | 0335D1813D
[-] Rauchmelder | ONLINE | firmware UP_TO_DATE | battery OK | 0335D18247
[-] Waschküche | ONLINE | firmware UP_TO_DATE | battery OK | 0324D89F22
[-] Rauchmelder | ONLINE | firmware UP_TO_DATE | battery OK | 0335D180BF
[-] Bewegungsmelder | ONLINE | firmware UP_TO_DATE | battery OK | 031C1798A9
[-] Esszimmerlampe Unten | ONLINE | firmware UP_TO_DATE
[-] Feuerwehrhelm | ONLINE | firmware UP_TO_DATE
[-] Garagentür | ONLINE | firmware UP_TO_DATE | battery OK | 033E3C755A
[-] Wohnungstür | ONLINE | firmware UP_TO_DATE | battery OK | 033E3C7403
[-] Fenstersensor | ONLINE | firmware UP_TO_DATE | battery OK | temperatur e 17.0 | pressure 987 | 0335A97EE6
[-] Fenstersensor | ONLINE | firmware UP_TO_DATE | battery OK | temperatur e 18.4 | pressure 987 | 033E1776D8
[-] Wohnungstür | ONLINE | firmware UP_TO_DATE | battery OK | temperatur e 19.4 | pressure 987 | 033E3C7403
[-] Garagentür | ONLINE | firmware UP_TO_DATE | battery OK | temperatur
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
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.
Sounds great, thank you 
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
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
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.
My Gigaset entity is duplicated in HA since the update:
However, the intrusion alarm now works properly.
