Hi guys.
Ive had this up and runnig for some time now, and only just noticed that its stopped working.
Im currently on 103.5.
So ive grabbed the latest code from github, but still not getting any luck.
This component is not working
Check the Home Assistant log for more details.
This integration: v1.11.2pre1
Home Assistant: v0.103.5
Nothing in the HA logs.
@joelones, @sh00t2kill - Iād recommend to stick to HA 0.103.0 (as this integration works fine with any HA release up to this one) unless there are reasons to update, in which case you have to disable mqtt.
Hope HA devs will fix it soon (in 0.104?) so there will be no need to create a temporary workaround for this integration.
I have downgraded for the moment ā I didn put 2 and 2 together and realise this was the same issue (as i didnt have any errors in the HA log)
Hi guys!
Iām new to home assistant and bwalarm component. Iām experimenting because I want to migrate from a zipato home automation, but one feature I canāt give up is the virtual alarm. Seems that bwalarm can help me, but actually, as I understant, it lacks of multiple partitions: I need it almost mandatory, because Iām implementing a system in a building with two flats and one common zone, that need different arming logics.
Anyone know if thereās a workoround or a fork that implement wat I need? Or, at least, if thereās a plan to add that feature in bwalarm?
Thank you guys and thanks to the componentās author!
Could you tell us more about virtual alarms and multiple partitions?
So far there is no zones and the only option is to define separate sets of sensors for Home, Away and Night modes.
The possibility of adding these features depends on how important it is for the users.
Do you know if the HA devs are aware something is wrong? Is the problem not specific to bwalarm, is that what you are saying?
To be honest, I donāt know. My suggestion was to stick to working version of HA.
@Dawnes @whyitsbob @joelones @John_Schutte @sh00t2kill do you care creating a new HA issue (as I canāt afford updating my HA instance atm)?
I think that, in a complete alarm setup for an home automation system, a zone managment and a multiple partition management features is near to be mandatory.
Especially in a bigger environment that involve separate flats or buildings alla under the same home management system.
Obviosly this is a free project and this cannot be asked, but only suggested to people that are able to contribute. 
Quick one. Is it possible to change only the name on the buttons for the Alarm Card?
So instead of āAwayā and āHomeā, it could be āInā and āOutā?
I actually moved away from Zipato to home assistant a few years ago. That is the one thing I noticed is lacking from Home Assistant. Zipato allowed you to set up multiple different alarms with each having their own alarm modes within them. This allowed people to set up letās say Apartment complexes and run the alarms all in one system.
The different zones is kinda similar to the different sensors being set up for each mode in Home assistant. The only advantage I seen in zones is reporting what area is tripping the alarm instead of sensor. This can be accomplished in home Assistant but it was more convenient with zones.
The only item I seen missing that would be nice is cross grouping between sensors. This helps prevents false alarms from triggering. All that is you would group sensors and set a time limit between them to see 8f the alarm should go off or not. For example you have two motion sensor in one room and one detects motion. With cross grouping you can set letās say 30 seconds and if that second motion sensor detects motion the alarm would trigger otherwise it would not.
@ExTrEmE @schildgenb thanks for the information.
I have to say that I donāt personally know anyone who manages separate flats or buildings using HA, itās a bit risky 
On the other hand, I know people having 2 separate objects to guard (a house and a shed/garage) and I know it can be done in theory, but cannot test it right now.
Zones and cross grouping is interesting, Iāll give it a thought.
@Yoinkz if youāre talking about native view of this integration (and not Lovelace Alarm card) then the short answer is not at the moment. Does that really make sense?
@AhmadK my case is a āclassicā: single large property with garden, 2 floor building with two flats (one mine, one my parents) and an adjacent former carpentry now a big garage deposit.
Actually Iām on zipato ad I use multiple partition for each one, with auto arming-logics, one āhealth careā parition (inverse alarm logic, silent alarm when no moves inside my parentās flat for more than certain time 
) and so on; I know itās not a real safe solution (real alarm is obviously better), but it works form my needs (accepting the risk of jamming).
I want to move away from zipato but the big lack of various vendors is exactly the virtual alarm feature. >Thanks to bwalarm, thereās something near my needs, but actually not applicable (I canāt setup a single partition for the whole building).
So for now I have to wait.
Obviously one solution could be to buy one rpi for each building portion and run an instance of hassio on each oneā¦ but in this case I should buy three aeon stick, three conbee, three rpiā¦ and three system to maintain 
Cross grouping is very useful, I can confirmā¦it can avoid many false alarms.
Zones is useful too, exactly for the same reason just exposed by @schildgenb
I see.
Still donāt quite get whatās a partition.
Is virtual alarm = multiple alarms controlled by one system?
Will have a look at their website when I have time
Yes with Zipatoās system you can have multiple alarms set up and each alarm will have its own settings and users. Thereās also multiple different types of an alarm. You would have silent alarm, battery alarm, normal alarm and health care. The silent alarm is set up the same as a normal only just only notifies you instead of setting off the sirens. The battery alarm was to notify you when a devices battery was low did not have much luck with this one working. The health care is used like mentioned above for health and safety purposes.
Will an issue for a custom integration be automatically closed though?
I created one anyway. Issue #30540.
Thanks for that. The issue for this integration wonāt be automatically closed if they close your HA one as far as I understand.
according to the documentation there is no option to change buttonsā labels.
however, there as a custom alarm panel card that might be configured (havenāt tried it myself though).
My question stands - does that change really make sense? I mean, is it valid to replace Arm Home with In and Arm Away with Out?
I understand what you mean and probably no, it doesnāt make sense to change it. In my case it it because the text-size does that the two buttons are dropping just below each other, which then pushes my card below even further down. So now I canāt see all of it on my Tablet.
But I think I got it nailed by just using the āstatesā and then only use - arm_away. That is the only state I use - so for know that will be my Fix 
Thanks for a quick reply as always!
