I will check my tasmotas. I also yse Mosquitto Addon and integration. Thanks.
Maybe there is something related to an update of tasmota:
"Tasmota 9.5.0
BREAKING Lights using MQTT discovery will not work correcty in Home Assistant 2021.5 due to new color modes. Upgrade to v9.5 of Tasmota and use Tasmota integration"I am using 9.1.0 in some and much older in others (which has no discovery, so they are not the problem).
Ah I have everything on 9.5.0 and don’t have any lights, it’s all plugs and ESP8266 for various things
I was just thinking about Gas consumption.
With my provider (Octopus Energy) they have an API I can grab all of my usage for yesterday.
After lots of messing around in nodered would it be possible to populate a sensor with yesterdays information then add that into the energy panel.
Hey, all this new stuff is cool but there is a bug that this very annoying and already have months without a fix. The Google Cast integration makes JBL speakers with Google Assistant unresponsive and I needed to disable the integration because I got so frustrated that everytime when I tried to use my speaker it only say to open the Google Home app. The only temporary fix is to reboot the speaker. Disabling the integration ceased the problem but now I cant get voice notifications on my speakers. A bug report was already filled up in GitHub
I updated my RPI4B w/SSD yesterday and generally went fine (logs complained about a few things in config but nothing that got in the way of coming up). I would still suggest waiting as my HA locked up about 1:30am and was totally unresponsive. As it’s on a top shelf, couldn’t plug into keyboard and monitor to check locally so powered down and restarted. It felt very warm to the touch and when it did come back up, history for CPU temp was blank from 1:30am till 7am when I restarted, then started out at about 150 deg F, finally settling back to about 120 deg F within about an hour.
I suspect my issue is actually unrelated to 2021.9, or at least was something already in play that was exacerbated by the update, since swap memory had climbed daily starting at midnight every day the last 3 days and was up around 75% when the system crashed, is now back down at 2%.
Next time, I’ll wait for second release of the month to be on safe side, particularly after seeing issues people with RPI3 are having.
Mine upgraded fine and did not crash. Actually I seemed to be having some sort of memory leak with the previous version which I have not seen yet on this version. Maybe unrelated but the available memory is at its highest.
I did notice something off in the Energy Tab post upgrade though. I posted here:
I don’t know if the addon expose the rest api.
My Aqara Opple remotes have stopped sending events (on button press) after upgrading, anyone have any ideas? I have these added via ZHA.
Tasmota themselves now recommend using the HA Tasmota integration. If you’re using HA OS or a supervised install you should use the MQTT Broker provided and configure MQTT via the GUI instead of yaml as well. Tasmota are gradually withdrawing features for MQTT Discovery in HA now as well. So use the MQTT Broker addon, GUI for MQTT and add the tasmota integration as well.
Thanks. I’m in a Yarra Valley Water and it looks like they are only testing in one suburb and not taking volunteers. Hopefully we’ll get this one day. There’s no mention of in-home reading of the meters that I saw.
My energy panel seems to have stopped updating costs after the update.
It has been working great and you can see in the pic it was updating in the morning but after the upgrade it has carried on with energy but the costs haven’t updated and today is 3.77kWh peak but 0p.
I have tried removing and re-adding the sensors and also set them to different prices but doesn’t seem to work.
13.7kWh x 0.055 for offpeak should be 75p ish
Not sure if you managed to get an anwser. The long term statistics are allso stored in the HA db if you use the standard config.
You could install SQLite Web add on to explore this data. In statitics_meta you can find the ID for the sensor , then in statistics you could run:
delete
FROM “statistics”
where metadata_id =‘YOUR ID FROM STATISTICS_META’
This will delete ALL data for the ID you select. Offcource you can add additional operators in the where clause to limit the results.
(Allways create a backup before running queries like this. 
)
Ah yes, reading that thread it looks like that is my problem.
Logger: homeassistant.components.sensor.recorder
Source: components/sensor/recorder.py:353
Integration: Sensor (documentation, issues)
First occurred: 3 September 2021, 23:12:07 (2 occurrences)
Last logged: 3 September 2021, 23:12:07
The unit of sensor.energy_real_sensors_day_kwh_offpeak_cost (GBP) does not match the unit of already compiled statistics (EUR). Generation of long term statistics will be suppressed unless the unit changes back to EUR
The unit of sensor.energy_real_sensors_day_kwh_peak_cost (GBP) does not match the unit of already compiled statistics (EUR). Generation of long term statistics will be suppressed unless the unit changes back to EUR
So I guess it is getting supressed.
Will have to have a look at it later, not sure why the upgrade has caused this though I don’t think I have changed EUR to GBP at anypoint.
Just updated to core-2021.9.2 and looking at my Shelly i3 all entities for the 3 entries are gone. In the device “Shelly i3…” have only 4 entities left and all are marked as “not available”.
Cloud, firmwareupdater, RSSI and uptime.
Shelly Firmware is latest v1.11.3, CoIoT and MQTT are activated as well.
Hi, Just installed 2019.9.3
can anyone help me out where I can find a recap of all issues?
Currently I am looking at:
twitter / facebook / github for some integrations / this thread / this website
but no overview of issues found.
for me energy is not working anymore,
new integration for tractive not working, I am getting error " Config flow could not be loaded"
So not searching enough can cause many new threads/ questions while there is an answer somewhere 
As explained on FB group, There are no list of per release issues, all issues if they are reported are on github.
The best you can do is search with the string, core-2021.9, this is only applicable if they have added that in their issue
Issues · home-assistant/core (github.com)
maybe a suggestion for future to tag all issues with label of version. So a kind of recap page can be build to show all known/ repported issues
I think it can prevent a lot of double questions.
for me as a relative newbie it is a very big forest right now, and I can not so any trees at all.
I had to find out via twitter the initial release was withdrawn, why it was not reported in this blog?
You can search the issues by version, but that will fall down if the person reporting it fails to add it
just add something like core-2021.9 and it should pickup all those with it in