what are the entity_id’s of the piezo and the front door sensor in HA?
I’m not sure what you mean by that… The piezo is attached directly to the konnected board. On zone " out" . It gets its power directly from the board.
but does it not show up as an entity in HA? (in the dev panel)
EDIT: if you look in the dev panel you should see something like switch.konnected_door_chime or however it has been allocated by HA (I dont have experience with Konnected to know how the entities are handled by HA)
I’ve managed to get everything working fine with latest version and 0.87 after making a few edits here and there, the only thing I’m having issues with is the round buttons reset back to square after every reboot although when i enter the settings its still checked, I have to toggle it off then back on and all is good until the next reboot. any ideas??
Yeah I see the same behaviour (I have made all the code updates listed above).
Hi All,
Apologies I’ve been away for sometime. I’ve uploaded changes which should fix a lot of the compatibility issues. I’ll work my way through the issues log in the github repo. Please post issues there as they are easier to track then we can use this forum for support/advice etc.
I’m also busy working on a react version of the panel and will be looking to depreciate the polymer version as it’s too much effort to keep upto date. Everytime HA releases a new version something tends to break due to a change in polymer.
Thanks
7 Likes
You know that everytime you post after a while, we get hyped with your announcement for new features or better interface right? Dont apologize… WE thank YOU! 
1 Like
Welcome back mate
Look forward to using and testing it
How do I get the times the Activity page to display in local vice UTC time?
thanks for the updates, FYI current alarm.yaml admin password is “a”
“Failed to call service alarm_control_panel/ALARM_YAML_SAVE.” when trying to select sensors in alarm settings. Running 0.87.1
1 Like
Change your panels/alarm.html so in every t.toLocaleString call (there are 2 in there) it does not use timezone, like this:
from
return t.toLocaleString('en-GB', { timeZone: 'UTC' }).split(",")[1] + " - " + t.toLocaleString('en-GB', { timeZone: 'UTC' }).split(",")[0];
to
return t.toLocaleString('en-GB').split(",")[1] + " - " + t.toLocaleString('en-GB').split(",")[0];
and don’t forget to clear your browser(s)’ cache
there is a PR here
Thanks!!
I suppose then there is also a way to switch the date to mm-DD-yyyy vice dd-mm-yyyy in there as well?
you can try this:
replace all calls of
toLocaleString('en-GB', { timeZone: 'UTC' })
to
toLocaleString('en-US', { hour12: false })
for more info check that out
In addition to the bugs that @AhmadK mentioned, (and akasma74 on github put in PR’s for. I hope they get merged soon!)
I’m having problems writing the configuration when trying to select sensors from the frontend.
I get:
Failed to call service alarm_control_panel/ALARM_YAML_SAVE.
However, settings on the other pages do get written.
Hi.
Running Hassio 0.87.1 and latest version of the alarm. Everything seems to work fine, but in Safari (not in eg. Chrome) I keep getting an error in the log when accessing the alarm-panel:
https://mydomain.com/local/lib/jscolor.js:532:50 TypeError: undefined is not an object (evaluating 'e.path[0]')
Is this something that’s easy fixable?
It would be great if you could file a bug report on Github or at least describe how to reproduce the issue.
I tried to select a lot of sensors for all modes, and it works fine, no errors in the log.