Hi, will it be safe to update to HA 2023.6 since it moves to python 3.11?
just want to make sure this integration won’t break…
thanks in advance =]
Haha I guess we’ll find out soon enough 
Joking aside, it’s a good question to ask whenever a fundamental change to Home Assistant is made.
As far as I know the Integration itself in HA should work with 3.11 and I have a test environment for some of the code that I use and it uses 3.11 … having said that, there are no guarantees here, after all, it is software 
and I have not tested the Integration with any beta HA 2023.6 releases. The only library dependency I have is on pyserial_asyncio and I’m assuming at the moment that it will be OK until I know different (as this is also part of my test environment, that does not include Home Assistant).
My final comment is one of caution, if you rely heavily on Home Assistant itself (with or without this Integration) then I suggest that you delay any update when 2023.6 is released. This will allow myself and other brave souls the time to ensure that the Integration works with 2023.6 and python 3.11.
1 Like
Hello, I have updated to HA 6.0 and have had no issues with the Visonic Integration version 0.8.4.1
1 Like
I upgraded HA to 6.1 and it works with Visonic Integration 0.8.4.1. Then I upgraded to Visonic Integration 0.8.5.0 and it works but I do see an warning in the log.
Log Details (WARNING)
This error originated from a custom integration.
Logger: custom_components.visonic
Source: custom_components/visonic/init.py:263
Integration: Visonic Intruder Alarm (documentation, issues)
First occurred: 9:00:40 PM (1 occurrences)
Last logged: 9:00:40 PM
[Visonic Setup] CONF_PANEL_NUMBER not in configuration, defaulting to panel 0 (before uniqueness check)
That’s good to know, thanks
I too have not had any issues updating to 2023.6
Ah yes, when I removed auto panel numbering for those with multiple panels I should have made that a debug message for the log file and not a Warning. Please ignore the Warning. I’ll do a minor update to Github to change it to a debug log file entry.
EDIT: I decided to just do it and I’ve updated the version to 0.8.5.1 on github, including a HACS release.
Thanks. I upgraded. That fixed the warning.
Hi Dave,
Been using your integration for years, but after upgrading from 0.8.2.4 to 0.8.5.2 in HA 2023.6 it wont load anymore. this is the only thing the debug logs show:
2023-06-16 17:26:56.529 DEBUG (MainThread) [custom_components.visonic.pyvisonic] Initialising Protocol - Protocol Version 1.0.20.0
2023-06-16 17:26:56.531 DEBUG (MainThread) [custom_components.visonic.client] Initialising Client - Version 0.8.5.2
2023-06-16 17:26:56.535 INFO (MainThread) [homeassistant.setup] Setting up visonic
2023-06-16 17:26:56.535 INFO (MainThread) [custom_components.visonic] Starting Visonic Component
2023-06-16 17:26:56.536 INFO (MainThread) [homeassistant.setup] Setup of domain visonic took 0.0 seconds
2023-06-16 17:26:56.539 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.utility_meter
2023-06-16 17:26:56.566 DEBUG (MainThread) [custom_components.visonic] [Visonic Setup] ************* create connection here **************
2023-06-16 17:26:56.566 INFO (MainThread) [custom_components.visonic] [Visonic Setup] Starting Visonic with entry id=cb41fb192910fd68fbce48b0f837a2d1 configured panels=1
2023-06-16 17:26:56.566 DEBUG (MainThread) [custom_components.visonic] [Visonic Setup] CONF_PANEL_NUMBER not in configuration, defaulting to panel 0 (before uniqueness check)
2023-06-16 17:26:56.566 DEBUG (MainThread) [custom_components.visonic] [Visonic Setup] Panel Ident 0
2023-06-16 17:26:56.566 INFO (MainThread) [custom_components.visonic.client] Exclude sensor list = [] Exclude x10 list = [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15]
2023-06-16 17:26:56.566 DEBUG (MainThread) [custom_components.visonic] [Visonic Setup] Setting client ID for entry id cb41fb192910fd68fbce48b0f837a2d1
2023-06-16 17:27:49.947 WARNING (MainThread) [homeassistant.helpers.service] Unable to find referenced entities alarm_control_panel.visonic_alarm or it is/they are currently not available
reverting back to an old snapshot (VM running docker) works again with 0.8.2.4.
Any ideas?
Greetings,
Oliver
Hi, is that as far as it gets, is there any more in the log file?
I have an alarm panel (PowerMaster30) that I use to develop and test, I then deploy releases to Github/HACS and then use my proper house panel to get updates from HACS to make sure it works. Once, quite a while ago, I updated from HACS and I didn’t get all of the updated files, I never worked out why and it only happened once.
From your log file it looks like it’s got some of the new files but not all, can you make certain that you have all the files for the new release in the visonic directory and restart Home Assistant.
Hi Dave, sorry it took a while, havent had the time to look into it before now.
I tried the upgrade again, both trough HACS and also with manual updating alle files in the custom compontent directory, same result: The integration is no longer available.
When i look at the (debug) logs in the faulty situation (0.8.5.2) the visonic component entries stop after “Setting client ID for entry id cb41fb192910fd68fbce48b0f837a2d1”
2023-07-19 17:25:35.837 DEBUG (MainThread) [custom_components.visonic.pyvisonic] Initialising Protocol - Protocol Version 1.0.20.0
2023-07-19 17:25:35.842 DEBUG (MainThread) [custom_components.visonic.client] Initialising Client - Version 0.8.5.2
2023-07-19 17:25:35.847 INFO (MainThread) [homeassistant.setup] Setting up visonic
2023-07-19 17:25:35.847 INFO (MainThread) [custom_components.visonic] Starting Visonic Component
2023-07-19 17:25:35.847 INFO (MainThread) [homeassistant.setup] Setup of domain visonic took 0.0 seconds
2023-07-19 17:25:35.855 INFO (MainThread) [homeassistant.setup] Setup of domain automation took 0.4 seconds
2023-07-19 17:25:35.859 DEBUG (MainThread) [custom_components.visonic] [Visonic Setup] ************* create connection here **************
2023-07-19 17:25:35.859 INFO (MainThread) [custom_components.visonic] [Visonic Setup] Starting Visonic with entry id=cb41fb192910fd68fbce48b0f837a2d1 configured panels=1
2023-07-19 17:25:35.859 DEBUG (MainThread) [custom_components.visonic] [Visonic Setup] CONF_PANEL_NUMBER not in configuration, defaulting to panel 0 (before uniqueness check)
2023-07-19 17:25:35.859 DEBUG (MainThread) [custom_components.visonic] [Visonic Setup] Panel Ident 0
2023-07-19 17:25:35.859 INFO (MainThread) [custom_components.visonic.client] Exclude sensor list = [] Exclude x10 list = [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15]
2023-07-19 17:25:35.859 DEBUG (MainThread) [custom_components.visonic] [Visonic Setup] Setting client ID for entry id cb41fb192910fd68fbce48b0f837a2d1
When i revert to 0.8.2.4 every thing works again:
2023-07-20 10:52:46.059 DEBUG (MainThread) [custom_components.visonic.pyvisonic] Initialising Protocol - Protocol Version 1.0.17.2
2023-07-20 10:52:46.061 DEBUG (MainThread) [custom_components.visonic.client] Initialising Client - Version 0.8.2.4
2023-07-20 10:52:46.062 INFO (MainThread) [homeassistant.setup] Setting up visonic
2023-07-20 10:52:46.062 INFO (MainThread) [custom_components.visonic] Starting Visonic Component
2023-07-20 10:52:46.062 INFO (MainThread) [homeassistant.setup] Setup of domain visonic took 0.0 seconds
2023-07-20 10:52:46.064 DEBUG (MainThread) [custom_components.visonic] ************* create connection here **************
2023-07-20 10:52:46.064 INFO (MainThread) [custom_components.visonic] Starting Visonic with entry id=cb41fb192910fd68fbce48b0f837a2d1 configured panels=1
2023-07-20 10:52:46.065 DEBUG (MainThread) [custom_components.visonic] Panel Ident set up: panelident = 0 next auto panelident = 1
2023-07-20 10:52:46.065 DEBUG (MainThread) [custom_components.visonic.client] Exclude sensor list = [] Exclude x10 list = [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15]
2023-07-20 10:52:46.065 DEBUG (MainThread) [custom_components.visonic] Setting client ID for entry id cb41fb192910fd68fbce48b0f837a2d1
2023-07-20 10:52:46.066 DEBUG (MainThread) [custom_components.visonic.client] ........... attempting connection
2023-07-20 10:52:46.066 DEBUG (MainThread) [custom_components.visonic.client] Visonic Connection Device Type is ethernet {<PyConfiguration.DownloadCode: 0>: '', <PyConfiguration.ForceStandard: 9>: False, <PyConfiguration.ForceAutoEnroll: 1>: True, <PyConfiguration.AutoSyncTime: 2>: True, <PyConfiguration.PluginLanguage: 3>: 'EN', <PyConfiguration.MotionOffDelay: 4>: 120, <PyConfiguration.SirenTriggerList: 5>: ['intruder'], <PyConfiguration.B0_Enable: 6>: False, <PyConfiguration.B0_Min_Interval_Time: 7>: 5, <PyConfiguration.B0_Max_Wait_Time: 8>: 30}
2023-07-20 10:52:46.066 DEBUG (MainThread) [custom_components.visonic.pyvisonic] Setting TCP socket Options
2023-07-20 10:52:46.120 DEBUG (MainThread) [custom_components.visonic.pyvisonic] Buffer Flushed and Received some data!
2023-07-20 10:52:46.122 DEBUG (MainThread) [custom_components.visonic.pyvisonic] Initialising Protocol - Using Home Assistant Loop
2023-07-20 10:52:46.122 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [Settings] Force Standard set to False
2023-07-20 10:52:46.122 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [Settings] Force Auto Enroll set to True
2023-07-20 10:52:46.122 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [Settings] Force Auto Sync Time set to True
2023-07-20 10:52:46.122 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [Settings] Language set to EN
2023-07-20 10:52:46.122 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [Settings] Motion Off Delay set to 120
2023-07-20 10:52:46.122 DEBUG (MainThread) [custom_components.visonic..pyvisonic] [Settings] Siren Trigger List set to ['intruder']
2023-07-20 10:52:46.122 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [Settings] B0 Enable set to False
2023-07-20 10:52:46.122 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [Settings] B0 Min Interval set to 5
2023-07-20 10:52:46.122 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [Settings] B0 Max Wait Time set to 30
2023-07-20 10:52:46.125 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [Connection] Connected to local Protocol handler and Transport Layer
2023-07-20 10:52:46.125 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [_clearList] Setting queue empty
2023-07-20 10:52:46.125 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [StartDownload] Starting download mode
This happened in 2023.6, but now also in 2023.7. Its reproducable every time.
Regards,
Oliver
Hi,
Can you try installing 0.8.5.2 and then after you restart HA go into the Installer > Configure
Make sure these values are valid
And then restart HA again, if that doesn’t fix it then please show me the log file snipped again please.
D
Hi Dave,
There is something wrong with the GUI when I try to configure these settings after upgrading to 0.8.5.2:
Most text fields are missing somehow.
Besides that, I assumed the setting above the setting that had value “90” was the connection attempt number, so I changed that to 5. Now the integration works!
The textfields missing in the settings panel is still strange though.
Regards,
Oliver
I’m pleased that you finally got it working. However, by the look of the GUI I suspect that I have a problem with the GUI panel and that it might reveal a bug.
Can you please go in to the GUI settings again, change a value (say the 90 to 91) on the first GUI that looks wrong and then progress through the settings again so it saves the settings i.e. keep selecting “submit”. Then could you go in to the log file and upload that time segment please so I can take a look.
It would be good if you turned on debug, before you select Configure, turn on debug on this GUI at the bottom, unless you already have added the logger settings to your configuration.yaml and set to debug.
Hi Dav, first setting that is not showing text is actually the connection attempt setting. I edited it from 5 to 6, and back to 6. See the output of that timeframe below:
2023-07-24 09:54:01.114 WARNING (MainThread) [homeassistant.components.slide] Slide 2380 (246F28440400) is offline with code=500
2023-07-24 09:54:02.615 DEBUG (MainThread) [custom_components.visonic.config_flow] Visonic async_get_options_flow
2023-07-24 09:54:02.615 DEBUG (MainThread) [custom_components.visonic.config_flow] init cb41fb192910fd68fbce48b0f837a2d1 {'type': 'ethernet', 'host': '192.168.4.210', 'port': '23', 'language': 'EN', 'exclude_x10': [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15], 'force_standard': False, 'force_autoenroll': True, 'sync_time': True, 'download_code': '', 'exclude_sensor': [], 'motion_off': 120.0, 'siren_sounding': ['intruder'], 'panel_state_notifications': ['connectionproblem', 'sirensounding', 'paneltamper'], 'arm_without_usercode': False, 'force_numeric_keypad': False, 'arm_away_instant': False, 'arm_home_instant': False, 'allow_remote_arm': True, 'allow_remote_disarm': True, 'allow_sensor_bypass': False, 'override_code': '', 'panellog_logentry_event': True, 'panellog_complete_event': False, 'panellog_reverse_order': False, 'panellog_csv_add_title_row': False, 'panellog_xml_filename': 'visonic_log_file.xml', 'panellog_csv_filename': 'visonic_log_file.csv', 'panellog_max_entries': 10000, 'panelident': 0, 'retry_connection_count': 6.0, 'retry_connection_delay': 90.0, 'arm_home_enabled': True, 'arm_night_enabled': True}
2023-07-24 09:54:02.616 DEBUG (MainThread) [custom_components.visonic.config_flow] Edit config option settings, powermaster = False
2023-07-24 09:54:02.971 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [sendPdu] Resetting expected response counter, it got to 25 Response list is now 1
2023-07-24 09:54:02.971 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [sendPdu] Sending Command (Get Bypass Status) raw data 0d a2 00 00 20 00 00 00 00 00 00 00 43 f9 0a waiting for message response ['0XA5']
2023-07-24 09:54:03.028 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [handle_msgtype02] Ack Received data = 43
2023-07-24 09:54:03.028 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [data receiver] msgType 0XA5 got it so removed from list, list is now []
2023-07-24 09:54:03.028 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [data receiver] msgType 0XA5 resetting expected response counter, it got up to 0
2023-07-24 09:54:03.028 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [handle_msgtypeA5] Parsing A5 packet 00 06 03 de 03 00 00 00 00 00 43
2023-07-24 09:54:03.029 DEBUG (MainThread) [custom_components.visonic.pyvisonic] ================================================== Display Status ==================================================
2023-07-24 09:54:03.029 DEBUG (MainThread) [custom_components.visonic.pyvisonic] key 0 Sensor id=1 Zone=Z01 Type=Motion Loc=Front door ztypeName=Delay 1 ztamper=0 ztrip=0 bypass=0 lowbatt=0 status=0 tamper=0 enrolled=1 triggered=0
2023-07-24 09:54:03.029 DEBUG (MainThread) [custom_components.visonic.pyvisonic] key 1 Sensor id=2 Zone=Z02 Type=Motion Loc=Front door ztypeName=Perimeter ztamper=0 ztrip=0 bypass=0 lowbatt=0 status=0 tamper=0 enrolled=1 triggered=0
2023-07-24 09:54:03.029 DEBUG (MainThread) [custom_components.visonic.pyvisonic] key 9 Sensor id=10 Zone=Z10 Type=Motion Loc=Hall ztypeName=Home Delay ztamper=0 ztrip=0 bypass=0 lowbatt=0 status=0 tamper=0 enrolled=1 triggered=0
2023-07-24 09:54:03.029 DEBUG (MainThread) [custom_components.visonic.pyvisonic] key 10 Sensor id=11 Zone=Z11 Type=Motion Loc=Custom 2 ztypeName=Perimeter ztamper=0 ztrip=0 bypass=0 lowbatt=0 status=0 tamper=0 enrolled=1 triggered=0
2023-07-24 09:54:03.029 DEBUG (MainThread) [custom_components.visonic.pyvisonic] key 11 Sensor id=12 Zone=Z12 Type=Motion Loc=Custom 3 ztypeName=Perimeter ztamper=0 ztrip=0 bypass=0 lowbatt=0 status=0 tamper=0 enrolled=1 triggered=0
2023-07-24 09:54:03.029 DEBUG (MainThread) [custom_components.visonic.pyvisonic] key 12 Sensor id=13 Zone=Z13 Type=Motion Loc=Master bedroom ztypeName=Interior ztamper=0 ztrip=0 bypass=0 lowbatt=0 status=1 tamper=0 enrolled=1 triggered=0
2023-07-24 09:54:03.029 DEBUG (MainThread) [custom_components.visonic.pyvisonic] key 14 Sensor id=15 Zone=Z15 Type=Motion Loc=Play room ztypeName=Interior ztamper=0 ztrip=0 bypass=0 lowbatt=1 status=0 tamper=0 enrolled=1 triggered=0
2023-07-24 09:54:03.029 DEBUG (MainThread) [custom_components.visonic.pyvisonic] key 15 Sensor id=16 Zone=Z16 Type=Motion Loc=Upstairs ztypeName=Interior ztamper=0 ztrip=0 bypass=0 lowbatt=0 status=0 tamper=0 enrolled=1 triggered=0
2023-07-24 09:54:03.029 DEBUG (MainThread) [custom_components.visonic.pyvisonic] key 16 Sensor id=17 Zone=Z17 Type=Motion Loc=Child room ztypeName=Interior ztamper=0 ztrip=0 bypass=0 lowbatt=0 status=0 tamper=0 enrolled=1 triggered=0
2023-07-24 09:54:03.029 DEBUG (MainThread) [custom_components.visonic.pyvisonic] key 17 Sensor id=18 Zone=Z18 Type=Motion Loc=Garage door ztypeName=Non-Alarm ztamper=0 ztrip=0 bypass=0 lowbatt=0 status=1 tamper=0 enrolled=1 triggered=0
2023-07-24 09:54:03.029 DEBUG (MainThread) [custom_components.visonic.pyvisonic] Model PowerMax Pro Part PowerMaster No LastEvent None Ready No
2023-07-24 09:54:03.029 DEBUG (MainThread) [custom_components.visonic.pyvisonic] Mode Powerlink Status Disarmed Armed No Trouble None AlarmStatus None
2023-07-24 09:54:03.029 DEBUG (MainThread) [custom_components.visonic.pyvisonic] ====================================================================================================================
2023-07-24 09:54:03.121 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [sendPdu] Sending Command (Ack) raw data 0d 02 fd 0a waiting for message response []
2023-07-24 09:54:08.445 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [handle_msgtypeAB] data 03 00 1e 00 31 2e 30 36 00 00 43
2023-07-24 09:54:08.445 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [handle_msgtypeAB] ***************************** Got PowerLink Keep-Alive ****************************
2023-07-24 09:54:08.445 DEBUG (MainThread) [custom_components.visonic.pyvisonic] ================================================== Display Status ==================================================
2023-07-24 09:54:08.446 DEBUG (MainThread) [custom_components.visonic.pyvisonic] key 0 Sensor id=1 Zone=Z01 Type=Motion Loc=Front door ztypeName=Delay 1 ztamper=0 ztrip=0 bypass=0 lowbatt=0 status=0 tamper=0 enrolled=1 triggered=0
2023-07-24 09:54:08.446 DEBUG (MainThread) [custom_components.visonic.pyvisonic] key 1 Sensor id=2 Zone=Z02 Type=Motion Loc=Front door ztypeName=Perimeter ztamper=0 ztrip=0 bypass=0 lowbatt=0 status=0 tamper=0 enrolled=1 triggered=0
2023-07-24 09:54:08.446 DEBUG (MainThread) [custom_components.visonic.pyvisonic] key 9 Sensor id=10 Zone=Z10 Type=Motion Loc=Hall ztypeName=Home Delay ztamper=0 ztrip=0 bypass=0 lowbatt=0 status=0 tamper=0 enrolled=1 triggered=0
2023-07-24 09:54:08.446 DEBUG (MainThread) [custom_components.visonic.pyvisonic] key 10 Sensor id=11 Zone=Z11 Type=Motion Loc=Custom 2 ztypeName=Perimeter ztamper=0 ztrip=0 bypass=0 lowbatt=0 status=0 tamper=0 enrolled=1 triggered=0
2023-07-24 09:54:08.446 DEBUG (MainThread) [custom_components.visonic.pyvisonic] key 11 Sensor id=12 Zone=Z12 Type=Motion Loc=Custom 3 ztypeName=Perimeter ztamper=0 ztrip=0 bypass=0 lowbatt=0 status=0 tamper=0 enrolled=1 triggered=0
2023-07-24 09:54:08.446 DEBUG (MainThread) [custom_components.visonic.pyvisonic] key 12 Sensor id=13 Zone=Z13 Type=Motion Loc=Master bedroom ztypeName=Interior ztamper=0 ztrip=0 bypass=0 lowbatt=0 status=1 tamper=0 enrolled=1 triggered=0
2023-07-24 09:54:08.446 DEBUG (MainThread) [custom_components.visonic.pyvisonic] key 14 Sensor id=15 Zone=Z15 Type=Motion Loc=Play room ztypeName=Interior ztamper=0 ztrip=0 bypass=0 lowbatt=1 status=0 tamper=0 enrolled=1 triggered=0
2023-07-24 09:54:08.446 DEBUG (MainThread) [custom_components.visonic.pyvisonic] key 15 Sensor id=16 Zone=Z16 Type=Motion Loc=Upstairs ztypeName=Interior ztamper=0 ztrip=0 bypass=0 lowbatt=0 status=0 tamper=0 enrolled=1 triggered=0
2023-07-24 09:54:08.446 DEBUG (MainThread) [custom_components.visonic.pyvisonic] key 16 Sensor id=17 Zone=Z17 Type=Motion Loc=Child room ztypeName=Interior ztamper=0 ztrip=0 bypass=0 lowbatt=0 status=0 tamper=0 enrolled=1 triggered=0
2023-07-24 09:54:08.446 DEBUG (MainThread) [custom_components.visonic.pyvisonic] key 17 Sensor id=18 Zone=Z18 Type=Motion Loc=Garage door ztypeName=Non-Alarm ztamper=0 ztrip=0 bypass=0 lowbatt=0 status=1 tamper=0 enrolled=1 triggered=0
2023-07-24 09:54:08.446 DEBUG (MainThread) [custom_components.visonic.pyvisonic] Model PowerMax Pro Part PowerMaster No LastEvent None Ready No
2023-07-24 09:54:08.446 DEBUG (MainThread) [custom_components.visonic.pyvisonic] Mode Powerlink Status Disarmed Armed No Trouble None AlarmStatus None
2023-07-24 09:54:08.446 DEBUG (MainThread) [custom_components.visonic.pyvisonic] ====================================================================================================================
2023-07-24 09:54:08.447 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [sendPdu] Sending Command (Ack Long) raw data 0d 02 43 ba 0a waiting for message response []
2023-07-24 09:54:08.447 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [sendPdu] Resetting expected response counter, it got to 0 Response list is now 1
2023-07-24 09:54:08.598 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [sendPdu] Sending Command (I think this is an alive message to the panel) raw data 0d ab 0e 00 17 1e 00 03 03 01 04 00 43 c2 0a waiting for message response ['0X2']
2023-07-24 09:54:08.635 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [data receiver] msgType 0X2 got it so removed from list, list is now []
2023-07-24 09:54:08.635 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [data receiver] msgType 0X2 resetting expected response counter, it got up to 0
2023-07-24 09:54:08.635 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [handle_msgtype02] Ack Received data = 43
2023-07-24 09:54:11.893 DEBUG (MainThread) [custom_components.visonic.config_flow] Detected a powermax so not asking about B0 parameters
2023-07-24 09:54:11.894 DEBUG (MainThread) [custom_components.visonic] ************* update connection data **************
2023-07-24 09:54:11.894 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [Settings] Force Standard set to False
2023-07-24 09:54:11.894 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [Settings] Force Auto Enroll set to True
2023-07-24 09:54:11.895 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [Settings] Force Auto Sync Time set to True
2023-07-24 09:54:11.895 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [Settings] Language set to EN
2023-07-24 09:54:11.895 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [Settings] Motion Off Delay set to 120.0
2023-07-24 09:54:11.895 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [Settings] Siren Trigger List set to ['intruder']
2023-07-24 09:54:11.895 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [Settings] B0 Enable set to False
2023-07-24 09:54:11.895 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [Settings] B0 Min Interval set to 5
2023-07-24 09:54:11.895 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [Settings] B0 Max Wait Time set to 30
There’s nothing there that indictes badly formed data so I can’t see any problems.
In other words, I have no idea why the GUI is formatted badly.
Are you using the dark mode display? It may be this that’s the problem but that’s all within HA itself.
Hi Dave,
Question, is it possible to enable/disable the Chime function via Home assistant instead of using the keypad (powermax+) button 8? If so, can you tell me how i can do this?
Hi,
I’m relatively new to home automation, particularly when it comes to HomeAssistant. I’ve been using Smarthings and Visonic integration by cjcharles but that no longer works since Samsung have disabled the Groovy code.
The Visonic has been flashed 3-4 times now but I still see the same error messages in the logs:
- Error connecting to (‘192.168.1.110’, 6053): [Errno 113] Connect call failed (‘192.168.1.110’, 6053) (SocketAPIError)
- visonicinterface @ 192.168.1.110: Connection error occurred: Ping response not received after 90.0 seconds
I’ve reflashed the unit 3-4 times now and still get teh same issue even after following the wiki guide step my step. My panel is a Visonic Powermax complete.
Hi,
That’s OK and welcome, we all have to start somewhere.
So I need a bit more information from you so help me by answering a few questions.
When you say that you’ve flashed “The Visonic” I don’t know what you mean. My integration works differently to that of cjcharles, there’s nothing wrong with that, it’s just different.
His system puts the intelligence in a gadget that you put inside the Alarm Panel, this gadget has some software in it that makes it interact with the alarm panel.
My system puts this intelligence in the Home Assistant integration itself and the gadget in the alarm panel is pretty dumb. It just passes the data back and forth, between the alarm panel and the integration (both ways).
To be honest it works either way but I think that for the Home Assistant setup, having the intelligence part closely coupled with Home Assistant works better.
Anyway, back to your issue. You need a dumb gadget that just passes data back and forth installed inside the panel. As you have had this working before then I’ll assume that you have it wired correctly.
There are lots of different options for this dumb gadget but I assume that you have an ESP or Wemos D1 R2, is that correct? If you have a Wemos D1 R2 then please look here on the wiki. I haven’t tried this for a while but I assume it still works. You could use the ESPHome Home Assistant Integration to set it up and update it. Don’t forget to set up secrets.yaml
If you set it up like this then you should be able to open a command window / terminal / powershell and ping the IP address that you use. You should then be able to set up my integration in Home Assistant, use the network_ip and network_port that you put in the secrets.yaml.
You say that you used the wiki guide, is this the same as the wiki page I referred you to?
What step do you think it doesn’t work on?
Let me know how you get on and you have specific questions.
Dave
EDIT: I just took a closer look at my ESPHOME visonic.yaml script and noticed a difference. There’s been an ESPHome update and I haven’t updated the yaml files on the wiki. The HA info on this is here
In the version on the wiki it looks like this
api:
password: !secret device_password
# encryption:
# key: !secret esphome_encrypt
services:
In my ESPHOME it looks like this
# Enable Home Assistant API
api:
# password: !secret device_password
encryption:
key: !secret esphome_encrypt
services:
Change/Replace this in your yaml file
To generate a key go here
As it’s randomly generated I’ll show you what you could have in your secrets.yaml
Everytime you refresh your browser it creates a new key
esphome_encrypt: GHZm4c1iQxw4ChtLsBXg294pN9qdqreT4eaD6T+MkjM=
Hope this helps
Dave
Hi,
I’ve never come across this, sorry.
I include an attribute of the sensor that tells you what the chime setting is but I’ve not found a way to control it.
EDIT: Just to correct something I said. What I actually do is set the chime attribute of the sensor in Home Assistant when the panel EPROM is downloaded i.e. when the integration starts. It is not updated after that, so the user could change panel chime settings but the sensor attributes in HA will not be updated.
Apologies, I just realised how poorly I’ve explained the issue. I meant flashed the Wemos D1 R2 with ESPHome which is housed inside the alarm panel case.
I can complete all the steps apart from configuring powerlink as I don’t see that option on my panel. The log file does show the panel mode reaches Powerlink though and I can arm and disarm the panel using HA.
I did notice the difference about using API key Vs password and updated the yaml file accordingly.
The problem I’m facing is that I keep getting “unavailable” status in HA for the panel. This happens within a few minutes to a couple of hours.
I can ping the Wemos IP but I have to restart the visonic integration in HA to get it working again.
I even tried the recommendation of using a service to restart when HA shows the status as unavailable but doesn’t fix the problem.
Hope that helps.
A Powermax Complete should automatically enroll and get to Powerlink Mode and you do not need to manually enroll it from your panel (as defined here on the wiki).
As you’re getting to Powerlink Mode and then having problems I can only assume that it’s disconnecting somehow but without seeing a log file I have no further ideas. Can you set your log settings as per the wiki here and upload the log file with a link to it in a post here. If you zip it you may be able to attach it directly to the post.