Hi all,
Version 0.6.1 is now available:
For the Volume settings, please read uc-intg-onkyo-avr/docs/volume.md at main · EddyMcNut/uc-intg-onkyo-avr · GitHub
Screenshots using volume button and slider:
Cheers,
Ed
Well, I’m sure this is something on my side but this update broke my integration.
Watched a movie last night with the previous version. No issues. Worked great. Just now I updated to this new version and:
I would revert back to .60 but I’m worried I’m going to have to re-set up all my activities again!
Here’s what the logs show:
2025-10-18 18:03:43.980076 +00:00 core ERROR [AppleTV] error executing activity command uc_onkyo-avr_driver_custom.main.RZ1100 192.168.1.84:media_player.on (ignore error: false): No information found
2025-10-18 18:03:43.978730 +00:00 ui INFO qml: Activity state changed to: Running
2025-10-18 18:03:43.971362 +00:00 core NOTICE [AppleTV] activity command: uc_onkyo-avr_driver_custom.main.RZ1100 192.168.1.84:media_player.on
One more data point. If I go into the entity, under “state” it says “unknown” and if I hit the toggle button it says “Resource Not Found.”
I’m sorry to read that. I reinstalled multiple times without issues and for sure it is not needed to replace the entity as long as the name and IP stayed the same, as documented here uc-intg-onkyo-avr/docs/new-version.md at main · EddyMcNut/uc-intg-onkyo-avr · GitHub
Did you make a backup of the remote that you could restore?
Which version were you running before installing 0.6.1?
ah 0.6.0 you mentioned it already
Restore a backup and install 0.6.0 again to first get back to a working state where you can double check the entity name
Was you AVR auto-discovered?
You could also try again a reboot of the remote, give a a couple of seconds and try an activity but I think/assume you already tried that.
OK, before I saw your response I decided to simply remove the integration and start over. Good news is, no clue why, it worked! Bad news is I once again had to re-set up all my activities. Weird. Attached is a screenshot you can see my existing entities on the right with the “Non-existent” error. On the left are my available entities and there is the new one, named the exact same thing. When I bring it over the old one disappears but it nukes all the activity line items and button mappings. When I did the same process with my projector, no issues. Thanks again for your work on this! It was SO SMOOTH last night watching a movie.
The name does not mean much. Each entity gets an UID from the integration and if this has changed you have two identical names with different UIDs.
Well I don’t understand what went wrong but Im glad that it is working again for you after installing it for a second time!
So maybe during install for some reason an issue occured with UUIDs?
I installed multiple times, with and without reboots, restoring backup and updating again, and no issues at all.
I blame a guy called Murphy.
Old message:
Damn, the same happened to me. Non-existent entity after the update.
Unfortunately, the backup function of the remote doesn’t backup custom entities, so restoring the backup I did before the update didn’t help. Will set up the activities again.
Update:
After I reconfigured the entity in the integration settings, everything worked again. I wasn’t aware that this was required, but maybe this also resolves the matter for others.
No need to reconfigure the activities, just add the entity again in the integration settings.
That is still normal. The good thing is after you run setup again your activities will be unharmed.
Hi, aha so it is about needing to run setup again after installing new version. I’m so sorry, I did not get it from the first posts.
Will add something about that to the documentation this weekend. The doc does explain how to upload a new version but it does not explicitly mention to run setup again.
Thanks for mentioning it @j_o_e !
So I’ve run into an interesting new issue. Everything worked fine on Thursday. Left for the weekend. Came home tonight (Sunday) and just tried to turn everything on. The Onkyo portion of my activity failed (projector turns on fine). Did the following:
After all this I went into the web configurator and the entity says “State: unknown” and I can’t toggle. I went back into the Integration and did “Start Setup” again. It finished setup just fine. Went back into the entity…still unknown and unreachable. Opened the Onkyo app on my phone and I can easily toggle the AVR on and off. Can’t get the UCR3 to recognize it! Hmm…any suggestions? I guess the last option is to delete the integration and re-install but hoping to avoid that! P.S…yes it’s on a static IP and the same network node as the remote and docks.
Additionally, after I re-ran the integration set-up I’m now seeing the entity to the right with a red line through it. Odd. Not sure what that is or how to fix it!
Hi, please collect the logs as explained here collect logs and post them here or in Discord?
I think it’s related to the previous problem you had after installing new version but not sure, I hope the logs will tell something.
In the last screenshot, if you select the ‘+’ at the right for configured entities, does it show a second instance of your AVR maybe?
@Eddy - Thanks for the help. What’s so odd is that it worked flawlessly since my last install and I did nothing to change any configurations. And now this just pops up! I just launched my AppleTV activity and it once again failed at the Onkyo step. Step one is my Sony Projector and that turns on fine via IP before the remote throws the error. Below is the log. Note that to save space I skipped the original activity call as well as all the projector power on lines. The bottom line is the first time the Onkyo is called:
2025-10-28 02:04:14.123525 +00:00 core NOTICE Removed standby inhibitor: activity ‘AppleTV’ (on) (max 65s)
2025-10-28 02:04:14.122916 +00:00 core ERROR [AppleTV] error executing activity command uc_onkyo-avr_driver_custom.main.TX-RZ1100 192.168.1.84:media_player.on (ignore error: false): TimedOut
2025-10-28 02:04:14.119535 +00:00 core WARN [uc_onkyo-avr_driver_custom.main] Timeout while waiting for request id: 17
2025-10-28 02:04:09.124123 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO at process.processTimers (node:internal/timers:529:7)
2025-10-28 02:04:09.124123 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO at listOnTimeout (node:internal/timers:594:17)
2025-10-28 02:04:09.124123 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO at Timeout._onTimeout (file:///app/eiscp.js:455:24)
2025-10-28 02:04:09.124123 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration (sender): [TX-RZ1100 192.168.1.84] Could not send command, AVR not connected: Error: Timeout waiting for AVR connection
2025-10-28 02:04:04.127620 +00:00 ui INFO qml: Current step changed: undefined
2025-10-28 02:04:04.127049 +00:00 ui INFO qml: Activity state changed to: Running
2025-10-28 02:04:04.116333 +00:00 core NOTICE [AppleTV] activity command: uc_onkyo-avr_driver_custom.main.TX-RZ1100 192.168.1.84:media_player.on
It basically is not finding the AVR which aligns with my prior comment that I can’t even “Toggle” the power state in the entity screen and it says State is “unknown.” When it was working a few days ago the State was correct and the toggle button worked. Also reiterating that the AVR is working fine and I can toggle the power state via the Onkyo app.
Lastly, when I hit the + it does not show a second instance of the AVR. The list is blank. Screenshot below. Thanks for any help!
@PNWUC Seems like the AVR entity is lost or not registered (anymore). Very weird that it now suddenly happened without changing anything, must be related to the issue you had a while ago during install of new version.
Im using it every day and have not stumbled upon this behavior.
I think the only thing to do is:
To be honest, I dont understand what happened and why but the above steps is what I should do.
And if step 14 already shows the problem again, then I think I would create all activities again instead of replacing one entity in an existing activity.
Its frustrating to have to do that, but I don’t see an other way to solve the issue.
Kind regards,
Ed
OK. Here’s what happened. Up through 14, everything worked great. When I went into Entities, the Status of the Onkyo was “Standby".” Great! Then after shutting down and powering back up the remote, the Standby status in the Entity was now “unknown” and all the activities failed. I deleted the Entity and re-ran the integration set-up. Still unknown this time.
I re-deleted the entity and re-deleted the integration. Installed the integration again and ran the setup again. Entity was re-added and now says “Standby” as the status. I paused there and tried to run the activities. They worked great! All of them.
I rebooted the remote and they all fail again. Entity once again reads “unknown.” So, for some reason, upon first install everything works great. Upon rebooting the remote, the Onkyo integration fails. Seems to be the only way to get it back is to uninstall/reinstall the integration!
I replicated this exercise five times and the same each time. Install the integration, works great, reboot remote, entity state unknown and activities fail, uninstall/reinstall integration, works great again. Rinse and repeat. When it fails, the logs look like this:
2025-10-28 16:57:50.082289 +00:00 core ERROR [Test Onkyo] error executing activity command uc_onkyo-avr_driver_custom.main.TX-RZ1100 192.168.1.84:media_player.on (ignore error: false): No information found
2025-10-28 16:57:50.075701 +00:00 core NOTICE [Test Onkyo] activity command: uc_onkyo-avr_driver_custom.main.TX-RZ1100 192.168.1.84:media_player.on
2025-10-28 16:57:50.075409 +00:00 core NOTICE Added standby inhibitor: activity ‘Test Onkyo’ (on) (max 65s)
2025-10-28 16:57:50.075002 +00:00 core NOTICE Started activity ‘Test Onkyo’ (uc.main.770bdf25-57b0-4711-a02f-7eaa6a7572f4) with timeout of 60s
2025-10-28 16:57:50.074605 +00:00 core NOTICE Starting activity ‘Test Onkyo’ (uc.main.770bdf25-57b0-4711-a02f-7eaa6a7572f4) in activity group: ‘Default’
And then after reinstalling the integration, here is a sucessful on and off activity:
2025-10-28 17:04:59.406878 +00:00 core NOTICE Removed standby inhibitor: activity ‘Test Onkyo’ (off) (max 65s)
2025-10-28 17:04:59.406004 +00:00 core NOTICE [Test Onkyo] activity finished
2025-10-28 17:04:59.393911 +00:00 core NOTICE [Test Onkyo] activity command: uc_onkyo-avr_driver_custom.main.TX-RZ1100 192.168.1.84:media_player.off
2025-10-28 17:04:59.393217 +00:00 core NOTICE Added standby inhibitor: activity ‘Test Onkyo’ (off) (max 65s)
2025-10-28 17:04:59.389547 +00:00 core NOTICE Started activity ‘Test Onkyo’ (uc.main.770bdf25-57b0-4711-a02f-7eaa6a7572f4) with timeout of 60s
2025-10-28 17:04:54.849292 +00:00 core NOTICE Removed standby inhibitor: activity ‘Test Onkyo’ (on) (max 65s)
2025-10-28 17:04:54.848756 +00:00 core NOTICE [Test Onkyo] activity finished
2025-10-28 17:04:54.832601 +00:00 core NOTICE [Test Onkyo] activity command: uc_onkyo-avr_driver_custom.main.TX-RZ1100 192.168.1.84:media_player.on
2025-10-28 17:04:54.832394 +00:00 core NOTICE Added standby inhibitor: activity ‘Test Onkyo’ (on) (max 65s)
2025-10-28 17:04:54.832063 +00:00 core NOTICE Started activity ‘Test Onkyo’ (uc.main.770bdf25-57b0-4711-a02f-7eaa6a7572f4) with timeout of 60s
2025-10-28 17:04:54.830831 +00:00 core NOTICE Starting activity ‘Test Onkyo’ (uc.main.770bdf25-57b0-4711-a02f-7eaa6a7572f4) in activity group:
So the big question…why does rebooting the remote cause the integration to go into permanent state of breaking the integration?
A bit more context. I rebooted the remote and had the Test Onkyo activity fail. I dumped the logs selecting only “Core” and Onkyo integration. Here is the log starting from when the Onkyo configures itself…then towards the top you’ll see the activity fail.
2025-10-28 17:12:39.869080 +00:00 core NOTICE No dock updates available
2025-10-28 17:12:39.255333 +00:00 core NOTICE Removed standby inhibitor: activity ‘Test Onkyo’ (on) (max 65s)
2025-10-28 17:12:39.254935 +00:00 core ERROR [Test Onkyo] error executing activity command uc_onkyo-avr_driver_custom.main.TX-RZ1100 192.168.1.84:media_player.on (ignore error: false): No information found
2025-10-28 17:12:39.249604 +00:00 core NOTICE [Test Onkyo] activity command: uc_onkyo-avr_driver_custom.main.TX-RZ1100 192.168.1.84:media_player.on
2025-10-28 17:12:39.249464 +00:00 core NOTICE Added standby inhibitor: activity ‘Test Onkyo’ (on) (max 65s)
2025-10-28 17:12:39.249266 +00:00 core NOTICE Started activity ‘Test Onkyo’ (uc.main.770bdf25-57b0-4711-a02f-7eaa6a7572f4) with timeout of 60s
2025-10-28 17:12:39.248910 +00:00 core NOTICE Starting activity ‘Test Onkyo’ (uc.main.770bdf25-57b0-4711-a02f-7eaa6a7572f4) in activity group: ‘Default’ (default)
2025-10-28 17:12:39.244247 +00:00 core NOTICE Created Dock IR emitter: dock_id=UCD3-0C8AB0, name=‘Charger’, model=UCD3, active=true, port_mask=0
2025-10-28 17:12:39.243522 +00:00 core NOTICE Contacting OTA server for dock update check. Channel=testing, model=UCD3, version=0.8.0
2025-10-28 17:12:39.186740 +00:00 core NOTICE Check OTA server for UCD3 firmware update: UCD3-0C8AB0
2025-10-28 17:12:39.144563 +00:00 core NOTICE Setting rgb button backlight to: (191, 191, 191)
2025-10-28 17:12:39.143324 +00:00 core NOTICE Enter normal mode: standby in 1800s
2025-10-28 17:12:38.782934 +00:00 core NOTICE No dock updates available
2025-10-28 17:12:38.282189 +00:00 core NOTICE Created Dock IR emitter: dock_id=UCD3-0C8AB0, name=‘Charger’, model=UCD3, active=true, port_mask=0
2025-10-28 17:12:38.036417 +00:00 core NOTICE Added standby inhibitor: Web configurator
2025-10-28 17:12:38.035772 +00:00 core NOTICE Contacting OTA server for dock update check. Channel=testing, model=UCD3, version=0.8.0
2025-10-28 17:12:37.951810 +00:00 core NOTICE Check OTA server for UCD3 firmware update: UCD3-0CBB00
2025-10-28 17:12:37.951202 +00:00 core NOTICE Created Dock IR emitter: dock_id=UCD3-0CBB00, name=‘Closet’, model=UCD3, active=true, port_mask=4
2025-10-28 17:12:37.949593 +00:00 core NOTICE [UCD3-0C8AB0] Authenticated (features=3)
2025-10-28 17:12:37.664478 +00:00 core NOTICE [UCD3-0C8AB0] Connected to: ws://192.168.1.29/ws
2025-10-28 17:12:36.148340 +00:00 core NOTICE Sent get_entity_states to uc_appletv_driver: Ok(())
2025-10-28 17:12:35.317503 +00:00 core NOTICE Sent get_entity_states to uc_appletv_driver: Ok(())
2025-10-28 17:12:35.302010 +00:00 core NOTICE [uc_appletv_driver] SessionAuthenticated msg
2025-10-28 17:12:35.301793 +00:00 core NOTICE [uc_appletv_driver] Session state change: Authenticated
2025-10-28 17:12:35.300085 +00:00 core NOTICE [uc_appletv_driver] Session became active: sending subscribe_events, get_driver_version, connect
2025-10-28 17:12:35.299565 +00:00 core NOTICE [uc_appletv_driver] SessionAuthenticated msg
2025-10-28 17:12:35.299260 +00:00 core NOTICE [uc_appletv_driver] Session state change: Authenticated
2025-10-28 17:12:35.293458 +00:00 core NOTICE [uc_appletv_driver] Connected to: ws://127.0.0.1:8097
2025-10-28 17:12:35.136143 +00:00 core NOTICE No session state has been found for a valid session key, creating a new empty session.
2025-10-28 17:12:35.082316 +00:00 core NOTICE No session state has been found for a valid session key, creating a new empty session.
2025-10-28 17:12:35.067664 +00:00 core NOTICE No session state has been found for a valid session key, creating a new empty session.
2025-10-28 17:12:35.065971 +00:00 core ERROR Error encountered while processing the incoming HTTP request: AuthError(“Authentication error”)
2025-10-28 17:12:35.064204 +00:00 core NOTICE No session state has been found for a valid session key, creating a new empty session.
2025-10-28 17:12:34.884631 +00:00 core NOTICE No session state has been found for a valid session key, creating a new empty session.
2025-10-28 17:12:34.057235 +00:00 core NOTICE Setting rgb button backlight to: (0, 0, 0)
2025-10-28 17:12:34.055967 +00:00 core NOTICE Enter idle mode: standby in 1785s
2025-10-28 17:12:33.260095 +00:00 core NOTICE [UCD3-0C8AB0] Reconnecting in: 4.068s
2025-10-28 17:12:33.256358 +00:00 core ERROR [UCD3-0C8AB0] Error connecting to dock ws://192.168.1.29/ws: ServiceUnavailable(“Failed to connect to host: No route to host (os error 113)”)
2025-10-28 17:12:31.212303 +00:00 core ERROR [uc_appletv_driver] Error connecting to driver ws://127.0.0.1:8097: ServiceUnavailable(“Failed to connect to host: Connection refused (os error 111)”)
2025-10-28 17:12:31.134510 +00:00 core WARN [UCD3-0CBB00] Can’t handle dock TryReconnect command in state: Active
2025-10-28 17:12:31.134105 +00:00 core WARN [UCD3-0CBB00] No transition for: state=Active, event=TryReconnect
2025-10-28 17:12:31.121478 +00:00 core WARN [UCD3-0C8AB0] Can’t handle dock TryReconnect command in state: Connecting
2025-10-28 17:12:31.120577 +00:00 core WARN [UCD3-0C8AB0] No transition for: state=Connecting, event=TryReconnect
2025-10-28 17:12:30.535334 +00:00 core NOTICE Created Dock IR emitter: dock_id=UCD3-0CBB00, name=‘Closet’, model=UCD3, active=true, port_mask=4
2025-10-28 17:12:30.459342 +00:00 core NOTICE [UCD3-0CBB00] Authenticated (features=3)
2025-10-28 17:12:31.342129 +00:00 core NOTICE [UCD3-0CBB00] Connected to: ws://192.168.1.79/ws
2025-10-28 17:12:31.184597 +00:00 core NOTICE [UCD3-0CBB00] WiFi connected: connecting dock
2025-10-28 17:12:31.184308 +00:00 core NOTICE [UCD3-0C8AB0] WiFi connected: connecting dock
2025-10-28 17:12:31.183938 +00:00 core NOTICE WiFi interface is up and routable, sending connected event
2025-10-28 17:12:31.183041 +00:00 core NOTICE Network changed: link_name: wlan0, operational_state: routable, address_state: routable, ipv4_address_state: routable, online_state: online
2025-10-28 17:12:30.549594 +00:00 core NOTICE Ignoring connected event from WiFi driver, using operational state instead
2025-10-28 17:12:30.432775 +00:00 core NOTICE Network changed: link_name: wlan0, operational_state: carrier, carrier_state: carrier
2025-10-28 17:12:30.360258 +00:00 core NOTICE Network changed: link_name: wlan0, operational_state: dormant, carrier_state: dormant
2025-10-28 17:12:29.662373 +00:00 core NOTICE Sent get_entity_states to uc_onkyo-avr_driver_custom: Ok(())
2025-10-28 17:12:29.660730 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: [TX-RZ1100 192.168.1.84] Already connected to AVR, re-registering entity
2025-10-28 17:12:29.659734 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: Discovered 0 AVR(s) via autodiscovery
2025-10-28 17:12:29.658120 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO [EiscpDriver] UDP socket closed
2025-10-28 17:12:29.054385 +00:00 core ERROR [uc_appletv_driver] Error connecting to driver ws://127.0.0.1:8097: ServiceUnavailable(“Failed to connect to host: Connection refused (os error 111)”)
2025-10-28 17:12:28.984102 +00:00 core NOTICE [UCD3-0CBB00] Reconnecting in: 3.13s
2025-10-28 17:12:28.983814 +00:00 core ERROR [UCD3-0CBB00] Error connecting to dock ws://192.168.1.79/ws: ServiceUnavailable(“Failed to connect to host: Network is unreachable (os error 101)”)
2025-10-28 17:12:28.970161 +00:00 core NOTICE [UCD3-0C8AB0] Reconnecting in: 3.13s
2025-10-28 17:12:28.969823 +00:00 core ERROR [UCD3-0C8AB0] Error connecting to dock ws://192.168.1.29/ws: ServiceUnavailable(“Failed to connect to host: Network is unreachable (os error 101)”)
2025-10-28 17:12:28.848742 +00:00 core NOTICE Sent get_entity_states to uc_onkyo-avr_driver_custom: Ok(())
2025-10-28 17:12:28.841015 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: [TX-RZ1100 192.168.1.84] Connected to AVR: model=TX-RZ1100, ip=192.168.1.84, port=60128
2025-10-28 17:12:28.833440 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: [TX-RZ1100] Connecting to AVR at 192.168.1.84:60128
2025-10-28 17:12:28.833440 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: Discovered 0 AVR(s) via autodiscovery
2025-10-28 17:12:28.827068 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO [EiscpDriver] UDP socket closed
2025-10-28 17:12:28.341872 +00:00 core NOTICE WifiEvent: NETWORK_NOT_FOUND
2025-10-28 17:12:26.650247 +00:00 core ERROR [uc_appletv_driver] Error connecting to driver ws://127.0.0.1:8097: ServiceUnavailable(“Failed to connect to host: Connection refused (os error 111)”)
2025-10-28 17:12:26.583190 +00:00 core NOTICE [UCD3-0CBB00] Reconnecting in: 2.408s
2025-10-28 17:12:26.582737 +00:00 core ERROR [UCD3-0CBB00] Error connecting to dock ws://192.168.1.79/ws: ServiceUnavailable(“Failed to connect to host: Network is unreachable (os error 101)”)
2025-10-28 17:12:26.559826 +00:00 core NOTICE [UCD3-0C8AB0] Reconnecting in: 2.408s
2025-10-28 17:12:26.559594 +00:00 core ERROR [UCD3-0C8AB0] Error connecting to dock ws://192.168.1.29/ws: ServiceUnavailable(“Failed to connect to host: Network is unreachable (os error 101)”)
2025-10-28 17:12:25.656389 +00:00 core NOTICE Sent get_entity_states to sonyadcp: Ok(())
2025-10-28 17:12:25.596019 +00:00 core NOTICE [sonyadcp] SessionAuthenticated msg
2025-10-28 17:12:25.595878 +00:00 core NOTICE [sonyadcp] Session state change: Authenticated
2025-10-28 17:12:25.595504 +00:00 core NOTICE [sonyadcp] Session became active: sending subscribe_events, get_driver_version, connect
2025-10-28 17:12:25.595080 +00:00 core NOTICE [sonyadcp] SessionAuthenticated msg
2025-10-28 17:12:25.594824 +00:00 core NOTICE [sonyadcp] Session state change: Authenticated
2025-10-28 17:12:25.583445 +00:00 core NOTICE [sonyadcp] Connected to: ws://127.0.0.1:9001
2025-10-28 17:12:24.916813 +00:00 core ERROR [sonyadcp] Error connecting to driver ws://127.0.0.1:9001: ServiceUnavailable(“Failed to connect to host: Connection refused (os error 111)”)
2025-10-28 17:12:24.795073 +00:00 core ERROR [uc_appletv_driver] Error connecting to driver ws://127.0.0.1:8097: ServiceUnavailable(“Failed to connect to host: Connection refused (os error 111)”)
2025-10-28 17:12:24.718725 +00:00 core NOTICE [UCD3-0CBB00] Reconnecting in: 1.853s
2025-10-28 17:12:24.718417 +00:00 core ERROR [UCD3-0CBB00] Error connecting to dock ws://192.168.1.79/ws: ServiceUnavailable(“Failed to connect to host: Network is unreachable (os error 101)”)
2025-10-28 17:12:24.705414 +00:00 core NOTICE [UCD3-0C8AB0] Reconnecting in: 1.853s
2025-10-28 17:12:24.705067 +00:00 core ERROR [UCD3-0C8AB0] Error connecting to dock ws://192.168.1.29/ws: ServiceUnavailable(“Failed to connect to host: Network is unreachable (os error 101)”)
2025-10-28 17:12:24.660196 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO }
2025-10-28 17:12:24.660196 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO port: 60128
2025-10-28 17:12:24.660196 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO address: ‘255.255.255.255’,
2025-10-28 17:12:24.660196 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO syscall: ‘send’,
2025-10-28 17:12:24.660196 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO code: ‘ENETUNREACH’,
2025-10-28 17:12:24.660196 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO errno: -101,
2025-10-28 17:12:24.660196 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO at process.processTicksAndRejections (node:internal/process/task_queues:91:21) {
2025-10-28 17:12:24.660196 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO at afterDns (node:dgram:699:5)
2025-10-28 17:12:24.660196 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO at defaultTriggerAsyncIdScope (node:internal/async_hooks:464:18)
2025-10-28 17:12:24.660196 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO at doSend (node:dgram:760:16)
2025-10-28 17:12:24.660196 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO [EiscpDriver] UDP send error: Error: send ENETUNREACH 255.255.255.255:60128
2025-10-28 17:12:24.609427 +00:00 core NOTICE Added standby inhibitor: charger
2025-10-28 17:12:24.609089 +00:00 core NOTICE Changed battery status: 92% Discharging, 3943mV, charger: false
2025-10-28 17:12:24.555180 +00:00 core NOTICE [uc_onkyo-avr_driver_custom] SessionAuthenticated msg
2025-10-28 17:12:24.555047 +00:00 core NOTICE [uc_onkyo-avr_driver_custom] Session state change: Authenticated
2025-10-28 17:12:24.535995 +00:00 core NOTICE [uc_onkyo-avr_driver_custom] Session became active: sending subscribe_events, get_driver_version, connect
2025-10-28 17:12:24.535608 +00:00 core NOTICE [uc_onkyo-avr_driver_custom] SessionAuthenticated msg
2025-10-28 17:12:24.535132 +00:00 core NOTICE [uc_onkyo-avr_driver_custom] Session state change: Authenticated
2025-10-28 17:12:24.517447 +00:00 core NOTICE [uc_onkyo-avr_driver_custom] Connected to: ws://127.0.0.1:9002
2025-10-28 17:12:24.421498 +00:00 core ERROR Error starting custom integration session: Failed to connect to host: Connection refused (os error 111)
2025-10-28 17:12:24.415428 +00:00 core ERROR [sonyadcp] Error connecting to driver ws://127.0.0.1:9001: ServiceUnavailable(“Failed to connect to host: Connection refused (os error 111)”)
2025-10-28 17:12:23.835634 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO }
2025-10-28 17:12:23.835634 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO port: 60128
2025-10-28 17:12:23.835634 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO address: ‘255.255.255.255’,
2025-10-28 17:12:23.835634 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO syscall: ‘send’,
2025-10-28 17:12:23.835634 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO code: ‘ENETUNREACH’,
2025-10-28 17:12:23.835634 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO errno: -101,
2025-10-28 17:12:23.835634 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO at process.processTicksAndRejections (node:internal/process/task_queues:91:21) {
2025-10-28 17:12:23.835634 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO at afterDns (node:dgram:699:5)
2025-10-28 17:12:23.835634 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO at defaultTriggerAsyncIdScope (node:internal/async_hooks:464:18)
2025-10-28 17:12:23.835634 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO at doSend (node:dgram:760:16)
2025-10-28 17:12:23.835634 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO [EiscpDriver] UDP send error: Error: send ENETUNREACH 255.255.255.255:60128
2025-10-28 17:12:23.744519 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: Initializing…
2025-10-28 17:12:23.695148 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO }
2025-10-28 17:12:23.695148 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO ]
2025-10-28 17:12:23.695148 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO }
2025-10-28 17:12:23.695148 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO useHalfDbSteps: true
2025-10-28 17:12:23.695148 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO volumeScale: 100,
2025-10-28 17:12:23.695148 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO albumArtURL: ‘album_art.cgi’,
2025-10-28 17:12:23.695148 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO queueThreshold: 100,
2025-10-28 17:12:23.695148 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO port: 60128,
2025-10-28 17:12:23.695148 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO ip: ‘192.168.1.84’,
2025-10-28 17:12:23.695148 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO model: ‘TX-RZ1100’,
2025-10-28 17:12:23.695148 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO {
2025-10-28 17:12:23.695148 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO avrs: [
2025-10-28 17:12:23.695148 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Loaded config at startup: {
Hi @PNWUC , thanks for the logs. Will take a closer look to it this evening and come back to you. I have no clue yet.
Hi @PNWUC please download temporary build (v0.6.2 not a full release yet) on the bottom of this page, install it instead of 0.6.1, run setup and let me know of that helps.
BTW it will download a zip, unzip it to get the .tar.gz which you can upload to the remote.
Kind regards,
Ed
