So does that mean the only way you’d ever see “ac_present” as true would be if you lost power and it was restored?
I wonder if it’d be saner to start assuming AC is present if it can’t be requested.
Yes that’s true- you’re right. It probably would be in this case.
Can I put these in the same mqtt.yaml file or what the right format. every time I do HA does not start and what about this “- platform:owntracks”
mqtt: local
broker: 127.0.0.1
port: 1883
client_id: home-assistant-1
username: pi
password: raspberry
mqtt: tracking
broker xxx.cloudmqtt.com
port:18315
client_id:Bobby Cell
keepalive:60
username:user
password:password
Indentation matters, so when you post, be sure to use a pre-formatted text block.
But that doesn’t look like the right formatting for MQTT.
I think it might be best to start a separate thread for help on that.
Has anyone tested out the alarm_trigger service to make a panic alarm with DSC alarm?
If I call it on mine it goes into panic but then immediately shows ‘Panic alarm cleared’ as the alpha.
I’ll research it more if anyone else is able to replicate, potentially something to do with my panel setup though.
I was able to trigger mine just now. It ran till I disabled it at the alarm panel. Here’s the log in case you want to see something.
16-10-24 21:06:42 homeassistant.components.envisalink: Envisalink sent a zone update event. Updating zones…
16-10-24 21:06:42 homeassistant.core: Bus:Handling <Event state_changed[L]: entity_id=binary_sensor.family_room_motion, new_state=<state binary_sensor.family_room_motion=off; last_tripped_time=230, sensor_class=motion, friendly_name=Family Room Motion @ 2016-10-24T21:06:42.384352-05:00>, old_state=<state binary_sensor.family_room_motion=on; last_tripped_time=230, sensor_class=motion, friendly_name=Family Room Motion @ 2016-10-24T21:06:37.383906-05:00>>
16-10-24 21:06:43 homeassistant.components.envisalink: Envisalink sent a zone update event. Updating zones…
16-10-24 21:06:43 homeassistant.core: Bus:Handling <Event state_changed[L]: entity_id=binary_sensor.front_door, new_state=<state binary_sensor.front_door=off; last_tripped_time=6545, sensor_class=opening, friendly_name=Front Door @ 2016-10-24T20:07:45.104737-05:00>, old_state=<state binary_sensor.front_door=off; last_tripped_time=6515, sensor_class=opening, friendly_name=Front Door @ 2016-10-24T20:07:45.104737-05:00>>
16-10-24 21:06:43 homeassistant.core: Bus:Handling <Event state_changed[L]: entity_id=binary_sensor.patio_door, new_state=<state binary_sensor.patio_door=off; last_tripped_time=5230, sensor_class=opening, friendly_name=Patio Door @ 2016-10-24T20:07:45.124361-05:00>, old_state=<state binary_sensor.patio_door=off; last_tripped_time=5200, sensor_class=opening, friendly_name=Patio Door @ 2016-10-24T20:07:45.124361-05:00>>
16-10-24 21:06:43 homeassistant.core: Bus:Handling <Event state_changed[L]: entity_id=binary_sensor.garage_entry, new_state=<state binary_sensor.garage_entry=off; last_tripped_time=6935, sensor_class=opening, friendly_name=Garage Entry @ 2016-10-24T20:07:45.114698-05:00>, old_state=<state binary_sensor.garage_entry=off; last_tripped_time=6905, sensor_class=opening, friendly_name=Garage Entry @ 2016-10-24T20:07:45.114698-05:00>>
16-10-24 21:06:43 homeassistant.core: Bus:Handling <Event state_changed[L]: entity_id=binary_sensor.family_room_motion, new_state=<state binary_sensor.family_room_motion=on; last_tripped_time=15, sensor_class=motion, friendly_name=Family Room Motion @ 2016-10-24T21:06:43.446611-05:00>, old_state=<state binary_sensor.family_room_motion=off; last_tripped_time=230, sensor_class=motion, friendly_name=Family Room Motion @ 2016-10-24T21:06:42.384352-05:00>>
16-10-24 21:06:48 homeassistant.components.http: Serving /api/bootstrap to 192.168.100.100 (auth: True)
16-10-24 21:06:49 homeassistant.components.http: Serving /api/stream to 192.168.100.100 (auth: True)
16-10-24 21:07:04 homeassistant.components.http: Serving /api/services/alarm_control_panel/alarm_trigger to 192.168.100.100 (auth: True)
16-10-24 21:07:04 homeassistant.core: Bus:Handling <Event call_service[L]: service_call_id=1978271536-47, domain=alarm_control_panel, service_data=, service=alarm_trigger>
16-10-24 21:07:04 homeassistant.core: Bus:Handling <Event service_executed[L]: service_call_id=1978271536-47>
16-10-24 21:07:05 homeassistant.components.envisalink: Envisalink sent new alarm info. Updating alarms…
16-10-24 21:07:05 homeassistant.components.envisalink: The envisalink sent a partition update event.
16-10-24 21:07:05 homeassistant.components.envisalink: Envisalink sent new alarm info. Updating alarms…
16-10-24 21:07:05 homeassistant.core: Bus:Handling <Event state_changed[L]: entity_id=sensor.home_alarm_keypad, new_state=<state sensor.home_alarm_keypad=Panic Alarm Cleared; armed_stay=False, armed_away=False, friendly_name=Home Alarm Keypad, ready=False, ac_present=False, exit_delay=False, alpha=Panic Alarm Cleared, alarm_in_memory=False, bat_trouble=False, alarm=False, armed_bypass=False, beep=False, entry_delay=False, chime=False, alarm_fire_zone=False, fire=False, icon=mdi:alarm, armed_zero_entry_delay=False, trouble=False @ 2016-10-24T21:07:05.402458-05:00>, old_state=<state sensor.home_alarm_keypad=Not Ready; armed_stay=False, armed_away=False, friendly_name=Home Alarm Keypad, ready=False, ac_present=False, exit_delay=False, alpha=Not Ready, alarm_in_memory=False, bat_trouble=False, alarm=False, armed_bypass=False, beep=False, entry_delay=False, chime=False, alarm_fire_zone=False, fire=False, icon=mdi:alarm, armed_zero_entry_delay=False, trouble=False @ 2016-10-24T20:20:59.626373-05:00>>
16-10-24 21:07:05 homeassistant.components.automation: Executing Alert Kodi from Alarm
16-10-24 21:07:05 homeassistant.core: Bus:Handling <Event logbook_entry[L]: message=has been triggered, domain=automation, name=Alert Kodi from Alarm, entity_id=automation.alert_kodi_from_alarm>
16-10-24 21:07:05 homeassistant.helpers.script: Script Alert Kodi from Alarm: Running script
16-10-24 21:07:05 homeassistant.helpers.script: Script Alert Kodi from Alarm: Executing step call service
16-10-24 21:07:05 homeassistant.core: Bus:Handling <Event call_service[L]: service_call_id=1978271536-48, domain=notify, service_data=message=One of your Security Sensors was activated !, data=displaytime=20000, icon=warni ng, title=Home Assistant, service=kodi_htpc>
16-10-24 21:07:05 homeassistant.core: Bus:Handling <Event state_changed[L]: entity_id=automation.alert_kodi_from_alarm, new_state=<state automation.alert_kodi_from_alarm=on; friendly_name=Alert Kodi from Alarm, last_triggered=2016-10-24T21:07:05.440264-05:00 @ 2016-10-24T20:07:48.643410-05:00>, old_state=<state automation.alert_kodi_from_alarm=on; friendly_name=Alert Kodi from Alarm, last_triggered=2016-10-24T20:20:59.662667-05:00 @ 2016-10-24T20:07:48.643410-05:00>>
16-10-24 21:07:05 homeassistant.core: Bus:Handling <Event service_executed[L]: service_call_id=1978271536-48>
16-10-24 21:07:05 homeassistant.helpers.script: Script Alert Kodi from Alarm: Executing step call service
16-10-24 21:07:05 homeassistant.core: Bus:Handling <Event call_service[L]: service_call_id=1978271536-49, domain=media_player, service_data=message=One of your Security Sensors was activated !, data=displaytime=20000, icon=warning, title=Home Assistant, service=kodifamily_room_tv>
16-10-24 21:07:05 homeassistant.core: Unable to find service media_player/kodifamily_room_tv
16-10-24 21:07:07 homeassistant.components.http: Serving /api/history/period to 192.168.100.100 (auth: True)
16-10-24 21:07:13 homeassistant.components.envisalink: Envisalink sent a zone update event. Updating zones…
16-10-24 21:07:13 homeassistant.core: Bus:Handling <Event state_changed[L]: entity_id=binary_sensor.front_door, new_state=<state binary_sensor.front_door=off; last_tripped_time=6575, sensor_class=opening, friendly_name=Front Door @ 2016-10-24T20:07:45.104737-05:00>, old_state=<state binary_sensor.front_door=off; last_tripped_time=6545, sensor_class=opening, friendly_name=Front Door @ 2016-10-24T20:07:45.104737-05:00>>
16-10-24 21:07:13 homeassistant.core: Bus:Handling <Event state_changed[L]: entity_id=binary_sensor.patio_door, new_state=<state binary_sensor.patio_door=off; last_tripped_time=5260, sensor_class=opening, friendly_name=Patio Door @ 2016-10-24T20:07:45.124361-05:00>, old_state=<state binary_sensor.patio_door=off; last_tripped_time=5230, sensor_class=opening, friendly_name=Patio Door @ 2016-10-24T20:07:45.124361-05:00>>
16-10-24 21:07:13 homeassistant.core: Bus:Handling <Event state_changed[L]: entity_id=binary_sensor.garage_entry, new_state=<state binary_sensor.garage_entry=off; last_tripped_time=6965, sensor_class=opening, friendly_name=Garage Entry @ 2016-10-24T20:07:45.114698-05:00>, old_state=<state binary_sensor.garage_entry=off; last_tripped_time=6935, sensor_class=opening, friendly_name=Garage Entry @ 2016-10-24T20:07:45.114698-05:00>>
16-10-24 21:07:13 homeassistant.core: Bus:Handling <Event state_changed[L]: entity_id=binary_sensor.family_room_motion, new_state=<state binary_sensor.family_room_motion=off; last_tripped_time=45, sensor_class=motion, friendly_name=Family Room Motion @ 2016-10-24T21:07:13.439508-05:00>, old_state=<state binary_sensor.family_room_motion=on; last_tripped_time=15, sensor_class=motion, friendly_name=Family Room Motion @ 2016-10-24T21:06:43.446611-05:00>>
16-10-24 21:07:15 homeassistant.helpers.script: Script Alert Kodi from Alarm: Executing step call service
16-10-24 21:07:15 homeassistant.core: Bus:Handling <Event call_service[L]: service_call_id=1978271536-50, domain=media_player, service_data=message=One of your Security Sensors was activated !, data=displaytime=20000, icon=warning, title=Home Assistant, service=kodigame_room_tv>
16-10-24 21:07:15 homeassistant.core: Unable to find service media_player/kodigame_room_tv
16-10-24 21:07:20 homeassistant.components.envisalink: The envisalink sent a partition update event.
16-10-24 21:07:20 homeassistant.core: Bus:Handling <Event state_changed[L]: entity_id=sensor.home_alarm_keypad, new_state=<state sensor.home_alarm_keypad=Not Ready; armed_stay=False, armed_away=False, friendly_name=Home Alarm Keypad, ready=False, ac_present=False, exit_delay=False, alpha=Not Ready, alarm_in_memory=False, bat_trouble=False, alarm=False, armed_bypass=False, beep=False, entry_delay=False, chime=False, alarm_fire_zone=False, fire=False, icon=mdi:alarm, armed_zero_entry_delay=False, trouble=False @ 2016-10-24T21:07:20.390069-05:00>, old_state=<state sensor.home_alarm_keypad=Panic Alarm Cleared; armed_stay=False, armed_away=False, friendly_name=Home Alarm Keypad, ready=False, ac_present=False, exit_delay=False, alpha=Panic Alarm Cleared, alarm_in_memory=False, bat_trouble=False, alarm=False, armed_bypass=False, beep=False, entry_delay=False, chime=False, alarm_fire_zone=False, fire=False, icon=mdi:alarm, armed_zero_entry_delay=False, trouble=False @ 2016-10-24T21:07:05.402458-05:00>>
16-10-24 21:07:20 homeassistant.components.automation: Executing Alert Kodi from Alarm
16-10-24 21:07:20 homeassistant.core: Bus:Handling <Event logbook_entry[L]: message=has been triggered, domain=automation, name=Alert Kodi from Alarm, entity_id=automation.alert_kodi_from_alarm>
16-10-24 21:07:20 homeassistant.helpers.script: Script Alert Kodi from Alarm: Executing step call service
16-10-24 21:07:20 homeassistant.core: Bus:Handling <Event call_service[L]: service_call_id=1978271536-51, domain=notify, service_data=message=One of your Security Sensors was activated !, data=displaytime=20000, icon=warni ng, title=Home Assistant, service=kodi_htpc>
16-10-24 21:07:20 homeassistant.core: Bus:Handling <Event state_changed[L]: entity_id=automation.alert_kodi_from_alarm, new_state=<state automation.alert_kodi_from_alarm=on; friendly_name=Alert Kodi from Alarm, last_triggered=2016-10-24T21:07:20.420047-05:00 @ 2016-10-24T20:07:48.643410-05:00>, old_state=<state automation.alert_kodi_from_alarm=on; friendly_name=Alert Kodi from Alarm, last_triggered=2016-10-24T21:07:05.440264-05:00 @ 2016-10-24T20:07:48.643410-05:00>>
16-10-24 21:07:20 homeassistant.core: Bus:Handling <Event service_executed[L]: service_call_id=1978271536-51>
16-10-24 21:07:20 homeassistant.helpers.script: Script Alert Kodi from Alarm: Executing step call service
16-10-24 21:07:20 homeassistant.core: Bus:Handling <Event call_service[L]: service_call_id=1978271536-52, domain=media_player, service_data=message=One of your Security Sensors was activated !, data=displaytime=20000, icon=warning, title=Home Assistant, service=kodifamily_room_tv>
16-10-24 21:07:20 homeassistant.core: Unable to find service media_player/kodifamily_room_tv
16-10-24 21:07:30 homeassistant.helpers.script: Script Alert Kodi from Alarm: Executing step call service
16-10-24 21:07:30 homeassistant.core: Bus:Handling <Event call_service[L]: service_call_id=1978271536-53, domain=media_player, service_data=message=One of your Security Sensors was activated !, data=displaytime=20000, icon=warning, title=Home Assistant, service=kodigame_room_tv>
16-10-24 21:07:30 homeassistant.core: Unable to find service media_player/kodigame_room_tv
16-10-24 21:07:30 homeassistant.core: Bus:Handling <Event state_changed[L]: entity_id=sun.sun, new_state=<state sun.sun=below_horizon; azimuth=275.52, next_setting=2016-10-25T23:42:01+00:00, friendly_name=Sun, next_rising=2016-10-25T12:40:26+00:00, elevation=-30.84 @ 2016-10-24T20:07:40.903607-05:00>, old_state=<state sun.sun=below_horizon; azimuth=275.37, next_setting=2016-10-25T23:42:01+00:00, friendly_name=Sun, next_rising=2016-10-25T12:40:26+00:00, elevation=-30.63 @ 2016-10-24T20:07:40.903607-05:00>>
Thanks for that, I won’t worry about mine cancelling then (it isn’t a feature I’m planning to use just yet anyway) - I haven’t tried triggering panic from the keypad it is possible it has been disabled or something funny.
Not sure if you’ve seen the new PR to make sure I don’t break anything - https://github.com/home-assistant/home-assistant/pull/3932
I’ve added the alarm_keypress to the manual alarm and setup tests in the hope they will approve that to be added as a service, it would be pointless to try and do the output_control service on the manual alarm so if they do require tests for it I’ll just pull that service out use the alarm_keypress instead.
Have modified the arm method so from the UI you just click arm or disarm and it will do so using the code from configuration, based on @sriram 's changes; but there is the option to specify a different code for the service calls. Is that OK? Otherwise we might need to make the setting user configurable.
stuck on this message after the last update everytime i restart HASS
INFO:pyenvisalink.envisalink_base_client:An event loop was given to us- we will shutdown when that event loop shuts down
any ideas
Sorry it’s been a crazy week- sure yeah that’s fine. I think i was outside the norm with how i was returning the code itself in that method- so I have no problems with the change.
1 Like
Hi-
Yeah don’t worry about that. It just means that the pyenvisalink library is acting as a “slave” to the home-assistant asynchronous event loop. It’s waiting for other HASS processes to finish.
Yeah Privatesam had also reported positive feedback on the alarm_trigger service, so perhaps it’s a configuration thing on the DSC side.
@ih8gates or anyone else, is there a way to give a guest a code to only work for a week when someone is visiting you? for example, 10/30/2016 to 11/05/2016.?
Not automated. My DSC can have a lot of users (99?), though. So it’s no big deal to add one, then remove it.
You’d have to write python that would send the correct keypresses to create/delete the user code. Look at the python script to arm/disarm, then modify that.
Service for sending key presses has been implemented and currently sitting in a pull request to be incorporated 
notify:
- name: Bobby_alarmAway
platform: pushbullet
api_key: xxxxxxxxxxxxxxxxxxxxxxxxxx
I put this in my config.yaml file, and I copied the example code to notify when disarm but I am not getting any alerts message on pushbullet any help? Thanks
and i have this
- alias: Alarm Armed Away
trigger:
- platform: state
entity_id: sensor.home_alarm_keypad
state: ‘Arm Away’
action:
- service: notify.Bobby_alarmAway
data:
message: “Alarm Armed Away”
title: “Alarm”
I have the Pushbullet app on my phone and I can send a txt from my phone and it will show up when I log into the Pushbullet website so I guess the API is working
Be sure to use preformatted text when posting configs. Makes the code easier to read and shows indentation. Here’s what I use. Make sure you’ve got the correct entity_id by checking your states dev tool
- alias: Alarm Armed Away
trigger:
- platform: state
entity_id: sensor.home_alarm_keypad
state: 'Arm Away'
action:
- service: notify.scott_notifier
data:
message: "Alarm Armed Away"
title: "Alarm"
Also - you’ve tested your Pushbullet notifications independently (use the services dev tab).
The code that you use is the same code I used… I copy it from this forum and paste into my automation.yaml file…
the only thing I change is this “- service: notify.scott_notifier”
to mines “- service: notify.Bobby_alarmAway”