I’ve taken a few hours last night and today to update the Wiki here
It’s quite a restructure with some new bits added so take a look, you might be missing out on something that the Integration can do, especially for all you HACS users with the updated version. I think that the structure is more logical now and I’ve also added a content list with links so it’s easier to navigate.
If you have a spare 10 minutes then take a look and let me have comments or things you think are missing 
Great that you are maintaining this actively Dave.
Couple of minor points for people starting from scratch -
Cheers.
Good idea, I’ve added a bit of a description and a link for it in the “Ethernet Option 2” section. It’s also referenced from the main contents list at the top so that should be OK I think.
This one isn’t true in all cases, for example I don’t have the /config at the start since I run docker and the /config is part of the docker config. I think it better to do it the way I’ve done it i.e. to go to the HA config directory and show the structure from custom_components. Do you not think so?
Thanks for your comments 
Yes 
It’s possible, too.
Hello,
Does anybody use this component with the latest Visonic PowerMaster-33 EXP G2 alarm ?
Still looking for the best alarm system with a perfect HA integration so that I can replace most of my PIR sensors with professional and more reliable PIR sensors. But for that I need an alarm system that will forward all sensor status to Hass without latency and whatever the alarm status (armed, disarmed, partially armed,…).
Visonic and Paradox are on my short-list.
Thanks,
David
Hi Dave, getting this warning since 0.110:
Logger: homeassistant.components.alarm_control_panel
Source: components/alarm_control_panel/init.py:96
Integration: Alarm control panel (documentation, issues)
First occurred: 7:32:20 AM (1 occurrences)
Last logged: 7:32:20 AMAlarmControlPanel is deprecated, modify VisonicAlarm to extend AlarmControlPanelEntity
And also this error:
Logger: homeassistant.config_entries
Source: helpers/entity_component.py:163
First occurred: 7:32:43 AM (2 occurrences)
Last logged: 7:32:43 AMError setting up entry Alarm Panel for binary_sensor
Error setting up entry Alarm Panel for switch
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/config_entries.py”, line 217, in async_setup
hass, self
File “/usr/src/homeassistant/homeassistant/components/binary_sensor/init.py”, line 139, in async_setup_entry
return await hass.data[DOMAIN].async_setup_entry(entry)
File “/usr/src/homeassistant/homeassistant/helpers/entity_component.py”, line 163, in async_setup_entry
raise ValueError(“Config entry has already been setup!”)
ValueError: Config entry has already been setup!
Is it something I can fix on my side or does it have to do with new 0.110 requisites?
So for the first problem you identify, I also get the same in my log files. I’ve looked at the latest master HA backend source code and AlarmControlPanelEntity doesn’t exist so for the time being I’ll ignore it and wait and see what happens in the next release. As it says deprecated, it will not make any difference to the existing capabilities i.e it will keep working.
The second problem is a known issue with the HA integration system I think (other custom integrations have the same problem), see this earlier post in this thread. I’m waiting for a solution in other components and then I’ll do the same in this one.
Hi Dave,
I have an issue with GUI config as it refuses to save changes with last version.
Result is i’ve lost possibility to bypass sensors as a (new?) option only exists in Gui for enabling bypass.
Whatever combination of checkbox or options in list i tried, i always have that error :
Any idea ?
I might be the only one using bypass fonctionnality from my dashboard thus.
I have to say i’m a bit lost with new GUI stuff. There are options that seems to overlap yaml ones and GUI doesn’t have all parameters for the integration.
But i guess it’s work in progress and next versions will give a more exhaustive config UI.
I have to admit that looks OK and I’ve tried the same in mine (on PC and android mobile phone) and it works. I do not use the HA app though, on my mobile phone I use it through a web browser, might that be it? Are you using the HA app?
Have you scrolled down to the bottom, the sensor bypass setting is the last entry. Have you tried it on a PC or Mac through a web browser.
This is what mine looks like on my PC.
All configuration.yaml settings are in the integration control flow i.e. all configuration settings are available from the configuration.yaml file and the integration settings. Some of the settings are only used at startup and cannot be altered so when you already have the integration and are modifying it then you only get shown the parameters that can be changed while the integration is running. If you delete the integration from HA and try to recreate it, then you will see all the settings.
The following settings are only used for the initial creation:
language, exclude_sensor, exclude_x10, force_standard, force_autoenroll, sync_time, download_code
When you modify an existing integration you do not see these.
Ah no. All the configuration parameters are there already.
Let me know how you get on 
I’ve updated the wiki here to hopefully make it clearer, please also comment on the wiki text if you think I’ve missed something or not explained it well enough.
@davesmeghead Dave - Suggest you add something more in the wiki about the download code, where you stated that the default is 5650, well maybe it is for many, but mine was not and looking through the thread I see a few mentions of AAAA, indicating I’m not alone. I’ve a UK Powermax Pro, I recently reset it (reset by shorting DEF pins internally, followed by a factory reset through the menu). I had wondered why my panel never achieved Powerlink mode, now I know - on my panel at least the Download Codes can be set under 5.Define Communication=>C.S. Reporting=>PSTN Up/Down in this menu there is a Master Download Code setting and a Installer Download Code setting which were AAAA and 0000 - I set them both to 5650, restarted Home Assistant and hey presto Powerlink achieved. Quite why these options are buried under PSTN options when they relate to PC connectivity is somewhat strange !
Hi Dave,
A few months ago I did ran into the problem that my PM Pro didn’t want to jump into powerlink mode. You suggested to make a change in pyvisonic.py and after that change the panel finally connected in powerlink mode. See post, https://community.home-assistant.io/t/visonic-powermax-and-powermaster-component/55949/1155?u=holland
Now with the latest version 4.2, I can only connect in standard mode. In addition, I can’t change any options within the integration panel (user input malformed), just like Olijouvra experienced yesterday (post 1248). I did change
self.PanelType from 3 to 2, but that didn’t fix it
Hopefully you could give a hand to troubleshoot this
Thanks
Hi Dave,
I realised i was using both yaml and integration config so i’ve missed first steps in GUI that were automaticaly set as you state in the wiki.
I’ve removed yaml visonic part, delete integration and recreate it.
Everything is good now after reset sensors’s friendly_name that got lost in the delete operation.
Thanks for your help !
Looks bob-on to me, should help.
I can take a look through a log file if upload it, set yout logger config like this.
For the change from 3 to 2 to fix it, it would need to be in Standard Plus mode and have finished downloading the EPROM (and therefore know what panel type you have). I believe that I fixed it in a different way for your panel so please upload a log file and I’ll take a look (and put the 2 back to a 3 for now so I know we have the same source code when I get your log file).
I just happened to be back at my PC to do something when your post came in. I spotted this straight away, lines 10 to 32 are wrong in the log file so I know that the import from your configuration.yaml file has not worked correctly. This is the 2nd time I know of this happening so I may investigate further.
Specifically, what is happening is that it imports your configuration.yaml incorrectly and sets force_standard to true. The only way for you to correct this is to delete the integration from the integrations page in your frontend, if you get stuck then instructions are here. I then suggest you create the integration from the frontend, you can do this (delete then create) without restarting HA. Do not tick force standard, remember to untick it.
Give it a try and let me know please
Hi Dave,
Good news. I removed the integration, an added it again via the frontend. And I’m back in powerlink mode.
Excellent, thanks!!
Quoting my own earlier post isn’t something I feel I should do but I’ve created another release to help get around what I think is a bug in the HA integrations control flow.
This is also a HACS release 0.4.4, apologies for the quick fire releases 
I have had to make a workaround for the Override Code in the integration settings. If you set the Override Code to “1234” for example and you then decide that you don’t need it, if you simply clear the Override Code text entry, this will not work. If you go back in to the integrations panel the code “1234” will still be there. Clearing a text field does not remove the setting, HA thinks that you want the previous setting. So, set it to an invalid value (anything except a valid 4 digit numeric code, such as a single “0”).
Edit: I just realised that it is the same problem for the csv and xml log file names but these are less important than the override code, it is unlikely you would want to clear the log file name text strings.
D
