Started work on an 'Onkyo AVR / Pioneer AVR / Integra AVR' custom integration

PNWUC · October 30, 2025, 7:05pm

Installed 0.6.0. Same behavior. Fails after reboot. The one slightly different thing is 0.6.0 fails as soon as I hit the activity and throws a “No information found” error while 0.6.3 hangs for a few seconds on the step and then throws an error that says “Timeout”

Eddy · October 30, 2025, 9:12pm

Ok thanks for this. So not all work for 0.6.3 is waste, just not solving the issue you have after reboot. Will do some more reading and trials.

Eddy · October 31, 2025, 7:31am

@PNWUC could you try 0.6.4-beta1 and in case of trouble send me the logs?

Eddy · October 31, 2025, 10:06am

hi @PNWUC forget about beta1, please try 0.6.4-beta2 and please send logs in case of anything

PNWUC · October 31, 2025, 5:21pm

Yes, I was letting auto-discovery configure the AVR. Way early on, like the first or second time I re-installed, I manually input a AVR name and the static IP address. The install failed. I don’t remember the exact error (it was many installs ago!) but it made me try to reinstall with auto-discovery and it all worked fine. If you’d like me to try something different, let me know.

0.6.4-beta2 installed, same issue. Sorry! Logs below:

Installed new Integration:

