restarting…
“Opslaan” is btw a complete incorrect translations of that button… 
well thats much better, I briefly saw this now:
and that is because it probably loads before these 2 entities are created (in a delayed startup sequence)
the repair seems to auto-disappear after they were created.
on the button: is the ‘ignore’ purposely left out?
on the edit the dashboard: that really should not be showing in yaml mode?
If those entities would have unique IDs that won’t happen (as HA will restore the entity registry items as part of the bootstrap). So, if you can add those, that will help (it also guarantees the entity ID is assigned/reserved).
Yup, if it detects it is resolved, it will clean up after itself.
Not really, I will check that out.
That is a nice improvement I guess. Right now it will probably redirect to an error message I guess.
o heck, I never thought about that, its made in a python script:
hass.states.set('sensor.overview_components', cnt, {
'friendly_name' : 'Components and domains',
'icon' : 'mdi:format-list-bulleted-type',
'components' : cnt,
'---------------' : '--------',
'per domain' : complist,
'subdomains' : cntsub,
'***************' : '--------',
'per subdomain' : sublist
})
and I never considered that to be an option.
Ill try and see what happens
o wait, unique_id is not an attribute of course… can we add that in hass.states.set ?
That is not how you manage entities. That is directly interfacing with the state machine, which should not be done.
Basically, you are injecting a state directly into the state machine, without having an actual entity.
…/Frenck
Why is that a python script anyways, you can get all that in templates now
Ive opened a topic for that, didnt want to hijack this thread…
This Spook repair on a missing service was fixed ( had installed my mobile_app integration and renamed it), but it is not automatically fixed and still showing for automations using it
That is not a repair raised by Spook…
Spook will alway reveal itself in the messages.
…/Frenck
hmmm, sorry for the delay, but it seems you are right 
Hadn’t realized HA also checks for available services.
It’s odd though, and my memory might be playing with me here, but since it wouldn’t go away, I decided to check the hidden repairs.issue_registry and did find these listed. So I edited/deleted them and restarted. Issue gone.
Would have sworn Spook was listed as source on them.
will keep an eye out for it the next time it happens (which it certainly will, after the mobile app gets auto-banned once again…)
btw, Frenck, is this something you would be willing to consider adding?
We now have total domains, and entities, but sorted components is not yet available.
Ive been using
{{state_attr('sensor.ha_main_config','components')|sort}}
and it splits it all out, but its a bit complex to jinja template it into a nice entity with attributes…
the template is based on the rest api sensor to the instance, listing all its components
rest:
- resource: !secret config_resource
scan_interval: 86400
verify_ssl: false
headers:
Content-Type: application/json
Authorization: !secret api_bearer_token
sensor:
- unique_id: ha_main_config_rest
name: Ha Main config
icon: mdi:memory
value_template: >
{{value_json.version}}
json_attributes:
- components
- unit_system
- config_dir
cant first them all here ofc…
would be nice if we had that listed per domain, and then the subsequent integrations (not sure of the terminology here tbh) as sublist
so:
alarm_control_panel: 5
for: manual, mqtt, overkiz, zha
etcetc
always a bit confusing when to use which terminology because
{% for d in states|groupby('domain') -%}
{% if loop.first %} Domains: {{loop.length}} - Entities: {{states|count}} {% endif %}
{{ d[0] -}}
{% endfor %}
spits out the domains, which are components in the sensor above and then some…
anyways, maybe you can have a look at the components?
v0.13.131313
Bug fixes
- Make Lovelace repair more resilient against configuration variations @frenck (#184)
Enhancements
- Update German translation @steffenrapp (#177)
Dependency updates
-
Lock file maintenance @renovate (#179)
Nope, that is just bad data on a state machine level. HA isn’t designed to store large amounts of data in the state machine. Even for Spook I would not feel comfortable adding that.
this seems to have popped up after updating:
Deze fout is ontstaan door een aangepaste integratie.
Logger: custom_components.spook
Source: custom_components/spook/repairs/lovelace_unknown_entity_references.py:264
Integration: Spook (documentation, issues)
First occurred: 16:07:32 (119 occurrences)
Last logged: 16:54:43
Unexpected exception from <function AbstractSpookRepair.async_activate.<locals>._async_inspect at 0x7f8c1b6aa660>
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/debounce.py", line 117, in _handle_timer_finish
await task
File "/config/custom_components/spook/repairs/__init__.py", line 130, in _async_inspect
await self.async_inspect()
File "/config/custom_components/spook/repairs/lovelace_unknown_entity_references.py", line 108, in async_inspect
for entity_id in self.__async_extract_entities(config)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/spook/repairs/lovelace_unknown_entity_references.py", line 159, in __async_extract_entities
entities.update(self.__async_extract_entities_from_card(card))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/spook/repairs/lovelace_unknown_entity_references.py", line 221, in __async_extract_entities_from_card
entities.update(self.__async_extract_entities_from_card(card))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/spook/repairs/lovelace_unknown_entity_references.py", line 225, in __async_extract_entities_from_card
entities.update(self.__async_extract_entities_from_card(card))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/spook/repairs/lovelace_unknown_entity_references.py", line 213, in __async_extract_entities_from_card
entities.update(self.__async_extract_entities_from_actions(config))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/spook/repairs/lovelace_unknown_entity_references.py", line 255, in __async_extract_entities_from_actions
entities.update(self.__async_extract_entities_from_action(action))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/spook/repairs/lovelace_unknown_entity_references.py", line 264, in __async_extract_entities_from_action
(target := config.get(key))
^^^^^^^^^^
AttributeError: 'str' object has no attribute 'get'
edit
was picked up in the GitHub: AttributeError: 'str' object has no attribute 'get' · Issue #188 · frenck/spook · GitHub
fixed! thanks for the update.
this however remains a mystery:
somehow, fixing the issue that indeed happens every once in a while (mobile app using the device name, and not the user name we have to manually reset upon registering the device), does not trigger Spook to auto -resolve this.
Whatsmore, it is persistent over restarts… Ive restarted HA many times now in the beta, and the Spook notification remains. the service is readily available and used.
v0.14.0
New features
- Add more Home Assistant diagnostic sensors @frenck (#207)
Enhancements
- Spook speaks Dutch @frenck (#204)
- Add Ectoplasms
@frenck (#205) - Add entity name translations to all entities @frenck (#210)
- ¡Spook ahora habla español también! @frenck (#211)
Dependency updates
-
Update dependency homeassistant to ^2023.6.0-beta.0 @renovate (#209)
1 Like
I didn’t use it, but in some scary way it helped me clean up the system.
1 Like
