SynologyDSM sensors are not working post 0.95 upgrade. The docs show the new “name” setting as optional but that is not the case.
Downgrading to 0.94.4, the sensors still work.
1 Like
Maybe read the release about the breaking change?
- Added name to sensors (@cliffordwhansen - #24525) (synologydsm docs) (breaking change)
And my config is exactly the same as per https://github.com/home-assistant/home-assistant/pull/24525, so perhaps stop assuming people are dumb and can’t read?
Where did i assume people are dumb, ffs get a grip. i just posted a link to the change
You assumed I hadn’t read the article like a competent human being and directed me (quite unhelpfully) to docs I’ve already reviewed and made the required changes to my sensors.yaml.
1 Like
Ahh well, cant help some people then, if they think showing them about a change that i have no way of knowing or that they had not indicated they had read.
It’s the re-authenticate message for Google calendar you are talking about? Have you re-authenticated as per the instructions in the persistent notification and restarted hass?
you’re right, unrelated to this update. As a matter of fact, I now remember this has been an issue for a longer period, and fellow members and I posted on it earlier. Much earlier…
Hi,
check Google Calendar config the authentication seems to be there
.95.0 just about completely broke my Google Assistant Integration. After applying the update, only 3 devices were able to be controlled (Wifi/IP switches) and none of my Z-Wave devices were no longer recognized in Google Assistant. I decided to unlink the hass.io service in Google Assistant and then re-link it, but I was no longer able to link. It would just error and tell me to check my network connection. I rolled back to .94.4 and I was able to get it all working again.
Did the re-authentication for google calendar work for you then, if you did it?
Yes it work! I found it this morning.
I thought the new platform google_cloud was the problem, my bad.
So, Google calendar is ok, but I have a “tts.google_cloud” platform not found when validating my config in configuration panel. I have re-installed HA instance (just in case) but still no luck.
If you have an idea
Thank you for your help 
2 Likes
more error logs on bluetooth docker:
2019-06-27 13:52:19 WARNING (SyncWorker_19) [switchbot] Failed to connect to Switchbot
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/switchbot/__init__.py", line 35, in _connect
bluepy.btle.ADDR_TYPE_RANDOM)
File "/usr/local/lib/python3.7/site-packages/bluepy/btle.py", line 391, in __init__
self._connect(deviceAddr, addrType, iface)
File "/usr/local/lib/python3.7/site-packages/bluepy/btle.py", line 439, in _connect
raise BTLEDisconnectError("Failed to connect to peripheral %s, addr type: %s" % (addr, addrType), rsp)
bluepy.btle.BTLEDisconnectError: Failed to connect to peripheral d7:2e:95:d5:29:38, addr type: random
2019-06-27 13:52:19 ERROR (SyncWorker_19) [switchbot] Cannot connect to switchbot.
2019-06-27 13:52:22 WARNING (MainThread) [homeassistant.components.sensor] Updating mitemp_bt sensor took longer than the scheduled update interval 0:00:30
2019-06-27 13:52:42 WARNING (SyncWorker_15) [homeassistant.components.mitemp_bt.sensor] Polling error Exit read_ble, no data (<Thread(SyncWorker_15, started daemon 139800287889152)>)
2019-06-27 13:52:42 WARNING (SyncWorker_7) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 58:2D:34:32:E1:6F
2019-06-27 13:52:52 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.living_room_temp_battery is taking over 10 seconds
2019-06-27 13:52:53 WARNING (MainThread) [homeassistant.components.sensor] Updating mitemp_bt sensor took longer than the scheduled update interval 0:00:30
2019-06-27 13:53:23 WARNING (MainThread) [homeassistant.components.sensor] Updating mitemp_bt sensor took longer than the scheduled update interval 0:00:30
2019-06-27 13:53:38 WARNING (SyncWorker_13) [homeassistant.components.mitemp_bt.sensor] Polling error Exit read_ble, no data (<Thread(SyncWorker_13, started daemon 139800304674560)>)
2019-06-27 13:53:54 WARNING (SyncWorker_7) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 58:2D:34:32:E1:6F
2019-06-27 13:53:54 WARNING (SyncWorker_0) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 58:2D:34:32:E1:6F
2019-06-27 13:54:04 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.living_room_temp_battery is taking over 10 seconds
2019-06-27 13:54:25 WARNING (MainThread) [homeassistant.components.sensor] Updating mitemp_bt sensor took longer than the scheduled update interval 0:00:30
2019-06-27 13:54:49 WARNING (SyncWorker_11) [homeassistant.components.mitemp_bt.sensor] Polling error Exit read_ble, no data (<Thread(SyncWorker_11, started daemon 139800866690816)>)
2019-06-27 13:55:06 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.living_room_temp_battery is taking over 10 seconds
2019-06-27 13:55:27 WARNING (MainThread) [homeassistant.components.sensor] Updating mitemp_bt sensor took longer than the scheduled update interval 0:00:30
2019-06-27 13:55:54 WARNING (SyncWorker_4) [homeassistant.components.mitemp_bt.sensor] Polling error Exit read_ble, no data (<Thread(SyncWorker_4, started daemon 139801261360896)>)
2019-06-27 13:55:54 WARNING (SyncWorker_11) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 58:2D:34:32:E1:6F
2019-06-27 13:55:54 WARNING (SyncWorker_12) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 58:2D:34:32:E1:6F
2019-06-27 13:55:57 WARNING (SyncWorker_13) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 58:2D:34:32:E1:6F
2019-06-27 13:55:57 WARNING (SyncWorker_12) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 58:2D:34:32:E1:6F
2019-06-27 13:56:07 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.living_room_temp_battery is taking over 10 seconds
2019-06-27 13:56:28 WARNING (MainThread) [homeassistant.components.sensor] Updating mitemp_bt sensor took longer than the scheduled update interval 0:00:30
2019-06-27 13:56:44 WARNING (SyncWorker_7) [homeassistant.components.mitemp_bt.sensor] Polling error Exit read_ble, no data (<Thread(SyncWorker_7, started daemon 139800900261632)>)
2019-06-27 13:56:59 WARNING (SyncWorker_15) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 58:2D:34:32:E1:6F
2019-06-27 13:57:09 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.living_room_temp_battery is taking over 10 seconds
2019-06-27 13:57:30 WARNING (MainThread) [homeassistant.components.sensor] Updating mitemp_bt sensor took longer than the scheduled update interval 0:00:30
2019-06-27 13:57:55 WARNING (SyncWorker_12) [homeassistant.components.mitemp_bt.sensor] Polling error Exit read_ble, no data (<Thread(SyncWorker_12, started daemon 139800313067264)>)
2019-06-27 13:58:01 WARNING (MainThread) [homeassistant.components.sensor] Updating mitemp_bt sensor took longer than the scheduled update interval 0:00:30
2019-06-27 13:58:05 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.living_room_temp_humidity is taking over 10 seconds
2019-06-27 13:58:32 WARNING (MainThread) [homeassistant.components.sensor] Updating mitemp_bt sensor took longer than the scheduled update interval 0:00:30
2019-06-27 13:58:48 WARNING (SyncWorker_11) [homeassistant.components.mitemp_bt.sensor] Polling error Exit read_ble, no data (<Thread(SyncWorker_11, started daemon 139800866690816)>)
2019-06-27 13:59:03 WARNING (SyncWorker_4) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 58:2D:34:32:E1:6F
2019-06-27 13:59:13 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.living_room_temp_battery is taking over 10 seconds
2019-06-27 13:59:34 WARNING (MainThread) [homeassistant.components.sensor] Updating mitemp_bt sensor took longer than the scheduled update interval 0:00:30
2019-06-27 13:59:48 WARNING (SyncWorker_0) [homeassistant.components.mitemp_bt.sensor] Polling error Exit read_ble, no data (<Thread(SyncWorker_0, started daemon 139801300211456)>)
2019-06-27 13:59:48 WARNING (SyncWorker_4) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 58:2D:34:32:E1:6F
2019-06-27 14:00:15 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.living_room_temp_battery is taking over 10 seconds
2019-06-27 14:00:36 WARNING (MainThread) [homeassistant.components.sensor] Updating mitemp_bt sensor took longer than the scheduled update interval 0:00:30
2019-06-27 14:00:55 WARNING (SyncWorker_7) [homeassistant.components.mitemp_bt.sensor] Polling error Exit read_ble, no data (<Thread(SyncWorker_7, started daemon 139800900261632)>)
2019-06-27 14:00:55 WARNING (SyncWorker_11) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 58:2D:34:32:E1:6F
2019-06-27 14:00:55 WARNING (SyncWorker_13) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 58:2D:34:32:E1:6F
2019-06-27 14:01:07 WARNING (SyncWorker_15) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 58:2D:34:32:E1:6F
2019-06-27 14:01:07 WARNING (SyncWorker_11) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 58:2D:34:32:E1:6F
Anyone able to sort it out? or can the devs/admin acknowledge there are issues with bluetooth since 0.94?
I’m getting an odd zhaquirks warning for: zhaquirks.smartthings, zhaquirks.centralite.3315S and zhaquirks.centralite.3320
Oddly… I have a smartthings button (that I’m using as a generic zigbee button), but no smartthing hub or integration, and no centralite products that I know of.
## Log Details (WARNING)
Thu Jun 27 2019 07:14:31 GMT-0400 (Eastern Daylight Time)
<class 'zhaquirks.smartthings.tag_v4.SmartThingsTagV4'> signature update is required. Support for `signature = {1: { replacement }}` will be removed in the future releases. Use `signature = {'endpoints': {1: { replacement }}}
Well, who knows. I re-installed 95.0 and don’t appear to be having the same troubles.
0.95.1 is not merged yet! looks like someone jumped the gun…
Beyond the odd zha warnings… no matter how many times I authenticate and restart HA, I keep getting the notification to authenticate my google calendars. And my recorder, logbook, etc. seems to be borked… my MariaDB seems borked. (i3NUC, Ubuntu 18.04, Hassio in docker. Maria installed as Hassio addon on same machine.)
I even wiped and restored yesterday’s snapshot (0.94.4) and while I don’t have to authenticate my calendars, the MariaDB and dependencies all still fail. Any ideas?
Restored 0.94.4, unistalled MariaDB (for the moment), pulled the MariaDB stuff from config.yaml, rebooted and recorder, etc all came back. Will stick with the default for now and will sort MariaDB out later.
Anyone getting invalid config for Xiaomi-Aqara since updating to 0.95 ? Can’t see any breaking changes.
My bad luck today.
I click on Configuration – Integrations – the PLUS sign — I have a lot of integrations but NOT Life360 …
Well, for those relying on Netatmo weather station, don’t upgrade to 0.95: the integration is entirely broken, see https://github.com/home-assistant/home-assistant/pull/24788