Prepping for 0.107.0

Configuration
1

Hi there, i’ve been updating my configs to prep for 0.107.0 and in general cleaning up old configs that i no longer use and no longer supported (old frontend, groups etc)

i have 2 warnings that i can’t track down

"The ‘control’ option (with value ‘hidden’) is deprecated, please remove it from your configuration. This option will become invalid in version 0.107.0

The ‘view’ option (with value ‘True’) is deprecated, please remove it from your configuration. This option will become invalid in version 0.107.0"

I cannot track down where these might be. I’m probably being OCD, but i hate when i have warnings or errors.

i read in one of the recent release notes that this would be in the groups config, but i’ve thoroughly gone through it and there is no control or view option there

anyone have ideas where these might pop up?

it would be nice if it had the related entity these warnings came from

2

Shift+ctrl+f “control:”

Shift+ctrl+f “view:”

3

Check your groups

1 Like
4

looks like stuff from groups.yaml so remove the groups that were used for UI purposes only.

5

?? Was soll mir das sagen?

6

in my groups file i only have

group_name:
  name:
  entities: 
    - sensor.1
    - sensor.2 
    - etc

and i still get the two warnings

7

Das du nach “control” und “view” suchen sollst. Warum antwortest du in Deutsch?

8

Search everywhere doesn"t need to be in groups.yaml.

9

Sorry, war ein versehen, danke.
But by the way, I do not have such entries neither in groups nor in automation or configuration.yaml.
All what I’ve found is the old default_view in the groups yaml.
I already deleted these entries and will see if the warning during start up still appears.
cheers

10

that’s what i was hoping the warnings would point to where the issue was as my install is massive.

however, i did just stumble upon it.

the issue was in the only package i could think possibly had a group. it was the battery-alert package i use for batteries notifications.

11

Doesn’t matter how massive your code is. With Visual Studio code for example you can search your entire config in a few seconds.

2 Likes
12

understood. i’ll look into using something like that for the future. i’ve been just using simple editors over the past few years and haven’t used a full blown IDE with advanced search features yet

ty :+1:

13

Do it! It’s easy and there’s also an extension for visual studio code to connect to home assistant. This way it will auto-populate entities you have in your system and some other nice features.
If you use Home Assistant (formerly Hass.io) there’s also an add-on to have Visual Studio Code in the browser.

1 Like
14

Not if you’re on a pi (won’t run on arm) but you can install it on a third party workstation

15

Visual Studio Code does now work on RPi.

1 Like
16

Only on 64bit OS

17

I’m on Ubuntu with docker(recently migrated to hassio for easier add-on usage).

I try to do my research before asking but this was bugging the hell out of me. :slight_smile:

18

@sparkydave, @a_lunatic, Well … That’s half a step forward.
I run HA on a pi 3 and a pi 4.

The pi 3 runs hassos 32bit (recommended) - I suppose that could be upgraded to hassos 64bit ? Then restore a snapshot.

The pi 4 has an ssd, so runs buster from the sd to load the System from ssd. Buster is (I believe) only currently available in 32 bit form.

Bugger !!! :sob:

Actually, it’s pretty convenient running vsc from a workstation as its one instance for both pi’s (test and production) and Im not tempted to run it over a phone or tablet. Cutting and pasting is a nightmare.

19

I have a similar problem, but with a warning about hide_if_away.

I use VSC and have done a search but no results found.

Any ideas where it might be hiding ?

Thanks

20

Same here!

Cannot find hide_if_away anywhere.