How do I stop an activity on Remote 3? Resolved

Slaids · August 10, 2025, 3:42am

I have setup a Watch TV activity and it initiates all devices in that mode. The User Interface and button mapping are all displayed. How do I initiate the activity OFF sequence? Sorry but I’m a newbie to these remotes - do not have any previous experience with using Remote 2 to fall back on.

The activity is showing as ON on the remote. Tapping it again only brings up the User Inerface. Pressing the X in the top right corner only brings me back to the “Lounge” page I launch from.

After searching this forum I found my answer - use the hard POWER button on the remote and then select the activity from the menu popup.

JohnF · August 13, 2025, 4:36pm

I have this same issue. I have created a single activity - Watch TV. I have created the ON sequence and the OFF sequence. I have placed this activity on my single remote page.

When I click this activity on the remote, it starts the devices just fine. And then it goes into the configured Activity user interface. All good. But there is no way to run the OFF sequence.

I have tried the power button like you suggested here but it does nothing.

Previously (I think in the previous version), when I tapped an activity, it popped out a slider where there was an option to “Turn activity ON” and another for “Turn Activity OFF”. Now that slider doesn’t pop out. Just runs the ON sequence and then goes into user interface.

Any suggestions would be greatly appreciated.

kennymc.c · August 13, 2025, 4:40pm

Have you mapped anything to the power button? This will overwrite the default command for this button which is turning the activity off. Just make sure you either have nothing mapped for short press or long press and the empty mapping will be used for the default function of that button.

JohnF · August 13, 2025, 4:51pm

Hi Kenny, thanks for the reply. I have nothing specifically mapped to the power button. In other words, I have never configured anything for the power button in any Activity or any other entity. I have confirmed this by double checkking all entity configs. Still the power button does nothing. (Of course if I press and hold it for a few seconds, it gives option to reboot or power down the remote itself…).

kennymc.c · August 13, 2025, 4:54pm

Are you pressing the power button when you’re inside an activity? Only there the button mappings are working.

JohnF · August 13, 2025, 4:55pm

Yes exactly. I tap the activity, it runs the ON sequence and goes to user interface on the screen. Then I press power button while in that activity, and it does nothing.

kennymc.c · August 13, 2025, 5:11pm

Can you post the core and user interface logs after you startet and tried to stop the activity? You’ll find them in Settings/Development/Logs. From the Services dropdown choose Core service and User interface App. Use the preformated text button here at the top first to post the logs.

JohnF · August 13, 2025, 5:28pm

2025-08-13 17:24:57.077679 +00:00	ui	INFO	uc.ui.input: RELEASE CONTROL BACK TO -> "MainContainer_QMLTYPE_236(0xaaaae8adcef0)"
2025-08-13 17:24:56.878176 +00:00	ui	WARN	uc.ui.resources: Empty ID passed to getIcon()
2025-08-13 17:24:56.874864 +00:00	ui	INFO	qml: Button control disabled for: QQuickContentItem(0xaaaae89b2db0, "QQuickPopupItem")
2025-08-13 17:24:55.391860 +00:00	ui	INFO	qml: Activity state changed to: Off
2025-08-13 17:24:55.367890 +00:00	core	NOTICE	Removed standby inhibitor: activity 'Watch TV' (off) (max 65s)
2025-08-13 17:24:55.367347 +00:00	core	NOTICE	[Watch TV] activity finished
2025-08-13 17:24:55.180375 +00:00	ui	INFO	qml: Current step changed: undefined
2025-08-13 17:24:55.178671 +00:00	ui	INFO	qml: Activity state changed to: Running
2025-08-13 17:24:55.176605 +00:00	core	NOTICE	[Watch TV] activity command: uc.main.629b46f5-2946-4f2b-8d79-198ca50a04c0:POWER_TOGGLE
2025-08-13 17:24:54.923669 +00:00	ui	INFO	qml: Current step changed: undefined
2025-08-13 17:24:54.921548 +00:00	ui	WARN	uc.ui.resources: Empty ID passed to getIcon()
2025-08-13 17:24:54.919736 +00:00	ui	INFO	qml: Activity state changed to: Running
2025-08-13 17:24:54.883414 +00:00	core	NOTICE	[Watch TV] activity command: uc.main.629b46f5-2946-4f2b-8d79-198ca50a04c0:POWER_TOGGLE
2025-08-13 17:24:54.712076 +00:00	ui	INFO	qml: Current step changed: undefined
2025-08-13 17:24:54.710188 +00:00	ui	INFO	qml: Activity state changed to: Running
2025-08-13 17:24:54.681988 +00:00	core	NOTICE	[Watch TV] activity delay: 200 ms
2025-08-13 17:24:54.569200 +00:00	ui	INFO	uc.ui.input: TAKE CONTROL FROM "MainContainer_QMLTYPE_236(0xaaaae8adcef0)" -> "QQuickContentItem(0xaaaae89b2db0, \"QQuickPopupItem\")"
2025-08-13 17:24:54.467923 +00:00	ui	INFO	qml: Current step changed: undefined
2025-08-13 17:24:54.466336 +00:00	ui	INFO	qml: Activity state changed to: Running
2025-08-13 17:24:54.457417 +00:00	core	NOTICE	[Watch TV] activity command: uc.main.d4d7785b-0d11-49ab-b854-bb6972f4f83d:POWER_TOGGLE
2025-08-13 17:24:54.378506 +00:00	ui	INFO	uc.ui.input: Key released: "POWER" "QQuickContentItem(0xaaaae89b2db0, \"QQuickPopupItem\")"
2025-08-13 17:24:54.360178 +00:00	ui	INFO	uc.ui.input: TAKE CONTROL FROM "MainContainer_QMLTYPE_236(0xaaaae8adcef0)" -> "QQuickContentItem(0xaaaae89b2db0, \"QQuickPopupItem\")"
2025-08-13 17:24:54.341357 +00:00	ui	INFO	qml: Button control enabled for: QQuickContentItem(0xaaaae89b2db0, "QQuickPopupItem")
2025-08-13 17:24:54.192598 +00:00	ui	INFO	qml: Current step changed: undefined
2025-08-13 17:24:54.189133 +00:00	ui	INFO	qml: Activity state changed to: Running
2025-08-13 17:24:54.177374 +00:00	core	NOTICE	[Watch TV] activity command: uc.main.d4d7785b-0d11-49ab-b854-bb6972f4f83d:POWER_TOGGLE
2025-08-13 17:24:54.176916 +00:00	core	NOTICE	Added standby inhibitor: activity 'Watch TV' (off) (max 65s)
2025-08-13 17:24:54.174162 +00:00	core	NOTICE	Started activity 'Watch TV' (uc.main.c65ee272-ab9f-49cb-8b9e-5c8019d643f5) with timeout of 60s
2025-08-13 17:24:54.149864 +00:00	ui	INFO	uc.ui.input: Key pressed: "POWER" "MainContainer_QMLTYPE_236(0xaaaae8adcef0)"
2025-08-13 17:24:54.144989 +00:00	ui	INFO	qml: Button control enabled for: MainContainer_QMLTYPE_236(0xaaaae8adcef0)
2025-08-13 17:24:34.820122 +00:00	ui	INFO	uc.ui.input: TAKE CONTROL FROM "MainContainer_QMLTYPE_236(0xaaaae8adcef0)" -> "Activity_QMLTYPE_244(0xaaaae9091740)"
2025-08-13 17:24:34.612463 +00:00	ui	INFO	qml: Button control enabled for: Activity_QMLTYPE_244(0xaaaae9091740)
2025-08-13 17:24:34.609200 +00:00	ui	INFO	qml: Setting up button mappings for activity: Watch TV
2025-08-13 17:24:34.516694 +00:00	ui	WARN	uc.ui.resources: Empty ID passed to getIcon()
2025-08-13 17:24:34.489489 +00:00	ui	WARN	qrc:/components/entities/activity/deviceclass/Activity.qml:649: TypeError: Cannot call method 'hasFeature' of null
2025-08-13 17:24:34.489202 +00:00	ui	WARN	qrc:/components/TouchSlider.qml:162: TypeError: Cannot read property 'name' of null
2025-08-13 17:24:34.488914 +00:00	ui	WARN	qrc:/components/TouchSlider.qml:149: TypeError: Cannot read property 'volume' of null
2025-08-13 17:24:34.488419 +00:00	ui	WARN	qrc:/components/TouchSlider.qml:120: TypeError: Cannot read property 'volume' of null
2025-08-13 17:24:34.478981 +00:00	ui	WARN	uc.ui.resources: Empty ID passed to getIcon()
2025-08-13 17:24:34.442279 +00:00	ui	INFO	uc.ui.input: RELEASE CONTROL BACK TO -> "MainContainer_QMLTYPE_236(0xaaaae8adcef0)"
2025-08-13 17:24:34.438197 +00:00	ui	WARN	uc.ui.resources: Empty ID passed to getIcon()
2025-08-13 17:24:34.387520 +00:00	ui	WARN	uc.ui.resources: Empty ID passed to getIcon()
2025-08-13 17:24:34.331628 +00:00	ui	WARN	uc.ui.resources: Empty ID passed to getIcon()
2025-08-13 17:24:34.212747 +00:00	ui	WARN	uc.ui.resources: Empty ID passed to getIcon()
2025-08-13 17:24:34.208382 +00:00	ui	INFO	qml: Button control disabled for: QQuickContentItem(0xaaaae89b2db0, "QQuickPopupItem")
2025-08-13 17:24:32.742288 +00:00	ui	WARN	qrc:/components/entities/activity/MediaComponent.qml:92:9: Unable to assign [undefined] to QString
2025-08-13 17:24:32.742175 +00:00	ui	WARN	qrc:/components/entities/activity/MediaComponent.qml:112: TypeError: Cannot read property 'hslLightness' of undefined
2025-08-13 17:24:32.742011 +00:00	ui	WARN	qrc:/components/entities/activity/MediaComponent.qml:221:13: Unable to assign [undefined] to QString
2025-08-13 17:24:32.741733 +00:00	ui	WARN	qrc:/components/entities/activity/MediaComponent.qml:231:9: Unable to assign [undefined] to QString
2025-08-13 17:24:32.740824 +00:00	ui	WARN	qrc:/components/entities/activity/MediaComponent.qml:314:25: Unable to assign null to QColor
2025-08-13 17:24:32.723478 +00:00	ui	WARN	qrc:/components/Page.qml:466: TypeError: Cannot call method 'toLowerCase' of undefined
2025-08-13 17:24:32.722622 +00:00	ui	WARN	uc.ui.resources: Empty ID passed to getIcon()
2025-08-13 17:24:32.721495 +00:00	ui	WARN	qrc:/components/Page.qml:491:41: Unable to assign [undefined] to QString
2025-08-13 17:24:32.718901 +00:00	ui	WARN	qrc:/components/entities/activity/MediaComponent.qml:92: TypeError: Cannot read property 'mediaImage' of null
2025-08-13 17:24:32.718274 +00:00	ui	WARN	uc.ui.resources: Empty ID passed to getIcon()
2025-08-13 17:24:32.717363 +00:00	ui	WARN	qrc:/components/entities/activity/MediaComponent.qml:112: TypeError: Cannot read property 'mediaImageColor' of null
2025-08-13 17:24:32.717066 +00:00	ui	WARN	qrc:/components/entities/activity/MediaComponent.qml:113: TypeError: Cannot read property 'state' of null
2025-08-13 17:24:32.713902 +00:00	ui	WARN	qrc:/components/entities/activity/MediaComponent.qml:221: TypeError: Cannot read property 'mediaTitle' of null
2025-08-13 17:24:32.713326 +00:00	ui	WARN	qrc:/components/entities/activity/MediaComponent.qml:231: TypeError: Cannot read property 'mediaArtist' of null
2025-08-13 17:24:32.713020 +00:00	ui	WARN	qrc:/components/entities/activity/MediaComponent.qml:249: TypeError: Cannot call method 'hasAllFeatures' of null
2025-08-13 17:24:32.712571 +00:00	ui	WARN	qrc:/components/entities/activity/MediaComponent.qml:254: TypeError: Cannot read property 'mediaPosition' of null
2025-08-13 17:24:32.712115 +00:00	ui	WARN	qrc:/components/entities/activity/MediaComponent.qml:262: TypeError: Cannot read property 'mediaDuration' of null
2025-08-13 17:24:32.711400 +00:00	ui	WARN	qrc:/components/entities/activity/MediaComponent.qml:314: TypeError: Cannot read property 'mediaImageColor' of null
2025-08-13 17:24:32.711102 +00:00	ui	WARN	qrc:/components/entities/activity/MediaComponent.qml:283: TypeError: Cannot read property 'mediaPosition' of null
2025-08-13 17:24:32.710702 +00:00	ui	WARN	qrc:/components/entities/activity/MediaComponent.qml:271: TypeError: Cannot call method 'hasFeature' of null
2025-08-13 17:24:32.693851 +00:00	ui	INFO	qml: Activity state changed to: On
2025-08-13 17:24:32.689927 +00:00	core	NOTICE	Removed standby inhibitor: activity 'Watch TV' (on) (max 65s)
2025-08-13 17:24:32.688482 +00:00	core	NOTICE	[Watch TV] activity finished
2025-08-13 17:24:32.464746 +00:00	ui	INFO	qml: Current step changed: undefined
2025-08-13 17:24:32.464007 +00:00	ui	INFO	qml: Activity state changed to: Running
2025-08-13 17:24:32.461564 +00:00	core	NOTICE	[Watch TV] activity command: uc.main.629b46f5-2946-4f2b-8d79-198ca50a04c0:POWER_TOGGLE
2025-08-13 17:24:32.222514 +00:00	ui	INFO	qml: Current step changed: undefined
2025-08-13 17:24:32.219777 +00:00	ui	WARN	uc.ui.resources: Empty ID passed to getIcon()
2025-08-13 17:24:32.218645 +00:00	ui	INFO	qml: Activity state changed to: Running
2025-08-13 17:24:32.189117 +00:00	core	NOTICE	[Watch TV] activity command: uc.main.629b46f5-2946-4f2b-8d79-198ca50a04c0:POWER_TOGGLE
2025-08-13 17:24:32.012196 +00:00	ui	INFO	qml: Current step changed: undefined
2025-08-13 17:24:32.005052 +00:00	ui	INFO	qml: Activity state changed to: Running
2025-08-13 17:24:31.988377 +00:00	core	NOTICE	[Watch TV] activity delay: 200 ms
2025-08-13 17:24:31.834563 +00:00	ui	INFO	uc.ui.input: TAKE CONTROL FROM "MainContainer_QMLTYPE_236(0xaaaae8adcef0)" -> "QQuickContentItem(0xaaaae89b2db0, \"QQuickPopupItem\")"
2025-08-13 17:24:31.680901 +00:00	ui	INFO	qml: Current step changed: undefined
2025-08-13 17:24:31.679592 +00:00	ui	INFO	qml: Activity state changed to: Running
2025-08-13 17:24:31.673628 +00:00	core	NOTICE	[Watch TV] activity command: uc.main.d4d7785b-0d11-49ab-b854-bb6972f4f83d:POWER_TOGGLE
2025-08-13 17:24:31.605579 +00:00	ui	INFO	qml: Button control enabled for: QQuickContentItem(0xaaaae89b2db0, "QQuickPopupItem")
2025-08-13 17:24:31.403310 +00:00	ui	INFO	qml: Current step changed: undefined
2025-08-13 17:24:31.398330 +00:00	ui	INFO	qml: Activity state changed to: Running
2025-08-13 17:24:31.386368 +00:00	core	NOTICE	[Watch TV] activity command: uc.main.d4d7785b-0d11-49ab-b854-bb6972f4f83d:POWER_TOGGLE
2025-08-13 17:24:31.385657 +00:00	core	NOTICE	Added standby inhibitor: activity 'Watch TV' (on) (max 65s)
2025-08-13 17:24:31.381509 +00:00	core	NOTICE	Started activity 'Watch TV' (uc.main.c65ee272-ab9f-49cb-8b9e-5c8019d643f5) with timeout of 60s
2025-08-13 17:24:14.392562 +00:00	core	NOTICE	Setting rgb button backlight to: (127, 127, 127)
2025-08-13 17:24:14.391367 +00:00	core	NOTICE	Enter normal mode: standby in 180s
2025-08-13 17:24:13.472079 +00:00	core	NOTICE	Setting rgb button backlight to: (0, 0, 0)
2025-08-13 17:24:13.470755 +00:00	core	NOTICE	Enter idle mode: standby in 150s
2025-08-13 17:23:55.141115 +00:00	core	NOTICE	Changed battery status: 96% Discharging, 4053mV, charger: false
2025-08-13 17:23:09.805592 +00:00	core	NOTICE	Setting rgb button backlight to: (127, 127, 127)
2025-08-13 17:23:09.804210 +00:00	core	NOTICE	Enter normal mode: standby in 180s
2025-08-13 17:22:59.472099 +00:00	core	NOTICE	Setting rgb button backlight to: (0, 0, 0)
2025-08-13 17:22:59.470671 +00:00	core	NOTICE	Enter idle mode: standby in 150s
2025-08-13 17:21:41.077206 +00:00	core	NOTICE	Setting rgb button backlight to: (127, 127, 127)
2025-08-13 17:21:41.075913 +00:00	core	NOTICE	Enter normal mode: standby in 180s
2025-08-13 17:21:32.470136 +00:00	core	NOTICE	Setting rgb button backlight to: (0, 0, 0)
2025-08-13 17:21:32.469662 +00:00	core	NOTICE	Enter idle mode: standby in 150s
2025-08-13 17:20:34.368342 +00:00	core	NOTICE	No session state has been found for a valid session key, creating a new empty session.
2025-08-13 17:20:34.347980 +00:00	core	NOTICE	No session state has been found for a valid session key, creating a new empty session.
2025-08-13 17:20:34.341498 +00:00	core	NOTICE	No session state has been found for a valid session key, creating a new empty session.
2025-08-13 17:20:34.301681 +00:00	core	NOTICE	No session state has been found for a valid session key, creating a new empty session.
2025-08-13 17:20:33.235427 +00:00	ui	INFO	uc.ui.input: TAKE CONTROL FROM "MainContainer_QMLTYPE_236(0xaaaae8adcef0)" -> "MainContainer_QMLTYPE_236(0xaaaae8adcef0)"
2025-08-13 17:20:33.218929 +00:00	ui	INFO	uc.ui.input: TAKE CONTROL FROM "MainContainer_QMLTYPE_236(0xaaaae8adcef0)" -> "MainContainer_QMLTYPE_236(0xaaaae8adcef0)"
2025-08-13 17:20:33.023994 +00:00	ui	INFO	qml: Button control enabled for: MainContainer_QMLTYPE_236(0xaaaae8adcef0)
2025-08-13 17:20:33.015037 +00:00	ui	WARN	qrc:/components/StatusBar.qml:387: TypeError: Cannot read property 'currentPage' of null
2025-08-13 17:20:33.014901 +00:00	ui	WARN	qrc:/components/StatusBar.qml:34: TypeError: Cannot read property 'currentPage' of null
2025-08-13 17:20:33.014691 +00:00	ui	WARN	qrc:/components/StatusBar.qml:19: TypeError: Cannot read property 'currentPage' of null
2025-08-13 17:20:33.014315 +00:00	ui	WARN	qrc:/components/StatusBar.qml:20: TypeError: Cannot read property 'currentPage' of null
2025-08-13 17:20:33.012578 +00:00	ui	INFO	qml: Button control enabled for: MainContainer_QMLTYPE_236(0xaaaae8adcef0)
2025-08-13 17:20:32.956643 +00:00	ui	WARN	uc.ui.resources: Empty ID passed to getIcon()
2025-08-13 17:20:32.850025 +00:00	ui	WARN	uc.ui.resources: Empty ID passed to getIcon()
2025-08-13 17:20:32.746536 +00:00	ui	WARN	uc.ui.resources: Empty ID passed to getIcon()
2025-08-13 17:20:32.639811 +00:00	ui	WARN	uc.ui.resources: Empty ID passed to getIcon()
2025-08-13 17:20:32.555472 +00:00	ui	WARN	uc.ui.resources: Invalid id format, missing ':' in ""
2025-08-13 17:20:32.552995 +00:00	ui	WARN	QQmlComponent: Cannot create new component instance before completing the previous
2025-08-13 17:20:32.236848 +00:00	ui	WARN	uc.ui.resources: Empty ID passed to getIcon()
2025-08-13 17:20:31.842085 +00:00	ui	WARN	uc.ui.resources: Empty ID passed to getIcon()
2025-08-13 17:20:31.652004 +00:00	ui	WARN	uc.app.i18n: Failed to remove translation
2025-08-13 17:20:31.154975 +00:00	ui	INFO	uc.ui.input: RELEASE CONTROL BACK TO -> "ProfileSwitch_QMLTYPE_121(0xaaaae87fd0f0)"
2025-08-13 17:20:30.976235 +00:00	core	NOTICE	Added standby inhibitor: charger
2025-08-13 17:20:30.973021 +00:00	core	NOTICE	Changed battery status: 97% Discharging, 3994mV, charger: false
2025-08-13 17:20:30.577278 +00:00	ui	WARN	Cannot find EGLConfig, returning null config
2025-08-13 17:20:30.495250 +00:00	ui	INFO	qml: Button control disabled for: ProfileAdd_QMLTYPE_104(0xaaaae89209e0)
2025-08-13 17:20:30.120850 +00:00	ui	WARN	uc.ui.resources: Empty ID passed to getIcon()
2025-08-13 17:20:29.681752 +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 85D075", version: "0.6.0" }
2025-08-13 17:20:29.671888 +00:00	core	NOTICE	[BT] Scan mode: discoverable=false, connectable=false
2025-08-13 17:20:29.501302 +00:00	core	NOTICE	Created Dock IR emitter: dock_id=UCD3-0CC8B0, name='UCD3-0CC8B0', model=UCD3, active=true, port_mask=0
2025-08-13 17:20:29.154899 +00:00	core	NOTICE	[UCD3-0CC8B0] SessionAuthenticated msg
2025-08-13 17:20:29.151134 +00:00	core	NOTICE	[UCD3-0CC8B0] Session state change: Authenticated
2025-08-13 17:20:29.094809 +00:00	core	NOTICE	[UCD3-0CC8B0] Resolved ucd3-0cc8b0.local: 192.168.36.197
2025-08-13 17:20:29.077676 +00:00	core	NOTICE	[UCD3-0CC8B0] Resolving: ucd3-0cc8b0.local
2025-08-13 17:20:29.073237 +00:00	core	NOTICE	[UCD3-0CC8B0] Connected to: ws://ucd3-0cc8b0.local/ws
2025-08-13 17:20:28.842573 +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-08-13 17:20:28.840341 +00:00	core	NOTICE	Connected to BT daemon: 127.0.0.1:13333
2025-08-13 17:20:28.839301 +00:00	core	NOTICE	Restarting BT daemon client, enabled=true
2025-08-13 17:20:28.822920 +00:00	core	WARN	[UCD3-0CC8B0] Can't handle dock TryReconnect command in state: Connecting
2025-08-13 17:20:28.822092 +00:00	core	WARN	[UCD3-0CC8B0] No transition for: state=Connecting, event=TryReconnect
2025-08-13 17:20:28.728531 +00:00	core	NOTICE	Ignoring connected event from WiFi driver, using operational state instead
2025-08-13 17:20:28.630579 +00:00	core	NOTICE	[UCD3-0CC8B0] WiFi connected: connecting dock
2025-08-13 17:20:28.630165 +00:00	core	NOTICE	WiFi interface is up and routable, sending connected event
2025-08-13 17:20:28.629914 +00:00	core	NOTICE	Network changed: link_name: wlan0, operational_state: routable, address_state: routable, ipv4_address_state: routable
2025-08-13 17:20:28.552408 +00:00	core	NOTICE	Network changed: link_name: wlan0, operational_state: degraded, carrier_state: carrier, online_state: online
2025-08-13 17:20:28.527 +00:00	core	NOTICE	Network changed: link_name: wlan0, operational_state: dormant, carrier_state: dormant
2025-08-13 17:20:27.989783 +00:00	core	NOTICE	[UCD3-0CC8B0] Reconnecting in: 844ms
2025-08-13 17:20:27.985861 +00:00	core	ERROR	[UCD3-0CC8B0] Error connecting to dock ws://ucd3-0cc8b0.local/ws: ServiceUnavailable("Failed to connect to host: Failed resolving hostname: failed to lookup address information: Temporary failure in name resolution")
2025-08-13 17:20:27.977073 +00:00	core	ERROR	Cannot connect to BT daemon: I/O error. Reconnecting in 862.662916ms
2025-08-13 17:20:27.976564 +00:00	core	NOTICE	Restarting BT daemon client, enabled=true
2025-08-13 17:20:27.315317 +00:00	core	NOTICE	[UCD3-0CC8B0] Reconnecting in: 650ms
2025-08-13 17:20:27.314742 +00:00	core	ERROR	[UCD3-0CC8B0] Error connecting to dock ws://ucd3-0cc8b0.local/ws: ServiceUnavailable("Failed to connect to host: Failed resolving hostname: failed to lookup address information: Temporary failure in name resolution")
2025-08-13 17:20:27.037650 +00:00	core	ERROR	Cannot connect to BT daemon: I/O error. Reconnecting in 930.729219ms
2025-08-13 17:20:27.036059 +00:00	core	NOTICE	Restarting BT daemon client, enabled=true
2025-08-13 17:20:26.925137 +00:00	core	NOTICE	WifiEvent: DISCONNECTED
2025-08-13 17:20:26.859933 +00:00	core	NOTICE	Network changed: link_name: wlan0, operational_state: unknown, carrier_state: unknown
2025-08-13 17:20:26.837685 +00:00	core	NOTICE	Network changed: link_name: wlan0, operational_state: dormant, carrier_state: dormant, online_state: offline
2025-08-13 17:20:26.821358 +00:00	core	NOTICE	[UCD3-0CC8B0] Reconnecting in: 500ms
2025-08-13 17:20:26.816872 +00:00	core	ERROR	[UCD3-0CC8B0] Error connecting to dock ws://ucd3-0cc8b0.local/ws: ServiceUnavailable("Failed to connect to host: Failed resolving hostname: failed to lookup address information: Temporary failure in name resolution")
2025-08-13 17:20:26.722034 +00:00	core	NOTICE	Not starting driver 'uc_roku_driver': no configured instances
2025-08-13 17:20:26.721899 +00:00	core	NOTICE	Not starting driver 'uc_denon_driver': no configured instances
2025-08-13 17:20:26.721745 +00:00	core	NOTICE	Not starting driver 'uc_gc_driver': no configured instances
2025-08-13 17:20:26.721567 +00:00	core	NOTICE	Not starting driver 'uc_bo_driver': no configured instances
2025-08-13 17:20:26.721170 +00:00	core	NOTICE	Not starting driver 'uc_androidtv_driver': no configured instances
2025-08-13 17:20:26.713902 +00:00	core	NOTICE	  uccore : PWD=/opt/uc/data ; USER=root ; COMMAND=/usr/bin/systemctl start btstack
2025-08-13 17:20:26.712091 +00:00	core	NOTICE	  uccore : PWD=/opt/uc/data ; USER=root ; COMMAND=/usr/bin/systemctl start wpa_supplicant
2025-08-13 17:20:26.700444 +00:00	core	NOTICE	  uccore : PWD=/opt/uc/data ; USER=root ; COMMAND=/usr/sbin/wl country CA
2025-08-13 17:20:26.698838 +00:00	core	NOTICE	  uccore : PWD=/opt/uc/data ; USER=root ; COMMAND=/usr/sbin/wl band b
2025-08-13 17:20:26.692740 +00:00	core	NOTICE	Not starting driver 'uc_appletv_driver': no configured instances
2025-08-13 17:20:26.679105 +00:00	core	NOTICE	Not starting driver 'uc_roon_driver': no configured instances
2025-08-13 17:20:26.667387 +00:00	core	NOTICE	Not starting driver 'hass': no configured instances
2025-08-13 17:20:26.661723 +00:00	core	NOTICE	Not starting driver 'uc_sonos_driver': no configured instances
2025-08-13 17:20:26.646161 +00:00	core	NOTICE	Not starting driver 'uc_hue_driver': no configured instances
2025-08-13 17:20:26.616373 +00:00	core	ERROR	Cannot connect to BT daemon: I/O error. Reconnecting in 420.534256ms
2025-08-13 17:20:26.596160 +00:00	core	NOTICE	Created Dock IR emitter: dock_id=UCD3-0CC8B0, name='UCD3-0CC8B0', model=UCD3, active=true, port_mask=0
2025-08-13 17:20:26.595944 +00:00	core	NOTICE	[UCD3-0CC8B0] Resolved ws url: ws://UCD3-0CC8B0.local:80/ws
2025-08-13 17:20:26.576106 +00:00	core	NOTICE	Execute system command: StartBluetooth
2025-08-13 17:20:26.568997 +00:00	core	NOTICE	Updating BT service configuration file, connections=1
2025-08-13 17:20:26.539667 +00:00	core	NOTICE	Execute system command: StartWifi
2025-08-13 17:20:26.536689 +00:00	core	NOTICE	Execute system command: EnableWoWLAN(false)
2025-08-13 17:20:26.535684 +00:00	core	NOTICE	Execute system command: SetWifiBand(B)
2025-08-13 17:20:26.527136 +00:00	core	NOTICE	WiFi interface is up and routable, sending connected event
2025-08-13 17:20:26.524180 +00:00	core	NOTICE	Feature flag enabled: routable_if_link. Using operational state 'routable' for WiFi connect events.
2025-08-13 17:20:26.506951 +00:00	core	NOTICE	Monitoring network link 'wlan0' for changes
2025-08-13 17:20:26.494379 +00:00	core	NOTICE	Setting rgb button backlight to: (127, 127, 127)
2025-08-13 17:20:26.474256 +00:00	core	NOTICE	Execute system command: SetWlCommand("country", "CA")
2025-08-13 17:20:26.468136 +00:00	core	NOTICE	Enter normal mode: standby in 180s
2025-08-13 17:20:26.192070 +00:00	core	NOTICE	LIRC device opened.
2025-08-13 17:20:26.190684 +00:00	core	NOTICE	starting service: "actix-web-service-127.0.0.1:9000", workers: 1, listening on: 127.0.0.1:9000
2025-08-13 17:20:26.190313 +00:00	core	NOTICE	Actix runtime found; starting in Actix runtime
2025-08-13 17:20:26.187401 +00:00	core	NOTICE	Feature flag enabled: internal_ir. Creating IR emitter for internal IR.
2025-08-13 17:20:26.119563 +00:00	core	NOTICE	Ignoring connected event from WiFi driver, using operational state instead
2025-08-13 17:20:26.093296 +00:00	core	NOTICE	Feature flag enabled: routable_if_link. Using operational state 'routable' for WiFi connect events.
2025-08-13 17:20:25.750564 +00:00	core	NOTICE	starting 1 workers
2025-08-13 17:20:25.410450 +00:00	core	NOTICE	Cleaning up downloaded system OTA updates <= 2.6.5
2025-08-13 17:20:25.403451 +00:00	core	NOTICE	Core-API listening on: 127.0.0.1:9000

kennymc.c · August 13, 2025, 5:47pm

At least the log show that the Watch TV activity has been turned off. Can you check if the activity is shown as off? Maybe it’s just the actvity ui that is not closed automatically

JohnF · August 13, 2025, 6:28pm

The activity does show as OFF after clicking the PWR button while in the activity. However, everything remains on, I guess due to missing or unreceived/untransmitted IR codes… Then when I tap the Watch TV activity (now showing as OFF), the activity runs the ON sequence again (since it’s in OFF state, but remember that everything is still ON). The devices of course then turn OFF. This of course does make sense since the commands are simple POWER_TOGGLE commands. No distinct ON or OFF commands. SO the ON and the OFF sequences are identical. Now the activity is in the ON state, but the devices are OFF! LOL

After a bit of further testing, it appears to be missing or unreliable IR transmissions from the Dock3, which is about 10 feet away from the equipment, free line of site, no obstructions. I even tried moving the dock and/or blaster closer and closer, or holding it up at eye leve to the devices…

I have also tried setting the entity (device) to just use the dock to transmit, and as well setting it to all devices to transmit. Plugged in the little IR blaster, as well as enabling the Remote 3 as an IR blaster itself also. Doesn’t seem to make any difference in the reliability and the behavior.

I doubled up the POWER_TOGGLE commands on the TV and the receiver for both ON and OFF sequences, and put a small delay in between the two devices just to make sure there aren’t too many IR beams bouncing around.

