All was working well until last evening when I was unable to turn off a lamp using the Home Assistant app. When I tap on one of the lights to check the detail it says ‘master BR Lamp Unavailable’. When I tried to initiate it, I get the error message ‘Failed to call service light/turn on: service not found.’ When I checked the automation area the service selection does not contain ANY light/turn on or off functions.
How do I restore the 'light.turn_on’ and ‘light.turn.off’ services? Thanks
Yes and had been working right for almost a month. I changed to HA when Insteon failed and now regretting it for all the $$$ I’ve invested. Would like to get this back up and running right.
alias: Family Rm On (Sunset)
description: ‘’
trigger:
platform: sun
event: sunset
offset: ‘-00:30’
condition: []
action:
service: light.turn_on
data: {}
target:
entity_id:
- light.lamplinc_dimmer_27_20_8d
mode: single
My Insteon Hub is still working (now that Insteon came back online ) and I don’t know if that’s what’s causing the issues. On the device page, Insteon, I get an error for ‘retrying setup’ and when I click on ‘check the logs’ I get:
Could not connect to Insteon modem
8:50:54 AM – (ERROR) Insteon - message first occurred at July 24, 2022 at 9:35:32 AM and shows up 2037 times
An client error occurred: Cannot connect to host 192.168.68.121:25105 ssl:default [Connect call failed (‘192.168.68.121’, 25105)]
8:50:54 AM – (ERROR) /usr/local/lib/python3.10/site-packages/pyinsteon/protocol/http_reader_writer.py - message first occurred at July 24, 2022 at 9:35:32 AM and shows up 2037 times
Config entry ‘’ for insteon integration not ready yet; Retrying in background
July 24, 2022 at 9:35:32 AM – (WARNING) config_entries.py
When I go to the Settings > Automation, the YAML still runs BUT when I go to the Overview Dashboard nothing works. If a light has been turned on the dashboard will be grey out.
I also see this on one of my blueprints … on one of my test systems.
I call this with an entity_id: []
The cause was because I had NO light entities created in that instance … so the service was not there.
And I fixed the error by adding the following to configuration.yaml