-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2024.10.2 break SS integration stops working #101
Comments
I got the same issue Logger: homeassistant.config_entries Error setting up entry SecuritySpy for securityspy |
Same. |
Same |
I tried reconfiguring the setup. I also verified HTTP and 8000 on SS. No luck |
I rolled back core to 2024.9.2 and SSpy integration is working again. |
Well, it doesn't seem to be directly broken by core 10.2; I managed to get a dev environment set up and SSpy integration has no problems starting there. |
Tried upgrading to 10.3 on my real system just now, and it seems to be working for the moment. If it fails, my workaround idea to try is adding a fake Schedule Preset in my Security Spy (app) settings (Settings, Scheduling, Schedule Presets). |
10.3 has made the SS integration work again for me. |
Same. 10.3 is working. |
Error settup up SecuritySpy
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 594, in async_setup
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/securityspy/init.py", line 72, in async_setup_entry
server_info = await securityspyserver.get_server_information()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/pysecspy/secspy_server.py", line 212, in get_server_information
return await self._get_server_information()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/pysecspy/secspy_server.py", line 193, in _get_server_information
for preset in sched_preset["schedulepreset"]:
~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^
TypeError: string indices must be integers, not 'str'
The text was updated successfully, but these errors were encountered: