WLL Health: WeatherLink API Error: 403

[Dinant]

In the MXdiags the following line is shown very often:

Code: Select all

WLL Health: WeatherLink API Error: 403, Access is not authorized for station xxxx

Also the webtag <#LatestError> shows this error.
Because I have no paid subscription to use weatherlink.com I know this function is not allowed.
Is it possible to disable those error messages?

[mcrossley]

If you do not have any API information in the configuration, the call will be supressed.

[Dinant]

Mark, thanks for your quick response.

Is the data uploaded to weatherlink.com If I remove the API information?
I want to upload the data to weatherlink.com but I don't use the history (catch up) function of the weatherlink api.
Is that possible without setting the error level to Error?

[mcrossley]

Yes, MX does not upload anything to weatherlink.com, it only reads from it.

[Dinant]

Yes that does the job.

[Dinant]

I've removed the API keys.
Now after a restart a message is shown in the MXdiag file. That's fine for me but the webtag <#lastesterror> still shows an error:
"WLL - No WeatherLink.com API configuration supplied, just going to work locally".
For me this is not an error but more a warning.

[mcrossley]

I haven't checked, but it probably is a warning? Or have you also changed the logging level?

[Dinant]

I haven't checked, but it probably is a warning? Or have you also changed the logging level?

No I didn't change the warning level.
If it is a warning it shouldn't be in the <#lasterror> webtag.
I have tested it again but now another messaage is shown which overwrites the first message.

It is possible to see if it is a warning or an error?
I can't see the difference in the MXdiag file.
Maybe it is a good idea to add the word ERROR/WARNING/DEBUG after the date and time to the log.
An example of the logfile of Home Assistant:

Code: Select all