2025-10-31 16:56:43.402310 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration (receiver): [TX-RZ1100 192.168.1.84] audio-muting set to: false
2025-10-31 16:56:43.351157 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration (receiver): [TX-RZ1100 192.168.1.84] input-selector (source) set to: stm
2025-10-31 16:56:43.311418 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration (receiver): [TX-RZ1100 192.168.1.84] power set to: STANDBY
2025-10-31 16:56:43.208520 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: [TX-RZ1100 192.168.1.84] Subscribed entity, queue threshold set to: 100ms
2025-10-31 16:56:40.965476 +00:00 core NOTICE [uc_onkyo-avr_driver_custom.main] Waiting for available entities with request id: 9
2025-10-31 16:56:40.655385 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration (receiver): [TX-RZ1100 192.168.1.84] input-selector (source) set to: stm
2025-10-31 16:56:40.556058 +00:00 core NOTICE Ok(DriverSetupChange { event_type: Stop, state: Ok, error: None, require_user_action: None })
2025-10-31 16:56:40.536461 +00:00 core NOTICE Sent get_entity_states to uc_onkyo-avr_driver_custom: Ok(())
2025-10-31 16:56:40.534065 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: Setting device state to CONNECTED
2025-10-31 16:56:40.528070 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: [TX-RZ1100 192.168.1.84] Querying AVR state after re-registration…
2025-10-31 16:56:40.527537 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: [TX-RZ1100 192.168.1.84] Available entity added successfully
2025-10-31 16:56:40.527115 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: [TX-RZ1100 192.168.1.84] Re-adding available entity with ID: TX-RZ1100 192.168.1.84
2025-10-31 16:56:40.525958 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: [TX-RZ1100 192.168.1.84] eiscp.connected status: true
2025-10-31 16:56:40.525958 +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-31 16:56:40.525958 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: [TX-RZ1100 192.168.1.84] Processing AVR - model=‘TX-RZ1100’, ip=‘192.168.1.84’, entityID=‘TX-RZ1100 192.168.1.84’
2025-10-31 16:56:40.523968 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO ]
2025-10-31 16:56:40.523968 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO }
2025-10-31 16:56:40.523968 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO “ip”: “192.168.1.84”
2025-10-31 16:56:40.523968 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO “model”: “TX-RZ1100”,
2025-10-31 16:56:40.523968 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO {
2025-10-31 16:56:40.523968 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: AVR configs: [
2025-10-31 16:56:40.523172 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: Config loaded, AVRs count: 1
2025-10-31 16:56:40.521552 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
2025-10-31 16:56:40.521552 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO at OnkyoDriver.handleDriverSetup (file:///app/onkyo.js:135:20)
2025-10-31 16:56:40.521552 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO at OnkyoDriver.handleConnect (file:///app/onkyo.js:181:27)
2025-10-31 16:56:40.521027 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: handleConnect called from:
2025-10-31 16:56:40.519163 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO ConfigManager: AVR at 192.168.1.84 already exists, skipping update
2025-10-31 16:56:40.517991 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: Adding autodiscovered AVR with volumeScale: 100, useHalfDbSteps: true
2025-10-31 16:56:40.516864 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: Discovered 1 AVR(s) via autodiscovery
2025-10-31 16:56:40.515678 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO [EiscpDriver] UDP socket closed
2025-10-31 16:56:40.478778 +00:00 core NOTICE Removed standby inhibitor: Integration setup: uc_onkyo-avr_driver_custom
2025-10-31 16:56:40.475462 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: No manual AVR config provided, running autodiscovery during setup
2025-10-31 16:56:40.475462 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO }
2025-10-31 16:56:40.475462 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO useHalfDbSteps: true
2025-10-31 16:56:40.475462 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO volumeScale: 100,
2025-10-31 16:56:40.475462 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO albumArtURL: ‘album_art.cgi’,
2025-10-31 16:56:40.475462 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO queueThreshold: 100,
2025-10-31 16:56:40.475462 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: Stored setup data for autodiscovery: {
2025-10-31 16:56:40.466970 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: Setup data parsed - volumeScale: 100, useHalfDbSteps: true
2025-10-31 16:56:40.466970 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: Setup data received - volumeScale raw value: ‘100’ (type: string), useHalfDbSteps: ‘true’ (type: string)
2025-10-31 16:56:40.466970 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO }
2025-10-31 16:56:40.466970 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO }
2025-10-31 16:56:40.466970 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO “volumeScale”: “100”
2025-10-31 16:56:40.466970 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO “useHalfDbSteps”: “true”,
2025-10-31 16:56:40.466970 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO “queueThreshold”: “100”,
2025-10-31 16:56:40.466970 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO “port”: “60128”,
2025-10-31 16:56:40.466970 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO “model”: “”,
2025-10-31 16:56:40.466970 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO “ipAddress”: “”,
2025-10-31 16:56:40.466970 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO “albumArtURL”: “album_art.cgi”,
2025-10-31 16:56:40.466970 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO “setupData”: {
2025-10-31 16:56:40.466970 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO “reconfigure”: true,
2025-10-31 16:56:40.466970 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: Setup message: {
2025-10-31 16:56:40.466970 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: ===== SETUP HANDLER CALLED =====
2025-10-31 16:56:35.348558 +00:00 core NOTICE uccore : PWD=/opt/uc/data ; USER=root ; COMMAND=/usr/bin/systemctl start node-intg@uc_onkyo-avr_driver_custom
2025-10-31 16:56:35.286236 +00:00 core NOTICE Execute system command: StartCustomIntegration(“uc_onkyo-avr_driver_custom”, Some(“node-intg@uc_onkyo-avr_driver_custom”))
2025-10-31 16:56:35.281230 +00:00 core NOTICE Added standby inhibitor: Integration setup: uc_onkyo-avr_driver_custom
2025-10-31 16:56:33.277160 +00:00 core NOTICE [uc_onkyo-avr_driver_custom.main] Waiting for available entities with request id: 6
2025-10-31 16:56:29.906714 +00:00 core NOTICE [uc_onkyo-avr_driver_custom.main] Waiting for available entities with request id: 5
2025-10-31 16:56:29.473373 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration (receiver): [TX-RZ1100 192.168.1.84] input-selector (source) set to: stm
2025-10-31 16:56:29.295681 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration (receiver): [TX-RZ1100 192.168.1.84] input-selector (source) set to: stm
2025-10-31 16:56:29.190724 +00:00 core NOTICE Sent get_entity_states to uc_onkyo-avr_driver_custom: Ok(())
2025-10-31 16:56:29.187841 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: Setting device state to CONNECTED
2025-10-31 16:56:29.185433 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: [TX-RZ1100 192.168.1.84] Querying AVR state after re-registration…
2025-10-31 16:56:29.184982 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: [TX-RZ1100 192.168.1.84] Available entity added successfully
2025-10-31 16:56:29.184273 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: [TX-RZ1100 192.168.1.84] Re-adding available entity with ID: TX-RZ1100 192.168.1.84
2025-10-31 16:56:29.183431 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: [TX-RZ1100 192.168.1.84] eiscp.connected status: true
2025-10-31 16:56:29.182434 +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-31 16:56:29.182434 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: [TX-RZ1100 192.168.1.84] Processing AVR - model=‘TX-RZ1100’, ip=‘192.168.1.84’, entityID=‘TX-RZ1100 192.168.1.84’
2025-10-31 16:56:29.180355 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO ]
2025-10-31 16:56:29.180355 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO }
2025-10-31 16:56:29.180355 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO “ip”: “192.168.1.84”
2025-10-31 16:56:29.180355 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO “model”: “TX-RZ1100”,
2025-10-31 16:56:29.180355 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO {
2025-10-31 16:56:29.180355 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: AVR configs: [
2025-10-31 16:56:29.179423 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: Config loaded, AVRs count: 1
2025-10-31 16:56:29.177681 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO at #messageReceived (/ap@unfoldedcircle/node_modules/@unfoldedcircle/integration-api/dist/cjs/index.js:392:26)
2025-10-31 16:56:29.177681 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO at IntegrationAPI.emit (node:events:524:28)
2025-10-31 16:56:29.177681 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO at OnkyoDriver.handleConnect (file:///app/onkyo.js:181:27)
2025-10-31 16:56:29.176671 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: handleConnect called from:
2025-10-31 16:56:29.140699 +00:00 core NOTICE Ok(DriverSetupChange { event_type: Stop, state: Ok, error: None, require_user_action: None })
2025-10-31 16:56:29.102178 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: Setting device state to CONNECTED
2025-10-31 16:56:29.091068 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: [TX-RZ1100 192.168.1.84] Querying initial AVR state…
2025-10-31 16:56:29.090399 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: [TX-RZ1100 192.168.1.84] Available entity added successfully
2025-10-31 16:56:29.088299 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: [TX-RZ1100 192.168.1.84] Adding available entity with ID: TX-RZ1100 192.168.1.84
2025-10-31 16:56:29.079806 +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-31 16:56:28.960830 +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-31 16:56:28.960830 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: [TX-RZ1100 192.168.1.84] Processing AVR - model=‘TX-RZ1100’, ip=‘192.168.1.84’, entityID=‘TX-RZ1100 192.168.1.84’
2025-10-31 16:56:28.958580 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO ]
2025-10-31 16:56:28.958580 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO }
2025-10-31 16:56:28.958580 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO “ip”: “192.168.1.84”
2025-10-31 16:56:28.958580 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO “model”: “TX-RZ1100”,
2025-10-31 16:56:28.958580 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO {
2025-10-31 16:56:28.958580 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: AVR configs: [
2025-10-31 16:56:28.957123 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: Config loaded, AVRs count: 1
2025-10-31 16:56:28.954695 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
2025-10-31 16:56:28.954695 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO at OnkyoDriver.handleDriverSetup (file:///app/onkyo.js:135:20)
2025-10-31 16:56:28.954695 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO at OnkyoDriver.handleConnect (file:///app/onkyo.js:181:27)
2025-10-31 16:56:28.953986 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: handleConnect called from:
2025-10-31 16:56:28.943086 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Config successfully saved to: /etc/custom-intg/uc_onkyo-avr_driver_custom/config.json
2025-10-31 16:56:28.936876 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: Adding autodiscovered AVR with volumeScale: 100, useHalfDbSteps: true
2025-10-31 16:56:28.935367 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: Discovered 1 AVR(s) via autodiscovery
2025-10-31 16:56:28.934202 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO [EiscpDriver] UDP socket closed
2025-10-31 16:56:28.811418 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: No manual AVR config provided, running autodiscovery during setup
2025-10-31 16:56:28.806541 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO }
2025-10-31 16:56:28.806541 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO useHalfDbSteps: true
2025-10-31 16:56:28.806541 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO volumeScale: 100,
2025-10-31 16:56:28.806541 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO albumArtURL: ‘album_art.cgi’,
2025-10-31 16:56:28.806541 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO queueThreshold: 100,
2025-10-31 16:56:28.806541 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: Stored setup data for autodiscovery: {
2025-10-31 16:56:28.803019 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: Setup data parsed - volumeScale: 100, useHalfDbSteps: true
2025-10-31 16:56:28.798559 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: Setup data received - volumeScale raw value: ‘100’ (type: string), useHalfDbSteps: ‘true’ (type: string)
2025-10-31 16:56:28.798559 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO }
2025-10-31 16:56:28.798559 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO }
2025-10-31 16:56:28.798559 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO “volumeScale”: “100”
2025-10-31 16:56:28.798559 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO “useHalfDbSteps”: “true”,
2025-10-31 16:56:28.798559 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO “queueThreshold”: “100”,
2025-10-31 16:56:28.798559 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO “port”: “60128”,
2025-10-31 16:56:28.798559 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO “model”: “”,
2025-10-31 16:56:28.798559 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO “ipAddress”: “”,
2025-10-31 16:56:28.798559 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO “albumArtURL”: “album_art.cgi”,
2025-10-31 16:56:28.798559 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO “setupData”: {
2025-10-31 16:56:28.798559 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO “reconfigure”: false,
2025-10-31 16:56:28.798559 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: Setup message: {
2025-10-31 16:56:28.794822 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: ===== SETUP HANDLER CALLED =====
2025-10-31 16:56:28.787364 +00:00 core NOTICE Removed standby inhibitor: Integration setup: uc_onkyo-avr_driver_custom
2025-10-31 16:56:23.621203 +00:00 core NOTICE uccore : PWD=/opt/uc/data ; USER=root ; COMMAND=/usr/bin/systemctl start node-intg@uc_onkyo-avr_driver_custom
2025-10-31 16:56:23.517296 +00:00 core NOTICE Execute system command: StartCustomIntegration(“uc_onkyo-avr_driver_custom”, Some(“node-intg@uc_onkyo-avr_driver_custom”))
2025-10-31 16:56:23.511130 +00:00 core NOTICE Added standby inhibitor: Integration setup: uc_onkyo-avr_driver_custom
2025-10-31 16:56:20.400823 +00:00 core NOTICE [uc_onkyo-avr_driver_custom] SessionAuthenticated msg
2025-10-31 16:56:20.400023 +00:00 core NOTICE [uc_onkyo-avr_driver_custom] Session state change: Authenticated
2025-10-31 16:56:20.366895 +00:00 core WARN [uc_onkyo-avr_driver_custom] Failed to get integration session, not sending connect: BadRequest: Integration ID not found
2025-10-31 16:56:20.366265 +00:00 core NOTICE [uc_onkyo-avr_driver_custom] Session became active: sending subscribe_events, get_driver_version, connect
2025-10-31 16:56:20.365147 +00:00 core NOTICE [uc_onkyo-avr_driver_custom] SessionAuthenticated msg
2025-10-31 16:56:20.364474 +00:00 core NOTICE [uc_onkyo-avr_driver_custom] Session state change: Authenticated
2025-10-31 16:56:20.360481 +00:00 core NOTICE [uc_onkyo-avr_driver_custom] Connected to: ws://127.0.0.1:9002
2025-10-31 16:56:19.446512 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: Initializing…
2025-10-31 16:56:19.444884 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Config missing or incomplete, waiting for setup.
2025-10-31 16:56:19.444055 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Loaded config at startup: {}
2025-10-31 16:56:19.388105 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: Config directory: /etc/custom-intg/uc_onkyo-avr_driver_custom
2025-10-31 16:56:16.548917 +00:00 core NOTICE uccore : PWD=/opt/uc/data ; USER=root ; COMMAND=/usr/bin/systemctl start node-intg@uc_onkyo-avr_driver_custom
2025-10-31 16:56:16.485908 +00:00 core NOTICE Execute system command: StartCustomIntegration(“uc_onkyo-avr_driver_custom”, Some(“node-intg@uc_onkyo-avr_driver_custom”))
2025-10-31 16:56:14.844091 +00:00 core NOTICE uccore : PWD=/opt/uc/data ; USER=root ; COMMAND=/opt/uc/integrations/install-custom-intg.sh /tmp/upload/intg uc_onkyo-avr_driver_custom 9002
2025-10-31 16:56:08.159345 +00:00 core NOTICE uccore : PWD=/opt/uc/data ; USER=root ; COMMAND=/opt/uc/integrations/extract-custom-intg.sh /tmp/upload/uc-intg-onkyo-avr-0.6.4-beta2.tar.gz /tmp/upload/intg
2025-10-31 16:55:46.401464 +00:00 core NOTICE uccore : PWD=/opt/uc/data ; USER=root ; COMMAND=/opt/uc/integrations/remove-custom-intg.sh uc_onkyo-avr_driver_custom
2025-10-31 16:55:46.325268 +00:00 core NOTICE [uc_onkyo-avr_driver_custom] StopDriver msg
2025-10-31 16:55:45.488762 +00:00 core NOTICE Setting rgb button backlight to: (0, 0, 0)
2025-10-31 16:55:45.487245 +00:00 core NOTICE Enter low-power mode: standby in 1770s
2025-10-31 16:55:44.545554 +00:00 core NOTICE [uc_onkyo-avr_driver_custom] Session state change: Disconnected
2025-10-31 16:55:44.537273 +00:00 core NOTICE [uc_onkyo-avr_driver_custom] StopDriver msg
2025-10-31 16:55:44.536082 +00:00 core NOTICE Stopping driver ‘uc_onkyo-avr_driver_custom’: no more instances
2025-10-31 16:55:44.508413 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: Remote disconnected
2025-10-31 16:55:24.900813 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: Setting device state to CONNECTED
2025-10-31 16:55:24.900162 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: [TX-RZ1100 192.168.1.84] Skipping state query - AVR not connected yet
2025-10-31 16:55:24.900162 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: [TX-RZ1100 192.168.1.84] Available entity added successfully
2025-10-31 16:55:24.900162 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: [TX-RZ1100 192.168.1.84] Re-adding available entity with ID: TX-RZ1100 192.168.1.84
2025-10-31 16:55:24.898649 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO at process.processTimers (node:internal/timers:529:7)
2025-10-31 16:55:24.898649 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO at listOnTimeout (node:internal/timers:594:17)
2025-10-31 16:55:24.898649 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO at Timeout._onTimeout (file:///app/eiscp.js:464:24)
2025-10-31 16:55:24.898649 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: [TX-RZ1100 192.168.1.84] Failed to reconnect to AVR: Error: Timeout waiting for AVR connection
2025-10-31 16:55:19.887718 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: [TX-RZ1100 192.168.1.84] TCP connection lost, reconnecting to AVR…
2025-10-31 16:55:19.887158 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: [TX-RZ1100 192.168.1.84] eiscp.connected status: false
2025-10-31 16:55:19.884900 +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-31 16:55:19.884900 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: [TX-RZ1100 192.168.1.84] Processing AVR - model=‘TX-RZ1100’, ip=‘192.168.1.84’, entityID=‘TX-RZ1100 192.168.1.84’
2025-10-31 16:55:19.884900 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO ]
2025-10-31 16:55:19.884900 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO }
2025-10-31 16:55:19.884900 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO “ip”: “192.168.1.84”
2025-10-31 16:55:19.884900 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO “model”: “TX-RZ1100”,
2025-10-31 16:55:19.884900 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO {
2025-10-31 16:55:19.884900 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: AVR configs: [
2025-10-31 16:55:19.884900 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: Config loaded, AVRs count: 1
2025-10-31 16:55:19.881942 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO at #messa@unfoldedcircleeReceived (/app/node_modules/@unfoldedcircle/integration-api/dist/cjs/index.js:392:26)
2025-10-31 16:55:19.881942 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO at IntegrationAPI.emit (node:events:524:28)
2025-10-31 16:55:19.881942 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO at OnkyoDriver.handleConnect (file:///app/onkyo.js:181:27)
2025-10-31 16:55:19.876882 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: handleConnect called from:
2025-10-31 16:55:19.853557 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: [TX-RZ1100 192.168.1.84] Subscribed entity, queue threshold set to: 100ms
2025-10-31 16:55:19.848529 +00:00 core NOTICE [uc_onkyo-avr_driver_custom] SessionAuthenticated msg
2025-10-31 16:55:19.848327 +00:00 core NOTICE [uc_onkyo-avr_driver_custom] Session state change: Authenticated
2025-10-31 16:55:19.833076 +00:00 core NOTICE [uc_onkyo-avr_driver_custom] Session became active: sending subscribe_events, get_driver_version, connect
2025-10-31 16:55:19.832812 +00:00 core NOTICE [uc_onkyo-avr_driver_custom] SessionAuthenticated msg
2025-10-31 16:55:19.832578 +00:00 core NOTICE [uc_onkyo-avr_driver_custom] Session state change: Authenticated
2025-10-31 16:55:19.831372 +00:00 core NOTICE [uc_onkyo-avr_driver_custom] Connected to: ws://127.0.0.1:9002
2025-10-31 16:55:19.770975 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: Setting device state to CONNECTED
2025-10-31 16:55:19.770576 +00:00 core ERROR Error starting custom integration session: Failed to connect to host: Connection refused (os error 111)
2025-10-31 16:55:19.764160 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: [TX-RZ1100 192.168.1.84] Querying initial AVR state…
2025-10-31 16:55:19.764160 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: [TX-RZ1100 192.168.1.84] Available entity added successfully
2025-10-31 16:55:19.764160 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: [TX-RZ1100 192.168.1.84] Adding available entity with ID: TX-RZ1100 192.168.1.84
2025-10-31 16:55:19.763747 +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-31 16:55:19.759700 +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-31 16:55:19.599296 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: Initializing…
2025-10-31 16:55:19.558182 +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-31 16:55:19.550155 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: [TX-RZ1100 192.168.1.84] Processing AVR - model=‘TX-RZ1100’, ip=‘192.168.1.84’, entityID=‘TX-RZ1100 192.168.1.84’
2025-10-31 16:55:19.549653 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO ]
2025-10-31 16:55:19.549653 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO }
2025-10-31 16:55:19.549653 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO “ip”: “192.168.1.84”
2025-10-31 16:55:19.549653 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO “model”: “TX-RZ1100”,
2025-10-31 16:55:19.549653 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO {
2025-10-31 16:55:19.549653 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: AVR configs: [
2025-10-31 16:55:19.549113 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: Config loaded, AVRs count: 1
2025-10-31 16:55:19.549113 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO at file:///app/driver.js:2:16
2025-10-31 16:55:19.549113 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO at new OnkyoDriver (file:///app/onkyo.js:33:18)
2025-10-31 16:55:19.549113 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO at OnkyoDriver.handleConnect (file:///app/onkyo.js:181:27)
2025-10-31 16:55:19.549113 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: handleConnect called from:
2025-10-31 16:55:19.537200 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO }
2025-10-31 16:55:19.537200 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO ]
2025-10-31 16:55:19.537200 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO }
2025-10-31 16:55:19.537200 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO useHalfDbSteps: true
2025-10-31 16:55:19.537200 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO volumeScale: 100,
2025-10-31 16:55:19.537200 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO albumArtURL: ‘album_art.cgi’,
2025-10-31 16:55:19.537200 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO queueThreshold: 100,
2025-10-31 16:55:19.537200 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO port: 60128,
2025-10-31 16:55:19.537200 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO ip: ‘192.168.1.84’,
2025-10-31 16:55:19.537200 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO model: ‘TX-RZ1100’,
2025-10-31 16:55:19.537200 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO {
2025-10-31 16:55:19.537200 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO avrs: [
2025-10-31 16:55:19.537200 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Loaded config at startup: {
2025-10-31 16:55:19.480884 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: Config directory: /etc/custom-intg/uc_onkyo-avr_driver_custom

Successfully ran Test Onkyo

2025-10-31 16:58:05.391395 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration (receiver): [TX-RZ1100 192.168.1.84] input-selector (source) set to: stm
2025-10-31 16:58:04.554508 +00:00 core NOTICE Removed standby inhibitor: activity ‘Test Onkyo’ (off) (max 65s)
2025-10-31 16:58:04.553842 +00:00 core NOTICE [Test Onkyo] activity finished
2025-10-31 16:58:04.548379 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration (sender): [TX-RZ1100 192.168.1.84] media-player command request: off {}
2025-10-31 16:58:04.545992 +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-31 16:58:04.545172 +00:00 core NOTICE Added standby inhibitor: activity ‘Test Onkyo’ (off) (max 65s)
2025-10-31 16:58:04.541789 +00:00 core NOTICE Started activity ‘Test Onkyo’ (uc.main.770bdf25-57b0-4711-a02f-7eaa6a7572f4) with timeout of 60s
2025-10-31 16:58:04.304290 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration (receiver): [TX-RZ1100 192.168.1.84] power set to: ON
2025-10-31 16:58:01.124944 +00:00 core NOTICE Removed standby inhibitor: activity ‘Test Onkyo’ (on) (max 65s)
2025-10-31 16:58:01.124709 +00:00 core NOTICE [Test Onkyo] activity finished
2025-10-31 16:58:01.119484 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration (sender): [TX-RZ1100 192.168.1.84] media-player command request: on {}
2025-10-31 16:58:01.105526 +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-31 16:58:01.105063 +00:00 core NOTICE Added standby inhibitor: activity ‘Test Onkyo’ (on) (max 65s)
2025-10-31 16:58:01.104389 +00:00 core NOTICE Started activity ‘Test Onkyo’ (uc.main.770bdf25-57b0-4711-a02f-7eaa6a7572f4) with timeout of 60s
2025-10-31 16:58:01.103683 +00:00 core NOTICE Starting activity ‘Test Onkyo’ (uc.main.770bdf25-57b0-4711-a02f-7eaa6a7572f4) in activity group: ‘Default’ (default)

PNWUC · October 31, 2025, 5:23pm

Rebooted:

2025-10-31 16:58:45.142154 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: Setting device state to CONNECTED
2025-10-31 16:58:45.141685 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: [TX-RZ1100 192.168.1.84] Skipping state query - AVR not connected yet
2025-10-31 16:58:45.141685 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: [TX-RZ1100 192.168.1.84] Available entity added successfully
2025-10-31 16:58:45.141685 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: [TX-RZ1100 192.168.1.84] Re-adding available entity with ID: TX-RZ1100 192.168.1.84
2025-10-31 16:58:45.140207 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO at process.processTimers (node:internal/timers:529:7)
2025-10-31 16:58:45.140207 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO at listOnTimeout (node:internal/timers:594:17)
2025-10-31 16:58:45.140207 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO at Timeout._onTimeout (file:///app/eiscp.js:464:24)
2025-10-31 16:58:45.140207 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: [TX-RZ1100 192.168.1.84] Failed to reconnect to AVR: Error: Timeout waiting for AVR connection
2025-10-31 16:58:40.126700 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: [TX-RZ1100 192.168.1.84] TCP connection lost, reconnecting to AVR…
2025-10-31 16:58:40.126700 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: [TX-RZ1100 192.168.1.84] eiscp.connected status: false
2025-10-31 16:58:40.126700 +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-31 16:58:40.126700 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: [TX-RZ1100 192.168.1.84] Processing AVR - model=‘TX-RZ1100’, ip=‘192.168.1.84’, entityID=‘TX-RZ1100 192.168.1.84’
2025-10-31 16:58:40.126700 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO ]
2025-10-31 16:58:40.126700 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO }
2025-10-31 16:58:40.126700 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO “ip”: “192.168.1.84”
2025-10-31 16:58:40.126700 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO “model”: “TX-RZ1100”,
2025-10-31 16:58:40.126700 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO {
2025-10-31 16:58:40.126700 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: AVR configs: [
2025-10-31 16:58:40.126700 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: Config loaded, AVRs count: 1
2025-10-31 16:58:40.123200 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO at #messageReceived (/ap@unfoldedcircle/node_modules/@unfoldedcircle/integration-api/dist/cjs/index.js:392:26)
2025-10-31 16:58:40.123200 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO at IntegrationAPI.emit (node:events:524:28)
2025-10-31 16:58:40.123200 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO at OnkyoDriver.handleConnect (file:///app/onkyo.js:181:27)
2025-10-31 16:58:40.122776 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: handleConnect called from:
2025-10-31 16:58:40.112749 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: [TX-RZ1100 192.168.1.84] Subscribed entity, queue threshold set to: 100ms
2025-10-31 16:58:40.098509 +00:00 core NOTICE [uc_onkyo-avr_driver_custom] SessionAuthenticated msg
2025-10-31 16:58:40.098289 +00:00 core NOTICE [uc_onkyo-avr_driver_custom] Session state change: Authenticated
2025-10-31 16:58:40.077851 +00:00 core NOTICE [uc_onkyo-avr_driver_custom] Session became active: sending subscribe_events, get_driver_version, connect
2025-10-31 16:58:40.077575 +00:00 core NOTICE [uc_onkyo-avr_driver_custom] SessionAuthenticated msg
2025-10-31 16:58:40.077456 +00:00 core NOTICE [uc_onkyo-avr_driver_custom] Session state change: Authenticated
2025-10-31 16:58:40.076542 +00:00 core NOTICE [uc_onkyo-avr_driver_custom] Connected to: ws://127.0.0.1:9002
2025-10-31 16:58:39.945016 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: Setting device state to CONNECTED
2025-10-31 16:58:39.916358 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: [TX-RZ1100 192.168.1.84] Querying initial AVR state…
2025-10-31 16:58:39.916009 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: [TX-RZ1100 192.168.1.84] Available entity added successfully
2025-10-31 16:58:39.906431 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: [TX-RZ1100 192.168.1.84] Adding available entity with ID: TX-RZ1100 192.168.1.84
2025-10-31 16:58:39.878906 +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-31 16:58:39.854858 +00:00 core ERROR Error starting custom integration session: Failed to connect to host: Connection refused (os error 111)
2025-10-31 16:58:39.842798 +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-31 16:58:39.634912 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: Initializing…
2025-10-31 16:58:39.548958 +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-31 16:58:39.544941 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: [TX-RZ1100 192.168.1.84] Processing AVR - model=‘TX-RZ1100’, ip=‘192.168.1.84’, entityID=‘TX-RZ1100 192.168.1.84’
2025-10-31 16:58:39.544941 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO ]
2025-10-31 16:58:39.544941 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO }
2025-10-31 16:58:39.544941 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO “ip”: “192.168.1.84”
2025-10-31 16:58:39.544941 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO “model”: “TX-RZ1100”,
2025-10-31 16:58:39.544941 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO {
2025-10-31 16:58:39.544941 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: AVR configs: [
2025-10-31 16:58:39.528195 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: Config loaded, AVRs count: 1
2025-10-31 16:58:39.520921 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO at file:///app/driver.js:2:16
2025-10-31 16:58:39.520921 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO at new OnkyoDriver (file:///app/onkyo.js:33:18)
2025-10-31 16:58:39.520921 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO at OnkyoDriver.handleConnect (file:///app/onkyo.js:181:27)
2025-10-31 16:58:39.520921 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: handleConnect called from:
2025-10-31 16:58:39.510275 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO }
2025-10-31 16:58:39.510275 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO ]
2025-10-31 16:58:39.510275 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO }
2025-10-31 16:58:39.510275 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO useHalfDbSteps: true
2025-10-31 16:58:39.510275 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO volumeScale: 100,
2025-10-31 16:58:39.510275 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO albumArtURL: ‘album_art.cgi’,
2025-10-31 16:58:39.510275 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO queueThreshold: 100,
2025-10-31 16:58:39.510275 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO port: 60128,
2025-10-31 16:58:39.510275 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO ip: ‘192.168.1.84’,
2025-10-31 16:58:39.510275 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO model: ‘TX-RZ1100’,
2025-10-31 16:58:39.510275 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO {
2025-10-31 16:58:39.510275 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO avrs: [
2025-10-31 16:58:39.510275 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Loaded config at startup: {
2025-10-31 16:58:39.391178 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: Config directory: /etc/custom-intg/uc_onkyo-avr_driver_custom

Failed Test Onkyo after Reboot

2025-10-31 17:00:11.450672 +00:00 core NOTICE Removed standby inhibitor: activity ‘Test Onkyo’ (on) (max 65s)
2025-10-31 17:00:11.449900 +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): TimedOut
2025-10-31 17:00:11.446519 +00:00 core WARN [uc_onkyo-avr_driver_custom.main] Timeout while waiting for request id: 5
2025-10-31 17:00:06.465333 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO at process.processTimers (node:internal/timers:529:7)
2025-10-31 17:00:06.465333 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO at listOnTimeout (node:internal/timers:594:17)
2025-10-31 17:00:06.465333 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO at Timeout._onTimeout (file:///app/eiscp.js:464:24)
2025-10-31 17:00:06.465333 +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-31 17:00:01.446522 +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-31 17:00:01.445929 +00:00 core NOTICE Added standby inhibitor: activity ‘Test Onkyo’ (on) (max 65s)
2025-10-31 17:00:01.445318 +00:00 core NOTICE Started activity ‘Test Onkyo’ (uc.main.770bdf25-57b0-4711-a02f-7eaa6a7572f4) with timeout of 60s
2025-10-31 17:00:01.442473 +00:00 core NOTICE Starting activity ‘Test Onkyo’ (uc.main.770bdf25-57b0-4711-a02f-7eaa6a7572f4) in activity group: ‘Default’ (default)

Eddy · October 31, 2025, 6:49pm

Ok, will dive into the logs tomorrow!

Eddy · November 1, 2025, 10:22am

Hi @PNWUC please try 0.6.4-beta4 and also make sure that in settings/development you have enabled ‘new reconnect logic’.

PNWUC · November 2, 2025, 6:48pm

Sorry for the delay. Busy weekend! New reconnect logic has been on this whole time. I just installed Beta4 and…unfortunately…same.

I’m not opposed to doing a full factory reset. After doing that I could simply load the onkyo integration and see if it works. If it does we know it’s some phantom install issue. If it doesn’t, it’s something else in the code. Let me know!

Eddy · November 2, 2025, 7:26pm

Hi @PNWUC , no need to say sorry we all enjoy weekends

Frustrating that beta4 also does not make a difference.

Yeah it can be worth a shot do do a factory reset, install beta4 (not a restore of a backup, a real clean install) and test again, I have no new ideas at this moment…

Please keep me posted.

Cheers,

Ed

PNWUC · November 2, 2025, 11:53pm

@Eddy - Great. I’ll do the full reset. I like the idea of ONLY installing the Onkyo integration and going from there. Too much going on tonight so that’s a job for Monday. Stay tuned…and thanks again for your help!

Eddy · November 3, 2025, 5:26am

You’re very welcome and I hope it solves the issue or at least tells us more about what is going on!

PNWUC · November 3, 2025, 5:32pm

@Eddy I factory reset both docks as well as my remote. Upon restarting and setting up WiFi, I installed ONLY the Onkyo integration. I created a simple activity to turn on the AVR. It worked as expected. I rebooted the remote.

Bad news: It failed again like it always has.

Good news: I guess now we know it’s something in the integration that is failing and it has nothing to do with my old installs or any other integrations loaded into the remote! Argh!

Here are the logs from the reboot along with the failure:

2025-11-03 17:27:33.379535 +00:00 core NOTICE Changed battery status: 96% Discharging, 4075mV, charger: false
2025-11-03 17:27:25.751158 +00:00 core NOTICE Setting rgb button backlight to: (0, 0, 0)
2025-11-03 17:27:25.749747 +00:00 core NOTICE Enter low-power mode: standby in 120s
2025-11-03 17:26:55.686422 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO at process.processTimers (node:internal/timers:529:7)
2025-11-03 17:26:55.686422 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO at listOnTimeout (node:internal/timers:594:17)
2025-11-03 17:26:55.686422 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO at Timeout._onTimeout (file:///app/eiscp.js:464:24)
2025-11-03 17:26:55.686422 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration (sender): [TX-RZ1100 192.168.1.84] Could not connect to AVR after 5 attempts: Error: Timeout waiting for AVR connection
2025-11-03 17:26:54.745949 +00:00 core NOTICE Setting rgb button backlight to: (0, 0, 0)
2025-11-03 17:26:54.744414 +00:00 core NOTICE Enter idle mode: standby in 150s
2025-11-03 17:26:30.634544 +00:00 core NOTICE Removed standby inhibitor: activity ‘Test Onkyo’ (on) (max 65s)
2025-11-03 17:26:30.633696 +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): TimedOut
2025-11-03 17:26:30.629842 +00:00 core WARN [uc_onkyo-avr_driver_custom.main] Timeout while waiting for request id: 5
2025-11-03 17:26:25.639638 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO at process.processTimers (node:internal/timers:529:7)
2025-11-03 17:26:25.639638 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO at listOnTimeout (node:internal/timers:594:17)
2025-11-03 17:26:25.639638 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO at Timeout._onTimeout (file:///app/eiscp.js:464:24)
2025-11-03 17:26:25.639638 +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-11-03 17:26:20.627402 +00:00 core NOTICE [Test Onkyo] activity command: uc_onkyo-avr_driver_custom.main.TX-RZ1100 192.168.1.84:media_player.on
2025-11-03 17:26:20.627162 +00:00 core NOTICE Added standby inhibitor: activity ‘Test Onkyo’ (on) (max 65s)
2025-11-03 17:26:20.626752 +00:00 core NOTICE Started activity ‘Test Onkyo’ (uc.main.7307c553-b8b8-47ff-8dac-fab6c0583287) with timeout of 60s
2025-11-03 17:26:20.626369 +00:00 core NOTICE Starting activity ‘Test Onkyo’ (uc.main.7307c553-b8b8-47ff-8dac-fab6c0583287) in activity group: ‘Default’ (default)
2025-11-03 17:26:20.548643 +00:00 core NOTICE Setting rgb button backlight to: (127, 127, 127)
2025-11-03 17:26:20.547205 +00:00 core NOTICE Enter normal mode: standby in 180s
2025-11-03 17:26:15.012692 +00:00 core NOTICE Added standby inhibitor: Web configurator
2025-11-03 17:26:14.307209 +00:00 core NOTICE No session state has been found for a valid session key, creating a new empty session.
2025-11-03 17:26:13.801521 +00:00 core NOTICE No session state has been found for a valid session key, creating a new empty session.
2025-11-03 17:26:13.747528 +00:00 core NOTICE Setting rgb button backlight to: (0, 0, 0)
2025-11-03 17:26:13.746210 +00:00 core NOTICE Enter idle mode: standby in 150s
2025-11-03 17:26:11.411556 +00:00 core NOTICE No session state has been found for a valid session key, creating a new empty session.
2025-11-03 17:26:08.036312 +00:00 core NOTICE No session state has been found for a valid session key, creating a new empty session.
2025-11-03 17:26:07.953408 +00:00 core NOTICE No session state has been found for a valid session key, creating a new empty session.
2025-11-03 17:26:07.934801 +00:00 core NOTICE No session state has been found for a valid session key, creating a new empty session.
2025-11-03 17:26:07.732493 +00:00 core NOTICE No session state has been found for a valid session key, creating a new empty session.
2025-11-03 17:26:04.055576 +00:00 core NOTICE No session state has been found for a valid session key, creating a new empty session.
2025-11-03 17:26:04.042861 +00:00 core NOTICE No session state has been found for a valid session key, creating a new empty session.
2025-11-03 17:26:04.016683 +00:00 core ERROR Error encountered while processing the incoming HTTP request: AuthError(“Authentication error”)
2025-11-03 17:26:04.015745 +00:00 core NOTICE No session state has been found for a valid session key, creating a new empty session.
2025-11-03 17:25:57.404380 +00:00 core NOTICE WiFi interface is up and routable, sending connected event
2025-11-03 17:25:57.396939 +00:00 core NOTICE Network changed: link_name: wlan0, operational_state: routable, address_state: routable, ipv4_address_state: routable, online_state: online
2025-11-03 17:25:56.531788 +00:00 core NOTICE Ignoring connected event from WiFi driver, using operational state instead
2025-11-03 17:25:56.506381 +00:00 core NOTICE Network changed: link_name: wlan0, operational_state: carrier, carrier_state: carrier
2025-11-03 17:25:56.425832 +00:00 core NOTICE Network changed: link_name: wlan0, operational_state: dormant, carrier_state: dormant
2025-11-03 17:25:52.919764 +00:00 core NOTICE WifiEvent: NETWORK_NOT_FOUND
2025-11-03 17:25:51.660927 +00:00 core NOTICE Sent get_entity_states to uc_onkyo-avr_driver_custom: Ok(())
2025-11-03 17:25:51.649529 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: [TX-RZ1100 192.168.1.84] Cannot query AVR state (after entity registration), not connected
2025-11-03 17:25:51.649529 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: Registering 1 AVR entity(ies)
2025-11-03 17:25:51.644694 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO at process.processTimers (node:internal/timers:529:7)
2025-11-03 17:25:51.644694 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO at listOnTimeout (node:internal/timers:594:17)
2025-11-03 17:25:51.644694 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO at Timeout._onTimeout (file:///app/eiscp.js:464:24)
2025-11-03 17:25:51.644694 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: [TX-RZ1100 192.168.1.84] Failed to reconnect to AVR: Error: Timeout waiting for AVR connection
2025-11-03 17:25:49.202983 +00:00 core NOTICE Added standby inhibitor: charger
2025-11-03 17:25:49.202552 +00:00 core NOTICE Changed battery status: 97% Discharging, 3998mV, charger: false
2025-11-03 17:25:48.627334 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: [TX-RZ1100 192.168.1.84] Waiting for connection to be established…
2025-11-03 17:25:48.625370 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: [TX-RZ1100 192.168.1.84] Successfully reconnected to AVR
2025-11-03 17:25:48.618727 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: [TX-RZ1100 192.168.1.84] TCP connection lost, reconnecting to AVR…
2025-11-03 17:25:48.615372 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: [TX-RZ1100 192.168.1.84] Already connected to AVR, preparing for re-registration
2025-11-03 17:25:48.608406 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: [TX-RZ1100 192.168.1.84] Cannot query AVR state (on subscribe), not connected
2025-11-03 17:25:48.606455 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: [TX-RZ1100 192.168.1.84] Subscribed entity, queue threshold set to: 100ms
2025-11-03 17:25:48.585670 +00:00 core NOTICE [uc_onkyo-avr_driver_custom] SessionAuthenticated msg
2025-11-03 17:25:48.585138 +00:00 core NOTICE [uc_onkyo-avr_driver_custom] Session state change: Authenticated
2025-11-03 17:25:48.567954 +00:00 core NOTICE [uc_onkyo-avr_driver_custom] Session became active: sending subscribe_events, get_driver_version, connect
2025-11-03 17:25:48.567664 +00:00 core NOTICE [uc_onkyo-avr_driver_custom] SessionAuthenticated msg
2025-11-03 17:25:48.567471 +00:00 core NOTICE [uc_onkyo-avr_driver_custom] Session state change: Authenticated
2025-11-03 17:25:48.562569 +00:00 core NOTICE [uc_onkyo-avr_driver_custom] Connected to: ws://127.0.0.1:9001
2025-11-03 17:25:47.937748 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: [TX-RZ1100 192.168.1.84] Cannot query AVR state (after entity registration), not connected
2025-11-03 17:25:47.935398 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: Registering 1 AVR entity(ies)
2025-11-03 17:25:47.931992 +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-11-03 17:25:47.928593 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: Initializing…
2025-11-03 17:25:47.910356 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Onkyo-Integration: [TX-RZ1100] Connecting to AVR at 192.168.1.84:60128
2025-11-03 17:25:47.904757 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO }
2025-11-03 17:25:47.904757 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO ]
2025-11-03 17:25:47.904757 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO }
2025-11-03 17:25:47.904757 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO useHalfDbSteps: true
2025-11-03 17:25:47.904757 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO volumeScale: 100,
2025-11-03 17:25:47.904757 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO albumArtURL: ‘album_art.cgi’,
2025-11-03 17:25:47.904757 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO queueThreshold: 100,
2025-11-03 17:25:47.904757 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO port: 60128,
2025-11-03 17:25:47.904757 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO ip: ‘192.168.1.84’,
2025-11-03 17:25:47.904757 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO model: ‘TX-RZ1100’,
2025-11-03 17:25:47.904757 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO {
2025-11-03 17:25:47.904757 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO avrs: [
2025-11-03 17:25:47.904757 +00:00 node-intg-uc_onkyo-avr_driver_custom INFO Loaded config at startup: {
2025-11-03 17:25:47.843026 +00:00 core NOTICE BtDaemonStatus { status: Working, hci_log: true, log_level: Debug, connections: 0, max_connections: 1, paired_profiles: 0, active_profile: 0, advertising: true, advertising_name: “Remote3 B07BD5”, version: “0.6.0” }
2025-11-03 17:25:47.839795 +00:00 core NOTICE [BT] Scan mode: discoverable=false, connectable=false
2025-11-03 17:25:47.296213 +00:00 core NOTICE BtDaemonStatus { status: Initializing, hci_log: true, log_level: Debug, connections: 0, max_connections: 1, paired_profiles: 0, active_profile: 0, advertising: true, advertising_name: “Remote3 000000”, version: “0.6.0” }
2025-11-03 17:25:47.295838 +00:00 core NOTICE Connected to BT daemon: 127.0.0.1:13333
2025-11-03 17:25:47.281977 +00:00 core NOTICE Restarting BT daemon client, enabled=true
2025-11-03 17:25:45.917121 +00:00 core ERROR Cannot connect to BT daemon: I/O error. Reconnecting in 1.361962301s
2025-11-03 17:25:45.916437 +00:00 core NOTICE Restarting BT daemon client, enabled=true
2025-11-03 17:25:45.119411 +00:00 core ERROR Cannot connect to BT daemon: I/O error. Reconnecting in 797.760928ms
2025-11-03 17:25:45.112140 +00:00 core NOTICE Restarting BT daemon client, enabled=true
2025-11-03 17:25:45.060343 +00:00 core NOTICE uccore : PWD=/opt/uc/data ; USER=root ; COMMAND=/usr/bin/systemctl start node-intg@uc_onkyo-avr_driver_custom
2025-11-03 17:25:44.972919 +00:00 core NOTICE Execute system command: StartCustomIntegration(“uc_onkyo-avr_driver_custom”, Some(“node-intg@uc_onkyo-avr_driver_custom”))
2025-11-03 17:25:44.970263 +00:00 core NOTICE Not starting driver ‘uc_denon_driver’: no configured instances
2025-11-03 17:25:44.896576 +00:00 core NOTICE Not starting driver ‘uc_sonos_driver’: no configured instances
2025-11-03 17:25:44.896288 +00:00 core NOTICE Not starting driver ‘uc_androidtv_driver’: no configured instances
2025-11-03 17:25:44.894758 +00:00 core NOTICE Not starting driver ‘uc_hue_driver’: no configured instances
2025-11-03 17:25:44.894539 +00:00 core NOTICE Not starting driver ‘uc_appletv_driver’: no configured instances
2025-11-03 17:25:44.893087 +00:00 core NOTICE uccore : PWD=/opt/uc/data ; USER=root ; COMMAND=/usr/bin/systemctl start wpa_supplicant
2025-11-03 17:25:44.888036 +00:00 core NOTICE uccore : PWD=/opt/uc/data ; USER=root ; COMMAND=/usr/bin/systemctl start btstack
2025-11-03 17:25:44.887722 +00:00 core NOTICE Not starting driver ‘hass’: no configured instances
2025-11-03 17:25:44.869813 +00:00 core NOTICE uccore : PWD=/opt/uc/data ; USER=root ; COMMAND=/usr/sbin/wl band b
2025-11-03 17:25:44.852953 +00:00 core NOTICE uccore : PWD=/opt/uc/data ; USER=root ; COMMAND=/usr/sbin/iw phy0 wowlan disable magic-packet
2025-11-03 17:25:44.851345 +00:00 core NOTICE Not starting driver ‘uc_gc_driver’: no configured instances
2025-11-03 17:25:44.850353 +00:00 core NOTICE Not starting driver ‘uc_bo_driver’: no configured instances
2025-11-03 17:25:44.845052 +00:00 core NOTICE Not starting driver ‘uc_roon_driver’: no configured instances
2025-11-03 17:25:44.843485 +00:00 core NOTICE uccore : PWD=/opt/uc/data ; USER=root ; COMMAND=/usr/sbin/wl country US
2025-11-03 17:25:44.832268 +00:00 core NOTICE Not starting driver ‘uc_roku_driver’: no configured instances
2025-11-03 17:25:44.772606 +00:00 core ERROR Cannot connect to BT daemon: I/O error. Reconnecting in 332.99164ms
2025-11-03 17:25:44.768751 +00:00 core NOTICE Execute system command: StartBluetooth
2025-11-03 17:25:44.763986 +00:00 core NOTICE Enabling WoWLAN: false
2025-11-03 17:25:44.755126 +00:00 core NOTICE Updating BT service configuration file, connections=1
2025-11-03 17:25:44.723505 +00:00 core NOTICE Execute system command: StartWifi
2025-11-03 17:25:44.716712 +00:00 core NOTICE Execute system command: EnableWoWLAN(false)
2025-11-03 17:25:44.716354 +00:00 core NOTICE Execute system command: SetWifiBand(B)
2025-11-03 17:25:44.707379 +00:00 core NOTICE Starting active WiFi scanning interval: 10s
2025-11-03 17:25:44.706946 +00:00 core NOTICE Feature flag enabled: routable_if_link. Using operational state ‘routable’ for WiFi connect events.
2025-11-03 17:25:44.700377 +00:00 core NOTICE Monitoring network link ‘wlan0’ for changes
2025-11-03 17:25:44.666332 +00:00 core NOTICE Setting rgb button backlight to: (127, 127, 127)
2025-11-03 17:25:44.661361 +00:00 core NOTICE Execute system command: SetWlCommand(“country”, “US”)
2025-11-03 17:25:44.653363 +00:00 core NOTICE Enter normal mode: standby in 180s
2025-11-03 17:25:44.348366 +00:00 core NOTICE starting service: “actix-web-service-127.0.0.1:9000”, workers: 1, listening on: 127.0.0.1:9000
2025-11-03 17:25:44.348059 +00:00 core NOTICE Actix runtime found; starting in Actix runtime
2025-11-03 17:25:44.259161 +00:00 core NOTICE Feature flag enabled: routable_if_link. Using operational state ‘routable’ for WiFi connect events.
2025-11-03 17:25:43.940626 +00:00 core NOTICE starting 1 workers
2025-11-03 17:25:43.525076 +00:00 core NOTICE Cleaning up downloaded system OTA updates <= 2.7.0
2025-11-03 17:25:43.516317 +00:00 core NOTICE Core-API listening on: 127.0.0.1:9000

Eddy · November 3, 2025, 6:05pm

Hi @PNWUC , well that is very disappointing. And it’s confusing because I cannot reproduce it with my newer or older AVR. Also did not hear about it from any of the other users. So Im not sure it is the integration, could also be network related but will have a close look at the logs later.

Will have to think about any next steps…

Can you send me a short clip starting with the working integration then reboot and keep on recording till the failure, so I can see the complete sequence? I want to know what we do differently… if you cannot post it here then maybe it is possible in Discord

Is you remote running v2.6.12?

Kind regards,

Ed

PNWUC · November 3, 2025, 6:35pm

@Eddy Crazy, right?!?! I don’t want to go back to IR control! First of all, I’m actually running v2.7.0. Awhile back I was having an issue with my docks and they had me turn on Beta updates. That setting is still active. I would hope 2.7 vs 2.6.12 is not the issue but that is a difference.

For your viewing enjoyment, here is the entire process! Man, I hope you figure out that I’m simply doing something stupid here!

Eddy · November 3, 2025, 7:01pm

Thanks! Yes its the same routine that Im also doing. The thing that stands out is that it takes longer for the remote to be ready (little ball boumcing left/right).

I also hope its not about 2.7.0.

Have think about it. First will visit concert of Level42 (queueing at this moment).

Maybe I also have to go to 2.7.0…. Hmmm….

PNWUC · November 3, 2025, 8:41pm

Enjoy the concert!

I’d consider downgrading my firmware but that makes me nervous. Is 2.7 a beta? I wonder what will happen if I turn the beta toggle off now…

Eddy · November 3, 2025, 10:40pm

Concert wat great!

Don’t downgrade yet. I remember some comment for another integration on Discord. I asked that user if also running 2.7.0.

I might upgrade to 2.7.0 to see if I can then reproduce the issue. But am a bit reluctant because of WAF which is currently high

Eddy · November 4, 2025, 9:24am

@PNWUC I installed UC firmware v2.7.0 and could then easily reproduce the issue!

So I adjusted the (re)connection logic to have some retries with increased timeouts. Also added a background process which tries to recover when connection did not complete within those initial retries.

It seems to fix the issue for me so I hope it also does that for you.

Please play with beta5 and let me know?

I have high hopes now

Cheers,

Ed

PNWUC · November 4, 2025, 5:28pm

Your high hopes were justified…IT WORKS!!! Amazing work! Thank you! I’m just sorry I didn’t mention to you earlier that I was on 2.7.0…I had forgotten I switched on beta updates a few months ago. Wonder if it’s time to turn those off for now…

Again, amazing work. Thank you so much for sticking with me!