Now with the doubled up POWER_TOGGLE commands, tapping the activity on the remote “mostly” consistently turns on the devices. As for clicking the power button while in the activity, sometimes it works, and sometimes it doesn’t. Sometimes it will turn one device off but no the other. Sometimes it does nothing to either device. But the Activity does change to OFF. When I tap activity again it of course re-runs the ON sequence (because the activity did change to OFF. And remember that it is identical to the OFF sequence due to POWER_TOGGLE, not distinct ON and OFF commands). This of course then causes inconsitent states between what the remote says, and what state the devices are actually in – Remote now says Activity is ON, but devices are OFF… Oy…

All codes have been learned from the original remotes.

Wow, bit of a vicious circle. So the entire thing seems to be pointing to unreliable IR transmission performance, which then causes inconsitencies of state between remote and what is actually reality.

Sorry for the long post but I hope it is clear at least.

Any ideas or suggestions?

kennymc.c · August 13, 2025, 6:53pm

You could search for dedicated Power on/off comands maybe in the Global Caché database. Otherwise the main problem is indeed IR where signals may get lost. For me the blaster (round puck) works quite good im comparison to the Dock which only bounces signals to the top and a little to the front. Make sure the blaster is detected by the Dock. You need to connect it while the Dock is powered off.

JohnF · August 13, 2025, 7:11pm

