Thanks but it does not seem to contain the UI editor variables.
Not yet. It’s open to edit.
1 Like
I’m not arguing. Just explaining why I was in doubt: because “temporary” in IT world has pretty well defined meaning.
Also I answered you the question you asked on why not to disable integration. There is really no reason to be so unfriendly.
Why are backgrounded browser tabs with home assistant loaded disconnecting?
They did not do this in 2021.2
1 Like
They should? It’s a setting in your user profile.
Has been there forever, maybe a bug was fixed?
1 Like
Hmm. How did that get switched on?
Thanks. 
1 Like
Loving this new UI entering automations! And Im happy to see transitions on Hue Activate Scene. but sadly transition didnt make it to the UI you have to enter yaml-mode to enter transition. Hope to see it soon in the UI
Or maybe a bug has been introduced. With that switch off it is still disconnecting.
EDIT: never mind, the internet connection dropped out.
Search: in: devs_frontend codemirror theme
No results. Same for in: devs_frontend codemirror variable
I did find this: https://codemirror.net/theme/
see https://discord.com/channels/330944238910963714/460846676358332417/817319220684914698
and https://github.com/home-assistant/frontend/blob/845411b48c98554d5ced757fc96fba42781cb95d/src/resources/codemirror.ts
and my closed issue 
https://github.com/home-assistant/frontend/issues/8552
Regarding “phoning home” to haveibeenpwnd…
The point of how simple disabling this is or isn’t, it’s the principle of allowing users to opt out from unwanted network communication.
One point of HA is to allow one to run with local information only. It is a bit disturbing to see a trend where decisions on what to communicate with externally are being made for the user with no opt-in. And multiple recurring notifications with no means to get rid of them is more than just a little annoying.
One shouldn’t have to develop an internet-isolated network or sinkhole domains to prevent stuff like this.
5 Likes
Completely agree. Socialism doesn’t belong in HA — HA devs do NOT know better what we need than we do. Local-only access and local-only control is not just “one of the reasons” for HA to exist, it IS the reason for it to exist. 100% of all features that want/need WAN access should each and individually be strictly opt-in only on HA as a core value and philosophy. This breaks it, very badly. Not the path forward, full stop.
For now, I am configuring a firewall block for this, but I am actually considering blocking all HA WAN access by default now and just manually turning on each path after careful evaluation. This is the kind of lockdown policy reserved for incompetent and near-malicious vendors, devices, software, and products … yet here we are now with HA. {shakes head}
5 Likes
Frenck knows better than me. I trust him.
What a lovely fellow you have turned out to be.
I worked with support and found my issue was not having Int/Ext connection configured @ https://my.home-assistant.io/redirect/general/ I’ve been using HA since .30 and still had the HomeAssistant: section in my yaml. I took that out configured everything in general and my syncs started working again.
Convo can bee seen on this @ https://discordapp.com/channels/330944238910963714/402899129660997642/817086848857014302
Personally I’m fine with using haveibeenpwned’s API for passwords, but just in case someone decides to go code up a enable/disable PR, it might also be good to have an option to use the downloadable ones:
As long as they have ~10GB to spare.
I personally think that this should be available as integration and not enabled by default In HA core. Or even better, to be part of the NabuCasa subscription.