Yes please, and you can easily zip log files and copy/paste then into the issue
1 Like
I agree, and it is the only one that I’ve come across, all others seem to be unique.
Done, do you prefer zipped files or is the txt ok?
@davesmeghead with current dev Client Version: 0.11.1.0, my panel and my setup is working 100% as intended (PowerMaster 30)
At least the “daily things” I can think of testing.
Just some feedback if you plan to make it a HACS release 
@davesmeghead I assume I’m not the only one getting these Warnings on Home Assistant restart…? Should I be worried about something going wrong?
Logger: homeassistant.const
Source: helpers/deprecation.py:222
First occurred: 10:10:00 (12 occurrences)
Last logged: 10:10:04
* 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
* 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
* 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
* 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
* 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
Logger: homeassistant.helpers.frame
Source: helpers/frame.py:292
First occurred: 10:10:04 (1 occurrence)
Last logged: 10:10:04
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. This will stop working in Home Assistant 2025.11, please create a bug report at https://github.com/davesmeghead/visonic/issues
Short answer is No.
There are 2 parts to this answer:
- The warning refers to deprecated constants within the HACS/Master Release (0.9.9.9) that will be removed in “HA Core 2025.11”, and therefore this Integration will stop working. This is the planned November 2025 release, so we’re still 5 or 6 months away from that happening,
- I’ve already been working on a development release (dev on Github for those interested) with lots of changes, fixes, updates, new functionality; this dev release fixes the constants and the warnings have gone. I’m just waiting on some more testing by me and others to confirm its stability and I’ll make it the HACS/Master release, I expect this to happen in the next month or so.
So we’re OK 
4 Likes
On occasion, maybe a server restart or just restarting the HA docker, the integration stops working & shows this error. Usually restarting solves it, mentioning just in case it helps track any issues. Thanks
Logger: homeassistant.config_entries
Source: config_entries.py:749
First occurred: 4:39:57 PM (4 occurrences)
Last logged: 4:40:23 PM
Error setting up entry Panel 0 for alarm_control_panel
Error setting up entry Panel 0 for siren
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 749, in __async_setup_with_context
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/alarm_control_panel/__init__.py", line 118, in async_setup_entry
return await hass.data[DATA_COMPONENT].async_setup_entry(entry)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 182, in async_setup_entry
raise ValueError(
...<2 lines>...
)
ValueError: Config entry Panel 0 (8adf258543b64057d119a482ead5dccc) for visonic.alarm_control_panel has already been setup!```Hello Dave. I’m currently running on version 0.9.9.9 with the PowerMax+ panel and it works fine. I Installed the latest development version and manually enrolled the panel per the instructions on your wiki and the integration fails with the alarm_control_panel_visonic_alarm and all of the sensors in the unavailable status. Rolled back to 0.9.9.9 and everything works okay. I created a ticket and uploaded my logs to your integration web page. Thanks Trevor
@davesmeghead : hi Dave, between 2 days i have a problem. I can ping my esp but on the integration it’s impossible to have the visonic panel.
This is my log file.
Do you have a idea please ??
Another question, if i want to change my esp to see if i only have my problem, is it possible to flash it with esphome builder in home assistant ?
I just replied on the Github issue you created here
I have no idea what hardware you actually have and so can’t comment, what esp?
Actuallybi have a ESP01. All are ok between 3 years. But last 2 dans impossible to do a connexion between visonic and HA. But it ne possible to connect it with IO address
Has anything changed in your home network? or perhaps changed your HA setup? It’s a connection problem between the system that you run HA on and the ESP01 in your panel.
You may be able to use your ESP01 with ESPHome but it’s not a device that I have personally used so I’m not 100% certain.
my provider had me test my internet box. I put the good SSID back on but I wanted to check on the ESP whether it was connecting properly. Can I select another ssid in the esp to try?
I have another esp in a box a nodemcu, so i can try to flash it and test with a new one, no ?
yet I ping his IP, strange, no ?
Do you have a static or DHCP Reserved IP address for your ESP device?
If not, maybe a different device got the IP you used before and that device is responding to the ping.
Double check in your router what IP your ESP have right now.
Hi, shit you have right !! The IP change when i reset the internet box. How did i change the ip on HA ? Is it possible ? Or did i do a new bridge. But the problem has all my automation have the name of th old sensor and panel 0. How did i change it ?
I think you can only change the IP by manually editing some files in storage (not recommended).
Another solution is to remove the integration and readd it with the new IP.
Still I would recommend making a DHCP reservation on your router so the ESP always gets the same IP in the future.
If possible reserve the same IP as before, and restart the router so the new device don’t get that IP.
1 Like
It seems that version 0.12.0.0 was just released today ?
@davesmeghead Can we simply start testing it or do you want to give here some instructions before we start installing it and asking too many questions ?
Ah yes, it has 
It’s the same as the dev release with a few tweaks, so I’ve moved it across to a formal HACS Release (and removed the dev release).
If you had the dev release then this should not make any difference. If you currently have the Master release then it should update the config settings automatically (with new settings being set to default as per the wiki). If the update has problems then delete the integration from the HA Dashboard and re-create it. Other than that, for any general problems then post here, for specific problems then create an Issue on Github.
However, if you currently have the Main / Master Release then this may be a Breaking Change if you use Actions and Events so allow some time to make any needed changes, please see the wiki for more details.
Release notes are here
EDIT: Just to be clear, the Master release is what is installed by HACS. If you currently have the HACS Master (version 0.9.9.9), this is an update to HACS Master 0.12.0.0
I just uploaded the update. So far, so good. The only comment is it generated another entity: alarm_control_panel.visonic_alarm_2. I had to manually delete it.
Hey, I’ve also just moved to the newest HACS version, I got the same _2 alarm, plus it set all my sensors to hidden.
One other thing, none of my motion sensors are “working” any more, before the update, when I moved about it would work like a motion sensor, however now it does not show the same.
Info from visonic alarm
code_format: null
changed_by: System
code_arm_required: false
state: disarmed
ready: true
memory: true
trouble: none
bypass: false
tamper: false
battery: false
alarm: none
Protocol Version: 1.9.1.1
emulationmode: powerlink
Panel Model: PowerMaster 30
Power Master: "Yes"
Watchdog Timeout (Total): 0
Watchdog Timeout (Past 24 Hours): 0
Download Timeout: 0
Download Message Retries: 0
lasteventname: System
lasteventaction: Disarmed
lasteventtime: "2025-07-01T18:47:41.278296+01:00"
Client Version: 0.12.0.0
Disconnection Count: 0
panel: 0
friendly_name: Visonic Alarm
supported_features: 15