Closed mpfl closed 2 years ago
Sorry about that! I see the bug and am fixing now.
I was just going to say that I had the same issue, BUT then I restarted my RPi (after updating) and it was fine.
However, I just updated to the new version 7.03, and it seems to be dumping extra information in the command lines now?
@Anto79-ops Ugh, somehow, those crept back into #222 (despite me deleting them).
@bachya lol I'd like to buy you a coffee! Where is your buy a coffee link?
@Anto79-ops That's very kind of you; thank you! https://www.buymeacoffee.com/bachya1208P
I'm still seeing this error in the latest docker hub image. does it take a while for the fix to make it there?
@barcar Please post logs.
@bachya
@barcar Please post logs.
I've posted the latest logs to:
Thanks for any help.
@barcar Looks like you are experiencing a similar issue with the simmer zone sensor. 🤦🏻 I'll get working on a fix!
@barcar Actually, I don't see a gateway payload in your logs; could you please provide that?
@barcar Actually, I don't see a gateway payload in your logs; could you please provide that?
That's great - thanks so much for looking at it. I've updated the Gist I posted previously.
@barcar I'm still not seeing the posted payload. It would be recurring throughout the log and contain the string Received data from the Ecowitt device
.
Ok - let's try this...
2022-07-29 15:52:17,468 | ecowitt2mqtt | DEBUG | Received data from the Ecowitt device: {'PASSKEY': 'XXXXXXXXXXXXXXXXXXXXXX', 'stationtype': 'GW1100A_V2.1.7', 'runtime': '14158', 'dateutc': '2022-07-29 14:52:16', 'tempinf': '74.30', 'humidityin': '55', 'baromrelin': '30.029', 'baromabsin': '30.029', 'tempf': '79.34', 'humidity': '35', 'winddir': '233', 'windspeedmph': '0.22', 'windgustmph': '1.12', 'maxdailygust': '4.47', 'solarradiation': '435.03', 'uv': '4', 'rainratein': '0.000', 'eventrainin': '0.000', 'hourlyrainin': '0.000', 'dailyrainin': '0.000', 'weeklyrainin': '0.000', 'monthlyrainin': '0.000', 'yearlyrainin': '7.917', 'totalrainin': '7.917', 'wh65batt': '0', 'freq': '868M', 'model': 'GW1100A'}
Thanks, @barcar. Unfortunately, that latest payload works fine when added to the test suite; your error occurs at a specific temperature other than that.
The thermal perception issue was caused because my ranges had a gap. I don't see any similar gap in the Simmer Zone ranges:
If you can go back in the log and find that Received data from the Ecowitt device
line before the exception occurs, paste that here. Otherwise, I'll leave this open until you experience it again.
Here's my full log from startup to failure:
https://gist.github.com/barcar/fc8ae1bab36b09d5e86c5ff95f388321
@barcar Thanks! Here's the payload that immediately precedes the error:
{
"PASSKEY": "XXXXXXXXXXXXXXXXX",
"stationtype": "GW1100A_V2.1.7",
"runtime": "14158",
"dateutc": "2022-07-29 14:52:16",
"tempinf": "74.30",
"humidityin": "55",
"baromrelin": "30.029",
"baromabsin": "30.029",
"tempf": "79.34",
"humidity": "35",
"winddir": "233",
"windspeedmph": "0.22",
"windgustmph": "1.12",
"maxdailygust": "4.47",
"solarradiation": "435.03",
"uv": "4",
"rainratein": "0.000",
"eventrainin": "0.000",
"hourlyrainin": "0.000",
"dailyrainin": "0.000",
"weeklyrainin": "0.000",
"monthlyrainin": "0.000",
"yearlyrainin": "7.917",
"totalrainin": "7.917",
"wh65batt": "0",
"freq": "868M",
"model": "GW1100A",
}
When I try that payload against 2022.07.6, it works as expected (no exception). Can you confirm what version you're using?
The latest Docker image appears to also be v2022.7.6
But I think I found the issue - I had set:
ECOWITT2MQTT_INPUT_UNIT_SYSTEM=metric
Where I think my station always outputs imperial. When I changed that I'm no longer getting the error.
Sorry for wasting your time. User error I think.
Ah, okay – that makes sense: 79.34°F is 26.3°C, which is below even the lowest minimum for which Simmer Index is defined. No worries at all! Glad you're off and running. 👍🏻
Describe the bug Updating to 2022.07.02 has broken my implementation. Looking at the logs, it seems that the new thermal perception sensor is expecting some values that it cannot find, and throwing an unhandled exception.
To Reproduce Steps to reproduce the behavior:
Diagnostics
Additional context ecowitt2mqtt has been working flawlessly for months until this latest release.