2024-03-22 07:53:08.342 WARNING (MainThread) [homeassistant.const] TEMP_CELSIUS was used from nefiteasy, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfTemperature.CELSIUS instead, please create a bug report at https://github.com/ksya/ha-nefiteasy/issues
2024-03-22 07:53:08.345 WARNING (MainThread) [homeassistant.const] VOLUME_CUBIC_METERS was used from nefiteasy, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfVolume.CUBIC_METERS instead, please create a bug report at https://github.com/ksya/ha-nefiteasy/issues
2024-03-22 07:53:10.590 DEBUG (Thread-2 (_connect)) [RFXtrx] Send: 0x0d 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
2024-03-22 07:53:10.891 DEBUG (Thread-2 (_connect)) [RFXtrx] Send: 0x0d 0x00 0x00 0x01 0x02 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
2024-03-22 07:53:10.924 DEBUG (Thread-2 (_connect)) [RFXtrx] Recv: 0x14 0x01 0x00 0x01 0x02 0x53 0x30 0x00 0x80 0x06 0x02 0x03 0x01 0x00 0x13 0x7f 0x46 0x58 0x43 0x4f 0x4d
2024-03-22 07:53:10.924 DEBUG (Thread-2 (_connect)) [RFXtrx] Send: 0x0d 0x00 0x00 0x00 0x03 0x53 0x00 0x00 0x80 0x06 0x02 0x00 0x00 0x00
2024-03-22 07:53:11.071 DEBUG (Thread-2 (_connect)) [RFXtrx] Recv: 0x14 0x01 0x00 0x00 0x03 0x53 0x30 0x00 0x80 0x06 0x02 0x03 0x01 0x00 0x13 0x7f 0x46 0x58 0x43 0x4f 0x4d
2024-03-22 07:53:11.071 DEBUG (Thread-2 (_connect)) [RFXtrx] Send: 0x0d 0x00 0x00 0x01 0x02 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
2024-03-22 07:53:11.095 DEBUG (Thread-2 (_connect)) [RFXtrx] Recv: 0x14 0x01 0x00 0x01 0x02 0x53 0x30 0x00 0x80 0x06 0x02 0x03 0x01 0x00 0x13 0x7f 0x46 0x58 0x43 0x4f 0x4d
2024-03-22 07:53:11.095 DEBUG (Thread-2 (_connect)) [RFXtrx] Status: Status [subtype=433.92MHz, firmware=48, output_power=0, devices=['ac', 'arc', 'blindst1234', 'homeconfort']]
2024-03-22 07:53:11.095 DEBUG (Thread-2 (_connect)) [RFXtrx] Send: 0x0d 0x00 0x00 0x03 0x07 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
2024-03-22 07:53:11.223 DEBUG (Thread-2 (_connect)) [RFXtrx] Recv: 0x14 0x01 0x07 0x03 0x07 0x43 0x6f 0x70 0x79 0x72 0x69 0x67 0x68 0x74 0x20 0x52 0x46 0x58 0x43 0x4f 0x4d
2024-03-22 07:53:14.056 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'hacs' accesses hass.components.frontend. This is deprecated and will stop working in Home Assistant 2024.9, it should be updated to import functions used from frontend directly at custom_components/hacs/frontend.py, line 68: hass.components.frontend.async_register_built_in_panel(, please create a bug report at https://github.com/hacs/integration/issues
2024-03-22 07:53:15.393 WARNING (MainThread) [homeassistant.components.climate.const] CURRENT_HVAC_HEAT was used from nefiteasy, this is a deprecated constant which will be removed in HA Core 2025.1. Use HVACAction.HEATING instead, please create a bug report at https://github.com/ksya/ha-nefiteasy/issues
2024-03-22 07:53:15.400 WARNING (MainThread) [homeassistant.components.climate.const] CURRENT_HVAC_IDLE was used from nefiteasy, this is a deprecated constant which will be removed in HA Core 2025.1. Use HVACAction.IDLE instead, please create a bug report at https://github.com/ksya/ha-nefiteasy/issues
2024-03-22 07:53:15.406 WARNING (MainThread) [homeassistant.components.climate.const] HVAC_MODE_HEAT was used from nefiteasy, this is a deprecated constant which will be removed in HA Core 2025.1. Use HVACMode.HEAT instead, please create a bug report at https://github.com/ksya/ha-nefiteasy/issues
2024-03-22 07:53:15.412 WARNING (MainThread) [homeassistant.components.climate.const] SUPPORT_PRESET_MODE was used from nefiteasy, this is a deprecated constant which will be removed in HA Core 2025.1. Use ClimateEntityFeature.PRESET_MODE instead, please create a bug report at https://github.com/ksya/ha-nefiteasy/issues
2024-03-22 07:53:15.415 WARNING (MainThread) [homeassistant.components.climate.const] SUPPORT_TARGET_TEMPERATURE was used from nefiteasy, this is a deprecated constant which will be removed in HA Core 2025.1. Use ClimateEntityFeature.TARGET_TEMPERATURE instead, please create a bug report at https://github.com/ksya/ha-nefiteasy/issues
2024-03-22 07:53:15.419 WARNING (MainThread) [homeassistant.const] TEMP_CELSIUS was used from nefiteasy, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfTemperature.CELSIUS instead, please create a bug report at https://github.com/ksya/ha-nefiteasy/issues
2024-03-22 07:53:15.420 WARNING (MainThread) [homeassistant.helpers.entity] Entity None (<class 'custom_components.nefiteasy.climate.NefitThermostat'>) is using deprecated supported features values which will be removed in HA Core 2025.1. Instead it should use <ClimateEntityFeature.TARGET_TEMPERATURE|PRESET_MODE: 17>, please create a bug report at https://github.com/ksya/ha-nefiteasy/issues and reference https://developers.home-assistant.io/blog/2023/12/28/support-feature-magic-numbers-deprecation
2024-03-22 07:53:16.665 WARNING (MainThread) [bellows.zigbee.repairs] Fixing invalid TCLK partner IEEE (e0:79:8d:ff:fe:1d:00:96 => 00:12:4b:00:23:93:3a:40)
2024-03-22 07:53:16.674 WARNING (MainThread) [bellows.zigbee.repairs] NV3 interface not available in this firmware, please upgrade!
2024-03-22 07:56:41.668 ERROR (MainThread) [homeassistant.components.shelly] Error fetching shellyplug-s-80646F813F71 data: Error fetching data: DeviceConnectionError()
2024-03-22 08:10:36.668 ERROR (MainThread) [homeassistant.components.shelly] Error fetching shellyplug-s-80646F813F71 data: Error fetching data: DeviceConnectionError()
2024-03-22 08:29:16.033 WARNING (Thread-7 (_listen)) [homeconnect.sseclient] Exception while reading event: 

It looks nice in my opinion.

[mcrossley]

It does, but going through a couple thousand messages and changing them isn't a trivial task! Don't expect anything soon.

The latest error web tag uses the same logging filter as the recent errors display. Set it to error if that is all you want to see.

HA is using a "proper" logging system as well. MX isn't for the main log, but v4 uses that sort of logging for the FTP log.

[Dinant]

It does, but going through a couple thousand messages and changing them isn't a trivial task! Don't expect anything soon.

Ok, I understand from your answer there is no separate function/parameter for errors and warnings already. So indeed that will be a lot of work.
Everything is working fine so this has no priority. It's nice to have!

The latest error web tag uses the same logging filter as the recent errors display. Set it to error if that is all you want to see.

OK, I will set the filter to error. That's a good hint. Thanks!