@11194
So I created a basic Debian 11.2 VM, installed Docker, and started openhab (3.2.0). I did create the user openhab first.
Added the required feature:install openhab-transport-upnp and dropped my samsungtv binding into the addons folder (directly from the marketplace link).
Watching the logs, everything works normally, on both my old Samsung TV (2012), and my new Samsung TV (2021).
Here is the log from the openhab instance running in the docker container on my Debian 11.2 VM:
2022-01-31 15:46:07.303 [DEBUG] [tv.internal.handler.SamsungTvHandler] - 192.168.100.73: TV is Offline
...
... Turn TV on
...
2022-01-31 15:46:32.050 [DEBUG] [tv.internal.handler.SamsungTvHandler] - 192.168.100.73: remoteDeviceAdded: MediaRenderer, http://192.168.100.73:9197/dmr, upnpUDN=ea645e34-d3dd-4b9b-a246-e2947f8973d6
2022-01-31 15:46:32.050 [DEBUG] [covery.SamsungTvDiscoveryParticipant] - Retrieved Thing UID for a Samsung TV 'Samsung TV' model 'QN55LS03AAFXZC' thing with UDN 'ea645e34-d3dd-4b9b-a246-e2947f8973d6'
2022-01-31 15:46:32.050 [DEBUG] [tv.internal.handler.SamsungTvHandler] - 192.168.100.73: Check and create missing services
2022-01-31 15:46:32.050 [DEBUG] [covery.SamsungTvDiscoveryParticipant] - Created a DiscoveryResult for device 'QN55LS03AAFXZC' with UDN 'ea645e34-d3dd-4b9b-a246-e2947f8973d6' and properties: {hostName=192.168.100.73}
2022-01-31 15:46:32.050 [DEBUG] [nternal.service.MediaRendererService] - 192.168.100.73: Creating a Samsung TV MediaRenderer service
2022-01-31 15:46:32.051 [DEBUG] [tv.internal.handler.SamsungTvHandler] - 192.168.100.73: Started service for: QN55LS03AAFXZC, MediaRenderer (ea645e34-d3dd-4b9b-a246-e2947f8973d6)
2022-01-31 15:46:32.051 [DEBUG] [rnal.service.RemoteControllerService] - 192.168.100.73: Creating a Samsung TV RemoteController service: is UPNP:false
2022-01-31 15:46:32.056 [TRACE] [l.protocol.RemoteControllerWebSocket] - 192.168.100.73: openConnection()
2022-01-31 15:46:32.056 [DEBUG] [l.protocol.RemoteControllerWebSocket] - 192.168.100.73: RemoteControllerWebSocket start Client
2022-01-31 15:46:32.057 [TRACE] [l.protocol.RemoteControllerWebSocket] - 192.168.100.73: WebSocketClient starting
2022-01-31 15:46:32.063 [TRACE] [l.protocol.RemoteControllerWebSocket] - 192.168.100.73: WebSocketClient started
2022-01-31 15:46:32.063 [TRACE] [l.protocol.RemoteControllerWebSocket] - 192.168.100.73: connectWebSockets()
2022-01-31 15:46:32.064 [DEBUG] [ngtv.internal.protocol.WebSocketBase] - 192.168.100.73: WebSocketRemote connecting to: wss://192.168.100.73:8002/api/v2/channels/samsung.remote.control?name=b3BlbkhBQg==&token=15829348
... normal startup
I did have to accept the remote connection on the TV, otherwise commands to change volume/power etc don’t work, but that’s normal.
I didn’t have to do anything else. The TV’s were auto discovered, appeared in the inbox (without having to search), and when added, configured themselves properly. I had to accept the pop-up message on the TV, and link some channels to test volume/power/mute etc. But everything just worked. I turned the TV on and off several times, but still with no issues.
This is my docker run script:
docker run \
--name openhab \
--net=host \
-v /etc/localtime:/etc/localtime:ro \
-v /etc/timezone:/etc/timezone:ro \
-v /opt/openhab/addons:/openhab/addons \
-v /opt/openhab/conf:/openhab/conf \
-v /opt/openhab/userdata:/openhab/userdata \
-e "EXTRA_JAVA_OPTS=-Duser.timezone=America/Toronto" \
-d \
--restart=always \
openhab/openhab
this is from the OH console list command:
238 │ Active │ 80 │ 2.6.0 │ JUPnP Library
239 │ Active │ 80 │ 3.2.0 │ openHAB Core :: Bundles :: Configuration UPnP Discovery
240 │ Active │ 80 │ 3.2.0 │ openHAB Core :: Bundles :: UPnP Transport
241 │ Active │ 80 │ 3.3.0.202201061617 │ openHAB Add-ons :: Bundles :: SamsungTV Binding
So unfortunately this sheds no light on the problems you are seeing. It must be something specific to your configuration.
What other bindings do you have installed? any unusual configurations?
