Any update on the fix?
I would rollback to 69.1 till fix is out and tested
2 Likes
Ok folks, code is up on the repo.
Should only require you to update panels/alarm.html
Could you test fly this and post results please?
2 Likes
HI
Whilst it looks like it working and arming and disarming the alarm works, i get the following errors inthe log
018-05-29 21:02:51 ERROR (MainThread) [frontend.js.latest.201805264] http://10.0.0.18:8123/frontend/panels/alarm-8f550bd10f0a305e50f5934163775b21.html:364:9 Uncaught TypeError: this.async is not a function
2018-05-29 21:03:39 ERROR (MainThread) [frontend.js.latest.201805264] http://10.0.0.18:8123/frontend/panels/alarm-8f550bd10f0a305e50f5934163775b21.html:364:9 Uncaught TypeError: this.async is not a function
2018-05-29 21:03:51 ERROR (MainThread) [frontend.js.latest.201805264] http://10.0.0.18:8123/frontend/panels/alarm-8f550bd10f0a305e50f5934163775b21.html:363:60 Uncaught TypeError: this.fire is not a function
After update alarm.html VERSION: 1.1.1
Everything works perfect.
PASS: Test on raspbian stretch lite + ha 0.70.0 + rp3b
PASS: Test on raspbian stretch lite + ha 0.70.0 + rp3b+
PASS: Test on hassbian + ha 0.70.0 + rp3b
PASS: Test on hassbian + ha 0.70.0 + rp3b+
For people who got frontend.js.latest error ************
please change your javascript_version to auto / from what I read auto support more browser
frontend:
javascript_version: auto
1 Like
Thanks, it looks as though 0.70 prevents access to locking down the sidebar when armed. Will have to figure out another solution to that
For those out there using this on iOS, be advised if you change the javascript_version to “auto” then it will break again.
Updated alarm.yaml and kept javascript_version to latest and all working. I have noticed however that the temperature is no longer showing. Switched to javascript_version to auto and same.
Its no big deal but thought you should know.
Thanks for the update 
I think that is on the road map for removal anyway.
Please clear all browser cache as well. I always use javascript_version: lastest. It just broke on ios when I upgrade to 0.70.0
After a lot of read I found that javascript_version: auto supports on more browser. So I changed to javascript_version: auto and YES both on my pc and ios devices alive.
Hi,
I just updated to panel/alarm.yaml 1.1.1 on ha 0.70 and getting same errors And Weather not working.
homeassistant@HA:~/.homeassistant/panels$ cat ../home-assistant.log
2018-05-30 10:27:45 ERROR (MainThread) [frontend.js.latest.201805090] http://192.168.10.230:8123/frontend/panels/alarm-d681fb92e32d0d19f2ee11fc41a78f27.html:364:9 Uncaught TypeError: this.async is not a function
thanks in advance gazoscalvertos
Update to github
Alarm.html v1.1.2 - Sidebar issue fixed
1 Like
Trying to update to the latest version I get the following error:
Invalid config for [alarm_control_panel.bwalarm]: [armed_home] is an invalid option for [alarm_control_panel.bwalarm]. Check: alarm_control_panel.bwalarm->armed_home. (See ?, line ?). Please check the docs at https://home-assistant.io/components/alarm_control_panel.bwalarm/
Edit: reading back through the posts found @mikegrayton had the solution. A forced restart fixed it.
1 Like
Hope you can help with something. I use the alarm.com control panel. The codes on my door locks match the codes on my alarm panel. Was wondering if there was a way to pass the code used to unlock the door to the alarm panel to also disarm the alarm. I have found one solution but it isn’t code specific. It just disarms the alarm without using a code.
Sorry if this doesn’t fit in this thread but you seem to have a lot of knowledge in the area.
Thanks.
Hi Everyone,
I wanted to share a video preview of the upcoming interface and new editions to the back end:
[https://www.youtube.com/watch?v=aet7Sm7dE8M]
I’ve been working on this for quite some time and I have literally lost track of how many hours have been spent on it, literally every night (late into the night!) for a few months at least.
The breaking changes apart from the floorplan/camera/log integration is automated settings management. This new panel can configure your alarm.yaml without the need for a restart. You can literally start with a blank alarm.yml. The bugs in the vid have all been fixed.
I welcome any suggestions. I’m still working on responsiveness so that mobile/tablets layouts show as they should but hoping to have a working release soon.
I’m also considering standing up a dedicated website for guidance/advice and possibly direct support.
I also have a cracking idea of an additional add-on but would probably be chargeable. Basically using the blockchain (Same tech bitcoin works on) to write logs/config to the ledger meaning your alarm becomes non-repudiable i.e. if someone hacked your home wifi/setup they couldn’t change sensors that had been triggered within the log or manipulate your configuration remotely. This might be too high end for home but wouldn’t it be great??
As always donations are really appreciated! I did consider giving this gig up recently but I so want an alarm system anyone in the world can easily implement for free because why shouldn’t security be free??
11 Likes
I could be wrong here but looking at the spec sheet and zwave programming guide it looks as though you can’t read the user code when it’s used only the status of the lock? Have you a way to read the code via HA?
@gazoscalvertos, I used to have the locks programmed through Alarm.com. Through Alarm.com, I was able to use one of their pre-configured automations to disarm the alarm with the lock user codes. I have not figured out a way to replicate this in HA. Only thinking it can be done because of my past experience with ADC.