Yeah, though 20 seconds is crazy to me, for me its usually about 1 second or so which is usable, but of course push based is much preferred since that is instant
It might be possible to poll slightly faster, ill have to have a look
I know Bosch have released some updates for the ethernet module and the panel itself though, I wonder if any of them help at all
Appreciate your work and help here and on github. Firmware is latest, still same issue. So I just ordered a DSC board, keypad and Envisalink to replace the Bosch system.
Bosch do have a push based firmware in development which should fix this issue, but i have zero clue when that will be released.
Does this plugin work with the beta firmware that has push?
Yes, I have been working with Bosch specifically on said firmware
Will your plugin be the official plugin that Bosch is getting certified to work with Home Assistant?
Thatās the plan yes
Just added output support, and fixed the firmware version so that it reports the firmware version number instead of the protocol version number
Hi mate, hope you well. I installed the mag1024 repo and when try to add the integration it keeps on saying āPlease wait, starting configuration wizard for Bosch Alarmā for a long time and eventually shows this error " Error Config flow could not be loaded: Unknown error"
Any idea? Cheers.
Iām not really sure what would cause that, anything in your log?
Mind opening a ticket on GitHub? Itās easier to keep track of issues on there.
Hi folks, just wanted to share my experience getting this working.
I first tried about a year ago and couldnāt, eventually gave up. I recently resurrected my HA setup from scratch and am much happier AND I got the Bosch Solution 3000 working.
Setup is an intel NUC with HA running in Docker
I had a working B426 (not sure if itās -M) and RSC+ setup for about 2 years.
After setting up HA and HACS and loading the bosch integration I kept getting stuck at the āwizardā asking for host, port & RSC+ code. No matter what I entered I just got āFailed to connectā (this might not be the exact wording) and couldnāt proceed.
I eventually figured out how to enable debug msging for just HACS, by adding this to HAās configuration.yml:
logger:
default: info
logs:
custom_components.hacs: debug
aiogithubapi: debug
bosch_alarm_mode2.panel: debug
But didnāt see the reason for the connect failure. I eventually modified the local Bosch integrations source code to log the error so I could at least see if it was a timeout, a connection refused or one of the other 4 errors that cause the generic āFailed to connectā messageā¦ It was āConnection Refusedā.
I couldnāt telnet to the B426 card via its IP and port 7700 either, also āConnection Refusedā.
I eventually read that you can connect a web browser to it, but it wasnāt responding on port 80 (āConnection refusedā), however when I typed https:// it came up with a prompt āB426 Loginā. The seemingly widely known default password B42V2 worked. I didnāt see any obvious settings to enable incoming connections via 7700, and the port was 7700 (I saw this on my modems UPNP too). I found a setting called āLegacy TCP Automation Enableā and it was set to āNoā. I found some reference in a BOSCH manual that this is indeed for old automation methods, figured Iād give it a shot turning it on.
After this the B426 rebooted, and I was still able to log in via https and the default password, however the āLegacy TCP Automation Enableā setting was back to āNoā. I tried telnet to port 7700 once more, and it worked!!
I read some people here were in a similar situation and eventually gave up or bought a new B426. I donāt think the āLegacy TCP Automation Enableā setting was what fixed it, itās possibly just because the B426 rebootedā¦ I donāt know.
After this I was finally able to use the HA Bosch Alarm integration, saw it connect, and it picked up binary sensors for all my motion sensors, which I didnāt expect. Now I can view the sensor state change when people walk around in the house, this is awesome!!
Hope this helps someone, and thanks to Sanjay and anyone else who worked on this integration.
I had similar issues a few years ago but tried again. Initially I could not connect to the B426M but a reboot for the alarm brought it back up on my network. I web accessed it (https) and used the default password. I have updated the alarm unit (Solution 3000 to v2.10) and the B426M to V3.10.030 and rebooted again. Now I can use the HACS solution above and it all workes perfectly! This is awesome, I cant wait to set some automations to turn lights on as I enter rooms!
Not that i expect it to help anybody here, but AMAX support was just merged in
Just added logos and icons, both dark and light variants
Finally got mine to work - I believe I have a B426 and 3000 series alarm setup.
I can see all 5 of my zones in HA now, as well as the Area Control Panel.
However it looks like my Area Control Panel will become āUnavailableā for 30 seconds every 3 minutes. This might pose a problem if I want to construct any automation for it.
Anyone got any idea? As per the integration I have Firmware v2.0 which I believe might be outdated, but I donāt have the Direct Link Adapter tool to upgrade it 
I get these errors in the log everytime it happens:
Logger: root
Source: /usr/local/lib/python3.11/site-packages/bosch_alarm_mode2/panel.py:297
First occurred: 1:00:37 AM (4 occurrences)
Last logged: 1:11:20 AM
Connection monitor exception
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/bosch_alarm_mode2/panel.py", line 293, in _monitor_connection
await self._monitor_connection_once()
File "/usr/local/lib/python3.11/site-packages/bosch_alarm_mode2/panel.py", line 324, in _monitor_connection_once
await self._connect(load_selector)
File "/usr/local/lib/python3.11/site-packages/bosch_alarm_mode2/panel.py", line 256, in _connect
await self.load(load_selector)
File "/usr/local/lib/python3.11/site-packages/bosch_alarm_mode2/panel.py", line 181, in load
await self._load_history()
File "/usr/local/lib/python3.11/site-packages/bosch_alarm_mode2/panel.py", line 281, in _load_history
data = await self._connection.send_command(self._history_cmd, request)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Exception: ('NACK: ', 'Non-specific error')
and
Logger: bosch_alarm_mode2.panel
Source: runner.py:188
First occurred: 1:00:02 AM (4 occurrences)
Last logged: 1:10:46 AM
Heartbeat expired (0:03:02.669256): resetting connection.
Heartbeat expired (0:03:02.611324): resetting connection.
Heartbeat expired (0:03:02.627650): resetting connection.
Heartbeat expired (0:03:02.594038): resetting connection.
Can you check you have the latest firmware on your B426? That module can be updated via its web interface, so you can do that without the DLA
Yep I updated the the firmware on my B426M (found it was a 426M when i opened up the alarm) - version 03.10.0030 (May 15 2020 11:02:41)
Still having the same issue - it drops out at exactly 3 minutes for about 30 seconds and comes back and those errors are the only ones my HA logs show when I set the integration to debug mode
Dodgy cable?
