Spook -Your homie

[frenck (Franck Nijhof)]

v0.12.34

New features

• Add repair: Find missing source switches for switch_as_x helpers @frenck (#124)

Bug fixes

• Fix subtract instead of add @DurgNomis-drol (#114)

Enhancements

• Add aladdin_connect and scrape as known obsolete YAML @frenck (#106)
• Correction to German translation @steffenrapp (#117)

Maintenance

• Bump min required Home Assistant to 2023.4.0 @frenck (#126)

Documentation

• Add docs for switch_as_x repair @frenck (#125)

Dependency updates

Details

• Lock file maintenance @renovate (#101)
• Update dependency hass-nabucasa to v0.63.1 @renovate (#102)
• Update dependency black to v23.3.0 @renovate (#103)
• Update dependency ruff to v0.0.260 @renovate (#104)
• Lock file maintenance @renovate (#107)
• Update dependency pylint to v2.17.2 @renovate (#108)
• Update dependency pre-commit to v3.2.2 @renovate (#109)
• Update dependency hass-nabucasa to v0.64.0 @renovate (#110)
• Update dependency ruff to v0.0.261 @renovate (#111)
• Update dependency homeassistant to v2023.4.0 @renovate (#112)
• Update dependency homeassistant to v2023.4.1 @renovate (#113)
• Update dependency homeassistant to v2023.4.2 @renovate (#116)
• Lock file maintenance @renovate (#118)
• Update dependency hass-nabucasa to v0.64.1 @renovate (#119)
• Update actions/checkout action to v3.5.1 @renovate (#120)
• Update dependency homeassistant to v2023.4.3 @renovate (#121)
• Update actions/checkout action to v3.5.2 @renovate (#122)
• Update dependency homeassistant to v2023.4.4 @renovate (#123)

[smartin]

Have you succeeded in importing Statistics?
I need want to merge Statistics as well, don’t mind if i have to introduce new Sensors as well (of course, some Hints what to take care of if appending older Data would be awesome as well).

It would be e.g. really helpful to have an example of a working Dataset, as a starting Point.
Of course, i have a Dev-System, where i don’t install Spook first (as it is not allowed to).

[timseebeck]

No, sorry, I didn’t succeed. Although still interested, I had to give up.

[smartin]

Too Bad Thanks for getting back anyway!

Hope never dies, maybe someone with better Knowledge about Function and/or Code can help us out with some little Breadcrumbs?

[frenck (Franck Nijhof)]

v0.13.37

New features

• Add repair: Find unknown entities on dashboards @frenck (#170)

Enhancements

• Add samsungtv as known obsolete YAML config @frenck (#165)
• Add rainbird as known obsolete YAML config @frenck (#172)
• Add skybell as known obsolete YAML config @frenck (#171)

Dependency updates

• Lock file maintenance @renovate (#164)
• Update dependency homeassistant to v2023.5.4 @renovate (#166)
• Update actions/setup-python action to v4.6.1 @renovate (#167)
• Update dependency ruff to v0.0.270 @renovate (#168)
• Lock file maintenance @renovate (#169)

[Mariusthvdb (Marius)]

so the new Spook manages to show my yaml only Dashboards in the UI editor

also it finds some frontend entities that it shouldn’t:

I didnt dare to click ‘Opslaan’ as I seem to recall we had ‘Ignore’ (which I need to do). Obviously, ‘Ignore’ is no longer showing. Is this per design, or a bug?

[frenck (Franck Nijhof)]

I’m not sure what [[[ & ]]] is, that is not part of Home Assistant or its specifications.

entity, user and group are odd, how are those used?

…/Frenck

[Mariusthvdb (Marius)]

those brackets are from custom:button-card templates, and I suppose group and user are custom:state-switch. Some templates are used in custom:template-entity-row

btw, I only picked 1, there are 7 repairs, and they all seem to point to custom card settings

just for the fun of it I tried to edit a dash, and could do so up to clicking SAVE. it then choked, as these are Yaml dashboards.

other finds:

• mediaquery
• template
• light.{{states('input_select.hue_group')|slugify}}
• deviceID

Spook could have found way more in my config than those though, so if it finds them why not all.

[frenck (Franck Nijhof)]

Shipped v0.13.5791 that should address it.

[Mariusthvdb (Marius)]

restarting…

[frenck (Franck Nijhof)]

@Mariusthvdb

I didnt dare to click ‘Opslaan’ as I seem to recall we had ‘Ignore’ (which I need to do).

“Opslaan” is btw a complete incorrect translations of that button…

[Mariusthvdb (Marius)]

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?

[frenck (Franck Nijhof)]

@Mariusthvdb

because it probably loads before these 2 entities are created (in a delayed startup sequence)

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).

@Mariusthvdb

the repair seems to auto-disappear after they were created.

Yup, if it detects it is resolved, it will clean up after itself.

@Mariusthvdb

on the button: is the ‘ignore’ purposely left out?

Not really, I will check that out.

@Mariusthvdb

on the edit the dashboard: that really should be showing who in yaml mode?

That is a nice improvement I guess. Right now it will probably redirect to an error message I guess.

[Mariusthvdb (Marius)]

@frenck

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).

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 ?

[frenck (Franck Nijhof)]

@Mariusthvdb

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

[petro]

Why is that a python script anyways, you can get all that in templates now

[Mariusthvdb (Marius)]

Ive opened a topic for that, didnt want to hijack this thread…

[Mariusthvdb (Marius)]

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

[frenck (Franck Nijhof)]

That is not a repair raised by Spook…

Spook will alway reveal itself in the messages.

…/Frenck

[Mariusthvdb (Marius)]

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…)