I am always so close. I have an automation using the chose statement and I want a different action depending on whether a switch is on or off. The automation works fine when I remove the “for:” criteria. But I only want the automation to trigger when the switch is on for 30 minutes . Thanks in advance
I am getting this error:
Invalid config for [automation]: [to] is an invalid option for [automation]. Check: automation->condition->0->conditions->0->to.

Commenting it out works
entity_id: switch.spiral
state: 'on'
       # for:
       #   minutes: 30 
I also tried but no luck :
to: "on"
for: "00:30:00"

  alias: kidinbed
  trigger:
  - platform: state
    entity_id: switch.spiral
  condition: []
  action:
  - choose:
    - conditions:
      - condition: state
        entity_id: switch.spiral
        state: 'on'
        for:
          minutes: 1 
      sequence:
      - service: input_boolean.turn_on
        entity_id: input_boolean.kidsleepmode
      - service: switch.turn_on
        entity_id: switch.adaptive_lighting_sleep_mode_kid_adaptive
      - service: tts.google_say
        data_template:
          entity_id: media_player.dinning_room_speaker
          message: kid is now in Bed
      - service: homeassistant.turn_on
        entity_id: light.notificationlights
        data:
          brightness: 30
          rgb_color:
          - 0
          - 0
          - 255
      - delay: 00:00:15
      - service: homeassistant.turn_off
        entity_id: light.notificationlights
    - conditions:
      - condition: state
        entity_id: switch.spiral
        state: 'off'
      - condition: state
        entity_id: input_boolean.kidsleepmode
        state: 'on'        
      sequence:
      - service: input_boolean.turn_off
        entity_id: input_boolean.kidsleepmode
      - service: tts.google_say
        data_template:
          entity_id: media_player.dinning_room_speaker
          message: kid is Up
      - service: homeassistant.turn_on
        entity_id: light.notificationlights
        data:
          brightness: 255
          rgb_color:
          - 255
          - 0
          - 0
      - service: xiaomi_aqara.play_ringtone
        data:
          gw_mac: 7811DCFD69DF
          ringtone_id: 10001
          ringtone_vol: 100
      - delay: 00:00:58
      - service: homeassistant.turn_off
        entity_id: light.notificationlights
      - delay: 00:02:00
      - service: switch.turn_off
        entity_id: switch.adaptive_lighting_sleep_mode_kid_adapt
  mode: restart  

4 posts - 2 participants

Read full topic

I am noticing undesired behaviour, using HA iOS app.

In a dashoard, with multiple views, I have installed buttons, which have sliding functionality. (type:light with horseshoe slider and custom:slider-button-card). I notice this behaviour, using either button.

Behavoiur:
when using the slide function, the action controls light brightness as intendend. When “releasing” the button, the change to a different view occurs. Apparently, the direction of navigation is consistent with the direction of the slide action.

So for some reason, the use of the slider is also interpreted as a swipe navigation command.

I am not aware of having installed or specified swipe navigation; I also don’t know, where to verify, if I have, or where to switch it off, if installed.

I am also not aware, of any iOS specific feature, which can be controlled through the mobile device (app) directly

The behaviour is definitely undesired and makes the dashboard virtually unusable on the device, as I constantly have to navigate back to the original view.

Any input how to adjust or remove this behaviour?

1 post - 1 participant

Read full topic

Has anybody already looked at downloading the related image of a Nest Doorbell (or camera) Event?

When the doorbell is pushed, or a person is detected, the device trigger that is triggered in HA contains an event Id that can be used with the nest GenerateImage call to create a downloadable image.

See Doorbell  |  Device Access  |  Google Developers and Device Access  |  Google Developers

The most used usecase for this is to send a picture to somewhere when the doorbell has been pressed. Due to delays, fetching an image from the stream when the event is handled in HA gives a slightly newer picture, where the person might not correctly in the frame. That’s why it’s best to use the image that is linked to the event.

1 post - 1 participant

Read full topic

Hey guys,

Lets start with thanking the people of HA and all involved. Its so awesome! And it’s getting better every update.

Now for my question:

Ive searched quite a bit, and there are integrations available, but as far as I can see none of which are still maintained/updated.