Thank you for the help today kenny. I will do some further testing by changing to use the puck only. And try some other variations too. I will confirm that the puck is detected by the dock.
I’ll report back later today or tomorrow.

Slaids · August 14, 2025, 10:49am

I think your issue is the 11 feet distance, The IR transmission from just the dock is very poor and also when they state there must be direct line of site it needs to be absolute. The IRs on the bottom of the dock are impacted if the dock is on a table and the target device is lower. The IR beam appears to be very directional and narrow. The IR LEDS on top of the dock it appears only transmit upward. I have a post explaining the issues I am having. I can tell you that the positioning in this photo does not transmit to the player in the bottom right of the cabinet. I finally figured out it is because the table bounces the transmission straight across at table level which is above the player’s IR sensor. The IR blaster however does work even if placed along side the dock in this position. IR support does not appear to have been a design priority for the dock.

HarmonyFan · August 14, 2025, 12:27pm

I made a test with the transmitter of the remote itself and it worked even in 10 yard distance. I did not test the angle though.

Ralf

Slaids · August 14, 2025, 1:06pm

I haven’t done much with the remote as IR transmitter as I have fallen back to using the IR blaster placed on the edge of my cabinet with the dock on top of the cabinet and that works well (only because I have only one IR device). The blaster I think is the best option for IR if you can set up your positioning that way. The dock alone is not, in my experience so far, a viable option for controlling IR devices. In regard to using the remote my aim was to not have to point the remote at IR devices, given my other devices are via integrations and wifi. As I said it appears the dock alone as an IR transmitter is not a viable option unless you have a very specific layout that suits the limited transmission capabilities it has.

