opaulzen: OK, I can see from your log file that I try to go in to powerlink mode 3 times and each time it returns “Access Denied”.
The procedure for each of the 3 times is like this:
- Try to download the EPROM data, the pin is ox5650 (or “VP” in ascii)
- Panel responds back with “Access Denied”. This is normal.
- Try to Auto-Enroll, the pin is again 0x5650
- What the panel would normally do is accept this and start powerlink enrollment. Yours doesn’t, if just sends back another “Access Denied”. Compare this with the log file from hypernative and you’ll see what I mean.
That is why you have 6 occurances of “Access Denied” in the log file.
I don’t really know what else to suggest. Perhaps as you’ve got (or had) another device connected then it has enrolled that as powerlink and refuses my connection.
However, I think the panel has some kind of tamper function that if you try to get powerlink too often then it refuses to cooperate. I have found this as part of my development with my alarm, if I leave it for 24 hours and try again it starts behaving normally again. That’s all I can suggest.
So now for your other questions:
What would actually be the main advantage of Powerlink mode, besides the auto code downloading and more Panel info?
As I said previously, 2 advantages of powerlink, you get to see all the information instead of “Unknown” and it downloads your user code from EPROM inside the panel so you don’t need to enter it.
Without using the override code (which I’m not fond of, because of the clear text code in my config)
I can understand you not wanting to include your panel user code in clear text.
I cannot arm, because i dont see/get a panel to enter the code (like with disarm)
Oh that’s new! My panel allows me to Arm the panel without entering/sending the user code. I do have a physical button on the front of my panel that does this too, maybe that is the difference. I only have to enter and send the user code for disarm. I can include a config parameter to set it to do either way!
Only then i can use disarm again. Really weird.
I agree but it’s part of the built in HA operation of the generic alarm function. I don’t think that I can alter that operation, but it’s something I can check on.
But isn’t this something the panel/sensor itself decides? I know the visonic PIRS go into sleep mode until no motion is seen for about 120 seconds (or maybe even longer). Only after not seeing any motionfor this timer the PIR will send a new triggered status. Or is this something else?
You are correct. Use “motion_off” if you want to sleep longer than the panel settings value in HA.
Edit: This will also affect the number of events that are sent within HA so be careful when setting it too low.
Overal I’m very happy whith this component!!! Keep up the good work
Thankyou for saying so, very kind of you.
And i’ve discovered the blockquote edit function for making replies like this…