What I want to do is control a TCL A/C (via automation), that’s already connected to Google Home.
The TCL A/C I have is a newer edition that uses the “Intelligent AC” APP.
A lot of people tried connecting the particular A/C to HA directly by reverse engineering the app etc, but as of yet nothing really works. ( [SOLVED: for local access]A/C app named TFIAC, anyone ever heard of it? - #57 by pyby topic says solved, but it continued with our problem)

Now Ive found Assistant Relay, but its not maintained anymore.

All I would like it to do is have HA turn on the AC when outside raises above x and turn off when drops below x.

So all it needs send to Google Home is “ac on” or “ac off”, the rest I can do in HA.
Basically control a device that’s only connected through Google Assistant.

Thanks all.

1 post - 1 participant

Read full topic

(Sorry if this is not in the right forum section, if this needs to he moved let me know)

After updating to 2021.7.2 my Entities card will sometimes show the spacing on the card correctly but after a browser or app refresh it will squish all the entities to the left side of the card. After a few browser refreshes it is back to normal until the cycle repeats. Has anyone else seen this behavior before?

1 post - 1 participant

Read full topic

I suspect there’s something weird about the network setup that supervised HASS produces, I hope someone will be able to chime in and point me to right direction. I’m using supervised hass on top of RaspberryPi OS (buster).

My problem is that from time to time my RPi 4 loses WiFi connection and after reconnecting to it, it doesn’t get the internet connection back (even though I can ssh to it over WiFi). At least not until a reboot.

It’s unclear to me why it disconnects from wifi in the first place but anyways I have a cron job running every 5 minutes that restarts the NetworkManager service when connection is lost. Having restarted, it successfully reconnnects to wifi but the device won’t connect to the internet. I see nothing suspicious in syslog that could trigger the disconnect nor any errors while connecting.

The only thing I managed to diagnose is that the route is changed, and my device probably defaults to one of hass virtual networks it created, rather than using wlan0.

Before reboot

$ route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         0.0.0.0         0.0.0.0         U     207    0        0 veth47c24e9
0.0.0.0         192.168.50.1    0.0.0.0         UG    **600**    0        0 wlan0
169.254.0.0     0.0.0.0         255.255.0.0     U     207    0        0 veth47c24e9
169.254.0.0     0.0.0.0         255.255.0.0     U     209    0        0 veth66c4199
169.254.0.0     0.0.0.0         255.255.0.0     U     211    0        0 vethae8c724
169.254.0.0     0.0.0.0         255.255.0.0     U     213    0        0 veth1ee51c7
169.254.0.0     0.0.0.0         255.255.0.0     U     215    0        0 vetha757eae
169.254.0.0     0.0.0.0         255.255.0.0     U     217    0        0 veth126ec60
169.254.0.0     0.0.0.0         255.255.0.0     U     219    0        0 veth2bf023a
169.254.0.0     0.0.0.0         255.255.0.0     U     221    0        0 veth0c3cdc3
172.17.0.0      0.0.0.0         255.255.0.0     U     **0**      0        0 docker0
172.30.32.0     0.0.0.0         255.255.254.0   U     **0**      0        0 hassio
192.168.50.0    0.0.0.0         255.255.255.0   U     600    0        0 wlan0

After reboot

$ route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.50.1    0.0.0.0         UG    **0**      0        0 wlan0
0.0.0.0         0.0.0.0         0.0.0.0         U     207    0        0 veth5e60ad6
0.0.0.0         192.168.50.1    0.0.0.0         UG    600    0        0 wlan0
169.254.0.0     0.0.0.0         255.255.0.0     U     207    0        0 veth5e60ad6
169.254.0.0     0.0.0.0         255.255.0.0     U     209    0        0 veth1c8a93b
169.254.0.0     0.0.0.0         255.255.0.0     U     211    0        0 veth8a99575
169.254.0.0     0.0.0.0         255.255.0.0     U     213    0        0 veth483f273
169.254.0.0     0.0.0.0         255.255.0.0     U     215    0        0 vetha5e5c7a
169.254.0.0     0.0.0.0         255.255.0.0     U     217    0        0 vethdecaa67
169.254.0.0     0.0.0.0         255.255.0.0     U     219    0        0 vethb122bf8
169.254.0.0     0.0.0.0         255.255.0.0     U     221    0        0 veth61d0906
172.17.0.0      0.0.0.0         255.255.0.0     U     0      0        0 docker0
172.30.32.0     0.0.0.0         255.255.254.0   U     0      0        0 hassio
192.168.50.0    0.0.0.0         255.255.255.0   U     600    0        0 wlan0

I wonder if anyone could give me a hint how to debug/fix that?

1 post - 1 participant

Read full topic

So, basically this topic will be pointed to this; previous state
I was been able to put logic when binory_sensor.front_door is ‘on’ to trigger the lights. But I really want to put that light in “previous state” before automation kicks in.

So basically here is my code:

- alias: "Hallway LED Light Effect Frontdoor"
  trigger:
      platform: state
      entity_id: binary_sensor.front_door
  action:
    choose:
      - conditions:
          - condition: template
            value_template: "{{trigger.to_state.state == 'on'}}"
        sequence:
          - service: scene.create
            data:
              scene_id: hallway_led
              snapshot_entities: light.hallway_wled
          - service: light.turn_on
            data:
              color_name: green
              effect: Chase
            target:
              entity_id: light.hallway_wled
      - conditions:
          - condition: template
            value_template: "{{trigger.to_state.state == 'off'}}"
        sequence:
          - service: scene.turn_on
            data:
              entity_id: hallway_led

When I close the door, nothing happens. Light is still in this green color and effect Chase

2 posts - 2 participants

Read full topic

Hi!

Is there a way to see what movie/tvshow etc Shield is playing? Now it only shows “Netflix”, Tivimate and so on…

1 post - 1 participant

Read full topic

Hello,

my objective is to use 3 soundtouch speakers to broadcast messages via the tts command. In an automation I generate fields for the number of devices switched on, the status of the spotify player and lists for switched on/off devices. I pass those field to a script. After the tts sequence, I want to switch off those media_players, which were not on at the beginning (mediaplayer_off). This works fine with

service_template: |-
{% if count_off != 0 %}
media_player.turn_off
{% endif %}
data:
entity_id: ‘{{mediaplayer_off}}’

unless all media_players are on. Then mediaplayer_off is an empty list. I also restart spotify, if the spotify player played before with the following sequence:

service_template: |-
{% if spotify_on == true %}
media_player.media_play_pause
{% endif %}
data:
entity_id: media_player.spotify_player

If now all 3 media_players (soundtouch) are on I simply want to combine both sequences into

service_template: |-
{% if count_off != 0 %}
media_player.turn_off
{% elif spotify_on == true %}
media_player.media_play_pause
{% endif %}
data_template:
entity_id: |-
{% if count_off != 0 %}
‘{{mediaplayer_off}}’
{% elif spotify_on == true %}
media_player.spotify_player
{% endif %}

but this sequence is not executed. I tried the sequence in the developer_tools → templates and got in my opinion the right output, which would restart spotify, when all 3 mediaplayers (soundtouch) are on. Any idea, why the combination of service_template and data_template is not working?

Regards,

Volker

2 posts - 2 participants

Read full topic

Hello, I had my Dahua NVR added to HA and it had some Entities for the rules set in the DVR. In particular the Human detection rule. I noticed that I had two instances installed of the one NVR. So I deleted and reinstalled the device. Doing so removed the second device, all great there. However, no I no longer have the entity binary_sensor.rule1_field_detection_2. How can I get those entities back? Thanks

1 post - 1 participant

Read full topic

Dear Forum!

It’s a bit of a noob-question, but I’m having troubles to get two Rest-Sensors to run.
Both of them scan JSON-Data. On their own, they both work perfeclty fine and I can display the data.

But when activating both in my config.yaml, the first one (“sonnenbatterie34”) isn’t showing any new data?

config.yaml:

# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:

# Text to speech
tts:
  - platform: google_translate

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml

sensor:
  # Sonnenbatterie JSON via API V2
  # Für Vorlage siehe https://community.home-assistant.io/t/sonnenbatterie-with-apiv2-webhook/264907
  - platform: rest
    name: sonnenbatterie34
    scan_interval: 20
    resource: http://*IP*:80/api/v2/status
    headers:
      Authorization: *API-Key*
    json_attributes:
      - Apparent_output
      - BackupBuffer
      - BatteryCharging
      - BatteryDischarging
      - Consumption_W
      - Fac
      - FlowConsumptionBattery
      - FlowConsumptionGrid
      - FlowConsumptionProduction
      - FlowGridBattery
      - FlowProductionBattery
      - FlowProductionGrid
      - GridFeedIn_W
      - IsSystemInstalled
      - OperatingMode
      - Pac_total_W
      - Production_W
      - RSOC
      - Sac1
      - Sac2
      - Sac3
      - SystemStatus
      - Timestamp
      - USOC
      - Uac
      - Ubat
      - dischargeNotAllowed
      - generator_autostart
    value_template: '{{ value_json.sonnenbatterie34 }}'
  - platform: template
    sensors:
      sonnenbatterie34_apparent_output:
        friendly_name: 'Apparent_output'
        value_template: '{{ states.sensor.sonnenbatterie34.attributes["Apparent_output"] }}'
      sonnenbatterie34_backupbuffer:
        friendly_name: 'BackupBuffer'
        value_template: '{{ states.sensor.sonnenbatterie34.attributes["BackupBuffer"] }}'
      sonnenbatterie34_consumption_w:
        friendly_name: 'Verbrauch (W)'
        value_template: '{{ states.sensor.sonnenbatterie34.attributes["Consumption_W"] }}'
        unit_of_measurement: W
        device_class: power
      sonnenbatterie34_fac:
        friendly_name: 'Wechselstromfrequenz (Hz)'
        value_template: '{{ states.sensor.sonnenbatterie34.attributes["Fac"] }}'
        unit_of_measurement: Hz
      sonnenbatterie34_gridfeedin_w:
        friendly_name: 'Einspeisung (W)'
        value_template: '{{ states.sensor.sonnenbatterie34.attributes["GridFeedIn_W"] }}'
        unit_of_measurement: W
        device_class: power
      sonnenbatterie34_issysteminstalled:
        friendly_name: 'IsSystemInstalled'
        value_template: '{{ states.sensor.sonnenbatterie34.attributes["IsSystemInstalled"] }}'
      sonnenbatterie34_operatingmode:
        friendly_name: 'OperatingMode'
        value_template: '{{ states.sensor.sonnenbatterie34.attributes["OperatingMode"] }}'
      sonnenbatterie34_pac_total_w:
        friendly_name: 'Wechselrichter (W)'
        value_template: '{{ states.sensor.sonnenbatterie34.attributes["Pac_total_W"] }}'
        unit_of_measurement: W
        device_class: power
      sonnenbatterie34_production_w:
        friendly_name: 'Erzeugung (W)'
        value_template: '{{ states.sensor.sonnenbatterie34.attributes["Production_W"] }}'
        unit_of_measurement: W
        device_class: power
      sonnenbatterie34_rsoc:
        friendly_name: 'RSOC'
        value_template: '{{ states.sensor.sonnenbatterie34.attributes["RSOC"] }}'
        unit_of_measurement: '%'
      sonnenbatterie34_sac1:
        friendly_name: 'Sac1'
        value_template: '{{ states.sensor.sonnenbatterie34.attributes["Sac1"] }}'
      sonnenbatterie34_sac2:
        friendly_name: 'Sac2'
        value_template: '{{ states.sensor.sonnenbatterie34.attributes["Sac2"] }}'
      sonnenbatterie34_sac3:
        friendly_name: 'Sac3'
        value_template: '{{ states.sensor.sonnenbatterie34.attributes["Sac3"] }}'
      sonnenbatterie34_systemstatus:
        friendly_name: 'SystemStatus'
        value_template: '{{ states.sensor.sonnenbatterie34.attributes["SystemStatus"] }}'
      sonnenbatterie34_timestamp:
        friendly_name: 'Ablesedatum'
        value_template: '{{ states.sensor.sonnenbatterie34.attributes["Timestamp"] }}'
      sonnenbatterie34_usoc:
        friendly_name: 'SOC Akku'
        value_template: '{{ states.sensor.sonnenbatterie34.attributes["USOC"] }}'
        unit_of_measurement: '%'
      sonnenbatterie34_uac:
        friendly_name: 'Wechselstrom-Spannung (V)'
        value_template: '{{ states.sensor.sonnenbatterie34.attributes["Uac"] }}'
        unit_of_measurement: V
        device_class: voltage
      sonnenbatterie34_ubat:
        friendly_name: 'Batterie-Spannung (V)'
        value_template: '{{ states.sensor.sonnenbatterie34.attributes["Ubat"] }}'
        unit_of_measurement: V
        device_class: voltage

binary_sensor:
  - platform: template
    sensors:
      sonnenbatterie34_flowconsumptionbattery:
        friendly_name: 'FlowConsumptionBattery'
        value_template: '{{ states.sensor.sonnenbatterie34.attributes["FlowConsumptionBattery"] }}'
      sonnenbatterie34_flowconsumptiongrid:
        friendly_name: 'FlowConsumptionGrid'
        value_template: '{{ states.sensor.sonnenbatterie34.attributes["FlowConsumptionGrid"] }}'
      sonnenbatterie34_flowconsumptionproduction:
        friendly_name: 'FlowConsumptionProduction'
        value_template: '{{ states.sensor.sonnenbatterie34.attributes["FlowConsumptionProduction"] }}'
      sonnenbatterie34_flowgridbattery:
        friendly_name: 'FlowGridBattery'
        value_template: '{{ states.sensor.sonnenbatterie34.attributes["FlowGridBattery"] }}'
      sonnenbatterie34_flowproductionbattery:
        friendly_name: 'FlowProductionBattery'
        value_template: '{{ states.sensor.sonnenbatterie34.attributes["FlowProductionBattery"] }}'
      sonnenbatterie34_flowproductiongrid:
        friendly_name: 'FlowProductionGrid'
        value_template: '{{ states.sensor.sonnenbatterie34.attributes["FlowProductionGrid"] }}'
      sonnenbatterie34_batterycharging:
        friendly_name: 'BatteryCharging'
        value_template: '{{ states.sensor.sonnenbatterie34.attributes["BatteryCharging"] }}'
      sonnenbatterie34_batterydischarging:
        friendly_name: 'BatteryDischarging'
        value_template: '{{ states.sensor.sonnenbatterie34.attributes["BatteryDischarging"] }}'
      sonnenbatterie34_dischargenotallowed:
        friendly_name: 'dischargeNotAllowed'
        value_template: '{{ states.sensor.sonnenbatterie34.attributes["dischargeNotAllowed"] }}'
      sonnenbatterie34_generator_autostart:
        friendly_name: 'generator_autostart'
        value_template: '{{ states.sensor.sonnenbatterie34.attributes["generator_autostart"] }}'

sensor:
  # Ökofen JSON 
  - platform: rest
    name: oekofen34
    scan_interval: 20
    resource: http://*IP*:*Port*/*Secret*/all
    json_attributes:
      - system
      - weather
      - forecast
      - pe1
      - error
    #value_template: "OK"
    value_template: '{{ value_json.oekofen34 }}'
  - platform: template
    sensors:
      oekofen34_l_temp_act:
        value_template: "{{ state_attr('sensor.oekofen34', 'pe1')['L_temp_act'] | multiply(0.1) }}"
        friendly_name: 'L_temp_act'
        device_class: temperature
        unit_of_measurement: C
      oekofen34_l_temp_set:
        value_template: "{{ state_attr('sensor.oekofen34', 'pe1')['L_temp_set'] | multiply(0.1) }}"
        friendly_name: 'L_temp_set'
        device_class: temperature
        unit_of_measurement: C

If just using just one of the sensors “sonnenbatterie34” or “oekofen34” they work, togehter not.
Can you help me figuring out my mistake?

Kind regards,
gstoetti94

5 posts - 3 participants

Read full topic

Hello,
I want to realize some sort of access control using the OTP sensor. The sensor is already up and running, but now i want to have a boolean sensor which is on if the otp pin on the input text entity is correct, but off if not.
(i think of an automation or a template binary sensor, but i dont know how to do it right…)
Thanks

1 post - 1 participant

Read full topic

Hi!

I have problem with scene.create. What I found out when snapshotting entity which is climate, it doesn’t snapshot anything else than main state which is hvac_mode (cool, heat, dry, fan_only or off)

Thats ok for half of my climate automations but the another half would require the attribute of fan_mode (1,2,3,4 or 5) to be included and to be restorable.

So how I could get the state of attribute fan_mode included to scene.create snapshot?

I have tried with this manual by changing the “led strip” to my climate entity and changing xy color to fan_mode but no luck. Also I have tried to get that through Node-Red but no luck there.

I have used this JSON on Call-Service node to make the snapshots:

{"scene_id":"beforetuuletus12h","snapshot_entities":"climate.eteinen"}
and its working well but as I said it doesn’t snapshot anything else than hvac_mode.

It would be perfect to find to resolution to use with Node-Red, but if find working way through YAML that will be ok too.

Best regards
Tony

1 post - 1 participant

Read full topic

Hello,

I have a Nilan Compact P “HVAC” that speaks modbus and I am trying to integrate it with HA.

I can use the climate platform in mobus for this. This also works, but do not have access to all the functions that are available via modbus. E.g. can’t turn the unit on or off or change modes (cool, heat, auto).

So I tried to use the template platform to “build” my own HVAC.
Here, interestingly, unlike the other template integrations, the template platform is not suitable. You can only build a very simple heater from a sensor/switch, but not assign a real device to the HVAC properties.

For MQTT HVAC this seems to work, here the options I need are available. For Modbus unfortunately not.

Did I miss something, or does template somehow work differently here than for other device classes?

I haven’t found anything in HACS that can be used to implement something like this.
To push the entities provided by Modbus again via MQTT to use the MQTT HVAC cannot be really intended as a solution, I think.

Is there a trick to build your own HVAC and use service calls to set and entities to read? Thx for any help!

Sebastian

1 post - 1 participant

Read full topic

In the past I had made some updates to the upstream python library used by the integration, in order to add additional features. I am now doing the same thing to the integration component, such as supporting the new vacation arm mode. I will list other changes in another post when I get them working.

HOWEVER, I have noticed some things that are either incorrect or could lead to unexpected behavior when auditing the code.

The good:
The integration documentation lists the alarm_keypress function working on DSC and probably on Honeywell. Well, internally ALL the other functions use the keypress function to send commands to the panel, so it is definitely working. Also you can for sure send more than 6 characters at least for Honeywell panels, there does not actually seem to be a defined limit anywhere for those. An example is a zone bypass, CODE615 is the 7 character sequence to bypass zone 15, and that indeed works.

It should be mentioned the Honeywell panels expect a minimum 2 second delay between sending different sequences of commands to the panel, so if you need to toggle a connected relay, you cannot do it for less than 2 seconds, for example, a toggle of relay 11 is a set of 8 character sequences CODE#711 and CODE#811, but since they need to be different commands, the min 2s delay must be inserted before the 2nd sequence.

The bad:
alarm_trigger does not appear to send the trigger to the specified keypad for Honeywell, but rather the keypad for partition 1, this is hard coded in the library. If you are using multiple partitions, and P2 is set up for say, medical alerts, and you try to trigger it, it will trigger the alarm on P1 instead. In houses/apartments where the partitions are set up for different families or individuals, this can cause problems, potentially serious. The DSC code does not specify a partition at all, I am not sure if that is the correct behavior.

For Honeywell, the library internal partition status codes are not correct for ARMED_MAX and ARMED_INSTANT. Because of this arming MAX does not report the partition status internally at all, and arming INSTANT or NIGHT reports as ARMED_MAX. There is a similar issue in the integration code, where the night arm state is reported solely by the 0-entry delay flag being true. This will be true for MAX and INSTANT arming only, so the integration reports the wrong state 100% of the time if one of those 3 arming modes is used.

The state attribute armed_bypass actually reports the presence of a bypassed zone on Honeywell, regardless of arming status. I will submit a fix to the upstream lib to remove ‘armed_’. The DSC code does not even reference this, and I am not sure it applies.

The ugly:
the panic_type for alarm_trigger is also hardcoded in the library, but it may not match your keypad if you have Honeywell. This means if I try to trigger the default Police type, instead it triggers Fire. This is because the the trigger function in the library maps the type to a signal letter representing the A-C panic keys… and those are defined during panel program. The lib maps Fire,Ambulance,Police to A,B,C. If you need the correct trigger, send the correct keypress to the partition as a letter. DSC keypads have their panic types fixed and the library appears correct for them.

The arming code for the library function arm_night_partition is listed as 7, but this is actually the code for INSTANT arming. What this means is that if you call the function to NIGHT-STAY arm the panel, you INSTANT arm instead, and any night zones which would trigger the alarm remain unarmed. Additionally, NIGHT-STAY arming should include an entry delay, but INSTANT does not, as per its namesake referring to the 0-entry delay, so if somebody comes home at night, and they open the door… the alarm goes off immediately. The correct arming code for night mode is 33. I will also be submitting upstream fixes for this.

1 post - 1 participant

Read full topic

Hi all, in my configuration I have a LED configured like a switch.
The idea is toggle the led as far as the alarm panel is in arming state…
I am not able to do this…

Many thanks

1 post - 1 participant

Read full topic

Hi All,
I do a automation to send a notification on my iPhone to ask to turn on my coffee machine.
It was working on HA 2021.6 but since I upgrade to 2021.7 don’t get back the answer of the actionable notification.
Here is the code

alias: Coffee Machine Notification to iPhone (v2)
description: ''
trigger:
  - platform: time
    at: '12:10:00'
  - platform: time
    at: '15:20:00'
  - platform: time
    at: '18:30:00'
condition:
  - condition: zone
    entity_id: person.me
    zone: zone.home
  - condition: device
    type: is_off
    device_id: 5989f3d038c76ee1054569eb4cabaxxx
    entity_id: switch.smart_plug_2
    domain: switch
action:
  - service: notify.mobile_app_me_iphone
    data:
      message: Turn on ?
      title: Coffee machine
      data:
        actions:
          - action: COFFEE_ON
            title: 'Yes'
          - action: COFFEE_STAY_OFF
            title: 'No'
  - wait_for_trigger:
      - platform: event
        event_type: mobile_app_notification_action
        event_data:
          action: COFFEE_ON
        context:
          user_id:
            - 8f8c9dae2c704f709408b1ae3fed3xxx
    continue_on_timeout: false
    timeout: '00:00:30'
  - type: turn_on
    device_id: 5989f3d038c76ee1054569eb4cabaxxx
    entity_id: switch.smart_plug_2
    domain: switch
mode: single

Any idea why it doesn’t work anymore ?

1 post - 1 participant

Read full topic

Hi All-

Newbie here…I’ve got maybe 12 hours into my installation. I have my Ring alarm system integrated with hassio. All seems to be working well as far as motion sensors, alarm state, motion sensors, etc.

My question is that on my dashboard the door open closed states (which I think come thru Mosquito MQTT) show as safe/unsafe. Since they’re doors…I’d like them to show as closed/open.

Can I change that some how?

thanks for any advice,
-Spifl

1 post - 1 participant

Read full topic

Why utility meter won’t reset at given cycle? Why?

Here is my configuration:

basement_refrigerator_energy_daily:
  source: sensor.basement_refrigerator_power_usage_energy_power
  cycle: daily
  offset: '00:00:00'
  tariffs:
    - peak
    - offpeak

1 post - 1 participant

Read full topic

I’m trying to use events to set the state of a binary sensor showing when the doorbell detects a human, and the binary sensor should stay on until the human is no longer detected.

Here’s what I tried:

template:
  - trigger:
      -  platform: event
         id: start
         event_type: amcrest
         event_data:
           event: IntelliFrame
           payload:
             data:
               Action: Start
      - platform: event  
        id: stop       
        event_type: amcrest
        event_data:
          event: IntelliFrame
          payload:
            data:
              Action: Stop
    binary_sensor: 
      - name: Doorbell Human Detected
        state: "{% if is_state('trigger.id','start') %}on{% elif is_state('trigger.id','stop') %}off{% endif %}"

It does not work at all. I suppose it’s because I have no idea what I’m doing with templates. Any help would be greatly appreciated.

1 post - 1 participant

Read full topic