To get what to display correctly?
The adding sensor panel.
How can I change the size of the button panel? I am using a Fire 8" and I cannot seem ot get the whole thing in view. I am using the Fully Kiosk Browser.
I am getting multiple errors when i have updated to 82.1 and the latest version on github
2018-11-27 19:02:54 ERROR (MainThread) [frontend.js.latest.201811033] https://www.m.org/api/panel_custom/alarm:2196:24 Uncaught TypeError: Cannot read property ‘attributes’ of undefined
2018-11-27 19:02:57 ERROR (MainThread) [frontend.js.latest.201811033] https://www.m.org/api/panel_custom/alarm:1991:37 Uncaught TypeError: Cannot read property ‘classList’ of undefined
Thanks @tom_l
New code uploaded to repo.
- Fixed the display issue whereby the settings were being chopped at the bottom in firefox
- Have replaced the polymer checkbox with a custom one as I also was having random issues with it appearing. I believe this is due to the checkbox element not being used by HA.
- Sensors in settings sorted alphabetically
- Shadow text effects, clock, weather basically all true/false settings now work correctly including after reboot
- The sensor panel shows as all sensors when disarm, it will show in the groups when in an armed or arming state. Can you confirm this is the case for you?
- I have updated the readme on the repo with the additional instructions. The plan is to overhaul this at some point and include images possible a video setup
1 Like
I have: defined in one of my groups. Clicking on this sensor allows arming and disarming without entering a code.> I have “Require a code to set the alarm” off in alarm settings but this should still require a code to disarm (as it does require in the side panel).
I cannot seem to replicate this issue. Anychance you could provide some screenshots or video?
Also the following script now goes through the arming delay, where as with the old component it armed instantly:
I’ll update the readme. To override the code you need to pass the value ‘override’ as the code
Can you provide a screenshot mate? Getting the responsiveness just right is a bit tricky. I’ll take a look at the resolution of the 8"
Thanks for the headsup I’ll check this out
Aaah I see your using it in landscape mode. Ok I’ll need to change a few things to account for a smaller screen in landscape.
Just updated, no issues to report
Yep I can now see the whole “new” button. Is there a way to set the backend theme yet? As my theme changes depending on the time of day.
Yep all good.
I’ve actually decided I like the alarm warning. It gives me a chance to cancel it with ios actionable notifications if my auto arm automation goes awry.
The arm code I set originally was not in the alarm.yaml file. I added it again and now all is almost well.
I have code_to_arm: false
From your side pane interface I can arm without a code and have to enter a code to disarm. All as expected.
From the HA sensor pop up I have to enter a code to arm and disarm. I expect this may be beyond your control though.
Been using the NEWUI branch for months, worked perfectly.
Just updated to the new Master branch, however I have problems with the component not loading after configuring it via the ui.
I start with an almost empty alarm.yaml
a few things:
- checkboxes don’t appear, but when I click the sensor names it still works (gets written to alarm.yaml)
- after that, a restart of home-assistant results in a non-functioning alarm.
errors:
http://10.0.0.181:8123/api/panel_custom/alarm:2059:42 Uncaught TypeError: Cannot read property 'state' of undefined
EDIT: I seem to have narrowed it down to the persistence setting. After deleting the old json file everything works again!
1 Like
Hi All,
Today I updated my HA@RPi3 to the latest version and then decided to update this alarm panel (was using an older version from March).
I take it that there is no easy way to upgrade and I have to go to the Settings and configure everything using GUI… oh, well.
Currently the main problem I have is it displays only one binary_sensor that I can use as a trigger in Sensors pane. My other sensors (mostly RFLink switches) are not there.
I tried to restart HA, clear Chrome’s cache - no luck, seems like it’s by design.
So is there a way to use RFLink switches with the current version of this alarm panel?
Yeah the GUI shows sensors not switches.
Set up everything else via the GUI then try defining your switches as sensors in the alarm.yaml file manually. Untested. Not sure if this will work.
That kind of sucks… a bit harsh on users to remove working functionality without offering an alternative.
Have to figure out how to define my switches as the old alarm.yaml isn’t working anymore :\
Oh well, I’m not moaning…
Ask Gaz to re-include the functionality. Until then…
As I said, use the GUI to set up a new alarm.yaml file for everything except the sensors. Then try adding the switches to the yaml file manually.
The new format looks like this:
platform: bwalarm
name: House
panel:
cameras:
- camera.rear
- camera.front
enable_clock: true
hide_passcode: true
hide_sidebar: true
round_buttons: false
enable_sensors_panel: true
enable_camera_panel: true
camera_update_interval: '5'
shadow_effect: false
states:
armed_away:
immediate:
- binary_sensor.pir_bathroom ### add your switches in these sections ####
- binary_sensor.pir_dining
- binary_sensor.pir_ensuite
- binary_sensor.pir_hall
- binary_sensor.pir_laundry
- binary_sensor.pir_master_bedroom
- binary_sensor.pir_spare_bedroom
- binary_sensor.pir_study
- binary_sensor.pir_wardrobe
- binary_sensor.pir_workshop
delayed:
- binary_sensor.pir_entry
- binary_sensor.pir_rumpus
- binary_sensor.pir_lounge
override: []
pending_time: 20
warning_time: 20
trigger_time: 180
armed_home:
immediate: []
delayed:
- binary_sensor.pir_laundry
- binary_sensor.pir_rumpus
- binary_sensor.pir_study
- binary_sensor.pir_workshop
override: []
pending_time: 0
warning_time: 0
trigger_time: 60
armed_perimeter:
immediate: []
delayed: []
override: []
pending_time: 0
warning_time: 0
trigger_time: 600
users:
Thanks for your help.
Now I have a working alarm with the sensors hooked.
Good job the author and everyone who committed to this amazing project.
There are some glitches though, or at least it looks strange:
- Unless one changes Pending Time for Away mode, for example, it goes to Away mode immediately after the Away button is pressed. Looking at the GUI description, I assumed it’s 25 by default. confusing!
- The keypad panel looks differently in my desktop browser (with Clear/Disarm buttons to the right) and on my Android phone (with C and a fingerprint buttons at the bottom) - is that as it supposed to be?
- If one enters nothing and just clicks Disarm button, the alarm treats it as a Wrong code (according to the log file) - don’t think it should do that, probably it’s reasonable to react on Disarm button only if there is some code entered. And the worst bit is it resets countdown, so one can just keep on pressing that button and the alarm won’t go off.
- In Activity pane I can see : tripped by Sensor: and nothing else - definitely a bug here.
- Sensors on a corresponding pane are not sorted alphabetically (despite a statement in alarm.html)
Could anyone clarify what the Home mode is exactly?
p.s love the colours of my old alarm panel, hope it’s easy to change the current ones to something similar.
1 Like