Connect my Powermaster-30 to HA with NodeMCU

[jeanmilopez]

Hello,
I plan to connect my POWERMASTER-30 alarm to HA by following the wiki. I intend to follow the instructions provided (tutorial: Using NodeMCU PowermaxProModel6).

However, I'm not sure about the pin connections between the alarm and the NodeMCU.

Can I proceed as shown in the wiki? Here is a photo of the alarm's pins. I searched online but couldn't find any documentation describing the pins.

Could you help me? Thank you.

[davesmeghead]

Yes, the pins are as shown on the wiki, it's the same connector as the "IP" 10 pin IDC connector in your top diagram.
https://github.com/davesmeghead/visonic/wiki/Hardware-Setup

[jeanmilopez]

Thank you for your answer.
Today I will connect it to the NodeMCU.

Can you confirm that the connections are good? I based it on your photos but I'm not sure for TX and RX...

[jeanmilopez]

Hello,

I did the configuration of the ESP8266, the connections of the ESP8266 to the powermaster-30, integrated the Visonic plugin in HACS and followed the parameter entry. I chose the standard mode.

For the moment the alarm is unavailable.

Could you help me to solve the problems?
Otherwise, can we debug by validating certain steps such as, for example, the connection to the alarm is correct...

Here are some logs of HA-core:

