What is disabling a device suppose to do ?

[jerry34ha]

Hi,
I'm switching off my internet connexion and wifi at night to save energy.

I use the multiscrape custom component to scrape the wait time until the next bus every minute. Due to the lack of connectivity, HA logs are filled up with scrape errors every minute.
I want to keep the logs clean (and save my HA Green onboard storage...).

I installed Spook to homeassistant.disable_device multiscrape and disable_entity mysensor

This does not stop the multiscrape custom component from trying to refresh the entity, hence the logs are still full of errors.

The Overkiz integration also throws some errors at night so I used homeassistant.disable_integration but again that does not make errors go away at night.

Am I wrong to assume that disabling the multiscrape device would prevent HA from refreshing the associated sensors ?
Am I wrong to assume that disabling the Overkiz integration would stop it from attempting to refresh the associated devices/entities ?

Thank you

(HA core 2024.2.5 on HA Green)

[frenck]

This does not stop the multiscrape custom component from trying to refresh the entity

That is possible, the scape probably happens on config entry / integration level, and not device.

Am I wrong to assume that disabling the multiscrape device would prevent HA from refreshing the associated sensors ?

Depends on the case / integration. But to me it sounds like you are looking for disabling an integration (not a device).

../Frenck

[frenck]

but not in the disable_integration dropdown

Correct, as you won't disable an integration, but an instance of an integration; which is known as a config entry. So, look for disable_config_entry.

../Frenck

[jerry34ha]

Well, this did not work (scraping continued):

alias: Désactiver Scrape
description: >-
  Désactiver les entité Scrape la nuit car je coupe le wifi et ça évite de
  remplir le log d'erreurs
trigger:
  - platform: time
    at: "21:55:00"
condition: []
action:
  - service: homeassistant.disable_config_entry
    metadata: {}
    data:
      config_entry_id:
        - d6ad69489a018ea5ab0c6084f6b48b6b
mode: single

I will try with the Overkiz integration to see if the issue is with Multiscrape.

[jerry34ha]

Nope, this does not solve my problem.

I will try another approach: use the logger.set_level service to reduce logging to critical at night.

[frenck]

I will try another approach: use the logger.set_level service to reduce logging to critical at night.

That is no solution 🤷

[jerry34ha]

Ok, I succeeded in disabling Overkill (my automation was failing before reaching that part).

For multiscrape, i may not have found the correct config_entry_id or it is not responding to the service. I will investigate further but in the meantime, reducing log for this component did work so I achieved what I wanted.