Error with new group configuration interface on 0.39.3 #6396
Comments
|
Hi, any suggestion for the groups configuration not losing everything sudenly ? |
|
Problem still exists in 0.40 |
|
Same here. Finally upgraded to .40 and set up Get a similar error as OP. (See below) Went through entire groups.yaml file and made sure it was 'super compliant'; checked spacing, gave everything a name (removed any naming done in customize), used entities for everything even though these were never an issue before. Restarted and still getting same error. groups.yaml and error follows: -groups.yaml- error on save attempt: |
|
This is still an issue in 0.40.1. I have a feeling it may be due to a a fundamental lack of knowledge on how it is supposed to work with users who were already using includes prior, but there has been no explanation nor is there one in the documentation. |
|
Just here to state that I am experiencing the same problem with saving a group view. |
|
Me too - the error: in m y config: group: !include group.yamlMy groups aredefined in group.yaml: #
# Tabs
#
#test:
default_view:
name: General
view: yes
entities:
- script.test
- group.main_scenes
- group.info
- group.status
- updater.updater
- sensor.yr_symbol
- sensor.side_temp_corrected
- device_tracker.dedb5e711a24415baaae5cf8e880d852
- device_tracker.24dcbba223194e62b7965aa9012b1ad0
- device_tracker.andrews_iphone
- script.morning
- script.day
- script.evening
- script.night
outside:
name: Outside
view: yes
entities:
- group.outside_porch_info
- group.outside_side_info
- group.outside_drive_info
- group.outside_scenes
- group.outside_lights
garage:
name: Garage
view: yes
entities:
- group.garage_information
basement:
name: Basement
view: yes
entities:
- group.basement_information
- group.basement_media
downstairs:
name: Downstairs
view: yes
entities:
- group.downstairs_information
- group.downstairs_scenes
- group.downstairs_lights
- group.downstairs_media
upstairs:
name: Upstairs
view: yes
entities:
- group.upstairs_information
- group.upstairs_scenes
- group.upstairs_lights
weather:
name: Weather
view: yes
entities:
- sun.sun
- sensor.yr_symbol
- group.weather1
- group.weather2
- group.weather3
heating_and_cooling:
name: Heating and Cooling
view: yes
entities:
- group.heat_control
- group.basement_heat
- group.downstairs_heat
- group.upstairs_heat
ha_status:
name: HA Controls
view: yes
entities:
- group.home_assistant_status
- group.ha_controls
- group.ha_alarm
- group.ha_batteries
#
# Groups
#
info:
name: Information
entities:
- sensor.date__time
- sensor.side_multisensor_luminance_25_3
- sun.sun
- sensor.dark_sky_temperature
- sensor.dark_sky_apparent_temperature
- sensor.dark_sky_summary
- sensor.dark_sky_precip_probability
- sensor.dark_sky_pressure
- sensor.dark_sky_humidity
- sensor.dark_sky_dew_point
status:
name: Status
control: hidden
entities:
- input_select.house_mode
- sensor.presence_mode
- switch.garage_door
- binary_sensor.porch_multisensor_sensor_27_0
- input_boolean.heating
- input_boolean.cooling
- sensor.thermostat_set
- sensor.downstairs_thermometer
- sensor.upstairs_thermometer
- sensor.vacation_mode
- sensor.guest_mode
- sensor.upstairs_smoke
- sensor.downstairs_smoke
- sensor.basement_smoke
main_scenes:
name: Scenes
entities:
- scene.house_bright
- scene.house_off
- scene.downstairs_on
- scene.downstairs_on_transition
- scene.downstairs_off
- scene.downstairs_dim
- scene.downstairs_bright
- scene.wendys_lamp
- scene.porch_on
- scene.porch_off
- scene.outside_bright
- scene.outside_off
- scene.upstairs_on
- scene.upstairs_off
garage_information:
name: Garage Information
control: hidden
entities:
- switch.garage
- binary_sensor.garage_sensor_36_0
porch_light:
entities:
- light.porch_1
- light.porch_2
outside_lights:
name: Outside Lights
control: hidden
entities:
- light.porch_1
- light.porch_2
- light.drive
- switch.front_path_switch_42_0
- switch.outside_decorations_switch_23_0
outside_scenes:
name: Outside Scenes
entities:
- scene.porch_off
- scene.porch_on
- scene.drive_off
- scene.drive_on
- scene.outside_bright
- scene.outside_off
outside_porch_info:
name: Porch
entities:
- binary_sensor.porch_multisensor_sensor_27_0
- sensor.porch_multisensor_luminance_27_3
- sensor.porch_multisensor_temperature_27_1
- sensor.porch_multisensor_relative_humidity_27_5
outside_side_info:
name: Side of House
entities:
- binary_sensor.side_multisensor_sensor_25_0
- sensor.side_multisensor_luminance_25_3
- sensor.side_temp_corrected
- sensor.side_humidity_corrected
outside_drive_info:
name: Drive
entities:
- binary_sensor.drive_sensor_39_0
- sensor.drive_luminance_39_3
- sensor.drive_temperature_39_1
- sensor.drive_relative_humidity_39_5
downstairs_lights:
name: Downstairs Lights
control: hidden
entities:
- light.living_room_front
- light.kitchen
- light.living_room
- light.wendys_lamp
- light.andrews_lamp
- light.downstairs_hall
- light.jacks_lamp
- light.den_lamp
- switch.main_tree_switch_40_0
- switch.animal_tree_switch_41_0
decorations:
name: Decorations
entities:
- switch.main_tree_switch_40_0
- switch.animal_tree_switch_41_0
downstairs_scenes:
name: Downstairs Scenes
entities:
- scene.downstairs_off
- scene.downstairs_on
- scene.downstairs_on_transition
- scene.downstairs_dim
- scene.downstairs_bright
- scene.wendys_lamp
- scene.jacks_heat_lamp
- scene.jacks_heat_lamp_off
downstairs_information:
name: Information
entities:
- sensor.downstairs_smoke
- binary_sensor.downstairs_sensor_26_0_0
downstairs_media:
name: Downstairs Media
entities:
media_player.living_room
basement_information:
name: Basement Information
entities:
- sensor.basement_smoke
- binary_sensor.basement_sensor_35_0_0
basement_media:
name: Basement Media
entities:
media_player.roku_63261w020748
office_light:
entities:
- light.office_1
- light.office_2
upstairs_lights:
name: Upstairs Lights
control: hidden
entities:
- group.office_light
- light.office_lamp
- light.upstairs_hall
- light.andrew_bedside
- light.wendy_bedside
upstairs_scenes:
name: Upstairs Scenes
entities:
- scene.office_on
- scene.office_off
- scene.office_bright
- scene.office_dim
- scene.upstairs_off
- scene.upstairs_on
- scene.upstairs_bright
- scene.upstairs_dim
upstairs_information:
name: Information
entities:
- sensor.upstairs_smoke
- binary_sensor.upstairs_sensor_28_0
weather1:
name: Current Forcecast
entities:
- sensor.dark_sky_minutely_summary
- sensor.dark_sky_hourly_summary
- sensor.dark_sky_daily_summary
- sensor.dark_sky_icon
- sensor.dark_sky_temperature
- sensor.dark_sky_apparent_temperature
- sensor.dark_sky_humidity
weather2:
name: Outlook
entities:
- sensor.dark_sky_nearest_storm_distance
- sensor.dark_sky_nearest_storm_bearing
- sensor.dark_sky_precip_type
- sensor.dark_sky_precip_intensity
- sensor.dark_sky_precip_probability
- sensor.dark_sky_dew_point
weather3:
name: Specifics
entities:
- sensor.dark_sky_wind_speed
- sensor.dark_sky_wind_bearing
- sensor.dark_sky_cloud_cover
- sensor.dark_sky_visibility
- sensor.dark_sky_pressure
- sensor.dark_sky_ozone
heat_control:
name: Control
control: hidden
entities:
- input_boolean.heating
- input_boolean.cooling
basement_heat:
name: Basement
entities:
- climate.basement_thermostat_heating_1_24_1
- sensor.basement_thermostat_relative_humidity_24_5
downstairs_heat:
name: Downstairs
entities:
- climate.downstairs_thermostat_heating_1_51_1
- sensor.downstairs_thermostat_relative_humidity_51_5_3
upstairs_heat:
name: Upstairs
entities:
- climate.upstairs_thermostat_heating_1_14_1
- sensor.upstairs_thermostat_relative_humidity_14_5
Home Assistant Status:
- script.restart_ha
- weblink.reload
- sensor.cpu_use
- sensor.ram_free
- sensor.disk_free_home
- sensor.last_boot
ha_controls:
name: Home Assistant Controls
control: hidden
entities:
- input_select.house_mode
- input_boolean.heating
- input_boolean.vacation
- input_boolean.guest
- input_boolean.motion_notifications
- configurator.philips_hue
- script.andrew_home
- script.wendy_home
- script.andrew_away
- script.wendy_away
- input_slider.test
- input_slider.rene
ha_alarm:
name: Home Assistant Alarm
entities:
alarm_control_panel.ha_alarm
And I see this in weather:
entities:
- sun.sun
- sensor.yr_symbol
- group.weather3
- group.weather1
- group.weather2
name: Weather
view: trueAs rpitera said, it wasn;t clear to me if we could even use our existing groups, but it seems to work apart from this. Also, is Perhaps better docs could clarify this. |
|
If the format of groups has changed, can someone tell us the proper format? Seems to me this would be a breaking change. |
|
I thought maybe you were on to something with view: true as opposed to view: yes (which is how the docs currently show it) but there was no difference in the behavior or the text of the error message. In my case, the error references the default_view contents, which is (after updating the views): |
|
I love the fact that this product is evolving, but please can we have some clear documentation when there are fundamental changes to the configuration file structure. |
|
@dpritt - this has nothing to do with customize.yaml, and the documentation, but with issues with the new groups configuration through the UI. I'd personally suggest too that documentation feedback is better placed in the forum, where you'll find a number of threads on the issue you can add your voice to. |
|
DubhAd, sorry but groups can be part of the customize.yaml if you wish, so it is relevant. |
|
@dpritt - no, I get it. The documentation is far from great (though, given the rapid development, that's kind of to be expected). However, this is a bug report about the group configuration in the new UI. If you've got an issue with that, posting relevant data and log examples in this bug report will help the developers. Posting feedback, or complaining about other issues, isn't going to help you, and just risks adding confusion to the bug report. That's why I suggested the forum, where you'll be more likely to get help, and have people listen to your feedback. |
|
Further testing update - Removed: From groups.yaml as the two items (which work fine, BTW) show up as unknowns in the GUI. Doing so has moved my error message from referencing the default_view to referencing the next group down in the group list. It really seems like the accepted format must have changed but there is no information about it and no mention of it in the 'documentation' which really only serves to show pictures and descriptions of what config looks like. Nothing in the PRs for 0.41 indicate anything has been done with this either. Could really use some guidance from the core here about whether this should really work is more of a placeholder for future release. |
|
Would be great if @balloob could look into this because as of 0.41 it is still broken and I think he's the only one who can tell us why. |
|
Still an issue in 0.42.2. Wish someone would at least look into this issue. Doesn't make sense to release feature in .39.x and still not even address the fact that it never worked. |
|
Throwing out another call to @balloob to ask you to look into this. A comment, some questions, anything at all regarding this issue? |
|
I'm super busy, it's not on the top of my list. Help welcome. |
|
Let us know how we can help. What information can we gather or analyze? |
|
Thank you so much, @balloob! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
HA: 0.39.3
Python: 3.4.2
Raspberry Pi, Jessie (Debian 8.0)
With the new configuration interface, it displays my existing groups without issue. However, when attempting to change anything it spins, never completing. Checking the logs shows a typical error:
If I have only a single group in groups.yaml, then it behaves as expected and updates the group. However as with most people, I don't have a single group.
The following groups.yaml is enough to trigger this problem:
The text was updated successfully, but these errors were encountered: