Your Bluetooth adapter is stuck/crashed, but since there regression in the bluetooth adapter auto recovery code which is fixed in 2023.9.2, it cannot be reset automatically. You can still unplug/power cycle it to reset it manually in the mean time.
I too am experiencing huge, degraded frontend and slowness issues. In some cases this frontend loading slowness has actually crashed my Proxmox host, requiring a reboot.
I can wait up to 1 minute (worst case circumstances) after opening the HA app, for my dashboard to load and become usable.
Hi.
After update HA my IamMeter modbus don’t read data. I must use backup to previous version of ha and IamMeter modbus work fine. I try everything. Log file:
Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File “/config/custom_components/iammeter_modbus/init.py”, line 143, in async_refresh_modbus_data
update_result = self.read_modbus_data()
^^^^^^^^^^^^^^^^^^^^^^^
File “/config/custom_components/iammeter_modbus/init.py”, line 173, in read_modbus_data
return self.read_modbus_holding_registers()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/config/custom_components/iammeter_modbus/init.py”, line 189, in read_modbus_holding_registers
inverter_data.registers, byteorder=Endian.Big
^^^^^^^^^^
File “/usr/local/lib/python3.11/enum.py”, line 784, in getattr
raise AttributeError(name) from None
AttributeError: Big
On the more info on light: weren’t we supposed to be able to change that percentage above the slider to show the actual temp value likt it shows when sliding ?
Seems odd to show the brightness percentage while having selected the color-temp button
Can only click the last-changed to change format now
The file editor is broken for me too after installing 9.1. I get “file not found” for configuration.yaml and the file system is empty, so I can’t inspect for errors to post here.
Several other lovelace cards are only partially working with some custom:card_templater features not working.
I’ve tried restoring to 9.0 which makes my card work OK but still no file system that I can access. It must be there somewhere otherwise all my other cards wouldn’t be working.
another Frontend thingy. with all the development/attention having gone to the Tile cards features, why is the compactness of its original (mushroom) not imported? out of the main options we now seem to have in either core )tile and thermostat) and custom Mushroom remains the winner imho:
all three have the same new and shiny more-info, so thats not important for selecting either of these cards.
the original Thermostat shows all info, and the mushroom compresses that even further into a 1 height card.
its the tile card that stands out to be the card taking most space, and revealing least info… those full width sliders and buttons are a true waste of screen/card estate, makes me wonder if I do something wrong here?
But BTW and related to this. Why is there so much space on mobile, which could be used, but the buttons are at the bottom in one singlehorzontal scroll row?
I have compact features in mind.
Features has been designed to be more flexible than mushroom controls. Because you can change the order for example and there is no limit for the number of features you can add. So it’s not easy to find a good UX to switch between these different features.
I don’t have yet a good solution to switch because 3 controls/features. For example inmushroom there are two buttons to switch between brightness, color and color temp for light card but the UX is not good enough to be on the tile card.
its just that we all want to use core cards as much as possible, but your Mushroom makes it very difficult for us
not sure what your thoughts on ‘not good enough’ are, I find the UX rather satisfactory. If only for the completeness, showing all relevant numbers. As it stands we are obliged to click for the more-info to see the current And target.
Was there an unknown/unintended breaking change with the MyQ integration? After updating to this version, the MyQ integration fails to initialize. I tried deleting the integration and re-adding it, and it successfully signs into my account, but the integration continuously fails to initialize, even after full reboots.
After checking logs, the following is reported, so it’s possible it’s an issue on the MyQ side and not HA?
Config entry '{REDACTED EMAIL}' for myq integration not ready yet: Error requesting data from https://devices.myq-cloud.com/api/v5.2/Accounts/{REDACTED}/Devices: 403 - Forbidden; Retrying in background
Haven’t investigated deeply but my Z-Wave network has been super flakey after this update. It’s never been flakey ever since the move to Z-Wave JS a couple years ago. I’m getting Z-Wave events that are verified as firing in the Developer Tools but that don’t trigger their automation. I’m getting light switches that don’t respond to HA. I’ve restarted the whole system twice and each time things have gone back to normal for a while. I’ll keep watching for patterns.
This will get lost in this thread, suggest you post a separate question. But you will need more detail - your modbus config, and what you have tried (not “tried everything”!).
My Iammeters work OK in 2023.9, albeit there is an issue with comms dropping which stops the sensors working as it does not retry. Search for recent posts on modbus.
theres also a new feature on the trigger templates: they’re counting twice now
somehow the response has been a bit low, making me wonder if people actually noticed/suffer the issue, or use this kind of trigger templates a lot, but it might be worth checking.
It was first noticed in the Heads up Persisten notifications thread, and another topic or here. Not yet really centralized yet, so here’s call to please check in your configs and +1 if indeed experienced
