Really sad to see what's happened with Visonic after being bought out.
3G service is being retired across the board by Cellular companies ...and Visonic (now Johnson Controls) has no plan to build a 5G cellular module even though, as best as I can tell, a whole bunch of the task from a radio perspective is available off the shelf from the same vendor (Telit) they have used for years.
The company wants us back at their trough buying new panels I'm sure. I have one of the more recent versions of the Power series of panels. Works fine, no need to change it except for this communications dilemma. There are folks posting in this thread having some of the really early Visonic panels STILL working, I remember those well.
I don't believe the original Visonic team would have left customers out on a communications limb with perfectly functional boxes of recent vintage.
So many small companies sell out and give up their niche to big players who then RUIN the good. I can tell you this, the evolution of alarm systems has brought a lot of other options beyond what Johnson Controls offers and I don't trust them now.
@cjcharles - I need to revisit what you have done to link these panels to HE and see how I might get it working on the Powermaster-30 PG2 which basically uses some improved device communication but otherwise shares A LOT of similarities with the other panels you've integrated.
Yes, they were a bit chaotic in their early days with thousands of versions of each model, but at least they were similar and mostly worked without modification. Its definitely harder now!
I actually splashed out on a couple of Powermaster boards recently (late December) so I could work on the integration for those models, and make it reliable, but I havent had the time to test things properly ever since Definitely something that needs to happen though!
If this helps bolster the info on the Powermaster-30 here is a picture of the IP connector on one S-303151(Rev.A0) which is the "newer" PowerG or PG2 series of Powermaster panels. This connector is where the Visonic PowerLink module gets plugged into.
Some time ago I connected a CP2102 USB-TTL Ver.3.0 board to the IP connector for using the Visonic panel remote/configuration software on a PC instead of doing it all through the panel's keyboard. The board just plugs into PC's USB, is powered by it, and is recognized by the Visonic software (there may have been some set up to find it, don't recall).
Ten pins, 5 top, 5 bottom, I forgot the numbering order. Visonic's connector "key notch" is facing up and not shown in photo.
Top three middle pins of the Visonic connector are connected to the CP2102 as follows, left to right:
Ground - Green wire
CO2102 Rxd ( the Visonic's Txd) - Yellow wire
CP2102 Txd (the Visonic's Rxd) - Blue wire
So have you basically reversed engineered the command interface for talking to the panel in the same way that their Remote/Configuration Software has? Or the full blown communication that's done back to the Central Station to the PowerManage platform?
Just curious from your experience and best guess....what kind of "dead-end" do you think I might end up at if I embark on setting all this up with the newer Powermaster 10/30 PG series unit?
Am I likely to see immediate and obvious success or failure ...or is there a chance I'll spend the time getting this together, THINK that it's all good, only to later find some % of things not working right and therefore not dependable?
I updated my device drivers this morning for the most current hosted on github.
Device settings 'Arm Alarm', and 'Alarm disarm' work correctly on the Visonic bridge device settings.
Local IP 192.168.0.XX reserved, and made static for the visonic bridge (respond to http://192.168.0.XX/getzonenames, with a list of my 4 zones correctly).
'Create child devices that control the alarm ' toggled on
'Update HSM mode when alarm arms/disarms *' toggled on
I'm not using the password field on the device settings
Ok, I am a bit confused by all the info here. I am looking to integrate a Interogix/Networx NX-8E with Hubitat. Hoping I can just get a Wemos board and flash some firmware, connect to wifi, install apps/drivers and be off to the races. However, are there any instructions on where to get the firmware that can talk to the NX-8E as well as how this should be wired to panel (home automation port?)?
I see you have just found the thread on Smartthings forums, which was where the NX-8E integration started. Let me know if you have any questions and I can help getting things setup if needed.
I think I figured it out ... LeeFL apparently programmed a Wemos with a RS232 and a relay shield to work with the NX584. This is essentially what the pynx584 does but probably has a different API.
Your app/driver I assume only works with LeeFL's device. I tried to see if he is still selling them. Happy to build one if it is open source but would need to know the components and where to get the firmware.
If you pick up a chat between the three of us Im sure we can coordinate something that works - as Im sure he is like me in that selling the Wemos boards is far from profitable given the effort and crazy low volumes!
Great to find all the parallel interest in connecting Visonic panels to home automation. Thought the links below might be of interest to folks as some of the biggest questions seem to surround installation/connection of kit and the various panels this might be achieved with.
Confirmed compatibility of the subject Hubitat driver with the newer Powermaster-30 PG2 model would be GREAT. Willing to try if I can be assured of not burning up an operating alarm panel.
I bought myself a Powermaster panel to test compatability and implement a few fixes that I think will be needed, but I just havent had any time on this project recently. Im not sure when I will have more time but possibly not until late summer (depends how much time I have for my random projects above work requirements)
Hey could you check the Firmware version of your system someday when you have a chance?
It will be in the Installer Menu - Serial Number - then advance through the screens.
There should be two fields you can advance through, each that start with "JS#######" and then behind that:
maybe something like v1.0.02
and then on the other
maybe something like K13.###
or
maybe B17.###
Trying to compare my system and compatibility with that Powerlink 3.1 that you have plugged in there. Visonic information seems to indicate that the PL3.1 module requires v17 but others mention v13 and up is the required version level to be able to add this module.
Thanks. No rush, just when you have time/desire to do it.
@cjcharles I'll try this out with my Powermaster 30 (US model), and order your plugin, but unsure if I need Arduino also? I guess relay is completely optional?
Ive been working on some updates to this integration while trying to get Powermaster support to be reliable. In anticipation of this I have updated this device handler to use Component child devices rather than the Virtual devices and my custom switch device.
Sadly this is a breaking change, hence if you update to the latest version (on HPM) then you will need to take a few manual steps to get everything working. Fear not it should only take you a minute or two, but it does require a couple of steps as below:
The children zone devices may stop updating from this change so I recommend changing them to Component Motion/Contact devices. There is some chance they will still work, but given it takes a second I suggest updating. The easiest way to do this is to open all the zone devices in separate tabs, update the 'Type' to use the relevant 'Generic Component' handler before pressing save, closing the tab, and moving to the next zone.
The arm/disarm child devices also need to change from using my custom child zone, to using 'Generic Component Switch'. You can do this in the same way as for the zones, but this step is 100% required for the devices to function.
This step is optional, but involves a firmware update of the Wemos with the firmware bin file here. This allows Hubitat to request the latest zone status from all zones when required. Ive noticed very rarely an update message gets lost in the ether, and the zones appear open when they should be closed (or similar), so this finally allows Hubitat to do an occasional poll for status if required. This firmware update IS required if you are setting up the integration from scratch.
After making the changes to device types your devices list should look like this:
Definitely something that needs to happen though!
![[image]](https://community.hubitat.com/uploads/default/original/3X/8/1/81c2fbdec0a25efb88aff31b0265d8204123b1a0.jpeg){kind=link}