YET another take on an alarm system

Share your Projects!
996

hello, because of the restart problem I leave you some details. As you will see in the images there are two, one before the restart and another after restarting the raspberry. the sensors go from active to inactive.
provisionally we have been able to fix that with an automation for each mode.
type like this:

  • alias: reinicio ha modo AWAY
    trigger:
    • event: start
      platform: homeassistant
      condition:
    • condition: state
      entity_id: alarm_control_panel.house
      state: ‘armed_away’
      action:
    • service: alarm_control_panel.alarm_disarm
    • delay: 00:00:03
    • alias: ‘’
      service: alarm_control_panel.alarm_arm_away!
      the first photo is after the restart and the second before the restart
      image
      image1242×2208 146 KB
      image
      image1242×2208 153 KB
997

I have the same issue and it’s utterly annoying, I have tried everything and then I give up for a couple of months. I am at it again today but man…heh

998

So does Lovelace change everything and push back the release date?

2 Likes
999

For some reason I keep getting errors that point to line 175 of the alarm.html.

	updateTime(hass){
		if (this.alarm.attributes.clock){
			this.time = this.hass.states['sensor.time'];
			if (this.time == null){
				this.error("Time Sensor (sensor.time) not found in HA");

It says that there is a problem with this.alarm and that it is undefined.
“TypeError: this.alarm is undefined 175:1”

I cleared cache in the browsers I tested, updated to the latest alarm.html but still getting the same error.

I feel like I’ve come so far to just pull the plug on the whole thing and give up.

Any help would be greatly appreciated

1000

You need to have date and time sensor in HA so that it can be display in your alarm system.

1001

Do I add this to alarm.yaml or configuration.yaml? I have this in configuration.yaml, currently.

1002

reading the time&date link you were provided it says:
To enable this sensor in your installation, add the following to your configuration.yaml file:

I think it should go in your configuration.yaml unless you have a separate sensor.yaml file where you have all your sensors then i would put it there.

1 Like
1003

add to configuration.yaml under sensor platform, can be individual file if you have sensor.yaml then the alarm will read from ha

1 Like
1004

Ok so I have it in the right place then, spelling correct as provided.

1005

I have had this in the configuration.yaml file for almost a month now, but I still get the error

1006

check from entity_id page that you have sensor.time

or hide the clock in alarm.yaml
clock: False

1007

I can confirm that I do have sensor.time as a listed entity

1008

Try left the clock: False and see if the the alarm system works.

1009

I set the clock to false but the error remains

1010

check what is the error.

1011

The error that pops up says Service system_log/write called.

The console says: TypeError: this.alarm is undefined

1012

Is there somewhere specific you would like me to look?

1013

What browser do you use. Did you put javascript_version: latest on your frontend setting in configuration.yaml

Also when do any change or setting to HA. check config and restart your ha to take effect.

1014

Ok I use Firefox, but tested IE, Chrome, and Edge. Cleared cookies and cache in each, I have javascript_version: latest in the frontend, and I have restarted hass.io and the raspberry pi itself, but the error remains

1015

@gazoscalvertos
I got a bug here. Tell me if it is only me or if anyone can reproduce this:

  1. Arm the alarm (home or away mode)
  2. Restart HA (not raspberry, just HA)
  3. Open any door/window
    Unfortunately the alarm wont trigger. Yea, the state is the same (armed) when HA starts again, but it wont trigger. There are no errors in HA however…
1 Like