Logger: homeassistant.config_entries
Source: config_entries.py:406
First occurred: 15:54:25 (1 occurrences)
Last logged: 15:54:25
Error setting up entry Not your homie for spook
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 406, in async_setup
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/spook/__init__.py", line 90, in async_setup_entry
await services.async_setup()
File "/config/custom_components/spook/services.py", line 288, in async_setup
self.async_register_service(service)
File "/config/custom_components/spook/services.py", line 293, in async_register_service
service.async_register()
File "/config/custom_components/spook/services.py", line 168, in async_register
for platform in self.hass.data[DATA_ENTITY_PLATFORM][self.domain]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^
KeyError: 'timer'
Thanks for this work, @frenck ! Lot’s of usefull stuff in your integration !!
Is there any service to change the friendly_name of an entity? That could be quite handy.
For instance, I have an imput_boolean to switch my “Christmas Mode” on, when I assemble my tree, and I get some devices I have in storage for the lights; I keep track of how many devices I have offline, and when chritmas mode is off I add a “®” to the start of the name, so that my templates ignore this devices as they are in “Reserve”. It would be nice to have an automation to do this when I turn on / off my christmas mode.
Other uses: For instance, a smart plug with power monitoring could change the name according to device consumption (if you know the consuption of the devices you connect there it is easy enough to ‘guess’ whats connected and change the name accordingly.
Any thoughts on this? Thanks in advance!
I was looking for exactly this. I came up with a routine in Node-RED that is supposed to batch rename entities based on their entity ID (all of which have the desired values already — that was a lot of work to standardize) plus some text regex fu. No such service to set friendly name exists, though.
Spook has been fantastic to help keep thinks “clean”. It would be most helpful if when identifying a missing entity in a dashboard, it was able to tell me which sub view.
Spook was working great until today update. I think it was an Operation System update, and now Spook showing NOT LOADED. Even after system restart, reboot. Anybody else experience the same issue ?
The new Proximity integration, which was revamped for Home Assistant 2024.2, has been added to Spook as well.
It will be able to detect configuration issues with the UI configuration of those. For example, if proximity is set on a zone that no longer exists, ignores non-existing zones, or tracks unknown devices or persons.
As usual, Spook will create a nice repair issue for those.
Spook can figure out the used services in automations now and will use this to check if all called services in action are existing services. If not, well, you guessed it: A repair issue will be raised.
Home Assistant itself can raise these too. However, Spook will detect and raise them proactively.
Translation fixes
Home Assistant 2024.2 can raise warnings in the logs in case there are translation issues. Many of those warnings have been fixed in the translations used by Spook.
If you find more, please let us know! Or, help out translating Spook. All you need is a browser.
feel honored to see my mobile_app service being shown as example here.
and thx for the update with the new unknown services scanner.
could this be a bug related to that new functionality:
Deze fout is ontstaan door een aangepaste integratie.
Logger: custom_components.spook
Source: helpers/debounce.py:114
Integration: Spook (documentation, issues)
First occurred: 22:01:30 (1 occurrences)
Last logged: 22:01:30
Unexpected exception from <function AbstractSpookRepair.async_activate.<locals>._async_inspect at 0x7fcc85ea3560>
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/debounce.py", line 114, in _handle_timer_finish
await task
File "/config/custom_components/spook/repairs.py", line 134, in _async_inspect
await self.async_inspect()
File "/config/custom_components/spook/ectoplasms/automation/repairs/unknown_service_references.py", line 67, in async_inspect
_async_find_services_in_sequence(
File "/config/custom_components/spook/ectoplasms/automation/repairs/unknown_service_references.py", line 136, in _async_find_services_in_sequence
_async_find_services_in_sequence(called_services, step[CONF_SEQUENCE])
~~~~^^^^^^^^^^^^^^^
KeyError: 'sequence'
there is no Repair created, and as far as manually checkable, no service unknown. There was an earlier (fixed) repair on an uninstalled integration, but 3 restarts later this still shows, without anything further.
Not sure this is an ‘issue’ in the sense of a ‘bug’ so before filing anything in the repo, asking here for some feedback
New features
Bug fixes
Maintenance
Documentation
Dependency updates
… maybe the integration not found you authorized for such a task 
!!
