Haha, just when you thought it was safe to update…
Hi Rob, I’ve just uploaded 0.4.0.6 to Github for you to try. Quick fix for creation of an integration from within HA.
I’m off to bed now so no more updates for tonight (it’s 1:30am here in the UK) 
That’s easy enough to change
So the logic is still upside down? In either case the panel provided status, but would not go to Powerlink or have the ability to arm from HA. You’ll also see the absence of EPROM download.
This log is with setting force_standard: 'yes'
This log is with setting force_standard: 'no'. You’ll see where it stays in Standard mode after a Powerlink acknowledge. At lease, that’s how I interpret what I see in the log.
I’ll comment out the configuration.yaml entries and see what I can do with the UI.
Thanks again.
Currently, I’m in the Integration UI. When reviewing options, this popped up:
Continuing, this one shows the same diagnostic message:
Here’s a log:
Again, I cannot arm the panel from within HA.
More thanks.
Yup. I was busy testing various configurations of 0.4.0.3, and in that amount of time with an open editor, you downloaded three more versions! It’s difficult to keep up with you! 
I just tried 0.4.0.6 and I don’t have a working configuration. I’d like to know how to configure force_standard: for Powerlink. Is it 'yes', 'no', 'true', or 'false'? It’s ambiguous to me at the moment.
Assuming I have inadvertently set it correctly, there are exception errors during communication. I’d like to know if I have a configuration problem before jumping to the Integration UI.
With that, I’m going horizontal. It’s 0146 EDT.
As always, thanks.
Hi Rob, I’ve taken a look at your log file and there are 2 main problems:
- I think you’ve pummeled your panel too much and it’s just streaming out ‘A5 04’ messages all the time. We’ve seen this before when the panel gets initialised too many times over a short period of time it seems to then just stop receiving data and streams out the ‘A5 04’ data all the time.
- You are not deleting the integration before restarting HA
On this last point, I think that you’re in a position where you have duff data in the integration and each time you start it is trying to reuse the same duff data. One thing I know for sure, the log file you uploaded indicates that it did not read in the data from your configuration.yaml file.
I suggest you go in to the “Integrations” Page in your HA. On the Visonic Intruder Alarm integration, click the 3 vertical dots and delete the integration. Wait a minute or so and you should see that all sensors are remove etc etc. Restart HA and it should read the settings from the configuration.yaml file this time.
I have uploaded 0.4.0.7 with a couple of bug fixes as well but no major changes to the 2 input schemas.
Let me know how you get on 
EDIT:
Forgot to answer this one. In the configuration.yaml file it should be fairly flexible, you should be able to do these:
allow_sensor_bypass: 'true'
allow_sensor_bypass: 'True'
allow_sensor_bypass: True
allow_sensor_bypass: 'false'
allow_sensor_bypass: 'False'
allow_sensor_bypass: False
allow_sensor_bypass: 'no'
allow_sensor_bypass: 'yes'
allow_sensor_bypass: 0
allow_sensor_bypass: 56
I looked up the python code in HA.
You can also use the strings ‘on’, ‘off’, ‘enable’, ‘disable’, ‘0’, ‘1’ for conversion to boolean values. They must all be in quotes except True and False which are read in as the boolean states.
You can also use an integer directly, 0 is False and not 0 is True.
OK. It’s communicating, but not fully functional.
This time I decided to go straight to the UI integration. I removed it, restarted, commented out the configuration.yaml entries, and restarted again. When I went to integrate the Visonic component, its tile was already visible (a surprise). I guess the configuration entries triggered discovery.
At that point, I selected options, but did not see the communication parameters. It went straight to Alarm Panel Settings which looked OK, so I looked at the log. It was in Powerlink mode. I then tried to arm and disarm the panel, but after arming it, the disarm popup did not replace it. I disarmed the alarm at the panel, but now I’m not getting status from the sensors. Currently, there is no indication of a trouble state.
EDIT: Here’s the log:
https://pastebin.com/XvR0pzQ2
What should I try next?
More info:
If I allow the panel to count down and arm, the disarm popup displays. It disarms the panel, however the state still shows ‘armed.’
After another HA Restart, the panel status shows ‘disarmed’. I can arm the panel and it counts down and goes to the ‘armed’ state, but the integration still displays ‘disarmed.’ It takes sever tens of seconds before a state change to ‘armed’, but once that happens, I can get the ‘disarm’ popup to appear.
Hear is a log prior to the HA Restart:
https://pastebin.com/XvR0pzQ2
Here’s a log after the HA Restart:
https://pastebin.com/D50PP1a1
Well this was a tricky one but another bug is squashed. This is nothing to do with the integration and the control flow, it’s to do with the decoding of the B0 messages from your PowerMaster panel. So this is a bit of a side issue. I’ve uploaded 0.4.0.8 for you to try please.
Hopefully this will decode variable length B0 messages in a more consistent way, it was losing some messages while it re-synced itself with the panel and would then need time to catch up. Meanwhile you see crazy looking things in the frontend as the interface with the panel is out of sync. I suggest you delete the integration though and start again.
That’s better! 
A toast to Dave 
So far so good. I’ll let you know if there are any more gremlins.
OK that’s good. Can you please upload a log file so I can check my decoding of the variable length B0 messages. I have a PowerMax and so I don’t get B0 data. Thanks.
OK. I’ll enable the B0 messages, restart, and post a log after I have some dinner.
Thanks for everything.
Here’s the log:
Let me know if you need more of the log or anything else.
Hmm…download doesn’t seem to be working.
New to HA, coming here specifically because of the excellent work in this thread. I’m using a NodeMCU and esp-link to connect to my Powermax Pro, from the look of the strange characters occasionally appearing on the esp-link console I think my wiring is good.
However I seem to have a problem with the visonic component, I have a visionic alarm widget on the HA overview page (with just a disarm button on it and nothing else) and when I enable debugging in the configuration.yaml all I get is the following, there doesn’t seem to be any failure here, but there’s no real sign of anything much happening …
Help apprecited.
2020-05-04 19:02:29 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for visonic which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant. 2020-05-04 19:02:41 INFO (MainThread) [custom_components.visonic.pyvisonic] Initialising Protocol - Component Version 0.4.0.8 2020-05-04 19:02:41 INFO (MainThread) [custom_components.visonic] ************* create connection here ************** 2020-05-04 19:02:41 INFO (MainThread) [custom_components.visonic.client] Exclude sensor list = [] Exclude x10 list = [] 2020-05-04 19:02:41 INFO (SyncWorker_6) [custom_components.visonic.client] [Settings] Log Max Entries set to 10000 2020-05-04 19:02:41 INFO (SyncWorker_6) [custom_components.visonic.client] [Settings] Log Reverse set to False 2020-05-04 19:02:41 INFO (SyncWorker_6) [custom_components.visonic.client] [Settings] Log Create Event set to True 2020-05-04 19:02:41 INFO (SyncWorker_6) [custom_components.visonic.client] [Settings] Log Final Event set to True 2020-05-04 19:02:41 INFO (SyncWorker_6) [custom_components.visonic.client] [Settings] Log XML Filename set to panel_log.xml 2020-05-04 19:02:41 INFO (SyncWorker_6) [custom_components.visonic.client] [Settings] Log CSV Filename set to panel_log.csv 2020-05-04 19:02:41 INFO (SyncWorker_6) [custom_components.visonic.client] [Settings] Log CSV title Row set to True 2020-05-04 19:02:42 INFO (SyncWorker_6) [custom_components.visonic.pyvisonic] Setting USB Options 2020-05-04 19:02:42 DEBUG (MainThread) [custom_components.visonic.alarm_control_panel] code format called ***************************** 2020-05-04 19:02:42 DEBUG (MainThread) [custom_components.visonic.alarm_control_panel] code format none as armcode is none (panel starting up?) *****************************
configuration.yaml snippet (only thing editted for posting here is the IP address)
visonic:
device:
type: ethernet
host: '192.168.1.19'
port: 23
motion_off: 120
language: 'EN'
force_standard: 'no'
sync_time: 'yes'
allow_remote_arm: 'yes'
allow_remote_disarm: 'yes'
panellog_logentry_event: 'yes'
panellog_csv_add_title_row: 'yes'
panellog_xml_filename: 'panel_log.xml'
panellog_csv_filename: 'panel_log.csv'
panellog_complete_event: 'yes'
arm_away_instant: 'no'
arm_home_instant: 'yes'
# force_numeric_keypad: 'yes'
# override_code: '1234'
# download_code: '9876'
# arm_without_usercode: 'yes'
Its a brand new HA install with nothing else configured except the Sonos speakers etc that it auto-discovered when I first started HA yesterday.
Did you enable debug logging using the logger setting in configuration.yaml i.e. logger: as per the Wiki here. I suggest you read through the wiki page if you haven’t already, well worth it 
Also, can you upload your full log files to pastebin or dropbox instead of trying to push them in to this forum page please, it just makes it easier for me to look through and gives me the info I need. Without a proper log file I can’t tell anything about the communication with your panel. The log info that you’ve put here only has the first few lines, I need much more:
- set the
loggersetting in the configuration.yaml file as per the wiki - Restart HA
- Leave it running for 3 or 4 minutes
- Look at other peoples pastebin logger files and make sure yours looks similar (but probably different)
- Upload your log file to pastebin
- Tell me about it here
If, after 3 or 4 minutes, the only entries you get then you have an issue with your hardware/wiring.
In your log file, if you search the file and get several occurances of:
- “[pmSendPdu]”. That is my component sending data to your panel.
- “[data receiver]”. That is data received from your panel.
If you get neither then there’s a problem with your HA setup
If you get “[pmSendPdu]” but not “[data receiver]” then it’s likely a problem with the hardware/wiring.
Let me know how you get on
D
EDIT: If you’re using the latest version of this component the it only reads in the visonic configuration once and then uses the HA integration for config after that. Just in case you’re changing your configuration.yaml settings and not seeing a change in operation.
Hi Rob, That log file looks OK (and it downloaded the EPROM). There are a couple of tweaks that I need to make in the code but nothing major.
Indeed, I am changing the configuration.yaml - was originally set to USB (thought that would be an easier way to start) and then changed it to network. Where is that config for the communication type available to edit, I saw some of the options are available to edit in the “Visonic Intruder Alarm” options under integrations, but the communications type is not there…
I did read the wiki several times but I don’t think it mentions about the configuration.yaml only being ever read once.
I’m assuming that you’ve downloaded and installed version 0.4.0.X of this component from github
It’s here
You would need to delete the integration from within HA, restart HA and then it would re-read the configuration.yaml file. To delete the integration
- Go to configuration - integrations
- On Visonic Intruder Alarm, select the 3 vertical dots and then select delete
Have you read this on the wiki, about NodeMCU and using esp-link?
If this doesn’t make sense then I can go through it in more detail with you if you like
Forgot to mention, once you set ethernet or usb then this (and a few other parameters) cannot be edited. You need to remove the integration and then re create it (either restart HA to reimport configuration.yaml or create the integration again by selecting the big orange plus sign in the bottom right corner of the integrations page and add “Visonic Intruder Alarm”)
Well, that shows everybody how wrong I can be.
I recall a block of hex characters in prior versions. I also saw this message, which looked suspicious.
Sending a STOP and EXIT as we seem to be still in the downloading state and it should have finished
At any rate, I can see the multiple transaction prior to the above message.
Thanks for setting me straight.