You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This function stopped working with my printer, giving me this error: Failed setup, will retry: Invalid response from API: Timeout occurred while connecting to the IPP server. I tried remapping the IP and port but had no success. Any ideas?
What version of Home Assistant Core has the issue?
System Information version | core-2024.11.3 -- | -- installation_type | Home Assistant OS dev | false hassio | true docker | true user | root virtualenv | false python_version | 3.12.4 os_name | Linux os_version | 6.6.54-haos arch | x86_64 timezone | America/New_York config_dir | /config Home Assistant Community Store GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok HACS Data | ok GitHub API Calls Remaining | 5000 Installed Version | 2.0.1 Stage | running Available Repositories | 1532 Downloaded Repositories | 64 Home Assistant Cloud logged_in | true -- | -- subscription_expiration | December 27, 2024 at 7:00 PM relayer_connected | true relayer_region | us-east-1 remote_enabled | true remote_connected | true alexa_enabled | true google_enabled | true cloud_ice_servers_enabled | true remote_server | us-east-1-7.ui.nabu.casa certificate_status | ready instance_id | 91cd7617b92048efaa1061c369f9fc01 can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | ok Home Assistant Supervisor host_os | Home Assistant OS 13.2 -- | -- update_channel | stable supervisor_version | supervisor-2024.11.4 agent_version | 1.6.0 docker_version | 27.2.0 disk_total | 48.5 GB disk_used | 27.9 GB healthy | true supported | true host_connectivity | true supervisor_connectivity | true ntp_synchronized | true virtualization | kvm board | ova supervisor_api | ok version_api | ok installed_addons | Studio Code Server (5.17.3), Advanced SSH & Web Terminal (19.0.0), Mosquitto broker (6.4.1), Plex Media Server (3.6.0), Zigbee2MQTT (1.41.0-1), Govee to MQTT Bridge (2024.07.13-82ddc6e9), Matter Server (6.6.1), AppDaemon (0.16.7), Music Assistant Server (beta) (2.4.0b7), ESPHome Device Compiler (2024.11.2) Dashboards dashboards | 10 -- | -- resources | 46 views | 33 mode | storage Recorder oldest_recorder_run | November 28, 2024 at 7:10 AM -- | -- current_recorder_run | November 30, 2024 at 11:26 PM estimated_db_size | 661.77 MiB database_engine | sqlite database_version | 3.45.3
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
No response
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered:
We use GitHub for tracking issues with Home Assistant Core itself, not for providing support - so if you could provide more details like logs or any other helpful diagnostics data or error details or steps how to reproduce or your configuration, than we can handle it as an issue report, else it is a support request and you should try our Community Forum or join our Discord chat server.
The problem
This function stopped working with my printer, giving me this error: Failed setup, will retry: Invalid response from API: Timeout occurred while connecting to the IPP server. I tried remapping the IP and port but had no success. Any ideas?
What version of Home Assistant Core has the issue?
System Information version | core-2024.11.3 -- | -- installation_type | Home Assistant OS dev | false hassio | true docker | true user | root virtualenv | false python_version | 3.12.4 os_name | Linux os_version | 6.6.54-haos arch | x86_64 timezone | America/New_York config_dir | /config
Home Assistant Community Store
GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok HACS Data | ok GitHub API Calls Remaining | 5000 Installed Version | 2.0.1 Stage | running Available Repositories | 1532 Downloaded Repositories | 64Home Assistant Cloud
logged_in | true -- | -- subscription_expiration | December 27, 2024 at 7:00 PM relayer_connected | true relayer_region | us-east-1 remote_enabled | true remote_connected | true alexa_enabled | true google_enabled | true cloud_ice_servers_enabled | true remote_server | us-east-1-7.ui.nabu.casa certificate_status | ready instance_id | 91cd7617b92048efaa1061c369f9fc01 can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | okHome Assistant Supervisor
host_os | Home Assistant OS 13.2 -- | -- update_channel | stable supervisor_version | supervisor-2024.11.4 agent_version | 1.6.0 docker_version | 27.2.0 disk_total | 48.5 GB disk_used | 27.9 GB healthy | true supported | true host_connectivity | true supervisor_connectivity | true ntp_synchronized | true virtualization | kvm board | ova supervisor_api | ok version_api | ok installed_addons | Studio Code Server (5.17.3), Advanced SSH & Web Terminal (19.0.0), Mosquitto broker (6.4.1), Plex Media Server (3.6.0), Zigbee2MQTT (1.41.0-1), Govee to MQTT Bridge (2024.07.13-82ddc6e9), Matter Server (6.6.1), AppDaemon (0.16.7), Music Assistant Server (beta) (2.4.0b7), ESPHome Device Compiler (2024.11.2)Dashboards
dashboards | 10 -- | -- resources | 46 views | 33 mode | storageRecorder
oldest_recorder_run | November 28, 2024 at 7:10 AM -- | -- current_recorder_run | November 30, 2024 at 11:26 PM estimated_db_size | 661.77 MiB database_engine | sqlite database_version | 3.45.3What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
No response
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: