Bug Retrieve Data With Home Assistant 2025-02-04

Mar 13, 2025 by ADMIN 49 views

Introduction

Home Assistant is a popular open-source home automation platform that allows users to control and monitor their smart devices. However, like any software, it is not immune to bugs and issues. In this article, we will discuss a bug that was encountered while trying to retrieve data with Home Assistant version 2025.2.4.

Version of the custom_component

The custom component being used is the latest version, v8.0.5.

Describe the bug

The bug is a strange behavior where two multiscrape sensors are not working anymore in Home Assistant version 2025.2.4, but they were working fine in version 2025.1.4. The sensors in question are the Victron VRM Forecast and the Qualité de l'air (Air Quality) sensors.

Debug log

The debug log for the Victron VRM Forecast sensor is as follows:

Feb 17 12:52:14 pi hass[453299]: 2025-02-17 12:52:14.776 INFO (MainThread) [custom_components.multiscrape.button] Multiscrape triggered by button
Feb 17 12:52:14 pi hass[453299]: 2025-02-17 12:52:14.776 DEBUG (MainThread) [custom_components.multiscrape.coordinator] Victron VRM Forecast # New run: start (re)loading data from resource
Feb 17 12:52:14 pi hass[453299]: 2025-02-17 12:52:14.777 DEBUG (MainThread) [custom_components.multiscrape.coordinator] Victron VRM Forecast # Rendered resource template into: https://vrmapi.victronenergy.com/v2/installations/yyy/stats?type=forecast&interval=days&start=1739746800&end=1740002400
Feb 17 12:52:14 pi hass[453299]: 2025-02-17 12:52:14.777 DEBUG (MainThread) [custom_components.multiscrape.coordinator] Victron VRM Forecast # Request data from https://vrmapi.victronenergy.com/v2/installations/yyy/stats?type=forecast&interval=days&start=1739746800&end=1740002400
Feb 17 12:52:14 pi hass[453299]: 2025-02-17 12:52:14.777 DEBUG (MainThread) [custom_components.multiscrape.http] Victron VRM Forecast # Executing page-request with a get to url: https://vrmapi.victronenergy.com/v2/installations/yyy/stats?type=forecast&interval=days&start=1739746800&end=1740002400 with headers: {'Accept': 'text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8', 'Content-Type': 'application/json', 'User-Agent': 'HomeAssistant (linux-gnu)', 'X-Authorization': 'Token xxxxxxxxxxxxxxxxxxxxxxx'}
Feb 17 12:52:14 pi hass[453299]: 2025-02-17 12:52:14.984 DEBUG (MainThread) [custom_components.multiscrape.http] Victron VRM Forecast # Response status code received: 200
Feb 17 12:52:14 pi hass[453299]: 2025-02-17 12:52:14.985 DEBUG (MainThread) [custom_components.multiscrape.scraper] Victron VRM Forecast # Response seems to be json. Skip parsing with BeautifulSoup.
Feb 17 12:52:14 pi hass[453299]: 2025-02-17 12:52:14.985 DEBUG (MainThread) [custom_components.multiscrape.coordinator] Victron VRM Forecast # Data succesfully refreshed. Sensors will now start scraping to update.
Feb 17 12:52:14 pi hass[453299]: 2025-02-17 12:52:14.985 DEBUG (MainThread) [custom_components.multiscrape.coordinator] Finished fetching multiscrape data in 0.209 seconds (success: True)
Feb 17 12:52:14 pi hass[453299]: 2025-02-17 12:52:14.985 DEBUG (MainThread) [custom_components.multiscrape.sensor] Victron VRM Forecast # Victron Forecast Today # Start scraping to update sensor
Feb 17 12:52:14 pi hass[453299]: 2025-02-17 12:52:14.985 DEBUG (MainThread) [custom_components.multiscrape.scraper] Victron VRM Forecast # Victron Forecast Today # Applying value_template only.
Feb 17 12:52:14 pi hass[453299]: 2025-02-17 12:52:14.986 DEBUG (MainThread) [custom_components.multiscrape.sensor] Victron VRM Forecast # Victron Forecast Today # Selected: None
Feb 17 12:52:14 pi hass[453299]: 2025-02-17 12:52:14.986 DEBUG (MainThread) [custom_components.multiscrape.entity] Victron VRM Forecast # Victron Forecast Today # Icon template rendered and set to: mdi:solar-power
Feb 17 12:52:14 pi hass[453299]: 2025-02-17 12:52:14.986 DEBUG (MainThread) [custom_components.multiscrape.entity] Victron VRM Forecast # Victron Forecast Today # Sensor updated and state written to HA

The debug log for the Qualité de l'air (Air Quality) sensor is as follows:

