I’ve taken a look through your log file and it looks like:
You restarted this component in HA when your panel is in the installer menu, is this correct? If it is then quit out on the panel to the normal screen and reset HA.
You either do not request a manual powerlink enrollment or you have had a powerlink connected in the past and it hasn’t been un-enrolled. In the log file you uploaded, there is not a request from your panel to enroll so I don’t trigger the panel enrollment process for a Powermax Pro (there’s no point until the panel asks for it). Did you try to manually enroll during this log file?
I suggest that someone else with a Powermax Pro help out here with the sequence of things to do and try. Perhaps
Be on the normal panel screen (after un-enrolling a previous powerlink module)
restart HA or just this component with the service call
Wait until it shows Standard Plus
Go in to your installer menu and try to manually enroll a powerlink module
The pir camera lists its zone type for the pir and the camera is assigned a trigger action. Only ofther devices would be the keypad or RF fob.
Video cameras installed by suppliers like then connect to the panels wifi (360/360r) or gateway (10/30/33) but only present in applications from amdocs, alarm.com etc
Thanks for the info, I’d still like to make sure so
Anyone with a PowerMaster panel, can you check each visonic sensor details and look at the “zone type name” attribute, tell me if its incorrect please (according to your panel settings)
If it is then tell me what it is, what it should be instead and also the “zone type” number.
That’s correct, I did a reset of the connection via the visonic.alarm_panel_reconnect service. I followed the steps 1 to 4, and attached a new log. Also with step 1 to 4 the panel refuses to enroll a powerlink.
I did try to manually enroll the powerlink module, but to no prevail, as it results in a long beep.
There was no powerlink module installed before. As I’m the first owner, I’m sure about that. I also don;t have the option in the menu to remove a powerlink module. The only option I have is to enroll a powerlink module.
I’ve looked through your log file and it is now asking for enrollment (that’s good) but your panel isn’t sending the powerlink messages after that. You’re manually enrolling about 8 seconds apart, maybe try manually enrolling, exiting the installer menu and then leaving it a few minutes.
If you’re willing to experiment and you can change pyvisonic.py then try changing line 1255 (in version 0.3.7.0) from this
if self.PanelType >= 3: # Only attempt to auto enroll powerlink for newer panels. Older panels need the user to manually enroll, we should be in Standard Plus by now.
to this
if self.PanelType >= 2: # Only attempt to auto enroll powerlink for newer panels. Older panels need the user to manually enroll, we should be in Standard Plus by now.
i.e. change the 3 to a 2. This will try to send an Enrol to your panel instead of a Restore request after you manually enrol on your panel. I’ve seen mixed results with a Powermax Pro panel in doing this but I think it’s worth a try if you’re confident to have a go. If you decide to have a go then let me know the results (and another log file please).
Also remember to leave it much more than 8 seconds between manual enrolls on your panel D
If you’re willing to experiment a bit more, can you please try 2 things for me:
Make sure it’s in Powerlink Mode. Restart HA and see if it connects automatically and goes to Powerlink (without you having to do anything with your panel). If it doesn’t go to Powerlink then try to manually enroll. Save the log file and upload it please.
Make sure it’s in Powerlink Mode. Similar to 1 but this time Stop HA, wait for at least 30 minutes and then Start HA and see if it connects automatically and goes to Powerlink (without you having to do anything with your panel). If it doesn’t go to Powerlink then try to manually enroll. Save the log file and upload it please.
Thankyou very much, just so you know that I’ve looked through your logs and made a few changes to the code for users with your panel type. Nothing urgent to upload as a new release yet and I have it on test myself for a few days first. Thankyou again D
Earlier today I upgraded HA to 0.107.1 and nothing worked for me, several errors in my config about zwave (and none of my zwave devices worked) and this Visonic plugin doing really strange things. At first I thought it was just the Visonic component but I disabled it in the config and other components were still doing crazy things. I reverted back to HA 0.106.6 and everything is back to normal. I tried re-downloading 0.107.1 but still I had the same issues.
I strongly suggest you remain on HA 0.106 but if anyone else has updated and everything is OK then also let me know, just for my interest
I don’t have any issue with homekit either, but it doesn’t start automatically on my system, i have an automation that wait for 2 min, after HA restart , before to start homekit. It is to be sure Zwave has fully restarted before to load homekit.
FWIW, I’ve moved my lovelace resources to configuration.yaml and had a few initial difficulties when trying to transition piecemeal. It appears if lovelace sees one resource in configuration.yaml, it ignores any resource in ui-lovelace.yaml.
I’ve been experimenting a little with some new features and just ran across an error associated with the new Lovelace Dashboards. I’ve created a new dashboard using the discovery feature, which seems to use the existing ui-lovelace.yaml file. I’ve manually edited all the unwanted badges and performed additional editing using the UI. I’ve left the following in the added dashboard yaml for the Visonic alarm panel:
title: Home
views:
- badges:
- <snip of irrelevant info>
cards:
- <snip of irrelevant info>
- entity: alarm_control_panel.visonic_alarm
states:
- arm_home
- arm_away
type: alarm-panel
- <snip of irrelevant info>
path: default_view
title: Home
When I use my original dashboard, I’ve used the pop-up panel that results from a finger tap of the Visonic Alarm badge. With Lovelace Dashboard, an arm/disarm using the alarm_contol_panel card results in the following errors in home-assistant.log:
2020-03-24 18:32:25 ERROR (MainThread) [frontend.js.latest.202003181] http://192.168.0.21:8123/frontend_latest/chunk.xxxxxxxeditedxxxxxxx.js:142:705 TypeError: t is null
2020-03-24 18:32:29 ERROR (MainThread) [frontend.js.latest.202003181] http://192.168.0.21:8123/frontend_latest/chunk.xxxxxxxeditedxxxxxxx.js:142:705 TypeError: t is null
The last couple of updates (I have not installed all, but maybe for a couple of months) do I get this error when installing a new version of the Visonic Alarm Panel for Home Assistant:
File “/home/homeassistant/.homeassistant/custom_components/visonic/alarm_control_panel.py”, line 16, in
from homeassistant.components.alarm_control_panel.const import (
ModuleNotFoundError: No module named ‘homeassistant.components.alarm_control_panel.const’
Since this error is casuing issues to load the other modules, I have found out that I can bypass the issue by removing the folloing lines from the from file alarm_control_panel.py: (Line number first)
This is causing some errors when I use arm and disarm functions, but everything seems to be doing the job correctly. But is there any better way to solve this? Anyone else that got this issue?
Hi there, can you please confirm the version of Home Assistant that you are running. This change was put in to HA a couple of releases ago and meant that I had to make these changes in this Component. I’m guessing that you need to update your version of HA but if this is not the problem then please upload a log file with debug enabled. Stay safe and well
Thanks for the fast reply!
I thought that I was running on a newer version, because HA has not reported any new version and when I have been running the upgrade command it has not said that there is anything new. However; When I check my version with the current version I realize that mine is very old! So this is most likely the issue.
Thanks again!
Dave