A new release to Github 0.8.2.4. This is also a HACS release.
After following the HA instruction here to add the integration_type to the manifest file, this causes hassfest and the integration to fail. I have reported this in the development forums here.
This update simply removes the integration_type entry from the manifest file.
I upgraded trough hacs yesterday, and my intergration fails now, although I could not see this in my events. I just noticed all sensors being unavailable…I guess this is because of the hassfest issue? Is there an Easy way to fall back to another version? I can see the panel state btw…
I uploaded a release that removes the integration_type line from the manifest. Try updating through HACS again, it should be version 0.8.2.4. If you already have this version then capture and show me a log file please so I can take a proper look.
Ok, nevermind. This was not it. Apparently it is not a good idea to upgrade the integration when the panel is armed 
I did the upgrade while on vacation, since this never goes wrong normally. But when the panel is armed, the integration does not load properly. Its okay now after disarming and reloading.
OK, i’m just pleased that you got it sorted, i’ve never tried this before so i’m going to give it a go 
I’ve just bought a house with an ADT branded Visonic Powermax Express alarm with one MC-302 V PG2 W contact sensor and a number of PIR which I haven’t looked at yet to see which model (but I assume they are “Next PIR” (?))
I thought the easiest method - with limited experience - would be to use a UART, so I purchased a USB to TTL cable from Amazon which contains a prolific PL2303TA chip. I’ve connected it up to my panel using the information in this post
I can’t tell whether it has been picked up successfully by my Ubuntu server.
The output of lsusb is:
Bus 003 Device 006: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
sudo dmesg | grep tty gives:
[2378231.263324] usb 3-1: pl2303 converter now attached to ttyUSB1
stty -F /dev/ttyUSB1 -a gives:
speed 9600 baud; rows 0; columns 0; line = 0;
intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>;
eol2 = <undef>; swtch = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R;
werase = ^W; lnext = ^V; discard = ^O; min = 1; time = 0;
-parenb -parodd -cmspar cs8 hupcl -cstopb cread clocal -crtscts
-ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl ixon -ixoff
-iuclc -ixany -imaxbel -iutf8
opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0
isig icanon iexten echo echoe echok -echonl -noflsh -xcase -tostop -echoprt
echoctl echoke -flusho -extproc
I’ve installed the custom component in homeassistant but am consistently getting unable to connect errors:
Failed to connect into Visonic Alarm. Check Settings.
I enabled the logging and these are the entries related to the Visonic component:
2022-10-31 22:38:57.552 DEBUG (MainThread) [custom_components.visonic.pyvisonic] Initialising Protocol - Protocol Version 1.0.17.2
2022-10-31 22:38:57.554 DEBUG (MainThread) [custom_components.visonic.client] Initialising Client - Version 0.8.2.4
2022-10-31 22:38:57.556 INFO (MainThread) [custom_components.visonic] Starting Visonic Component
2022-10-31 22:38:57.563 DEBUG (MainThread) [custom_components.visonic] ************* create connection here **************
2022-10-31 22:38:57.563 INFO (MainThread) [custom_components.visonic] Starting Visonic with entry id=b1ce0a97f1e367fae206696e3ca73d01 configured panels=1
2022-10-31 22:38:57.563 DEBUG (MainThread) [custom_components.visonic] Panel Ident set up: panelident = 1 next auto panelident = 2
2022-10-31 22:38:57.563 DEBUG (MainThread) [custom_components.visonic.client] Exclude sensor list = [] Exclude x10 list = []
2022-10-31 22:38:57.563 DEBUG (MainThread) [custom_components.visonic] Setting client ID for entry id b1ce0a97f1e367fae206696e3ca73d01
2022-10-31 22:38:57.570 DEBUG (MainThread) [custom_components.visonic.client] ........... attempting connection
2022-10-31 22:38:57.570 DEBUG (MainThread) [custom_components.visonic.client] Visonic Connection Device Type is usb {<PyConfiguration.DownloadCode: 0>: '5650', <PyConfiguration.ForceStandard: 9>: True, <PyConfiguration.ForceAutoEnroll: 1>: True, <PyConfiguration.AutoSyncTime: 2>: True, <PyConfiguration.PluginLanguage: 3>: 'EN', <PyConfiguration.MotionOffDelay: 4>: 120.0, <PyConfiguration.SirenTriggerList: 5>: ['intruder'], <PyConfiguration.B0_Enable: 6>: False, <PyConfiguration.B0_Min_Interval_Time: 7>: 5, <PyConfiguration.B0_Max_Wait_Time: 8>: 30}
2022-10-31 22:38:57.572 DEBUG (MainThread) [custom_components.visonic.pyvisonic] Setting USB Options
2022-10-31 22:39:00.404 DEBUG (MainThread) [custom_components.visonic.pyvisonic] Waiting for Protocol Handler to Start
2022-10-31 22:39:01.442 DEBUG (MainThread) [custom_components.visonic.pyvisonic] Waiting for Protocol Handler to Start
2022-10-31 22:39:02.701 DEBUG (MainThread) [custom_components.visonic.pyvisonic] Waiting for Protocol Handler to Start
2022-10-31 22:39:03.703 DEBUG (MainThread) [custom_components.visonic.pyvisonic] Waiting for Protocol Handler to Start
2022-10-31 22:39:04.704 WARNING (MainThread) [custom_components.visonic.client] Failed to connect into Visonic Alarm. Check Settings.
2022-10-31 22:39:04.705 DEBUG (MainThread) [custom_components.visonic.client] ........... Closing down Current Task
I’ve got a number of “Troubles” with the panel which I’m struggling to solve and do not want to have to get an engineer to fix. I’m hoping to either get the panel integrated in home assistant or bin the whole system.
Annoyingly, I don’t have the installer code and I’ve tried all the default codes I can find. The last thing to try is a power cycle so see what that clears, but it’s late and my wife & child wouldn’t thank me if I trip the system at 11pm!
Any help you can give me would be much appreciated! If it helps I can reel off some of the trouble codes. I was wondering if I need to clear all of these before the panel will integrate?
Hello,
It was running smoothly since last year (and the last summer-winter change) and last week-end I lost the connection again because of the summer-winter time change.
I am using an “old” version 0.7.0.1 (because everything was running correctly, I haven’t upgraded in a while).
Here are the logs:
2022-10-30 02:06:13.944 DEBUG (MainThread) [custom_components.visonic.client] No Code Required as powerlink or std plus ********
2022-10-30 02:06:43.945 DEBUG (MainThread) [custom_components.visonic.client] No Code Required as powerlink or std plus ********
2022-10-30 02:07:01.735 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [Controller] ****************************** WatchDog Timer Expired ********************************
2022-10-30 02:07:01.736 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [Controller] ******************* Trigger Restore Status *******************
2022-10-30 02:07:01.736 DEBUG (MainThread) [custom_components.visonic.client] Visonic update event 9 {'condition': 9}
2022-10-30 02:07:01.736 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [_clearList] Setting queue empty
2022-10-30 02:07:01.737 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [Controller] Watchdog counter array, current=2
2022-10-30 02:07:01.737 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [Controller] [86160, 86280, 86400, 0, 0, 0, 0, 0, 0, 0]
2022-10-30 02:07:01.772 DEBUG (MainThread) [custom_components.visonic.client] No Code Required as powerlink or std plus ********
2022-10-30 02:07:13.946 DEBUG (MainThread) [custom_components.visonic.client] No Code Required as powerlink or std plus ********
2022-10-30 02:07:43.947 DEBUG (MainThread) [custom_components.visonic.client] No Code Required as powerlink or std plus ********
2022-10-30 02:08:13.947 DEBUG (MainThread) [custom_components.visonic.client] No Code Required as powerlink or std plus ********
2022-10-30 02:08:43.949 DEBUG (MainThread) [custom_components.visonic.client] No Code Required as powerlink or std plus ********
2022-10-30 02:09:01.913 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [Controller] ****************************** WatchDog Timer Expired ********************************
2022-10-30 02:09:01.913 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [Controller] ******************* Trigger Restore Status *******************
2022-10-30 02:09:01.916 DEBUG (MainThread) [custom_components.visonic.client] Visonic update event 9 {'condition': 9}
2022-10-30 02:09:01.916 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [_clearList] Setting queue empty
2022-10-30 02:09:01.917 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [Controller] Watchdog counter array, current=3
2022-10-30 02:09:01.917 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [Controller] [86040, 86160, 86280, 86400, 0, 0, 0, 0, 0, 0]
2022-10-30 02:09:01.952 DEBUG (MainThread) [custom_components.visonic.client] No Code Required as powerlink or std plus ********
2022-10-30 02:09:13.950 DEBUG (MainThread) [custom_components.visonic.client] No Code Required as powerlink or std plus ********
2022-10-30 02:09:43.952 DEBUG (MainThread) [custom_components.visonic.client] No Code Required as powerlink or std plus ********
2022-10-30 02:10:13.953 DEBUG (MainThread) [custom_components.visonic.client] No Code Required as powerlink or std plus ********
2022-10-30 02:10:40.055 ERROR (MainThread) [custom_components.visonic.pyvisonic] [Controller] Visonic Plugin has suspended all operations, there is a problem with the communication with the panel (i.e. data has not been received from the panel in 600 seconds)
2022-10-30 02:10:40.059 DEBUG (MainThread) [custom_components.visonic.client] Visonic update event 10 {'condition': 10}
2022-10-30 02:10:40.097 DEBUG (MainThread) [custom_components.visonic.client] No Code Required as code set in config
2022-10-30 02:59:14.077 DEBUG (MainThread) [custom_components.visonic.client] No Code Required as code set in config
2022-10-30 02:59:34.896 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [sendPdu] Sending Command (Ack Long) raw data 0d 02 43 ba 0a waiting for message response []
2022-10-30 02:59:35.046 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [sendPdu] Sending Command (Ack Long) raw data 0d 02 43 ba 0a waiting for message response []
2022-10-30 02:59:35.198 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [sendPdu] Sending Command (Ack Long) raw data 0d 02 43 ba 0a waiting for message response []
2022-10-30 02:59:35.350 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [sendPdu] Sending Command (Ack Long) raw data 0d 02 43 ba 0a waiting for message response []
2022-10-30 02:59:35.502 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [sendPdu] Sending Command (Ack Long) raw data 0d 02 43 ba 0a waiting for message response []
2022-10-30 02:59:35.653 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [sendPdu] Sending Command (Ack Long) raw data 0d 02 43 ba 0a waiting for message response []
2022-10-30 02:59:35.804 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [sendPdu] Sending Command (Ack Long) raw data 0d 02 43 ba 0a waiting for message response []
2022-10-30 02:59:35.956 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [sendPdu] Sending Command (Ack Long) raw data 0d 02 43 ba 0a waiting for message response []
2022-10-30 02:59:36.107 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [sendPdu] Sending Command (Ack Long) raw data 0d 02 43 ba 0a waiting for message response []
2022-10-30 02:59:36.258 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [sendPdu] Sending Command (Ack Long) raw data 0d 02 43 ba 0a waiting for message response []
2022-10-30 02:59:36.410 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [sendPdu] Sending Command (Ack Long) raw data 0d 02 43 ba 0a waiting for message response []
2022-10-30 02:59:36.561 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 []
2022-10-30 02:59:36.562 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [sendPdu] Resetting expected response counter, it got to 97 Response list length before 0 after 1
2022-10-30 02:59:36.562 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [sendPdu] Suspended all operations, not sending PDU
Perhaps this issue was already solved with 0.8.2.4 ?
I’ll have to wait for next year to be sure.
I can help with that if we can connect and download the EPROM from the panel.
Lets check wiring first. I assume that you have only connected 3 of the 4 wires on that cable i.e. Gnd, Rx and Tx. Do not connect the 5v cable. Have you crossed Rx and Tx? e.g. the white TXD of the cable to Rx on the black panel connector and the green RXD connector to the Tx on the black panel connector.
This is where I need to know how clever you are with computers, forgive me for being blunt. I assume that as you’re using Linux you can do the following. Forget about HomeAssistant for now. Download my integration as a zip file from Github and unzip it. Go in to the examples subdirectory and follow the guide on the wiki here. Check the version of python on your system
python3 --version
This should be at least Python 3.9.X I think
Then I suggest that you type:
pip3 install -r requirements.txt
python3 complete_example.py -usb /dev/ttyUSB1
Remember to click in the bottom box of the aconsole and type “c” return.
Let me know how you get on with this and get back to me here if you have questions…
EDIT: The only other thing that it might be is that the cable you’ve bought is 5v and the TTL levels of the panel are 3.75. You may need a level shifter.
This has been resolved, I can’t remember in which release. The Integration now uses 2 time sources. UTC time for all time calculations and time offsets. Local time to provide dates and times for when sensors are triggered etc. So the fact that it uses UTC time means that its OK, in fact mine worked across the time change last weekend.
I removed the red cable (5V) that I’d erroneously added, double checked that the TX and RX were in the right pins (they were).
I ran the python script - my computer skills are enough to debug this, but I’m lacking in figuring out interfacing issues like this.
The output of the script does not look promising…
python3 complete_example.py -usb /dev/ttyUSB1
Starting
General Exception
Goodbye cruel world
If you think it is my cable that is an issue, would you mind recommending something more appropriate to use? I have no experience with ESP32, Wemos etc so I’m more baffled there. The USB approached seemed the most straightforward as I’ve been able to relocate the alarm box into my office right next to my server.
I’ve tried to follow the wiki as best as possible. I have a Raspberry Pi W going spare if you think this might be more appropriate, but I couldn’t get my inexperienced head around what to do with the Wemos D1 for example.
On a side note I cleared all the troubles on the panel so it’s not that preventing it coming in to HA.
If complete_example exits with a general exception then chances are you’re using the wrong linux device. The problem I have is that I’ve never used it on linux, only windows. When you look in /dev does the device exist.
If you have a windows 10/11 PC then plug the USB cable in. Go to device manager and it should appear as a device in “Ports (COM & LPT)”, note down the COM number e.g.COM5
Install python3, install the library requirements (as per my previous post) and run complete_example like this from a Powershell window
python3 .\complete_example.py -usb \\.COM5\
To test it, one thing to try is my “loopback” test here on the wiki. Disconnect all cables from your panel and connect Rx to Tx on the USB cable you have. Run complete_example in the same way that you are, in the output log (in the Powershell window) you should see
[handle_msgtype0F] LOOPBACK TEST SUCCESS, Counter is 2
Where the counter value increments about every 5 seconds.
Thanks for the help. I don’t have access to a Windows PC where I can try this - only my locked down work laptop. After some digging on Ubuntu it’s just not picking up the device even though the drivers are installed.
I think the cable is the issue. I’m returning it and trying something that looks more suitable with 3.3V as standard. I’ll see how that goes and report back.
Just one question though - you said about reversing TX and RX - is it TX on the USB to TX on the alarm, or should it be TX on the USB to RX on the panel?
Connect Gnd to Gnd. Tx on the cable to Rx on the panel connector and Rx on the cable to Tx on the panel. If you are not using power from the panel to power the interface gadget then do not connect the Vcc (i.e. 5 volts / 3.3 volts). If you want to try the loopback test then ignore the panel and Tx to Rx on the cable itself.
Hi,
I should have done this a month ago but can you support my WTH by voting for it please, it this here
Love your integration, thank you for the work.
One thing that I would like to solve, is that sometimes, I suspect after powerloss or something, the panel appear “unavailable”.
The soution to solve it is simple press the reload integration, nothing else required.
Is that known issue ? couldn’t find here something like.
Using Powermax Pro
Hi, there’s a troubleshooting section on the wiki here but if that doesn’t help then create a log file with the settings here and upload part of the log file for me to take a look. As it occurs randomly, I just need the part of the log file that shows the disconnection, say 20 or 30 lines before it.
1 Like
I double checked all my wiring and bought a new USB to TTL device based on the CP2102 chip. TTYUSB1 now appears as a device in Ubuntu, but I still get the same general exception.
Has anyone got any experience with interfacing the Powermax Express to HA via USB? I assumed this would be the simplest method for me, but its looking more likely I’m going to need to try something down the Wemos route - but I’m thinking if I can’t use USB its fruitless with this panel to try anything else.
I found my mistake! I’m running HA in docker, and I wasn’t passing the device through to the container, so I went in and added /dev/ttyUSB1 to the compose file, fired everything up and now I have a Visonic panel appearing in HA along with a door sensor and three Next PG2 PIRs. Now that I’ve got this far I can try and figure out how to get everything else in, or whether it is purely a limitation of the panel.
Hello,
I’m trying to set up my PowerMaxPro with Wemos D1 R2. I successfully flashed the Wemos board and installed visonic_interface in HA. Communication with the board is OK, I can turn off and on the onboard LED. I connected RX, TX and ground signals between panel and Wemos. However I am stuck in integration installation, it fails to connect to the panel. Here is the log
2022-11-19 15:11:22.187 ERROR (MainThread) [homeassistant.config_entries] Error unloading entry Panel 3 for switch
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 496, in async_unload
result = await component.async_unload_entry(hass, self)
File "/usr/src/homeassistant/homeassistant/components/switch/__init__.py", line 87, in async_unload_entry
return await component.async_unload_entry(entry)
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 172, in async_unload_entry
raise ValueError("Config entry was never loaded!")
ValueError: Config entry was never loaded!
2022-11-19 15:11:22.188 DEBUG (MainThread) [custom_components.visonic.client] ........... Closing down Current Task
2022-11-19 15:11:24.189 DEBUG (MainThread) [custom_components.visonic.client] ........... Current Task Done
2022-11-19 15:11:24.190 DEBUG (MainThread) [custom_components.visonic] ************* terminate connection success **************
2022-11-19 15:11:24.190 DEBUG (MainThread) [custom_components.visonic] ************* create connection here **************
2022-11-19 15:11:24.190 INFO (MainThread) [custom_components.visonic] Starting Visonic with entry id=cc759e1211a75877fd95c9d23e05ee92 configured panels=1
2022-11-19 15:11:24.190 DEBUG (MainThread) [custom_components.visonic] Panel Ident set up: panelident = 3 next auto panelident = 4
2022-11-19 15:11:24.190 DEBUG (MainThread) [custom_components.visonic.client] Exclude sensor list = [] Exclude x10 list = []
2022-11-19 15:11:24.190 DEBUG (MainThread) [custom_components.visonic] Setting client ID for entry id cc759e1211a75877fd95c9d23e05ee92
2022-11-19 15:11:24.191 DEBUG (MainThread) [custom_components.visonic.client] ........... attempting connection
2022-11-19 15:11:24.192 DEBUG (MainThread) [custom_components.visonic.client] Visonic Connection Device Type is ethernet {<PyConfiguration.DownloadCode: 0>: 'AAAA', <PyConfiguration.ForceStandard: 9>: False, <PyConfiguration.ForceAutoEnroll: 1>: False, <PyConfiguration.AutoSyncTime: 2>: True, <PyConfiguration.PluginLanguage: 3>: 'EN', <PyConfiguration.MotionOffDelay: 4>: 120.0, <PyConfiguration.SirenTriggerList: 5>: ['intruder'], <PyConfiguration.B0_Enable: 6>: False, <PyConfiguration.B0_Min_Interval_Time: 7>: 5, <PyConfiguration.B0_Max_Wait_Time: 8>: 30}
2022-11-19 15:11:24.192 DEBUG (MainThread) [custom_components.visonic.pyvisonic] Setting TCP socket Options
2022-11-19 15:11:25.201 DEBUG (MainThread) [custom_components.visonic.pyvisonic] Initialising Protocol - Using Home Assistant Loop
2022-11-19 15:11:25.201 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [Settings] Force Standard set to False
2022-11-19 15:11:25.201 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [Settings] Force Auto Enroll set to False
2022-11-19 15:11:25.201 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [Settings] Force Auto Sync Time set to True
2022-11-19 15:11:25.201 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [Settings] Download Code set to AA AA
2022-11-19 15:11:25.201 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [Settings] Language set to EN
2022-11-19 15:11:25.201 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [Settings] Motion Off Delay set to 120.0
2022-11-19 15:11:25.201 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [Settings] Siren Trigger List set to ['intruder']
2022-11-19 15:11:25.201 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [Settings] B0 Enable set to False
2022-11-19 15:11:25.201 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [Settings] B0 Min Interval set to 5
2022-11-19 15:11:25.201 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [Settings] B0 Max Wait Time set to 30
2022-11-19 15:11:25.203 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [Connection] Connected to local Protocol handler and Transport Layer
2022-11-19 15:11:25.203 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [_clearList] Setting queue empty
2022-11-19 15:11:25.203 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [StartDownload] Starting download mode
2022-11-19 15:11:25.204 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [sendPdu] Sending Command (Exit) raw data 0d 0f f0 0a waiting for message response []
2022-11-19 15:11:25.204 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [sendPdu] Command has a wait time after transmission 1.5
2022-11-19 15:11:25.204 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [Controller] download_counter is 1
2022-11-19 15:11:25.227 ERROR (MainThread) [custom_components.visonic.pyvisonic] ERROR Connection Lost : disconnected because the Ethernet/USB connection was externally terminated.
2022-11-19 15:11:25.228 ERROR (MainThread) [custom_components.visonic.pyvisonic] ERROR Connection Lost : disconnected due to exception [Errno 104] Connection reset by peer
2022-11-19 15:11:30.234 ERROR (MainThread) [custom_components.visonic.pyvisonic] No Exception handler to call, terminating Component......
2022-11-19 15:11:30.237 DEBUG (MainThread) [custom_components.visonic.client] ........... connection made
2022-11-19 15:11:30.238 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [sendPdu] Suspended all operations, not sending PDU
2022-11-19 15:11:30.238 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [sendPdu] Resetting expected response counter, it got to 1 Response list length before 0 after 1
2022-11-19 15:11:30.238 DEBUG (MainThread) [custom_components.visonic.pyvisonic] [sendPdu] Suspended all operations, not sending PDU
What could be the problem?
BTW is it mandatory to specify the port in secrets.yaml? I didn’t do it and got default port 6053
Hi,
Looking at panelident = 3 in your log file you are trying to install your 3rd panel. Assuming that you only have 1 panel please delete the integration (probably multiple times) to remove it completely from HA and start again using the default panel 0. There are currently multiple instances of the integration trying to access the same address and port which could be your problem. It’s also confusing in the log file as the multiple instances all write to the log file so I can’t really tell what’s going on. I did notice however that the integration does try to send data to the panel but it receives nothing back. I’d suggest to check your wiring. Are you connecting Rx to Tx and Tx to Rx? I know it’s obvious but I’ve gotta check.
If you still have problems then try the loopback test as described on the wiki here. i.e. connect Tx to Rx on the Wemos, set the HA logger settings and look in the HA log file for LOOPBACK TEST SUCCESS, Counter is ....
If you still have problems then upload another log file and I’ll take a look.
Yes and use the same IP address and port when you install the integration in HA.
Ports 6052 and 6053 are something to do with ESPHome itself so do not use them.
Regards