Ok, after way too much effort, I have my fork compiled into a bin file and downloaded into my OHS2. For about 45 minutes I tried driver updates and all kinds of things only to find out my long usb cable was power only. I then found a 6 inch cable and had to hold everything in my hands while trying to update. Needless to say…. I now have auto discovery buttons.
I am still not connecting to the MQTT broker, so it is still not working right. But now at least I have the latest firmware.
I am having trouble getting MQTT to work. I keep getting:
2024-11-13 10:11:26: New connection from 192.xxx.x.x:52610 on port 1883.
2024-11-13 10:11:26: Client OHS2 disconnected, not authorised.
The x’s are actually numbers I removed…. But they were the correct IP address for my OHS2
I have my OHS2 in a dedicated subnet and my HA is in another subnet. I allowed MQTT ports in both directions…
I changed the settings to allow remote access…. Nothing.
I changed passwords a few times…. Nothing.
Opened all ports between the two pi addresses…. Nothing
I followed multiple tutorials on setting HA MQTT using Mosquitto …. Multiple times.
I updated the firmware last night to my 56 zones fork…. Now I see MQTT auto-discovery options in my settings, but still no connection to the broker.
HA appear as to be connecting fine. I can see another IP address connecting that appears to be the Docker Container from HA. At least that is what I concluded doing a WHOIS on the IP address. That IP is listed as a 172.xx.xx.x
I have certificates turned off. All that is running is the default settings but with a username and password. I can see the HA IP address connecting using the programmed in Broker password set in the integration.
I tried the same password and user for OHS, built also made a dedicated user and password for OHS and I get the same result.
Ok… tried password of ”1234567890”. One that I could type easily in both places to test…. Now it works…… I think the issue was I was using a really long password and OHS was not allowing the last few digits or my iPad was autocorrecting or auto capitalizing a letter.
System appears to be working and auto discovery is super convenient.
Adam, the developer of the OHS2, was super helpful. Not only did he write a custom firmware for my build so I could add extra zones, he helped me debug issues when I updated the firmware with my fork of his code. Now everything appears to be working. This is unheard of support. Thanks Adam!
Me next step is to add all of the sensors and my cellular SIM card.
As I add a sensor, I will label the zone, then integrate the zone into Home Assistant.
You are welcome
This a neat and nice build I must say. And also, I’m quite happy that the system scales above 20 zones that is normally installed by others quite well with minimal changes.
Just an update. For some reason, I only ordered 20 window sensors, so yesterday I installed 20 sensors.
The auto-discovery worked out great! My house was prewired but the wires were never labeled. So I would wire in a sensor, look at the OHS2 zone tab, then when I found the new zone that showed a closed circuit, I labeled the zone, turned on Auto-Discovery, and then the sensor automatically appeared in HA. I have 20 more sensors coming this week, then I hope to finish up my wiring.
After the zones are finished, I plan to add my hardware rfid buttons, add cellular, and start arming the system.
One of my door sensors is now showing “on” which is troubling because it does not have a magnet yet. Since I rebooted my HA, everything else is showing unknown. This tells me that I have an intermittent short that told the GW that the zone changed. I am going to add that zone to a group and arm it ti see if I get an alarm on that group.
