Here is the PR
That means you restarted HA without waiting for the database migration to finish.
So the migration may still be working or you caused an issue where the lock hasn’t been released. If you restarted your hardware, you most likely corrupted the database. It would probably be worth while to restore from a back up and try again. But be patient and wait for the migration to complete.
Of all the times it had failed i can only imagine the update to 2023.2.1 to have caused a reboot, all the other times not to my knowledge. Also not sure how long it should take it takes hours and hours 
Yes, it’s a database migration, if you have a large database, it can take hours.
Anyone else having issues with Synology DSM?
I get “TypeError: ClientSession._request() got an unexpected keyword argument ‘max_version’”
3 Likes
Hi
Has there been any changes in relation to the synology integration?
Since the last update, I do have trouble with this integration
I haven’t done any changes on synology side, which runs under DSM 7.1.1 - 42962 update 3
Appreciate any help
Logger: homeassistant.config_entries
Source: components/synology_dsm/common.py:94
First occurred: 13:36:28 (1 occurrences)
Last logged: 13:36:28
Error setting up entry Ds216Garbsen for synology_dsm
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 382, in async_setup
result = await component.async_setup_entry(hass, self)
File "/usr/src/homeassistant/homeassistant/components/synology_dsm/__init__.py", line 68, in async_setup_entry
await api.async_setup()
File "/usr/src/homeassistant/homeassistant/components/synology_dsm/common.py", line 94, in async_setup
await self.dsm.surveillance_station.update()
File "/usr/local/lib/python3.10/site-packages/synology_dsm/api/surveillance_station/__init__.py", line 25, in update
raw_data = await self._dsm.get(self.CAMERA_API_KEY, "List", max_version=7)
File "/usr/local/lib/python3.10/site-packages/synology_dsm/synology_dsm.py", line 207, in get
return await self._request("GET", api, method, params, **kwargs)
File "/usr/local/lib/python3.10/site-packages/synology_dsm/synology_dsm.py", line 282, in _request
response = await self._execute_request(request_method, url, params, **kwargs)
File "/usr/local/lib/python3.10/site-packages/synology_dsm/synology_dsm.py", line 308, in _execute_request
response = await self._session.get(url, params=params, **kwargs)
File "/usr/local/lib/python3.10/site-packages/aiohttp/client.py", line 919, in get
self._request(hdrs.METH_GET, url, allow_redirects=allow_redirects, **kwargs)
TypeError: ClientSession._request() got an unexpected keyword argument 'max_version'
Ok, it’s definitely related to 2023.2
I just rolled back and restored from my backup and synology integration is back to work.
So I‘ll wait wit upgrade till next release. Let’s hope the reason will be discovered soon.
Anyway, no big deal, thanks to backup
1 Like
That’s nothing compared to mine and there is no way to upgrade it.
It is on my Synology, for RAID reasons and it is version 10.3.32-1040
This is the latest version available according to them.
I couldn’t do the migration, the index can’t be created, too many rows in the states table.
I was also sad, when my Android tablet stopped working properly after last update of HA
Hm…
I’m not sure what i risk by creating “select” in sql (other than not working sensors when devs decide to change db without warning…) ?I’m not changing anything in db, i’m only reading.
Some things are either hard to get in HA or not possible at all. I searched, but i didn’t find yet an alternativ HA solution for my sql needs: to get MIN and MAX temperature from midnight 'till current time. Min/max for last xy hours is not useable for me.
1 Like
Hm. How many do you actually have? Mine is ~1.5M rows for 2 weeks of “detailed” history…
For actual long-term detailed history, I use influxdb. I was keeping 2 weeks for dashboard graphs, but now that statistics are mostly used, I’m not sure it’s even necessary to keep so many days.
The risk is that the tables change and you have to update your query
I think - and that’s only my personal opinion:
The HA Devs do listen to what people want.
Just take the response about state-icon colors from the December release into account and the huge amount of “Why not making the icons configurable?”
→ That has now be implemented. And honestly: way faster than I could imagine.
In addition to that:
HA is Opensource. Meaning, in theory everyone can participate and start implementing what he think HA should provide.
But: There’s also a company behind this project, with people working full time - and they want to be payed for doing the job.
So - NabuCasa needs to taking into account what technologies could be usefull to people.
People that might not want to write yaml configs, they don’t want to spent time in front of their smartphone to trigger something.
There is a huge Userbase that want Voice Control - even those that haven’t found the way to HomeAssistant yet.
And - if only a certain amount of those peoples would sign up for the NabuCasa Cloud, that’s what pays the devs.
So… the team needs to get their way through all of these reasons.
And while we might not agree to some decisions, others do.
Personally, I really looking forward to the voice controll - and time will tell if this will replace my current solution with echo / google… etc.
3 Likes
Clear your browser cache.
1 Like
Way to much, 24M rows.
I know, it is stupid, I’m not doing any purge. I wanted to see for a year.
But those 24M are just the last 8 months
I have a question that is unrelated to this topic. How do you get those nice graphs? I’m stuck with the blocky standard graphs
HA installed as Core on rPi4 and have an issue upgrading to 2023.2.
Failed building wheel for bcrypt.
From the log I understand I need to update Rust but the system says it’s already the latest version.
sudo apt install rustc gives me this
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
rustc is already the newest version (1.48.0+dfsg1-1+rpi1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
log from upgrade:
running build_rust
=============================DEBUG ASSISTANCE=============================
If you are seeing a compilation error please try the following steps to
successfully install bcrypt:
1) Upgrade to the latest pip and try again. This will fix errors for most
users. See: https://pip.pypa.io/en/stable/installing/#upgrading-pip
2) Ensure you have a recent Rust toolchain installed. bcrypt requires
rustc >= 1.56.0.
Python: 3.10.9
platform: Linux-5.15.84-v7l+-armv7l-with-glibc2.31
pip: n/a
setuptools: 67.1.0
setuptools_rust: 1.5.2
rustc: 1.48.0 (471d696c7 2020-12-10)
=============================DEBUG ASSISTANCE=============================
error: Rust 1.48.0 does not match extension requirement >=1.56.0
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for bcrypt
Failed to build bcrypt
ERROR: Could not build wheels for bcrypt, which is required to install pyproject.toml-based projects
Give your sensors a device_class and a state_class of measurement. Then the graphs show 5 minute means with min and max shading.
1 Like
This has been replied already
1 Like
Thanks Olivier I missed that in my searching