When we can see full support for day/night electricity in utility meter without crutches?
No, thank for idea
Does the Passive BLE monitor integration still work, with the Python 3.10 update?
Edit: it should work according to devs, they donât use bluepy nor pybluez.
Iâve never put much trust in that addon. Way too many false positives.
Make a backup, update then fix any breaking changes you need to.
If you donât like the update for some reason then rolling back to the previous version is one command and less than 5 minutes away.
ha core update --version 2022.6.7
4 Likes
Same for me, with the same setup 
leave a thumbs up for the initial issue
HaHa, Tom. I already did that in my recorder.yaml file. Itâs just broken now because the default behavior of the History panel changed to accommodate the masses who were unwilling to filter their data to improve their view, minimize their DB, and improve overall performance.
Iâm sorry, but suggesting that I go create a completely new dashboard with history graphs for the 156 entities listed in my recorder.yaml is absurd (and not at all amusing).
Anybody who has a recorder.yaml file (or a history.yaml) file now has to sort through perhaps several hundred entities, most of which donât even have any history in the DB. At a minimum, the drop-down list should at least be cognizant of whether the entity it is displaying to the user actually has any history to show if selected. 
5 Likes
I too have extensively managed my recorder, history and logbook.
However I rarely if ever use the history as all the history info I need is in my views.
Sorry you feel offended, it was just a suggestion.
1 Like
I should add that I run the following integrations âŚ
[âmqttâ, âtadoâ, âfritzâ, âdeconzâ, âfullykioskâ, âreolink_devâ, âmobile_appâ, âmotioneyeâ, âshellyâ, âtesla_wall_connectorâ, âfritzboxâ, âonvifâ, âmjpegâ, âicloudâ, âbrowser_modâ, âspotifyâ, âalexa_mediaâ, âaccuweatherâ, âsqlâ, âforecast_solarâ, âfritzbox_callmonitorâ, âhacsâ, âippâ, âsolcast_solarâ, âwatchmanâ, âhassioâ]
Created with
{% set devices = states | map(attribute='entity_id') | map('device_id') | unique | reject('eq',None) | list %}
{%- set ns = namespace(integrations = []) %}
{%- for device in devices %}
{%- set ids = device_attr(device, 'identifiers') | list | first %}
{%- if ids and ids | length == 2 %}
{%- set integration, something_unique = ids %}
{%- if integration not in ns.integrations %}
{%- set ns.integrations = ns.integrations + [ integration ] %}
{%- endif %}
{%- endif %}
{%- endfor %}
{{ ns.integrations }}
I had exactly the same with Toon integration
I used this redirect link:
https://My.home-assistant.io/auth/external/callbacks
Change the domain to your own 
No worries, Tom. Itâs not you. Itâs just that the more I use it the more frustrated I get with it.
It appears that the suggestion in beta to maintain the previous filter set was implemented, but if that relies on browser storage, then it will disappear every time I close my browser (thatâs just how I roll).
Hereâs an example: To reproduce what I had before in the History Panel, I would have to select 156 entities, since there is no way to select the particular ones using the filter system provided (e.g., combo of area, device, entity). And if I average 8 entities filter âbubblesâ per row, thatâs 20 rows of entity bubbles at the top of the page before I ever get to the actual history. I think this use case was missed.
I admit, I have very little history on my dashboard, because I used the History Panel for that purpose. When I needed history for a particular entity, I just clicked on that entity in the UI.
I think a simple fix would be an option to âdisplay all based upon Recorder/History filter.â That would make me extremely happy! 
3 Likes
What install method (core, container, HAOS or supervised)?
Configuration check is deprecated.
Iâve seen others reporting similar outputs with 2022.7.0, I believe it has to do with the newer Python (maybe the configuration add-on itself).
1 Like
Iâm currently trying to update, and lets see what happens.
Hi, the update looks nice and I love the new history filter. However configuration checker is stuck in a loop, and the history filter gets stuck on one location, an error some were in the config not in the YAML file with an unrecognised symbol < between binary sensor and binary sensor (should have noted this down before doing the restore sorry).
I had to restore from backup.
1 Like
I had to go back to 2022.6.7 because system was laggy and unreliably working, most probably due to recorder issues, like the one reported here.
After going back to 2022.6.7, all back to normal.
Anyone else with this issue?
Could you provide info on what settings are there with ZHA? Maybe a screenshot?
About history. I used one or two times without issues.
third test where I choose one area with 1 week data, I get the page waiting ⌠and this is keep like this since minutes. Even refresh is keeping the state. I see one request to card-mod.js in 404 in developper mode. The referer is history. I donât know if itâs link to this
Can we please also get âUpdate Device Firmwareâ in UI for Zigbee devices OTA updates via ZHA?
https://www.home-assistant.io/integrations/zha#ota-firmware-updates
ZHA integration does support OTA firmware updates for Zigbee devices but there are no UI settings.
Please consider reusing backend and frontend code from Z-Wave JS for this in ZHA too if possible:
4 Likes