You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the following warnings in log file related to alarmdecoder integration after update to core 2024.12.3
2024-12-14 17:11:36.743 WARNING (ImportExecutor_0) [py.warnings] /usr/local/lib/python3.13/site-packages/alarmdecoder/decoder.py:605: SyntaxWarning: invalid escape sequence '.'
matches = re.match('^!Sending(.{1,5})done.*', data)
I have the same problem here. Version 3.13 of python is barfing on some regex expressions in the alarmdecoder source code , which is an add-on package to Home Assistant.
The problem
the following warnings in log file related to alarmdecoder integration after update to core 2024.12.3
2024-12-14 17:11:36.743 WARNING (ImportExecutor_0) [py.warnings] /usr/local/lib/python3.13/site-packages/alarmdecoder/decoder.py:605: SyntaxWarning: invalid escape sequence '.'
matches = re.match('^!Sending(.{1,5})done.*', data)
2024-12-14 17:11:36.764 WARNING (ImportExecutor_0) [py.warnings] /usr/local/lib/python3.13/site-packages/alarmdecoder/messages/panel_message.py:73: SyntaxWarning: invalid escape sequence '['
_regex = re.compile('^(!KPM:){0,1}([[a-fA-F0-9-]+]),([a-fA-F0-9]+),([[a-fA-F0-9]+]),(".+")$')
2024-12-14 17:11:36.804 WARNING (ImportExecutor_0) [py.warnings] /usr/local/lib/python3.13/site-packages/alarmdecoder/zonetracking.py:186: SyntaxWarning: invalid escape sequence '\d'
zone_regex = re.compile('^CHECK (\d+).*$')
What version of Home Assistant Core has the issue?
core-2024.12.3
What was the last working version of Home Assistant Core?
core-2024-11
What type of installation are you running?
Home Assistant OS
Integration causing the issue
alarmdecoder
Link to integration documentation on our website
https://www.home-assistant.io/integrations/alarmdecoder
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: