I would personally ensure that the submitted data is anonymized so that you do not store any linking between the user and the data about the installation. They key about GDPR is PERSONAL data. If you do not store the data so anyone can link the user to the data then GDPR is not relevant. You then both avoid spamming us with concent emails and shit pop ups and avoid more conspiracy theories.
Its open source, feel free to audit.
1 Like
One per day is correct, but looking at the results it shows the word precipitation with no diferentation between each day. How would using the code as you entered know which one to pick?
I’m not too sure but I think you helped me realise something: The precipitation values I have are in the forecast section and none in the main section. That’s probably why it’s not displaying any value when I set the attribute. When left out, there still seems to be an issue, as it picks one of the forecasted values, specifically the next day’s. It should probably not do that.
@frenck
On another topic. Wouldn’t it be possible for you, to put a link to the minor releases at the top of the blog entry? An anchor should be not too much hassle, as the line for the minor releases already is a heading and therefor has an id. That would save a lot of time scrolling… 
Thanks for checking. 
5 Likes
Maybe a template sensor? Not sure how to do this for a “sub” category.
The supervisor might generate the information, but the storage is probably done by sentry.io within their platform, perhaps? It’s the combination of these two elements that would have GDPR (and these days also, CCPA) concerns.
I also have to worry to some degree about GDPR and data privacy concerns. I’m not complaining about this capability. I don’t have the ability to audio what and how sentry.io operates. My intent here in replying to this thread isn’t due to concern on my part; so auditing what code I can see doesn’t address the problem… that I don’t have.
But as others have pointed out, I hope that Nabu Casa is applying due care in this regard. It’s not my livelihood that’s at stake here - its the employees of Nabu Casa that I presume enjoy being paid to work Home Home Assistant. An ounce, er, gram of prevention now could save you several (metric) tons of $$$ in legal fees in the future.
If you’re not worried, that’s great! I hope the lack of concern has come from informed choices and due diligence.
2 Likes
Don’t even see it anymore because I upgraded to Ubuntu 20.4.1 and now it states unsupported.
But for the rest it runs fine
Btw the icon error message for the the default Lovelace is still there and generating 100s of messages per week
Zigbee2MQTTAssistent is causing:
Icon mdi:mixcloud was removed from MDI, please replace this icon with an other icon in your config, it will be removed in version 0.115.
Re you using that icon somehwee, if so replace it with something else
This is part of core. Its the icon in front of the default standard Lovelace tab.
See in configuration under Lovelace. You cannot edit this only the devs.
hmm, i dont see that error in my logs
Have you checked customize.yaml to confirm its not there
Nvm, it not part of core but from an addon you have loaded, if thats the case i would log issue within the github repo for that addon
what addons do you have installed?
This one is has the mixcloud still being referenced
Zigbee2Mqtt Assistant
@johntdyer - I updated to 114.2 a few minutes ago and restarted the host. HACS is still not available
I don’t know if I am missing something, but both my app and HA are up-to-date and I can’t seem to turn dark mode off. My interface is barely visible.
I can read the text, but have to guess where the buttons are.
It’s set on light in my profile.
My phone is setup in dark mode, but I didn’t mind HA being light (I could change that with a theme). If I put it on dark the buttons are a bit better visible, so there is a difference between light and dark, just not what I expected as difference.
There’s an issue open for that:
Hi! Is it me, or map in new dark mode is very, very hard to read? I’d suggest to leave it light, as in custom “Google Dark Theme”.
Thanks, I knew I missed something, reading the bugs. No worries then :).
There is a difference with dark mode, with dark mode I do see my buttons, so I’m using that for now as workaround.
I have this icon error:
Icon mdi:file-document-box-outline was renamed to mdi:text-box-outline, please change your config, it
How do I find it
Yup. Its the Zigbee2Mqtt Assistant thats the culprit and raised a bug report for it.
That its not showing in your logs may be due to fact of the logger settings.
This is mine:
logger:
default: info
That one is the logviewer addon i believe. There’s been a PR to fix it since 0.113.0b0
1 Like