JohnF · August 14, 2025, 1:47pm

Thank you for the replies.
Slaids, I just read your other post, thanks for the info. It seems the issues are “mostly” due to IR. As for the missing IR commands like you mentioned, I haven’t done the camera trick to troubleshoot that yet. But given the experience so far, that seems to also add to the performance inconsistencies.

Kenny’s guideance was also helpful, pointing out that the blasters are not “plug and play”. They need to be plugged in BEFORE the dock is powered up. So that helped as well.

I have now relocared the dock and blaster as in the photo below:

The blaster is where the circle is. I was using the remote’s internal IR blaster too, but I have since turned that off so as not to introduce too many variables in the troubleshooting.

This setup appears to work faily well at the moment. Every so often a button press goes missing. Almost seems like it takes a click or a tap to get the remote to talk to the dock.

I have even managed to get my ARRIS VIP5662W Bell IPTV set top box to work. It uses the PRONTO code format for the IR commands, which seemingly can NOT be learned. You have to paste the codes in.

So here is a summary of what I have done:

Relocate dock and blaster as in the picture.
Turned off the remote’s IR.
Doubled up on the power toggle commands for the TV (the upper one) and the receiver (under the blaster) in both the ON nad OFF sequences for the activity. I did this because of what I mentioned earlier - that it seems it takes a tap/click/command or two for the remote to reconnect to the dock. I suspected this when the TV and the receiver would take turned to turn off and on! So the first command in the sequence went missing, but the second command worked. Bit of a strange behavior….
When creating an entity, in the main settings of that entity, I selected to use ALL outputs to blast the IR out.
I added some quick commands in the user interface of the activity, and of each device, in case a command is missed - such as a device didn’t get powered on/off, or an HDMI input didn’t get set properly.
TIP: Just to help others, remember that the user interface settings (touch screen configs) and button mappings that you configure inside of an activity only work when you are inside that activity or device.
TIP: After making a config change (especially when adding IR codes), give the remote a few minutes to update and settle down, especially if you get the “unknown network error occured” but it looks like the config still took. Maybe even go back in on the change you did and then exit it again.

