The topic is acurite/loop and the payload is a JSON dictionary. The temperature value you want is in one of the dictionary’s keys. You access the key’s value with value_json.outTemp_C.
And it finally gives something other than “Unknown”, the whole response string. At least now, using the template you gave me, I should be able to figure out the rest. Thanks.
I think you’re falsely linking the update to this ‘change’. Home assistant only reads the topics (unless you’re publishing from HA). Your topic changed, therefore what ever is creating this topic is what changed.
Perhaps you meant 2022.11.5 because that’s currently the latest release (2022.11.6 was never released and 2022.12.0 should be available today).
What is responsible for publishing to acurite/loop? Like petro said, it’s not likely that the issue you experienced is due to a Home Assistant upgrade but rather to a change in whatever is publishing to acurite/loop.
Yeah, sorry. I went from 2021.8.6.to 2022.11.5. Mixed up the last digit. But now that I remember it, I did update my Weewx installation a few months ago and I basically only use the outside temperature in an automation that sets the time in the morning the thermostats raise their set points based on how cold it is outside. Now that it’s getting cold, I noticed it wasn’t working as expected and saw all my weather station data was unknown. With all my Tasmota lights going unresponsive after the upgrade, I made he wrong 1+1. But now, it’s back Thanks.
PS. The automation uses the ‘Environment Canada’ temperature sensor for my city if my weather station data can’t be read but that one was broken with the update. It used to be configured in the configuration.yaml file but now it’s an integration. Looks like I’ll need a fallback for my fallback lol