core: Service group.set not found
Home Assistant release with the issue: 0.84.1
Last working Home Assistant release (if known): 0.83.1
Operating environment (Hass.io/Docker/Windows/etc.): Hassbian, raspberry pi 3b+
Component/platform: NA
Description of problem: After upgrade from 0.83.1 I am constantly getting error and was not able to identify where the problem is…
2018-12-14 20:33:06 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/lib/python3.5/asyncio/tasks.py", line 239, in _step
result = coro.send(None)
File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/core.py", line 1098, in async_call
raise ServiceNotFound(domain, service) from None
homeassistant.exceptions.ServiceNotFound: (ServiceNotFound(...), 'Service group.set not found')
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
Traceback (if applicable):
Additional information: Attaching part of groups.yaml
home_view:
view: yes
# icon: mdi:home
name: Rooms
entities:
- device_tracker.katka__iphone
- device_tracker.iphone_bt_rasto
- group.garage_door_group
- group.outside_group
- group.kitchen
- group.living_roon_group
- group.kids_back_room_group
- group.bathroom_group
- group.hall_group
device_tab:
view: yes
name: Devices
entities:
- group.smoke_sensor_group
- group.water_sensor_group
- group.battery_group
- group.tamper_group
- group.windows_door_sensor
- group.temp_hum_group
- group.others_group
- group.media_group
monitoring_tab:
view: yes
name: Monitoring
entities:
- group.nas
- group.rpi
- group.core
- group.device_status_group
- group.asus_group
- group.gtw1_living_group
- group.garage_node_group
- group.ups_group
- group.inet_speed_group
settings_tab:
view: yes
name: Settings
entities:
- group.notifications
- group.alert
- group.state_reset
###################################
# #
# Groups #
# #
###################################
state_reset:
name: State Reset
control: hidden
entities:
# - script.turn_off_living_room_low_bat_state
# - script.turn_off_kids_room_low_bat_state
# - script.turn_off_living_room_tamper_state
# - script.turn_off_kids_room_tamper_state
- script.state_reset_tamper_off
- script.state_reset_smoke_off
- script.state_reset_water
# - script.test_reset_cmd_on
- script.state_reset_battery
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 2
- Comments: 48 (15 by maintainers)
Error still exist in 0.89.0
Have been seeing this for the past few releases…
Hi I have been able to track this down. For me it was that one automation still was using states.[sensor_name] instead of states(‘sensor_name’).
I thought that I had fixed this but maybe I accidently have introduced again after it was fixed. More about this can be read in the documentation: https://www.home-assistant.io/docs/configuration/templating/
It clearly warns that this error will occur during startup if states, is_state, state_attr… methods are not used.
Please, search your whole code base and confirm that sensor.[sensor_name.state] is not beeing used.
I just debugged this for a few hours. Turns out that this is caused by having more than 1 group. At least from 0.87.x. I never had this issue prior. I disabled groups.yaml and the error went away. I enabled and the errors came back. I then reduced groups.yaml down to 1 single group. No error. I added a 2nd group and the errors came back. Not as many as when I had a full groups.yaml but 2 errors. I then removed the 1st group and left the 2nd group as to have just 1 group in the yaml again. But a different one. Restarted and no error. Added a 2nd group back in and error again. So it seems no matter what, having more than 2 groups will produce this error. Again, I only see this in 0.87.x.
This below produces the error
This below does not produce an error or vice versa. (Just as long as there are 2 groups)
So after another couple of hours I located the problem to be Trådfri E27’s bulbs used in group. When I declared these bulbs in a group the error came back.
I could however workaround it but using a light group as described here: https://www.home-assistant.io/integrations/light.group/
Also another tip for those running on docker: to do a docker restart instead of a restart from the HASS GUI is a difference of 7X in speed. So for me this would have been solved much faster if I would have used the docker restart command instead of waiting for the GUI restart to be completed.
Try this approach in combination with the states() method describe above and see if it solves the issue!
Still exists on 0.99.3
This seems to have been resolved in 0.91.x.
Just trying to keep this issue alive in hopes that it will finally be addressed. Things have a tendency to be closed if there’s no traffic on it…
I hope they aren’t going to ignore groups in favor of the shiny new areas and persons features. ; )
All have their uses and many people still use groups. Seems like this thread laid out a good set of clues for the devs to follow. We know for sure that it occurs whenever more than one group is used.
Kind of sad to see this still exists SIX versions later. Just to confirm, still present in 0.90.1. Still happens if you have more than one entry in groups.yaml.
Confirmed here on 0.88.1 too.
Nice find @edif30! I too still have some use for groups and it seems like there would be more people out there who still have groups active from the old pre Lovelace days so you’d think more people would be experiencing this error and it would get a little more traction. Hope a core dev sees the recent traffic on this issue and looks into it. Thanks for your efforts!
Still seeing this error as of 0.86.4. so keeping this issue alive and open. Saw a reference to it in the forums as well so it’s not just us…
https://community.home-assistant.io/t/help-with-log-error-group-set-not-found/93235