When does the fix for Synology DSM come? Since 0.117.0 and 0.117.1 a lot of people are reporting issues with entities that are unavailable for the Synology DSM integration.
Problem seems to be with people who have 2FA enabled on synology. Before 0.117 it was working perfectly. What changed?
Here is the code of the REST sensor which no longer works since version 1.117.
sensor:
- platform: rest
scan_interval: '00:30:00'
name: vacances_scolaires
json_attributes_path: "$.records[0].fields"
json_attributes:
- start_date
- end_date
- description
resource_template: |-
{% set location = 'Limoges' %}
{% set rows = '1'%}
{% set aujourdhui = now().strftime('%Y-%m-%d')%}
{% set dayOfYear = now().strftime('%j') %}
{% set year = now().strftime('%Y') | int %}
{% set lastYear = year - 1 %}
{% set nextYear = year + 1 %}
{% if dayOfYear > '244' %}
{% set schoolYear = (year | string) + "-" + (nextYear | string) %}
{%- else -%}
{% set schoolYear = (lastYear | string) + "-" + (year | string) %}
{%- endif %}
https://data.education.gouv.fr/api/records/1.0/search/?dataset=fr-en-calendrier-scolaire&facet=start_date&facet=end_date&rows={{rows}}&refine.location={{location}}&sort=-end_date&q=end_date%3E={{aujourdhui}}
#https://data.education.gouv.fr/api/records/1.0/search/?dataset=fr-en-calendrier-scolaire&facet=start_date&facet=end_date&rows={{rows}}&refine.annee_scolaire={{schoolYear}}&refine.location={{location}}&sort=-end_date&q=end_date%3E={{aujourdhui}}
#&q=start_date%3E={{aujourdhui}}&q=end_date%3E={{aujourdhui}}
value_template: |-
{% set aujourdhui = now().strftime('%Y-%m-%d')%}
{% for record in value_json.records -%}
{% if aujourdhui >= record.fields.start_date and aujourdhui <= record.fields.end_date %}
{%- if record.fields.description %}{{record.fields.description}} jusqu'au {{ as_timestamp(record.fields.end_date) | timestamp_custom('%d-%m-%Y') }} {% endif %}
{% else %}
{%- if record.fields.end_date > aujourdhui and record.fields.description %} prochaines : {{record.fields.description}} {{ as_timestamp(record.fields.start_date) | timestamp_custom('%d-%m-%Y') }}{% endif %}
{% endif %}
{%- endfor %}
The source of this code is:
There are several topics, a solution seems to be in progress but I don’t know if it was applied in version 1.117.2, I don’t dare to try …
https://github.com/home-assistant/core/labels/templates
Tried 0.117.2 last night. But still having problems with the view on my tablets. Everything keeps to be didplayed out of screen since this update. Cards seem to e bigger as before now (changed DPI to make all fit). And need to scroll verticaly and horizontally now.
So went back to 0.116.4 again.
v0.117.2 doesn’t seem to be available on RPi3:
20-11-02 13:25:31 ERROR (SyncWorker_6) [supervisor.docker.interface] Can't install homeassistant/raspberrypi3-homeassistant:0.117.2 -> 404 Client Error: Not Found ("no such image: homeassistant/raspberrypi3-homeassistant:0.117.2: No such image: homeassistant/raspberrypi3-homeassistant:0.117.2").
Can it be added? Thank you.
Was added with the rest https://hub.docker.com/layers/homeassistant/raspberrypi3-homeassistant/0.117.2/images/sha256-4753e9a8c3174a2bae423054af6d4dd4c51aee897affd95d9d3a590ab5b3d13c?context=explore
You are most likely running low on free space.
Seems to only be an issue if you use a resource_template in the rest sensor.
Yeah, saw it now.
Running Home Assistant OS on virtualbox, currently on 0.116.4. I have more than enough space on my machine, but I don’t see the upgrade for 0.117.
If I run the check config add-on I get the following error:
Blockquote ERROR: After October 2020 you may experience errors when installing or updating packages. This is because pip will change the way that it resolves dependency conflicts.
We recommend you use --use-feature=2020-resolver to test your packages with the new resolver before it becomes the default.
aiohttp 3.6.2 requires multidict<5.0,>=4.5, but you’ll have multidict 5.0.0 which is incompatible.
Not 100% sure if this is the reason I don’t see 0.117 in my supervisor.
The first error isn’t an error, it’s a warning that wants to make itself known.
That’s not the reason, the reason will present itself in the supervisor logs
I see it mentioned in the log, but I have 40 GB available:
20-11-02 13:25:31 ERROR (SyncWorker_6) [supervisor.docker.interface] Can’t install homeassistant/raspberrypi3-homeassistant:0.117.2 -> 404 Client Error: Not Found (“no such image: homeassistant/raspberrypi3-homeassistant:0.117.2: No such image: homeassistant/raspberrypi3-homeassistant:0.117.2”).
20-11-02 13:25:31 INFO (SyncWorker_6) [supervisor.docker.interface] This error is often caused by not having enough disk space available. Available space in /data is: 40.6 GiB
Thanks for your help, it is strange. I rebooted my whole system and the update is now available. First time in a month that I rebooted the whole system 
I have 1 ONVIF Camera, but I don’t use the ONVIF Integration. Only a link to motioneye on another NAS.
Please fix yeelight
Create a new topic if you want more help.
Have the same setup, the same problem and the same error message ; didn’t see the upgrade to 0.117 (never had this problem before with other releases).
Tried to workout the “–use-feature=2020-resolver… etc” and “multidict etc” errors to no succes.
The solution (in my case) was quite simple; do a compleet reboot of the (hassos) host system (not only HA) and after that messages appeared about “Supervisor version 2020.10.0”, “HassOS 4.15” and also “HA 0.117.1”. Did upgrades in that order and everything is oke now.
Not sure what the cause was but it works fine now.
Edit1: Now I don’t see the “Release 0.117.2” message in Supervisor…
Edit2: Spoke too early; now (2 days later) it’s there so probably it was a one time hickup…
Yes. Seeing that too.
Had to roleback my update because yeelight just doesn’t work at all. Either manual or autodiscovery. I think there is a way to edit the .py file but figured i would just wait till its fixed.
