Yup. The following linked PR is what messed up the graphs.
It looks like there’s a hard coded set of colors, and that it will start at the top of the list and work down for all variables being graphed. Not only are the colors themselves that show up first hideous pastels, they are also so close to each other that it’s difficult to tell them apart.
There’s also code in there that screws with the sizing I’m sure. The single PR has 1,616 new lines of code and removed 1,568 existing lines, so it’s a bit hard to sort through.
Problem for me is I think the new look is bloody awful by comparison to the old one. Looks clunky/chunky wastes more screen space and that it changed the colours without an easy apparent way to change them back.
I was just thinking the exact opposite. I like the new graphs. Especially the larger expanded pop-up size and the colours fit well with my themes. They are about as legible as previously. Lost the fill in my climate history graphs that indicate the AC is heating/cooling, but it is populating again from now.
No issues with the update for me other than one I created. I replaced an @ in my MariaDB recorder URL with %40 and it broke the connection. Returned to @ and all is well again.
I guess it is because the @ symbol is not in my username or password but after it?
Logger: homeassistant.setup
Source: components/lutron/__init__.py:58
First occurred: 8:53:42 PM (1 occurrences)
Last logged: 8:53:42 PM
Error during setup of component lutron
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/setup.py", line 249, in _async_setup_component
result = await task
File "/usr/local/lib/python3.9/concurrent/futures/thread.py", line 52, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/src/homeassistant/homeassistant/components/lutron/__init__.py", line 58, in setup
hass.data[LUTRON_CONTROLLER].load_xml_db()
File "/usr/local/lib/python3.9/site-packages/pylutron/__init__.py", line 534, in load_xml_db
assert(parser.parse()) # throw our own exception
File "/usr/local/lib/python3.9/site-packages/pylutron/__init__.py", line 247, in parse
for group_xml in groups.getiterator('OccupancyGroup'):
AttributeError: 'xml.etree.ElementTree.Element' object has no attribute 'getiterator'
Same issue here as well.
Looking at the ESP32 camera log it shows the API is constantly disconnecting and reconnecting.
I’m using the ESP32 GPIO pins for a couple of other sensors and they are also frequently flapping between available and unavailable in HA 2021.7 due to the API disconnects.
Removing the esp32_camera config from the device stopped the API flapping (presumably because HA stops polling the camera), but obviously that negates the point of the device.
Rolling back HA fixed the issue for me too.
I would like to say that this seems to have gone smoothly on my machine.
I think that the forum thread that mirrors the blog should specifically say that you need to read the blog post to get the important and sometimes breaking changes. I think it might be the length of frenck’s informative blog post, but by the time it is mirrored into the forum, a lot of info is missed out.
I think a lot of people get the release announcements from the forum, not the blog post. Some of us know to read the blog post to get the whole story, but others clearly don’t. People are missing breaking changes, perhaps because of this. So they should be reminded on the forum.
not seeing the error here, but I dont think you’re missing out on anything valuable… the calculations are not very accurate, or even close to any reality really…
Seems my system wasn’t worth the trouble after all. I mean, I know it is cloudy today, but still have the odd watts now (thats without the sun seeing my panels yet)
so either the sensors are a completely mixed up (only thing coming to the true current production is the next 12 hours sensor) or something else is completely off. And before you ask, yes, I did enter the correct parameters in the config…
the units are wrong too, summed production shouldn’t be in Watt, but in kWh. Not sure if thats only a frontend issue, or whether the state of these sensors in fact is in Watts, havent checked the code yet.
