I was also having blank alarm panel on web but had alarm panel on mobile. I downloaded the /custom_components/bwalarm folder from GitHub replaced the existing /bwalarm in HA and now have a working panel on both web and mobile. However, I am not able to make any changes on the settings page of the alarm panel. When changing tabs in the settings page, it stays on the about tab.
I canāt for the life of me get this integration sorted. I had the original custom alarm setup at one point, but never really used it. Recently I went to use it, and noticed it broken. I went to the github and looked through the issues to see that the integration and forked and had been updated there. I downloaded and replaced all the files and changed the config. This is what Iām getting:
Could you please open a new issue here as this topic is not for reporting problems?
I take you just replaced files of your original alarm with ones from my Github?
If so, it wonāt work, please read installation instructions first.
Iād recommend to remove the old stuff and install it from scratch and then configure (you can reuse parts of your alarm.yaml if you want, just save it somewhere safe).
I removed everything, reinstall and settings is still not accessible. I will open a new issue, I only posted here because I saw other people discussing it.
I only use the side panel for controlling the arm/disarm state ( and adjusting alarm settings) other than the link with my hardwired alarm (see next point). I donāt use a Lovelace alarm card at all. The reason this side panel was created (aside from being the only way to control things in the beginning of this component) is that you can (at least could previously) make it such that the side panel was the only screen the user would have access to if the alarm was armed (this was an optional feature) and then once the alarm was disarmed the rest of the HA GUI would be available. It was a way of locking the interface if armed.
I do use the MQTT functionality heavily, as it keeps HA synchronised with my hard-wired alarm system.
Thanks for keeping this component going, itās awesome.
That answer was to another person but yes, please do that and provide as much info about the component and_what_ and how you did so I could reproduce it.
I think I now know how to do this. But Iād need access to the information which is possibly just internal to the alarm system: what has tripped the alarm.
Iāve installed the HACS integration āvariableā and my plan was to compare a sensor turning on against a stored variable, which would = the sensor which originally tripped the alarm.
Thanks for this. The point is as outlined above. But to give you a use case, last night my alarm went off erroneously twice, at 4.18 and 5.13am. I have three theories.
Faulty Xiaomi PIR (which has worked flawlessly for a year hitherto)
Low battery on Xiaomi PIR causing false positives?
Android tablet screen in kitchen turning on erroneously in an otherwise pitch dark kitchen causing a false positive.
I got notified on each occasion which was a bit scary. I want to instead only get notified (and woken) if TWO sensors are tripped within quick succession of each other.
How about using Bayesian sensor (havenāt used it yet but people use it exactly for that)?
collect statistics and then get rid of the faulty one if confirmed.
monitor batteries on a regular basis to avoid it
Are we talking about Passive InfraRed sensors?
By the way, the changed_by attribute wonāt help you if you hoped to capture its change after the alarm is tripped as I intentionally stop updating it when it happens to see what triggered the alarm.
Itās a thought, certainly. Iāll have a look through the forum for config ideas.
Yep, will be doing this.
Impossible without taking out the battery as the sensors donāt report any useful (read: reliable) battery info by telemetry, but something Iāll have to look into!
Are we talking about Passive InfraRed sensors? We are.
Thanks, good tip, but actually that should be OK as Iāll use regular automations and regular sensors to compare the captured variable against further developments!
Well, I have an automation that notifies me if a sensor _did not send a reading within a given interval (24hrs for PIRs). That way I know it has low batteries/out of RF range/broken.
it doesnāt go well with
as screens should not normally emit any tangible IR
Iāll freely admit Iām not an expert on this, but isnāt that a fundamental misunderstanding of what a PIR sensor does?
Since the primary source of infrared radiation is heat or thermal radiation , any object which has a temperature radiates in the infrared . Even objects that we think of as being very cold, such as an ice cube, emit infrared The warmer the object , the more infrared radiation it emits
Perhaps my forum search failing me, but I failed to find anyone reporting use of a bayesian sensor to help stop false positives.
Donāt limit yourself by this forum and āfalse positivesā - itās a more universal sensor (1 and 2). Have to admit it might be heavy lifting for someā¦ well, another option is to create a template binary sensor that does the job for less.
Hope you get the idea. PM me your non-working config if you get stuck
Thanks. Iām familiar with the concept and the principles, I just dislike the inevitable fine tuning I know lies in wait for me with a Bayesian sensor. I donāt like the āgreyā that exists with such sensors, preferring the binary nature of an on/off sensor!
Anyway the kitchen PIR is going nuts today. Itās either suddenly gone faulty, has a low battery or itās the tablet. Going to investigate which! Thanks