I did successfully add the Android TV integration, but I am not sure how to interact with it fully just yet and need to play around with it more. It does successfully control my ChromeCast though. I have the new Google TV Streamer 4K as well, which I will play with next.

Slaids · August 14, 2025, 2:50pm

I assume your IR controlled device is where the blaster is sitting on top of? If so you should find that the consistency of IR commands is not an issue. The blaster is the only reliable method for IR control from my experience. I found that the missing trasmissions I saw using the android tablet to see the IR were misleading as in normal operation of the remote I didn’t see missing commands once I had the IR blaster in place. My experience with the Denon and Samsung TV integrations I’m using has been good. Denon is native and the Samsung is custom. The integrations appear to be very good, but I only have experience with the two.

JohnF · August 14, 2025, 4:40pm

Yes that is one of the IR devices (receiver). Then the are the two TV’s and the ARRIS VIP5662W 4K TV box as well. That’s the only devices that is PRONTO format. The rest are HEX. Plus of course the ChromeCast and soon the Google 4K TV Streamer, which are integrations.
I think I might try that trick with the last digit in the HEX format being the repeat, rather than having duplicate commands in the ON/OFF sequences. Should work for the HEX format, but no idea where it would be in the PRONTO format…

I’ll start playing around with integrations some more also. For now I’ll continue with what I have and keep learning!