Good morning,
for now everything works correctly, but I would like to know if you have managed to connect the alarm using powerlink.
Attached log in case you want to review it.
It looks like it’s not enrolling at 15:20:12. Perhaps the pin code (56 50) is not as expected. My unit responds with [Enrolling Powerlink] Reading panel settings. Perhaps it’s being locked out (look at message 105). Is there any tamper indication on the panel?
I was looking at why there was a time discrepancy between HA and the alarm panel. It looks like there’s could be a discrepancy in the 0x46 - Set date and time command.
The first 5 bytes are 0d 46 f8 00 07
. . . . . . . . should be 0d 46 f8 00 00
Thanks Pocket, but for now everything works correctly.
Now I keep working with the X10 elements that I have with my powermax and I integrate them correctly to HA as switches. Is there any way to change the “device_class” of the X10 entities that Hassio recognizes?
As I have been able to see, they are included as “dim” but I would like them to be intregrated as light or blind.
I’m learning some things as I experiment with the alarm system and the Visonic Component. If you’re having trouble getting into Powerlink mode, go into Installer Mode on the alarm panel (using the Master Installer code), then exit installer mode. If I’m not imagining things, this seems to reset the system allowing Powerlink communication.
In the Home assistant menu, under Developer tools, there an Info icon. Click that and find the log at the bottom of the screen. Look at the log to make sure there are no red items. I’ve seen indication of API communication failures, which were resolved with a system reboot.
56 and 50 Hexadecimal are the characters VP for Visonic Panel, this is the default Download Code (nothing to do with Installer ot User codes) for all panels that I know of. I believe that you can change the download code but only with a programmer.
There are a couple of issues why it might continually reject download requests:
To do with timing, HA installations run on different hardware and the timing of each transaction with the panel at that stage in start up is critical
HA does other things as it starts up, messing up with the timing
I log this when it tries to download panel settings. Essentially this reads from the panels EEPROM data where it stores the various config values.
I don’t think it gets locked out, although if I keep running my script, stopping it, starting it, then the panel gets a bit weird. If I leave it for a few hours and come back then it starts behaving again. I have no idea why.
The value that you show as different i.e. the 07 should be 00, that is the seconds value. It’s possible that my output buffer is this long but I figured that a few seconds wouldn’t make any difference. It may be something I look at later on, that famous “todo” list
This is something I say on my Github web page near the bottom for if you’re having trouble. This does a reset of the panel (which I do log when it happens).
I’m capturing with “info”, but I haven’t replicated the lockout condition I mentioned in a prior post.
In poking around looking for more protocol information, I’ve stumbled on a link that has a definition of the A7 message in the form of some type of source file. You’re probably already aware of it.
You could be correct, I don’t know. I have a Powermax Pro and it seems to work on that. Let me know if you find out
I am aware of it I’m afraid and that particular one doesn’t have much really. I have tried to obtain as much info as I can and if you spot any others that you find please post them here as I may not have spotted them.
There are other example source files like this
There’s also this but it’s quite old, oh and this too. This is source code in Lua for the Vera device
As a side note, if you can add another language by translating some of the english parameters used in pyvisonic.py that would be great too.
I’ve set the time manually on the alarm panel about 8 minutes ahead of HA and executed a server restart. I see no jump in time after the Download status on the panel goes away.
Ah OK, that’s a shame. Unless I can get the correct message structure from somewhere as to how to set the time on a Powermaster then I’m stuck.
All I can do for now is to add a note to the Github description saying that this is only for Powermax.
Ah OK and I shouldn’t have directed it at you personally, sorry, it was meant to be a general callout to anyone who could do a translation but it was late lastnight when I posted
I have just uploaded release 0.1.3 to Github that includes the latest Powermaster changes, a change to when the date and time is sent for Powermax panels and a slight change for Powerlink and its sequencing.
Dave, thanks a mil for all the hard work you continuously put into this component and all the assistance you give to us who use it! It is highly appreciated!
I do have a feature request though. Would it be possible to opt out of the construction of the X10 switches with a config parameter? Like a x10: 'no' in the config? I suspect not many people actually use them, and they do take up a lot of space in the dev-state window, and perhaps also some resources for HA to maintain?