David Carson

> > Unfortunately, there is only 'code 1' status fault recognized by HomeKit: https://developer.apple.com/documentation/homekit/hmcharacteristicvaluestatusfault > > Edit: NoFault == 0 and generalFault == 1 > > Eve might use other...

Summary of changes needed: 1. If possible, calculate calculated fields even if there is a sensor error 2. If there is a sensor error, return the sensor_status number directly as...

> 1. If possible, calculate calculated fields even if there is a sensor error I checked the source code for the [weather formulas](https://github.com/oyve/weather-formulas) I am using and it will produce...

> 2. If there is a sensor error, return the sensor_status number directly as the StatusFault Tried this and I get an error message from HomeBridge. ``` [2/23/2024, 4:46:26 PM]...

Also, thank you very much for the testing and the feedback @wimleers and @jmissig. It does make the support better.

> 3\. Don't continuously log the sensor failure, log it every hour. Changed the logging to log initial failure and then every hour so that it doesn't spam the logs...

> 4. Make the code robust so that if apiKey and/or stationId values are missing or bad, don't crash. There are two changes needed here (https://github.com/naofireblade/homebridge-weather-plus/pull/285/commits/db03a9ecfaf8a8b57d13a77e6e8538bd80431a80). First change is to...

> [20c96ea](https://github.com/naofireblade/homebridge-weather-plus/commit/20c96ea5b808b412ef94e488e5bb664ebeec645d) specified `0` as the minimum temperature. That’s true in Kelvin (“absolute zero”), but not in Celsius, where negative degrees are freezing temperatures. I realized this too, yesterday. I...

Yes. The configuration page was unfortunately broken. Because there was one spelling for the field where you entered the value, and then another name in the config file. So the...

I started to investigate a migration path, and I wonder if this would work. I would **add** the correct spelling rather than correcting the spelling. The result is that the...