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 
2 Likes