Thanks for replying! Great theme btw and I appreciate the hard work.
Hm… for me partially… Physical NAS works fine, but DSM run in VM does not load any sensors, all unavailable.
Somethink broken with history graph? Mine shows unnecessary vertical scrollbars when mouse hover on and it does not dissapear:
Looks like card is expanding to make space for popup, that instead of staing on top is forced to stay within the card that does not resize (sorry not programmer, cannot find better explanation).
If it’s a frontend issue, then raise an issue over at
Dashbords with only single view miss view name or icon:
Did you set a name in the edit UI header?
Yes, here is how it looks in editor:
No, this part:
Hit the edit button.
Hm… OK, got it, but then it is possible to have only name, not icon… for other dashboard, where I have several view in this place icon is displayed if defined (and even if dasboard name is not defined in Edit UI):
Evidently minor issue, but sort of unexpected behaviour…
The same thing:
resource_template: https://10.11.1.99/api/menutree/read_datapoint.json?SessionId={{ states.sensor.sid_token.state }}&Id=1202
After I remove:
{{ states.sensor.sid_token.state }} Lovelace load
Is there any fix?
0.117.0 broke synology integration for me too. I’ve tried deleting and reinstalling the integration…but not luck. Hopefully this gets fixed fast.
My synology is working fine…
Do you use 2fa?
In HA yes but not synology
There are some posts that folk that use 2fa with synology are the ones having the problem (myself included).
I didn’t even know 2FA was a thing with synology
only usefull if you have exposes synology to internet 
i have turned off 2FA too on my synology, disabled port forwarding, since i dont need it anymore
I think 2FA should be used everywhere you can. Additionally, I have several docker instances running on my Synology so closing down ports and eliminating this extra security protection isn’t a route I want to go. I’m confident this is a new bug introduced with 0.117 as it was working perfectly fine w/ 2FA in previous versions.
yeah, probably something changed, why not load it as a custom? grab it from 116.4 release?
For a temp workaround
That sounds awesome, but have no idea how to do that. LOL