What might make it difficult is that I have a Nuon branded powermax. For now I only use the standard mode, this is also sufficient.
Thank you for your help so far.
Hi unreal,
Apologies for the delayed response, I’ve been away with work and although I could see the forum on my phone there’s no way I could analyse your log file until now.
I see that your panel type is a “PowerMax NUON key 4_17”. I haven’t come across this particular panel but it should be a panel that works with this Component.
I have a few observations that I have made when looking at your log file:
Zone 9 is showing a low battery. Can you confirm it has a low battery, your panel may indicate this.
Can you confirm that Zone 9 is a Smoke Detector?
On lines 643, 850 in the log file, for Zone 7 I see that your Kitchen “Gas” sensor was triggered, if this were a motion sensor that would mean that there was motion in your kitchen at the time of you capturing the log file, could this be true?
You do not need the OverrideCode in your Configuration file as we achieve what I call “Standard Plus”. This means we have downloaded the EPROM but not achieved a Powerlink connection with the Panel.
I ask the panel to go in to Powerlink several times. Each time it responds with the first part of the sequence but does not send the second and last part of the sequence i.e. An “0xAB” message. There’s nothing else I can do, you may be stuck with “Standard Plus”, sorry.
For the “Gas” sensors as Zones 6 and 7, I assume that my code is correct but is there anyone else using this Component that actually has a Gas sensor and does it appear correctly in Home Assistant. Specifically, I’m trying to decide whether to alter line 731 in pyvisonic.py.
Unreal, you could alter it yourself temporarily, on line 731 change “Gas” to “Motion”, you’ll see what I mean if you take a look
To anyone using this Component,
Do you have a Gas Sensor and does it appear correctly in Home Assistant?
Do you have a Smoke Sensor and does it appear correctly in Home Assistant?
Zone 9 is showing a low battery. Can you confirm it has a low battery, your panel may indicate this. is right and solved.
Can you confirm that Zone 9 is a Smoke Detector? yes
On lines 643, 850 in the log file, for Zone 7 I see that your Kitchen “Gas” sensor was triggered, if this were a motion sensor that would mean that there was motion in your kitchen at the time of you capturing the log file, could this be true? is right
You do not need the OverrideCode in your Configuration file as we achieve what I call “Standard Plus”. This means we have downloaded the EPROM but not achieved a Powerlink connection with the Panel. I deleted it, but “Standard plus” does not work anymore, unlike a view versions ago.
I ask the panel to go in to Powerlink several times. Each time it responds with the first part of the sequence but does not send the second and last part of the sequence i.e. An “0xAB” message. There’s nothing else I can do, you may be stuck with “Standard Plus”, sorry. I use the forced standard mode, no problem
For the “Gas” sensors as Zones 6 and 7, I assume that my code is correct but is there anyone else using this Component that actually has a Gas sensor and does it appear correctly in Home Assistant. Specifically, I’m trying to decide whether to alter line 731 in pyvisonic.py.
In forced standard mode de log shows:
Zone type for 6 is 0XC Interieur
Zone type for 7 is 0XC Interieur
I don’t know where 0xB comes from (Gas)
Can you please elaborate or maybe upload a log file to tell me why you think it isn’t working, that puzzles me.
The Zone Type and Sensor Type are 2 different things and you are mixing them here.
The Zone Type refers to how the panel uses that sensor in the zone, these are the Zone Types (in English, there are Dutch and French versions in the actual code):
“Non-Alarm”, “Emergency”, “Flood”, “Gas”, “Delay 1”, “Delay 2”, “Interior-Follow”, “Perimeter”, “Perimeter-Follow”, “24 Hours Silent”, “24 Hours Audible”, “Fire”, “Interior”, “Home Delay”, “Temperature”, “Outdoor”
The Sensor Type refers to what the actual sensor is, these are the Sensor Types:
“Vibration”, “Shock”, “Motion”, “Magnet”, “Smoke”, “Gas”, “Wired”
A PowerMaster can also have “Temperature” and “Camera”
The Sensor Type is only set from the EPROM i.e. “Standard Plus” and “Powerlink” modes
If you set ForceStandard then you will not get the Sensor Type at all.
And another thing
It is the Sensor Type that I use to set the HA device class. If it is in “Standard” mode then the Sensor Type is not set for each sensor and the device classes are set to the default.
It is the device class in HA that changes what the icon looks like and how it behaves in HA.
If you’re in “Standard” mode or you just need to override the device class then you can do this in your HA customization, for example:
So, in your case Z07 is coming out as a Gas sensor type, you can override it like the example above to make it appear in HA as a motion sensor type.
For a list of valid device classes look here
Just wanted to say a big thanks to @davesmeghead for this awesome component! It works flawlessly for me, using a USB-to-TTL-cable for 7€ connected to my Powermaster-10.
I get Powerlink mode quickly and I can finally ditch all my lousy 433Mhz magnetic sensors and use the alarm door sensors instead. Big thumbs up!
“Standard plus” does not work, after half an hour the panel is still in the downlaod mode. For the log file see https://pastebin.com/0B85H34a
Thank you for explaining how I can override a device class.
I’ve taken a look through and I’m really confused, your log file for this plugin starts at 19:24:27 and by 19:24:53 it says it’s in Standard Plus mode (line 280 in the log file)
[Process Settings] Entering Standard Plus Mode as we got the pin codes from the EPROM"
It’s downloaded the EPROM and confirms Standard Plus. It tries to get to Powerlink and fails.
Also, I notice throughout your log file:
[custom_components.visonic.alarm_control_panel] code format none as powerlink *****************************
This is HA getting the code status, this means that HA thinks it’s in Powerlink (it’s in Standard Plus but that’s another story, I should update the log file entry to “code format none as powerlink or standard plus”)
What makes you think it’s in Download Mode? If it were in Download Mode then the sensors wouldn’t work, do the sensors work in the HA Frontend?
Just to make sure, from the HA Frontend, can you go in to Developer Tools (it looks like a hammer), then select STATES. Find the entity “alarm_control_panel.visonic_alarm” and look at the attributes column (the 3rd column). Find the attribute called “Mode:” and tell me what it is set to.
The panel mode was not displayed correctly in lovelace and remained on download while in reality it was on standard plus. Problem solved, thank you also for the template help.
It looks like you may not be able to connect the original Powermax, this has been tried already. It seems like it depends on if you have a re-seller version or not I think. sosandstrom has tried this already and I don’t think that he succeeded. Check out the www.bankras.org link in the post below for more info.
Hello,
Is anyone else suffering with false alarm triggers? I have been getting this regularly for the last few weeks or so. I was running on a NUC with lots of automations and other stuff going on which I suspected was causing the problem. So I moved to a dedicated Raspberry Pi (4) which has nothing on it apart from this and I still get false alarms. If I turn off the PI then everything on the alarm has been working correctly with no false triggers.
I’m connected via Wifi currently running v0.100.3 and the latest version of this component.
Looking at the logs I can see one of the sensors does show a trigger on movement but this doesn’t seem to happen when not connected to Home Assistant.
I’d really like to get this working properly as it’s incredibly useful and the icing on my home automation cake!
If anyone has had similar issues I would be grateful of any advice.
Regards
Mark
I have a Powermax Pro and USR-TCP232-E Serial Server which on the surface are working well together however, I am finding that on an irregular basis (can be days or weeks) the USR-TCP232 appears to freeze (no change in TX or RX count) and the Lovelace overview remains but, of course, the alarm/disarm and other functionality doesn’t work.
Annoyingly this tends to occur whilst I’m out of the country but has, to date, been able to be resolved by remotely rebooting the USR-TCP232 & HA.
This week the same happened but the USR-TCP232 wasn’t accessible remotely this time and required the Powermax to be powered down and up before it could be reached.
I’m thinking that somewhere I’ve got the USR-TCP232 set up incorrectly, or some parameter is too tight. This is the RS232 page.
Hello to all.
This is my first post here, although I’ve been following the progress of this component since the beginning. At the first releases I gave it a try, but I was not able to use it with my iTach IP2SL module, so I kept my VERA Edge as the handler of the alar system.
My setup is a Visonic PowerMax Pro Panel with iTach IP2SL for serial communication. I had this setup since I bough the Alarm system as it was intended for the VERA plugin and it was confirmed to work flawlessly.
So… couple of days back I decided that it was time to try again.
Initially it all seemed fine and I was able to connect to the panel through the iTach module and operate it. But I noticed that after going to powerlink mode, the PIRs were not updated any more, and the state change was very slow. So I started digging into the code to see if I could find the cause. After enabling the debugging, I discovered that a type of packet stoped being sent by the panel, and this was “0d A5 00 04…” although packets “0d A5 0d 04…” kept coming.
After straggling for 2 days with a lot of debugging and comparing with the VERA plugin, I was able to find the problem, and I am reporting it here so that maybe I can help others to overcome this issue.
So after changing 2 parts of the code, the problem was solved and the PIRs are updated without any problem and without any delay.
Both changes were in “pyvisonic.py”
All I did was to disable the MSG_ALIVE message when in powerlink mode, and send message MSG_RESTORE instead of MSG_STATUS while in powerlink.
I am not sure if the MSG_ALIVE was even a problem, but it was never used in the VERA plugin, so i thought it is not of any use.
I’ve taken a look through your post and I really welcome your suggestions, I’ll incorporate your proposed code changes and test them with my Panel over the next few days or so. Your proposals seem sensible, I just want to make sure before everyone starts using them
You didn’t confirm this in your post but I assume that the code changes you made have now made your Home Assistant setup work? Do the PIRs pass through updates etc?
Can I ask you a hardware question. With your iTach IP2SL, does it use proper RS232 voltage levels or does it use TTL. The interface to the Panel is TTL unless you have a converter.
Now for a bit more on those A5 message from the Panel
The “04” means a Zone event has happened.
0d A5 00 04
0d A5 0d 04
The only difference is the 00 to 0d. This is just the message count from the Panel which I ignore anyway, my code would not make a difference between these 2 messages. The MSG_RESTORE and MSG_STATUS should trigger the panel to send the sequence of A5 messages and so the message count is not relevant.
Not without wiring it up and trying it, and that means buying the hardware (approx £20 or $20). You don’t need an HA install, just install python 3 on your computer (Windows or Linux and connected to the same network as the panel) and use test.py from my component.
Hi Dave,
Sorry for missing things at my message, but I focused on the problem and I forgot to mention the result.
Yes my setup now in HA is working perfectly with instant response.
Regarding the messages. I know that you are ignoring the count, but here is the big problem. 0d does not include the zone number so the code does not know which zone was triggered. Check the block of A5 packets at the image:
Before the change all these 04 00 were not sent by the panel once the first MSG_STATUS was sent to the panel after changing to powerlink mode. No idea why, but I suspect that it is triggering something that should not be triggered.
As for the iTach IP2SL I imagine it is TTL because I never used a converter. I also forgot to mention that it is a POE module, so no external power was required.
