PyViCare is broken since last bump. I cant add it or refresh it. i get an 500 error on this part of code:
file: home-assistant/core/blob/dev/homeassistant/components/vicare/init.py
I tried recreating the key on their dev portal, to no avail all i see in logs is
PyViCare.PyViCareUtils.PyViCareInternalServerError: (PyViCareInternalServerError(…), ‘Request failed with status code 500 and message “Internal server error”. ViCare ErrorId: req-46b155350e3d43f282f8d07507559291’)
I can confirm the issue exists with a blank system page as well after upgrading. I can verify on the mobile iPhone and PC in multiple browsers. I cleared cache in both and even reinstalled the mobile app.
For those seeing a blank settings page - it is an issue and its being looked at:
Please don’t keep replying that you have the same issue here or there (if you need a reason why, read this). Feel free to thumbs up the issue on github and follow it though. You can expect a resolution and new patch release soon.
I’m creating Bluetooth proxies for my Xiaomi temp/hum sensors running the latest ATC firmware but find this strange page. I am repurposing old ESP32s that ran Tasmota before. The whole process via the new Bluetooth proxy provisioning page completes but then I get this. I thought the device is wiped?
This is a general comment for the dev team. I consider myself an “advanced user”, I’ve installed a development environment for the front and core, I’ve been able to create my own custom devices and I read the source code when things go wrong…
I’ve the feeling that around HA source code, “small mistakes” can “break big things”. This is normally not good.
I’ll tell you an example that happened to me two days ago; I created a sensor using the node-red integration and I put “MΩ” in the unit_of_measurement field.
A month ago - more or less - I migrated my database from SQLite (inside the HA raspberry pi) to MariaDB installed in a separate server. I made the mistake of not changing the table character set to UTF-8 and the “omega” character was not compatible with the existing character set so that generated an SQL-Error.
Well, this is all my fault and, as developer, I take my responsibility on this. BUT. the point I want to highlight is that the “SQL-Error” caused the recorder integration to fail storing any other sensor value!
In other words, that mistake broke the entire recorder integration until I fixed it!
This is the point, I can understand that if I made a mistake in the unit_of_measurement value of one sensor I’ll have no values “for that sensor” stored. But that “small mistake” completely block the “recorder”.
Please, consider this as a positive feedback. Maybe a better error handling could improve user experience.
Weird of you to say that since there’s no details for you to analyze to come to that conclusion. Nothing changed except the HA version. Never had this until 2022.8.x. What made you say it’s my browser and don’t you think I already tried to adjust the window, change zoom level, clear cache cookies etc?
i think there’s a problem with multiple bluetooth adapters: raspberry + asus bt-400, both go on hci0 so it messes up things… i have to restart the raspberry, configure bt, shutdown, insert bt400, reboot, configure bt; the bt400 is active now but the raspberry adapter is marked with a configuration error…
(ps: i’m using a dongle because the raspberry adapter seems suffering of a reduced range starting from a recent update. is it possible?!)
