You can opt out by checking the boxes to not find new things. I forget the name in the UI. You will still find things on first loadup, but it will stop after that.
Yeah, that
Because, regardless how innovative it is, not all HA users want to use BT devices and/or be bothered by neighbors’ devices.
Shelly integration was also innovative and annoys me till today (in fact it forces me to have a mockup of non-functional shelly integration in custom integrations).
Nice to see iBeacon tracker may be globally disabled. It’s really step toward forward-thinking.
Not sure it disables recognition of all BT devices hovering around. Seems it’s only ibeacons related. But I’m not into BT tech thus I might be wrong.
sure, I see that. Though, the BT wont show you your neighbors devices, unless within 10m or so?
ble tracker is an entirely different beast (showing huge amounts of those) but you have to explicitly set it up in yaml.
iBeacon integration can be easily ignored, and I’m sincerely considering that myself. Only my curiosity is withholding me to do so just now.
leaves you with the BT integration itself. You can ‘not install’ that, with a small effort. You’d have to stop using default: as Petro already pointed out (is what I do indeed, for the sole reason I don’t want a Map in my left side menu…)
So, all in all, users have loads of options, (though some more iBeacon control wouldn’t hurt… 
)
1 Like
need another WTH for the Map thingy. shouldn’t be big…
Thanks for thinking with me. I couldn’t access the internet for a few days because I switched providers. Never do it before the weekend when the wrong cable comes with the modem.
Anyway. I still have the same error. Even after I deleted all the files of AppDaemon from HA. I deleted the addon AppDaemon and added it again. The files were restored by the addon so that only the app ‘Hello world’ was available and nothing else. Started up and yet again:
“HASS: Error getting Home Assistant state for None” etc…
I am running Debian 11 (Bullseye) on a supported version of HA supervised.
I just don’t know about it any more. And I don’t have enough knowledge to look under the hood.
Bye the way: Don’t mind the fake dash_url. I changed all url’s to something what came up spontaneously. 
Anybody know?
Please don’t bump your issue after less than 24 hours.
What is going on with Statistics card?
With “period: 5minutes” earlier it was displayed for no longer than 10 days, now it is for 7 days only.
If it is related - my Recorder’s settings is “purge_keep_days: 10”.
I really believed that ANY statistics is kept forever.
Described this issue here & here.
Just resolved up upgrade from 2022.10.2 to 2022.10.3 issue - seems that if you have Portainer-ce installed as a separate docker image on your host that it will no longer upgrade.
Not sure why this is the case - my Supervised installation has been like this since I first built it over 2 years ago yet it breaks now?
Interestingly one of my test instances running on Ubuntu server still has portainer running and is fine…
If you don’t follow the instructions, it will break.
there’s nothing in the breaking changes that said this would happen - it won’t even upgrade if the container image is still on the system…
There’s a thread somewhere about disabling that check on your system.
1 Like
You didn’t follow the instructions when you installed portainer, because the instructions say it is not allowed to install other software
The link to ADR14 is the first link in the supervised install instructions. Clearly many people have not read and/or understood what it says.
You don’t get a ‘breaking change’ notification when you broke it yourself.
1 Like
the whole idea of dockerising something is that you can run other containers on the same host. I run a managed environment, everything is updated which is my choice. If something stops working having worked for 2 years, then it’s a breaking change, irrespective of the instructions.
The fact that I can’t have the docker image for portainer-ce sitting on the filesystem is a concern - what will happen should that be extended to shell scripts, etc that guys call from within Home Assistant ?
I use a template sensor with the ibeacon from my andriod to reduce the logging (by removing various attributes) and also to only switch to ‘off’ if it’s in the off-state for 90 seconds
My raw data looks like the teeth of a comb
My “smoothed” data looks like this
1 Like
I’m curious to know if you experienced any speed difference with the new single dashboard and subviews compared with multiple dashboards
Yes, It’s a shame that “Ignore” does not stay sticky in the .storage folder files