2025-01-21 20:19:39.875 WARNING (ImportExecutor_0) [homeassistant.const] STATE_ALARM_ARMED_AWAY was used from visonic, this is a deprecated constant which will be removed in HA Core 2025.11. Use AlarmControlPanelState.ARMED_AWAY instead, please report it to the author of the 'visonic' custom integration
2025-01-21 20:19:39.904 WARNING (ImportExecutor_0) [homeassistant.const] STATE_ALARM_ARMED_HOME was used from visonic, this is a deprecated constant which will be removed in HA Core 2025.11. Use AlarmControlPanelState.ARMED_HOME instead, please report it to the author of the 'visonic' custom integration
2025-01-21 20:19:39.926 WARNING (ImportExecutor_0) [homeassistant.const] STATE_ALARM_ARMING was used from visonic, this is a deprecated constant which will be removed in HA Core 2025.11. Use AlarmControlPanelState.ARMING instead, please report it to the author of the 'visonic' custom integration
2025-01-21 20:19:39.950 WARNING (ImportExecutor_0) [homeassistant.const] STATE_ALARM_DISARMED was used from visonic, this is a deprecated constant which will be removed in HA Core 2025.11. Use AlarmControlPanelState.DISARMED instead, please report it to the author of the 'visonic' custom integration
2025-01-21 20:19:39.985 WARNING (ImportExecutor_0) [homeassistant.const] STATE_ALARM_PENDING was used from visonic, this is a deprecated constant which will be removed in HA Core 2025.11. Use AlarmControlPanelState.PENDING instead, please report it to the author of the 'visonic' custom integration
2025-01-21 20:19:40.011 WARNING (ImportExecutor_0) [homeassistant.const] STATE_ALARM_TRIGGERED was used from visonic, this is a deprecated constant which will be removed in HA Core 2025.11. Use AlarmControlPanelState.TRIGGERED instead, please report it to the author of the 'visonic' custom integration
2025-01-21 20:34:34.661 WARNING (ImportExecutor_0) [homeassistant.const] STATE_ALARM_ARMED_AWAY was used from visonic, this is a deprecated constant which will be removed in HA Core 2025.11. Use AlarmControlPanelState.ARMED_AWAY instead, please report it to the author of the 'visonic' custom integration
2025-01-21 20:34:34.693 WARNING (ImportExecutor_0) [homeassistant.const] STATE_ALARM_ARMED_HOME was used from visonic, this is a deprecated constant which will be removed in HA Core 2025.11. Use AlarmControlPanelState.ARMED_HOME instead, please report it to the author of the 'visonic' custom integration
2025-01-21 20:34:34.713 WARNING (ImportExecutor_0) [homeassistant.const] STATE_ALARM_ARMING was used from visonic, this is a deprecated constant which will be removed in HA Core 2025.11. Use AlarmControlPanelState.ARMING instead, please report it to the author of the 'visonic' custom integration
2025-01-21 20:34:34.734 WARNING (ImportExecutor_0) [homeassistant.const] STATE_ALARM_DISARMED was used from visonic, this is a deprecated constant which will be removed in HA Core 2025.11. Use AlarmControlPanelState.DISARMED instead, please report it to the author of the 'visonic' custom integration
2025-01-21 20:34:34.754 WARNING (ImportExecutor_0) [homeassistant.const] STATE_ALARM_PENDING was used from visonic, this is a deprecated constant which will be removed in HA Core 2025.11. Use AlarmControlPanelState.PENDING instead, please report it to the author of the 'visonic' custom integration
2025-01-21 20:34:34.774 WARNING (ImportExecutor_0) [homeassistant.const] STATE_ALARM_TRIGGERED was used from visonic, this is a deprecated constant which will be removed in HA Core 2025.11. Use AlarmControlPanelState.TRIGGERED instead, please report it to the author of the 'visonic' custom integration
2025-01-21 20:34:59.490 ERROR (MainThread) [custom_components.visonic.pyvisonic] [_sequencer] Visonic Plugin has suspended all operations, there is a problem with the communication with the panel (i.e. no data has been received from the panel)
2025-01-21 20:59:00.602 WARNING (ImportExecutor_0) [homeassistant.const] STATE_ALARM_ARMED_AWAY was used from visonic, this is a deprecated constant which will be removed in HA Core 2025.11. Use AlarmControlPanelState.ARMED_AWAY instead, please report it to the author of the 'visonic' custom integration
2025-01-21 20:59:00.632 WARNING (ImportExecutor_0) [homeassistant.const] STATE_ALARM_ARMED_HOME was used from visonic, this is a deprecated constant which will be removed in HA Core 2025.11. Use AlarmControlPanelState.ARMED_HOME instead, please report it to the author of the 'visonic' custom integration
2025-01-21 20:59:00.653 WARNING (ImportExecutor_0) [homeassistant.const] STATE_ALARM_ARMING was used from visonic, this is a deprecated constant which will be removed in HA Core 2025.11. Use AlarmControlPanelState.ARMING instead, please report it to the author of the 'visonic' custom integration
2025-01-21 20:59:00.672 WARNING (ImportExecutor_0) [homeassistant.const] STATE_ALARM_DISARMED was used from visonic, this is a deprecated constant which will be removed in HA Core 2025.11. Use AlarmControlPanelState.DISARMED instead, please report it to the author of the 'visonic' custom integration
2025-01-21 20:59:00.691 WARNING (ImportExecutor_0) [homeassistant.const] STATE_ALARM_PENDING was used from visonic, this is a deprecated constant which will be removed in HA Core 2025.11. Use AlarmControlPanelState.PENDING instead, please report it to the author of the 'visonic' custom integration
2025-01-21 20:59:00.710 WARNING (ImportExecutor_0) [homeassistant.const] STATE_ALARM_TRIGGERED was used from visonic, this is a deprecated constant which will be removed in HA Core 2025.11. Use AlarmControlPanelState.TRIGGERED instead, please report it to the author of the 'visonic' custom integration
2025-01-21 20:59:00.755 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'visonic' is setting state directly. Entity None (<class 'custom_components.visonic.alarm_control_panel.VisonicAlarm'>) should implement the 'alarm_state' property and return its state using the AlarmControlPanelState enum at custom_components/visonic/alarm_control_panel.py, line 57: async_add_entities(entities, True). This will stop working in Home Assistant 2025.11, please create a bug report at https://github.com/davesmeghead/visonic/issues
2025-01-21 20:59:25.565 ERROR (MainThread) [custom_components.visonic.pyvisonic] [_sequencer] Visonic Plugin has suspended all operations, there is a problem with the communication with the panel (i.e. no data has been received from the panel)
2025-01-21 21:03:07.524 ERROR (MainThread) [custom_components.visonic.diagnostics] async_get_config_entry_diagnostics {'created_at': '2025-01-21T19:58:59.347616+00:00', 'data': {'panel_number': 0, 'type': 'ethernet', 'host': 'XXX.XXX.X.XX 'port': '23', 'path': '', 'baud': 9600, 'emulation_mode': 'Standard', 'download_code': '5650', 'show_eeprom_attributes': True, 'exclude_x10': [], 'exclude_sensor': [], 'siren_sounding': ['intruder'], 'panel_state_notifications': ['connection_problem', 'siren_sounding'], 'sensor_event_list': ['problem'], 'retry_connection_count': 1.0, 'retry_connection_delay': 90.0, 'motion_off_delay': 120.0, 'magnet_closed_delay': 5.0, 'emergency_off_delay': 120.0, 'arm_without_usercode': False, 'force_numeric_keypad': False, 'arm_home_enabled': False, 'arm_night_enabled': False, 'arm_away_instant': False, 'arm_home_instant': False, 'allow_remote_arm': True, 'allow_remote_disarm': True, 'allow_sensor_bypass': False, '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}, 'discovery_keys': {}, 'disabled_by': None, 'domain': 'visonic', 'entry_id': '01JJ574R8KY4XE8230ADRFN0GV', 'minor_version': 1, 'modified_at': '2025-01-21T19:58:59.348963+00:00', 'options': {'panel_number': 0, 'type': 'ethernet', 'host': 'XXX.XXX.XX.XX', 'port': '23', 'path': '', 'baud': 9600, 'emulation_mode': 'Standard', 'download_code': '5650', 'show_eeprom_attributes': True, 'exclude_x10': [], 'exclude_sensor': [], 'siren_sounding': ['intruder'], 'panel_state_notifications': ['connection_problem', 'siren_sounding'], 'sensor_event_list': ['problem'], 'retry_connection_count': 1.0, 'retry_connection_delay': 90.0, 'motion_off_delay': 120.0, 'magnet_closed_delay': 5.0, 'emergency_off_delay': 120.0, 'arm_without_usercode': False, 'force_numeric_keypad': False, 'arm_home_enabled': False, 'arm_night_enabled': False, 'arm_away_instant': False, 'arm_home_instant': False, 'allow_remote_arm': True, 'allow_remote_disarm': True, 'allow_sensor_bypass': False, '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}, 'pref_disable_new_entities': False, 'pref_disable_polling': False, 'source': 'user', 'title': 'Panel 0', 'unique_id': 'Visonic Alarm Panel 0', 'version': 4} {'Disconnection Count': 0}
2025-01-21 21:07:42.291 ERROR (MainThread) [custom_components.visonic.diagnostics] async_get_config_entry_diagnostics {'created_at': '2025-01-21T19:58:59.347616+00:00', 'data': {'panel_number': 0, 'type': 'ethernet', 'host': 'XXX.XXX.XX.XX'', 'port': '23', 'path': '', 'baud': 9600, 'emulation_mode': 'Standard', 'download_code': '5650', 'show_eeprom_attributes': True, 'exclude_x10': [], 'exclude_sensor': [], 'siren_sounding': ['intruder'], 'panel_state_notifications': ['connection_problem', 'siren_sounding'], 'sensor_event_list': ['problem'], 'retry_connection_count': 1.0, 'retry_connection_delay': 90.0, 'motion_off_delay': 120.0, 'magnet_closed_delay': 5.0, 'emergency_off_delay': 120.0, 'arm_without_usercode': False, 'force_numeric_keypad': False, 'arm_home_enabled': False, 'arm_night_enabled': False, 'arm_away_instant': False, 'arm_home_instant': False, 'allow_remote_arm': True, 'allow_remote_disarm': True, 'allow_sensor_bypass': False, '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}, 'discovery_keys': {}, 'disabled_by': None, 'domain': 'visonic', 'entry_id': '01JJ574R8KY4XE8230ADRFN0GV', 'minor_version': 1, 'modified_at': '2025-01-21T19:58:59.348963+00:00', 'options': {'panel_number': 0, 'type': 'ethernet', 'host': 'XXX.XXX.XX.XX', 'port': '23', 'path': '', 'baud': 9600, 'emulation_mode': 'Standard', 'download_code': '5650', 'show_eeprom_attributes': True, 'exclude_x10': [], 'exclude_sensor': [], 'siren_sounding': ['intruder'], 'panel_state_notifications': ['connection_problem', 'siren_sounding'], 'sensor_event_list': ['problem'], 'retry_connection_count': 1.0, 'retry_connection_delay': 90.0, 'motion_off_delay': 120.0, 'magnet_closed_delay': 5.0, 'emergency_off_delay': 120.0, 'arm_without_usercode': False, 'force_numeric_keypad': False, 'arm_home_enabled': False, 'arm_night_enabled': False, 'arm_away_instant': False, 'arm_home_instant': False, 'allow_remote_arm': True, 'allow_remote_disarm': True, 'allow_sensor_bypass': False, '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}, 'pref_disable_new_entities': False, 'pref_disable_polling': False, 'source': 'user', 'title': 'Panel 0', 'unique_id': 'Visonic Alarm Panel 0', 'version': 4} {'Disconnection Count': 0}
2025-01-21 21:10:05.757 ERROR (MainThread) [homeassistant.components.hassio] Failed to to call /addons/core_ssh/start - Another job is running for job group addon_core_ssh
2025-01-21 21:11:52.440 WARNING (MainThread) [homeassistant.helpers.service] Referenced entities alarm_control_panel.visonic_alarm are missing or not currently available

The configuration :

{
"home_assistant": {
"installation_type": "Home Assistant OS",
"version": "2025.1.2",
"dev": false,
"hassio": true,
"virtualenv": false,
"python_version": "3.13.1",
"docker": true,
"arch": "aarch64",
"timezone": "Europe/Paris",
"os_name": "Linux",
"os_version": "6.6.62-haos-raspi",
"supervisor": "2024.12.3",
"host_os": "Home Assistant OS 14.1",
"docker_version": "27.2.0",
"chassis": "embedded",
"run_as_root": true
},
"custom_components": {
"hacs": {
"documentation": "https://hacs.xyz/docs/use/",
"version": "2.0.3",
"requirements": [
"aiogithubapi>=22.10.1"
]
},
"visonic": {
"documentation": "https://github.com/davesmeghead/visonic/wiki",
"version": "0.9.9.9",
"requirements": [
"Pillow",
"pyserial_asyncio"
]
},
"nodered": {
"documentation": "https://zachowj.github.io/node-red-contrib-home-assistant-websocket/guide/custom_integration/",
"version": "4.1.2",
"requirements": []
}
},
"integration_manifest": {
"domain": "visonic",
"name": "Visonic Intruder Alarm",
"codeowners": [
"davesmeghead"
],
"config_flow": true,
"dependencies": [],
"documentation": "https://github.com/davesmeghead/visonic/wiki",
"integration_type": "hub",
"iot_class": "local_push",
"issue_tracker": "https://github.com/davesmeghead/visonic/issues",
"loggers": [
"visonic"
],
"requirements": [
"Pillow",
"pyserial_asyncio"
],
"single_config_entry": false,
"version": "0.9.9.9",
"is_built_in": false,
"overwrites_built_in": false
},
"setup_times": {},
"data": {
"entry": {
"created_at": "2025-01-21T19:58:59.347616+00:00",
"data": {
"panel_number": 0,
"type": "ethernet",
"host": "REDACTED",
"port": "REDACTED",
"path": "",
"baud": 9600,
"emulation_mode": "Standard",
"download_code": "REDACTED",
"show_eeprom_attributes": true,
"exclude_x10": [],
"exclude_sensor": [],
"siren_sounding": [
"intruder"
],
"panel_state_notifications": [
"connection_problem",
"siren_sounding"
],
"sensor_event_list": [
"problem"
],
"retry_connection_count": 1.0,
"retry_connection_delay": 90.0,
"motion_off_delay": 120.0,
"magnet_closed_delay": 5.0,
"emergency_off_delay": 120.0,
"arm_without_usercode": false,
"force_numeric_keypad": false,
"arm_home_enabled": false,
"arm_night_enabled": false,
"arm_away_instant": false,
"arm_home_instant": false,
"allow_remote_arm": true,
"allow_remote_disarm": true,
"allow_sensor_bypass": false,
"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
},
"discovery_keys": {},
"disabled_by": null,
"domain": "visonic",
"entry_id": "01JJ574R8KY4XE8230ADRFN0GV",
"minor_version": 1,
"modified_at": "2025-01-21T19:58:59.348963+00:00",
"options": {
"panel_number": 0,
"type": "ethernet",
"host": "REDACTED",
"port": "REDACTED",
"path": "",
"baud": 9600,
"emulation_mode": "Standard",
"download_code": "REDACTED",
"show_eeprom_attributes": true,
"exclude_x10": [],
"exclude_sensor": [],
"siren_sounding": [
"intruder"
],
"panel_state_notifications": [
"connection_problem",
"siren_sounding"
],
"sensor_event_list": [
"problem"
],
"retry_connection_count": 1.0,
"retry_connection_delay": 90.0,
"motion_off_delay": 120.0,
"magnet_closed_delay": 5.0,
"emergency_off_delay": 120.0,
"arm_without_usercode": false,
"force_numeric_keypad": false,
"arm_home_enabled": false,
"arm_night_enabled": false,
"arm_away_instant": false,
"arm_home_instant": false,
"allow_remote_arm": true,
"allow_remote_disarm": true,
"allow_sensor_bypass": false,
"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
},
"pref_disable_new_entities": false,
"pref_disable_polling": false,
"source": "user",
"title": "Panel 0",
"unique_id": "Visonic Alarm Panel 0",
"version": 4
},
"client connected": "yes",
"panel connected": "no",
"visonic": {
"Disconnection Count": 0
},
"sensor": [],
"switch": [],
"clientlog": [
"2025-01-21 20:58:59.360218+01:00 D P0 init panel 0 language fr",
"2025-01-21 20:58:59.360638+01:00 D P0 reset client panel variables",
"2025-01-21 20:58:59.361125+01:00 I P0 Exclude sensor list = [] Exclude x10 list = []",
"2025-01-21 20:58:59.361693+01:00 D P0 ........... connection attempt 1 of 1",
"2025-01-21 20:58:59.361813+01:00 D P0 connect_to_alarm",
"2025-01-21 20:58:59.361948+01:00 D P0 Connection Device Type is ethernet",
"2025-01-21 20:58:59.362125+01:00 D P0 [getConfigData] Emulation Mode Standard so setting ForceStandard to True, DisableAllCommands to False",
"2025-01-21 20:59:00.386068+01:00 D P0 ........... connection made",
"2025-01-21 20:59:00.396265+01:00 D P0 Client: Sending HA Event visonic_alarm_panel_state {'panel': 0, 'panel_id': 'alarm_control_panel.visonic_alarm', 'action': 'connection', 'state': 'connected', 'attempt': 1}",
"2025-01-21 20:59:00.411032+01:00 D P0 Creating Alarm Panel Entity",
"2025-01-21 20:59:25.574859+01:00 D P0 Visonic has caused a disconnection, action=NO_DATA_FROM_PANEL, state=neverconnected",
"2025-01-21 20:59:25.583852+01:00 D P0 Client: Sending HA Event visonic_alarm_panel_state {'panel': 0, 'panel_id': 'alarm_control_panel.visonic_alarm', 'action': 'nopaneldata', 'state': 'neverconnected'}",
"2025-01-21 20:59:26.088213+01:00 D P0 Unloading platforms self.loaded_platforms={<Platform.SIREN: 'siren'>, <Platform.ALARM_CONTROL_PANEL: 'alarm_control_panel'>} Entry id=01JJ574R8KY4XE8230ADRFN0GV ",
"2025-01-21 20:59:26.091493+01:00 D P0 Unloading complete unload_ok=True",
"2025-01-21 20:59:26.091661+01:00 D P0 ........... Closing down Current Task",
"2025-01-21 20:59:28.094166+01:00 D P0 ........... Current Task Done",
"2025-01-21 20:59:28.099353+01:00 D P0 reset client panel variables"
]
}
}

[davesmeghead]

The integration has not received any data from your panel
Visonic has caused a disconnection, action=NO_DATA_FROM_PANEL, state=neverconnected

I suggest that you check your wiring, the host address and port

[jeanmilopez]

Thank you for your feedback. I appreciate so much your help.
I saw that no Data is displayed on the uConsole of the ESP-LINK.
i think, I must have in first data on the ESP-LINK console...

I have this on the debug (the version of the firmware of POWERMASTER-30 is K18) :

CONN led=-1
127> SER led=-1
195> Wifi init, mode=STA
195> Wifi uses DHCP, hostname=esp-link
195> "ip": "0.0.0.0"
195> "netmask": "0.0.0.0"
202> "gateway": "0.0.0.0"
210> "hostname": "esp-link"
218> sleep enable,type: 2
226> Httpd init, conn=0x3fff3820
236> No user file system found!
245> Serbridge pins: reset=-1 isp=-1 swap=0
283> Reset cause: 4=restart
284> exccause=0 epc1=0x0 epc2=0x0 epc3=0x0 excvaddr=0x0 depc=0x0
284> Flash map 4MB:512/512, manuf 0x5E chip 0x4016
298> ** esp-link v3.0.14-g963ffbb: ready, heap=21368
313> SNTP timesource set to us.pool.ntp.org with offset 0
329> initializing user application
339> Waiting for work to do...
348> mode : sta(XXXXX) + softAP(XXXXX)
366> add if0
370> add if1
375> dhcp server start:(ip:IP.1,mask:255.255.255.0,gw:IP.1)
396> bcn 100
520> scandone
520> state: 0 -> 2 (b0)
523> state: 2 -> 3 (0)
526> state: 3 -> 5 (10)
526> add 0
527> aid 1
528> cnt
559>
559> connected with MYSSIDNETWORK, channel 1
559> dhcp client start...
559> Wifi connected to ssid ARRIS-EABF, ch 1
3123> ip:IP.2,mask:255.255.255.0,gw:IP3
3124> Wifi got ip:IP.2,mask:255.255.255.0,gw:IP3
3130> host_name = esp-link
3138> server_name = _http._tcp.local
3235> HTTP GET /log/text: 200, 14ms, h=16840
13898> HTTP GET /log/text: 200, 9983ms, h=17288
15226> Wifi check: mode=AP+STA status=5
15226> Wifi got IP. Going into STA mode..
15227> bcn 0
15227> del if1
15230> pm open,type:2 0
15237> mode : sta(XXXXX)
15309> Turning OFF uart log
30309> Wifi check: mode=STA status=5
89035> HTTP GET /log/text: 200, 7ms, h=18088
105875> HTTP GET /log/text: 200, 6ms, h=18096
140698> HTTP GET /log/text: 200, 18ms, h=18096
168813> HTTP GET /log/text: 200, 11ms, h=18096
176200> HTTP GET /log/text: 200, 5ms, h=18096

I see the status is 5 => Lost connection... Do you think the problem is the wiring ?

[jeanmilopez]

The problem is resolved !!

And I see the sensors 👍

Next Step I will define the Frontend.

Thank you !!

[jeanmilopez]

Hello,

I'm getting back to you to give you some news. Thanks to your advice I managed to recover the sensors and their status :).

However, I can't arm my powermaster-30 with the HA panel. It tells me that I have to add a code... Do you know if I have to have one? If not, do you know if I can find it from the alarm panel?

For information, I use 2 remote controls to arm or disarm the alarm, there is no code.

Thank you for your help.

[jeanmilopez]

Hello, I've noticed that my ESP8266 becomes saturated and freezes after a certain period of time. The ESP is properly connected to the Wi-Fi network with an excellent signal strength of -26dBm. The micro-console correctly shows traffic at 38400 baud and 8N1. The sensors are successfully retrieved and the integration is configured in Powerlink emulation mode. The ESP is powered directly by the alarm panel using Dupont wires.

However, after a while, the ESP8266 stops working. When I try to access its URL via a web browser, it no longer responds. I suspect the device is freezing. I initially thought the baud rate was incorrect; I tried 9600 baud, but no traffic appeared in the micro-console. What can I do to fix this? I also tried switching to Standard mode, but no sensors are reported in that mode.

[davesmeghead]

Hi,
Once your panel is told to use 38400 baud then it keeps using it. There are 2 ways, as far as I know, that the panel will go back to 9600 baud: 1) hard reset the panel and 2) remove the ESP8266 for 24 hours with no communication. So you trying 9600 baud will not work as the panel wants 38400 baud.

It also sounds to me like the device is freezing, maybe change buffer sizes in the ESPHome yaml for the comms (I'm assuming you're using ESPHome). Do you have another device you could try? or perhaps an ESP32 device you could try?
How are you powering the device? If from the 3.75 volts on the panels RS232 connector then maybe get a DC-DC converter and connect to the panels 12v DC supply, then DC-DC down converted to 5v DC. Just some ideas....

[jeanmilopez]

Hi Dave,

Thanks for your insights! To answer your questions:

• Power: The ESP8266 is currently powered via a dedicated USB supply, so it should be getting a stable 5V.
• Firmware: I am currently using ESP-Link (v3.0.14) at 38400 baud.

Given the "freezing" issues I've encountered, do you recommend switching to ESPHome? I'm interested to know if ESPHome is better...

Following your advice, I am considering two options:

• Switching from ESP-Link to ESPHome on my current ESP8266 to increase the rx_buffer_size and get better integration with Home Assistant.
• Buying an ESP32 to benefit from its better hardware handling of serial comms and larger RAM.

In your experience with the Visonic integration, is the jump to an ESP32 worth it for long-term stability, or is a well-tuned ESPHome config on an ESP8266 usually enough to stop the "freezing" at 38400 baud?

Thanks again for your help!

[davesmeghead]

Hi,

I have no real experience with ESP-Link or ESP8266, I've only used ESP32 devices, so can't comment on stability of the ESP8266 using ESP-Link. At least for ESP32 devices I can recommend ESPHome, I include my yaml file in my latest release visonic_esphome_configuration.yaml to give you a good starting point.

It also creates a select entity in Home Assistant to change baud rates so it auto configures the baud with your panel, you need to delete and re-create the integration from within HA and set the select entity as part of the configuration.

[jeanmilopez]

Hi Dave,

Thanks for the advice and for sharing your YAML configuration!

I’ve decided to follow your recommendation and switch from ESP-Link to ESPHome on my current ESP8266. My plan is to:

1. Set the rx_buffer_size to 1024 (or even 2048) to prevent the "freezing" issues we suspect are caused by buffer overflows at 38400 baud.
2. Use your stream_server setup on port 10000 to maintain compatibility with the integration.
3. Re-install the integration in HA to take advantage of the new baud rate selection features.

If this doesn't solve the stability issues, I will then upgrade to an ESP32 as you suggested.

Thanks again

[jeanmilopez]

Hi Dave,

The integration successfully reaches Powerlink mode and all 13 sensors are working. However, after a certain period, the status drops back to Starting and gets stuck there. My diagnostic data shows a Disconnection Count: 5.

Technical Details:

Panel: PowerMaster 30 (Protocol 1.9.6.5).
Connection: Ethernet via ESP32 :).
ESP32 Config: Running ESPHome with a stream_server on port 8888. Baud rate is set to 38400.
Hardware: Raspberry Pi 3.

I have attached the full diagnostic logs (JSON) to this message for more details. I can also provide my ESPHome YAML configuration if you think it might be relevant.

Important Observation: When it gets stuck on "Starting", I have found that reloading the Visonic integration in Home Assistant immediately restores the connection and all sensors become operational again.

Do you have any suggestions on why the Powerlink connection might be dropping like this? Could it be a timing issue or related to the Pi 3 processing power?

Thanks a lot for your help.
config_entry-visonic-01KEJ70HA57TPRXMQK3WC7PQ78 (2).json

[davesmeghead]

Hi,
So I've taken a look and:

• at 15:30:45 the 1st connection is made to your panel (line 239)
• at 15:42:39 is the last time that there was panel communication, i.e. between panel and integration in HA (line 316)
• at 15:44:37 which is 2 minutes later, reason=powerlinkperiodexpired. This means that there has been no interaction with the panel for 2 minutes and so the integration is going to attempt a reconnection i.e. to stop and re-create the ethernet TCP connection (line 317)
• Lines 323 to 336, the integration attempts the reconnection. It seems to reconnect with the device (ESP32) inside the panel but does not receive any data for 4 minutes (line 330 to 331)
• The integration tries a 2nd time, lines 337 to 355. Same thing happens, I can't see the detail as you haven't created a detailed log file, but this time it tries for 14 minutes (line 349 to 350)
• This happens again for a 3rd, 4th and 5th time

When it logs "action=NO_DATA_FROM_PANEL, state=disconnected" it means that there has not been any data received from the panel.

I don't think it's a timing issue and a Pi3 should be OK I believe.
Can you please merge in my ESPHome yaml file (it's in the /config/custom_components/visonic directory) with yours and try reloading the ESP32 with a new build. Please include the select entity.

Please then delete the hub from within Home Assistant and re-create it. This is all in the release notes for 0.12.4.7, to use it you would need to delete your existing hub and re-create it to choose the ESPHome select entity in Home Assistant.