Feb 17 11:14:22 pi hass[453299]: 2025-02-17 11:14:22.279 INFO (MainThread) [custom_components.multiscrape.button] Multiscrape triggered by button
Feb 17 11:14:22 pi hass[453299]: 2025-02-17 11:14:22.279 DEBUG (MainThread) [custom_components.multiscrape.coordinator] Qualité de l'air # New run: start (re)loading data from resource
Feb 17 11:14:22 pi hass[453299]: 2025-02-17 11:14:22.279 DEBUG (MainThread) [custom_components.multiscrape.coordinator] Qualité de l'air # Rendered resource template into: http://api.atmo-aura.fr/api/v1/communes/yyy/indices/atmo?api_token=xxxxxxxxxxxxxxxxxxxxxxx&date_calcul=yesterday&echeance=1
Feb 17 11:14:22 pi hass[453299]: 2025-02-17 11:14:22.279 DEBUG (MainThread) [custom_components.multiscrape.coordinator] Qualité de l'air # Request data from http://api.atmo-aura.fr/api/v1/communes/yyy/indices/atmo?api_token=xxxxxxxxxxxxxxxxxxxxxxx&date_calcul=yesterday&echeance=1
Feb 17 11:14:22 pi hass[453299]: 2025-02-17 11:14:22.279 DEBUG (MainThread) [custom_components.multiscrape.http] Qualité de l'air # Executing page-request with a get to url: http://api.atmo-aura.fr/api/v1/communes/yyy/indices/atmo?api_token=xxxxxxxxxxxxxxxxxxxxxxx&date_calcul=yesterday&echeance=1 with headers: {}
Feb 17 11:14:22 pi hass[453299]: 2025-02-17 11:14:22.441 DEBUG (MainThread) [custom_components.multiscrape.http] Qualité de l'air # Response status code received: 401
Feb 17 11:14:22 pi hass[453299]: 2025-02-17 11:14:22.441 DEBUG (MainThread) [custom_components.multiscrape.http] Qualité de l'air # Error executing get request to url: http://api.atmo-aura.fr/api/v1/communes/yyy/indices/atmo?api_token=xxxxxxxxxxxxxxxxxxxxxxx&date_calcul=yesterday&echeance=1.
Feb 17 11:14:22 pi hass[453299]:  Error message:
Feb 17 11:14:22 pi hass[453299]:  HTTPStatusError("Client error '401 Unauthorized' for url 'http://api.atmo-aura.fr/api/v1/communes/yyy/indices/atmo'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/401")
Feb 17 11:14:22 pi hass[453299]: 2025-02-17 11:14:22.441 ERROR (MainThread) [custom_components.multiscrape.coordinator] Qualité de l'air # Updating failed with exception: Client error '401 Unauthorized' for url 'http://api.atmo-aura.fr/api/v1/communes/yyy/indices/atmo'
Feb 17 11:14:22 pi hass[453299]: For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/401
Feb 17 11:14:22 pi hass[453299]: 2025-02-17 11:14:22.441 DEBUG (MainThread) [custom_components.multiscrape.coordinator] Finished fetching multiscrape data in 0.<br/>
**Q&A: Bug Retrieve data with Home Assistant 2025-02-04**
=====================================================

**Q: What is the issue with the multiscrape sensors in Home Assistant 2025.2.4?**
--------------------------------------------------------------------------------

A: The issue is that two multiscrape sensors, the Victron VRM Forecast and the Qualité de l'air (Air Quality) sensors, are not working anymore in Home Assistant version 2025.2.4, but they were working fine in version 2025.1.4.

**Q: What is the error message for the Qualité de l'air (Air Quality) sensor?**
--------------------------------------------------------------------------------

A: The error message is a 401 Unauthorized error, which means that the API token is not valid or has expired.

**Q: What is the debug log for the Victron VRM Forecast sensor?**
--------------------------------------------------------------------------------

A: The debug log shows that the sensor is trying to retrieve data from the Victron VRM API, but it is not receiving any data. The log also shows that the sensor is trying to apply the value template, but it is not able to do so.

**Q: What is the debug log for the Qualité de l'air (Air Quality) sensor?**
--------------------------------------------------------------------------------

A: The debug log shows that the sensor is trying to retrieve data from the Atmo-Aura API, but it is receiving a 401 Unauthorized error. The log also shows that the sensor is trying to update the data, but it is not able to do so.

**Q: What is the solution to this issue?**
------------------------------------------

A: The solution to this issue is to update the API token for the Qualité de l'air (Air Quality) sensor to a valid token. This can be done by going to the Home Assistant configuration file and updating the API token.

**Q: What is the impact of this issue on Home Assistant users?**
---------------------------------------------------------

A: The impact of this issue on Home Assistant users is that they will not be able to retrieve data from the Victron VRM Forecast and the Qualité de l'air (Air Quality) sensors. This can cause issues with the functionality of their smart home system.

**Q: How can Home Assistant users troubleshoot this issue?**
---------------------------------------------------------

A: Home Assistant users can troubleshoot this issue by checking the debug log for the Victron VRM Forecast and the Qualité de l'air (Air Quality) sensors. They can also try updating the API token for the Qualité de l'air (Air Quality) sensor to a valid token.

**Q: What is the next step for Home Assistant developers?**
---------------------------------------------------------

A: The next step for Home Assistant developers is to investigate the issue and determine the cause of the problem. They can then work on a solution to fix the issue and prevent it from happening in the future.

**Q: What is the expected resolution time for this issue?**
---------------------------------------------------------

A: The expected resolution time for this issue is not known at this time. However, Home Assistant developers are working on a solution and will provide an update as soon as possible.

**Q: What is the recommended course of action for Home Assistant users?**
-------------------------------------------------------------------------

A: The recommended course of action for Home Assistant users is to wait for the solution to be implemented and then update their Home Assistant configuration file with the new API token.