Open Home Security Installation

Hello All,

I am working on an installation of a home alarm system that is based on an open source project.

Here is the home page for the system:

As you can see, the system is scalable with add on modules and cellular backup.

The creator of the project has been super helpful and I wanted to show my work as well as share my experience and progress moving forward.

I think he is presently working on MQTT Auto Discovery.

I am currently wiring up the unit on the kitchen counter, but hope to install the box this weekend.

Thanks,
Jack

2 Likes

Here is a picture showing the current status of the box.

Finally got the box mounted.

Installed network and can see all zones. I still need to wire in the zones to the panels.

Ok,

Thought I would relay some lessons learned.

All power comes from the JST connectors for each board. The kit comes with a connector and pigtail, but I bought crimp pins and shells and made my own harnesses so I could run them all directly to my fuse panel in the lower right area.

From Digikey:

The board power in shell is:
XHP-4
CONN RCPT HSG 4POS 2.50MM

The sockets are:
SXH-001T-P0.6N
CONN SOCKET 22-26AWG CRIMP TIN

I also extended the LORA and cellular antenna coax with:
135101-01-M2.00
CBL ASSY SMA PLUG TO PLUG 6.6’

And:
ADP-SMAF-SMAF-B-G
CONN ADAPT JACK-JACK SMA 50 OHM

The power supply out connector shell is:
VHR-6N
CONN RCPT HSG 6POS 3.96MM

The power supply in connector shell is:
VHR-3N
CONN RCPT HSG 3POS 3.96MM

The power supply sockets are:
SVH-41T-P1.1
CONN SOCKET 16-20AWG CRIMP TIN

I used 16awg wire and cut a lamp cord for AC in.

The power supply was bought from eBay under this title…. Way cheaper than Amazon:
1pcs MEAN WELL Security Power Supply PSC-60A-C PSC-60B-C

The RS-485 terminals need twisted pairs, so I used cat6 cable and pulled out a twisted pair. The power for the RS-485 devices must be isolated from the incoming power. I used 20awg wire with ferrules but cat6 would have worked fine.

Here is the fuse block:

https://a.co/d/1FVisXH

Here is the terminal block:

Here are the din rails:

https://a.co/d/e4LN8R1

Here is the wire duct:

https://a.co/d/i3EQv4D

I have invited the creator of this equipment to the forum as I think he will be able to answer questions publicly (to help others) and also get feedback as he is adding features useful in HA.

With my kit I got 3 different antennae.

Which antenna goes with which radio?

Hello Jack,
thanks for sharing :), and btw, very nice setup. The DIN terminal blocks bring nice touch to wiring and over all cleanness. I really like it.

The antennas are:

  • smallest one is 2G/3G cellular (auxiliary)
  • right angle is radio 868/915 Mhz for radio nodes
  • longest one is 2G/4G cellular.

Adam

You can check the correct connection on following interactive diagram:
https://vysocan.github.io/OHS_20x.html

And the holes at PCB near the 868/915 connector are there to secure the pigtail with a cable tie.

Thanks!

Also, for simple door contacts, I need to change the zone to be “Unballanced” and then connect one wire to the zone 12v and the other to the zone input…. Correct?

Yes, set it as unbalanced in web interface. But the closed circuit from input to GND is considered as OK. Anything else is alarm.

Ok, so connect zone terminal through the door sensor to GND? Correct?

Thanks!

For everyone else reading this, Adam made me a new branch of firmware because I wanted the capability of connecting 50 zones. He did not have to do that, but I really appreciate the rapid support and update just to get me what I needed.

Adam, I see a lot of action on GitHub showing updates. Are any of them for my branch with the 50 zones?

Yes, correct.

For the new versions, the Home Assistant MQTT Automatic Discovery in now fully done and implemented. Also with a new MQTT topic called /alert, where any of the existing alters can be propagated to HA. For example there are action like key actions, armed, disarmed, unknown. AC and battery states. Zone open, alarm or tamper states.

Your branch is not touched yet. I think we need to discuss how to produce binary for your special configuration. Since normally binary is being built from master branch by GitHub Actions, there is a whole build environment in my other repository. Maybe you can make a fork of my repo, merge my master and let the Actions to build a binary for you?

Adam

I will see if I can figure that out…… I have not really used GitHub except for pulling in hacs integrations.

Ok,

I created a fork of your whole repository. I am not too familiar with GitHub so I may need some help making sure I do what you are say. Do you mind stepping me through this? I have friends that use GitHub and can help but they were not sure where everything is that you are asking me to use.

You need to clone the repo with gateway firmware: https://github.com/vysocan/OHS_2-gateway

Then I guess you need to install git command line tool, and do merge of master branch to multi-extensions branch.
After that you modify the .github/workflows/compile_and_build.yml file and add multi-extensions to these statements:

add branches: [ main, master ]

Then you just push to GitHub, and wait for the GitHub to build it.

Most work will be to decide what to merge. For you the most important is to keep following in ohs_conf.h

#define ALARM_ZONES 56 // # of zones
#define MQTT_FIFO_SIZE 80 // To accommodate various sources like zones, groups, sensors

Rest can be taken from master.

Adam

Ok, I have the right repository forked now. My config file has the correct lines already in it per your example.

My compile_and_build.yml file has

branches: [ main, master ]

on two lines.

Are you saying I need to change both lines to:

branches: [ main, master, multi-extensions ]

???

Thanks for your help. Your post sale support has been great and very much appreciated.

Yes branches: [ main, master, multi-extensions ]
then the build will run also on multi-extensions, or better yet, you can actually remove the main, master, so it will be build only on your branch.

Hello Jack,
all good with the fork and merge?

Adam,

Sorry for the late response. I was out of town for work.

I think I did it right. Can you see my fork and tell if it is done right?

All,

Just got a SIM card in from Red Pocket. I checked their tech support hotline and they say the IMEI is compatible with their plans. It was. $30 per year with 1000 sms per month. Should be enough.

I hope to get back on this next week.

Thanks
Jack.