Hi All, I got the direct link adapter and updated the 3000 board to v2.1.3 and the B426m to 3.13 but when I try to add the panel to the integration it is still only asking for hte user code not the automation passcode. Is this to be expected? How else do you know if the integration is using the Mode 2 api?
Also the update for the main board is so easy if anyone lives around northwest sydney, happy to lend the adapter.
Yes this is expected. Mode 2 only requires a user code for the solution panels.
Anyone having issues with the B426m local connection? I have updated to the latest firmware and have this weird issue where using a-link I can reliably connect to it via the cloud but not locally. If I power cycle it seems to work for a few minutes locally with alink and in HA but then quickly becomes unavailable again. Cloud and RSC+ connection remain working consistently thoughā¦
Yeah I used to have that problem, but firmware updates and updates to the integration seemed to have fixed it for the most part.
Have you updated your controller to v2.1.3?
On the occasions it happens still, I do a reset of the network module from the control panel.
The user can use the Master Code Function to reset the network module 1 or 2 remotely from the codepads. To reset the network module: ā Enter your Master Code, followed by the [9][4][1] and [#] keys to reset the network module 1. ā Enter your Master Code, followed by the [9][4][2] and [#] keys to reset the network module 2
I am wanting to get the details of which user armed/disarmed the system. Other screenshots I have seen on here show the user. e.g (2022-07-08 14:38:31 | User1 AWAY Arm). But I only get Quick Area0 Away Arm.
history_2025-03-23 12:54:02: Quick Area0 Disarm
history_2025-03-23 12:54:41: Quick Area0 AWAY Arm
history_2025-03-23 12:54:43: Quick Area0 Disarm
I have tried playing with all sorts of panel settings to no avail. Running latest integration, panel and b426-m firmware. Anybody have any ideas?
Solution 3000 panel and b426-m
Yes the firmware is updated. I think it is actually worse since I updated the firmware as I could connect locally before. The reset code you suggested doesnāt seem to do anything when I try on my keypad.
The ability to reset the network module was only added in firmware 2.1.3, maybe you arenāt actually on that version?
Solution2000 30000 RLN V02
You should have your B426M on firmware on 3.13.208 and the main alarm firmware (which can only be updated via serial interface) on 2.1.3.
Thanks for clarifying, Sanjay - much appreciated! The siren and strobe are being used by the alarm, but I can think about the option of adding another speaker to Home Assistant for the feedback.
Oh wow, I didnāt know about this. I have the same problem too, and the process I normally go through is using A-Link to connect via Cloud (as direct connect over TCP/IP fails with ācommunication errorā), disabling the panel tamper, power cycling the Solution 2000 panel and B426-M), and then after that I am able to re-connect, re-enable tamper, etc. Only then does Home Assistant show thatās itās connected again, and I get to see zone sensor conditions, etc.
It seems to happen periodically, so the next time I get into a state where Home Assistant becomes ādisconnectedā from the Solution 2000, Iāll give this a go.
Confirming Iām on 2.1.3 on the Solution 2000, and 3.13.0208 on the B426-M.
Iām having a devil of a time getting this new integration to work. Can someone PLEASE help me out.
I have successfully used the old integration for my Solution 3000 for some years but for some reason it stopped working. I then found this new integration (thank you Sanjay), downloaded it, deleted the old solution 3000 folder under custom_components.
Rebooted. There was no wizard.
It shows up in ādevicesā but only āupdate.bosch_alarm_updateā in entities.
Iām on 2.1 on the Solution 3000, and 03.10.0030 on the B426-M.
I can log in to the web interface for the B426 no problem.
Any ideas anyone please?
Ok, so i put the previous post up too soon!
Just updated to latest core 2025.4 which has Bosch Alarm included.
Installed and the wizard came up. It now works. Thanks
Thanks for the suggestion. I decided to reflash the 2.1.3 firmware. Weird because it was reporting that version before anyway but it seems to have improved things.
So far seems stable - able to connect via a-link locally and HA for more than a few minutes. Will see how it goes over a few days. I think the [9][4][1] works now? Any good way to tell if its actually resetting - no real feedback on the panel. HA does report a connection drop and reconnect (although after a few mins delay) so maybe this is it.
Connection has stabilised but since updating to lastest core with the included Bosch Alarm integration I no longer can see the sensors as entities. I have reset the network module and re-added the integration but no luck. I get 2 devices - AREA1 and Bosch Solution 3000 and only 1 entity AREA1 which enables me to arm/disarm.
Any suggestions to getting the sensors back?
I think the core integration doesnāt have as many features as the hacs component. So if you want sensors you have to remove core and add through hacs.
Thank you that makes sense! If I read the official integration page properly I should have noted that it only provides āalarm control panelā entity. I reinstalled the HACS version and everything is as before. I will stick with this for now.
the plan is to get it so the core version has the same / more features than the HACS one, but with home assistant the merging process involves doing it bit by bit hence why it doesnt have all the features yet.