#I don’t know how to bump the post, I
1 messages · Page 1 of 1 (latest)
You need to share the automation (use a code share site) along with any errors in the log file, and any relevant details in the trace
If you're having problems with your updates to your configuration:
- Check the troubleshooting steps
- Check your log file - remembering you may need to set logger to
infoordebug - Explain what the problem you're having is - sharing configuration, errors, and logs
To test an automation there's three stages you can follow. Testing the action, the condition and action, and the whole automation:
- Use Configuration -> Automations to find the automation and then select Run in the three dots menu. If this fails your problem is in the
action:section, and details should be found in your log file - Use Developer tools -> Services and call
automation.triggeron the automation withskip_condition: false. If the first passes but this fails then the problem is in yourcondition:block - Use Developer tools -> States to find the trigger entity, click the name, then change the state (at the top) to something that'll trigger the automation before pushing Set State. If this fails then the problem is with your
trigger:section, or the automation is turned off (you can check that in Automations, automations that are turned off will show Disabled)
You can also see this section in the docs about testing and automation traces.
äh sorry, do you mean this?
H`ome Assistant Core
2023-11-07 08:25:53.585 ERROR (SyncWorker_0) [homeassistant.loader] Error loading integration: evohome
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/loader.py", line 867, in _resolve_integrations_from_root
integration = Integration.resolve_from_root(hass, root_module, domain)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/loader.py", line 573, in resolve_from_root
integration = cls(
^^^^
File "/usr/src/homeassistant/homeassistant/loader.py", line 645, in init
_LOGGER.info("Loaded %s from %s", self.domain, pkg_path)
^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/loader.py", line 660, in domain
return self.manifest["domain"]
KeyError: 'domain'
2023-11-07 08:25:53.609 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration solarman which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2023-11-07 08:56:03.349 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [139831651127744] Error handling message: Integration '' not found (unknown_error) nxxx from 172.17.0.1 (Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/119.0)`
The service call remote send command is working, the home_hold command doesn’t bring the upper menu on Apple TV, it only send a command like home, lets say I’m position on a lower icon on Apple TV and when I send home_hold command the cursor position is on the first icon. The home_hold command is exactly like home command.
I don’t have any errors on home assistant logs
Have you checked for known issues?
All the send commands are working correctly except home_hold. It was working fine before update, that’s why I was thinking it is something with the update and wanted someone to test it.
There's not a lot of users of that platform, but if it's a known bug then hopefully somebody else has opened an issue
I tried resetting the Apple TV 🙈 but didn’t fix it at all
Its a bug with home_hold command
Want to see what issues are open (or were open and are now closed)?
- The core (backend) - for HA itself, and integrations
- The frontend (UI) - for cards and display issues
- The Supervisor
- HAOS
- The documentation
Don't forget to check for any alerts
If you think an upgrade broke something then:
- Downgrade to the previous version to check if it works correctly there
- If it does then change the
loggersettings for that integration todebug - Upgrade to the new version again
- Look in the logs for errors
- Open an issue, following the template provided and including the log information