MagentaTV Binding for Deutsche Telekom MR 4xx

weralthoff · November 1, 2018, 3:35pm

No. When a recording is viewed on the MR200, the Play Info appears on the main unit (MR400).
Otherwise, the error message in the LOG is the same.

UdoJR · November 1, 2018, 3:43pm

Did it, but I think it is not doing anything, because I think the jar file at all is not recognized and I don’t get it why. The other three are loading w/o problem, also when I remove them and put them back, while running openHAB


openhab> bundle:start org.openhab.binding.entertaintv
Error executing command: No matching bundles

Same here, the binding is not available at all.

What I tried so far:

downloaded the new version of entertaintv from tonight
deleted the openHab caches
restart raspberry
copied new snapshot into /usr/share/openhab2/addons/

Checked log file, nothing, checked with bundle:list, it is still not available.

Do you use OpenHAB 2.3? Or 2.4?
Must their be a *.cfg file before? Read nothing about it in the documentation, but just to be sure.
Does someone know which packet try to load the binding, that I can put the log level up for it?

Thanks for all your help.

UdoJR · November 1, 2018, 3:45pm

Mmm ok, thought it works like the Android EntertainRC App, which worked for my old receivers too.

markus7017 · November 1, 2018, 3:50pm

I’m using OH 2.3 on the Pi and 2.4 on the macOS Dev system; maybe you need to reset the OH cache

markus7017 · November 1, 2018, 4:08pm

fyi: the binding for new has a problem to deal with more than one MR / thing. I’m awaiting logs to analyse

markus7017 · November 1, 2018, 4:11pm

clearing the OH cache:

please note: reatarting OH could take some minutes after cache was clears

markus7017 · November 1, 2018, 4:17pm

please try with a MR200 only setup (currently more then one thing creates conflicts).

open OH console and enter log:set TRACE org.openhab.binding.entertaintv
restart OH
when things gets discoverd you should see messages like EntertainTV: Device Discovered x - y

I need to model name to add this to the discover process (couls differ from MR200)

weralthoff · November 1, 2018, 4:45pm

Is that what you need

2018-11-01 17:34:22.069 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: Synology - DS213j
2018-11-01 17:34:22.070 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: Synology - DS213j
2018-11-01 17:34:22.368 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: Samsung Electronics - UE40F6400
2018-11-01 17:34:22.377 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: Samsung Electronics - UE40F6400
2018-11-01 17:34:22.393 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: Royal Philips Electronics - Philips hue bridge 2015
2018-11-01 17:34:22.846 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: Huawei Technologies Co.,Ltd - dmr_tpb
2018-11-01 17:34:22.847 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: Samsung Electronics - UE40F6400
2018-11-01 17:34:23.467 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: Huawei Technologies Co.,Ltd - dmr_tpb
2018-11-01 17:34:23.497 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: Samsung Electronics - UE40F6400
2018-11-01 17:34:23.808 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: Sonos, Inc. - Sonos Play:5
2018-11-01 17:34:24.280 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: Sonos, Inc. - Sonos Play:5
2018-11-01 17:34:24.355 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: Sonos, Inc. - Sonos Play:5
2018-11-01 17:34:24.474 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: Huawei Technologies Co.,Ltd - dms_tpb
2018-11-01 17:34:24.586 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: Sonos, Inc. - Sonos Play:5
2018-11-01 17:34:24.660 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: AVM Berlin - FRITZ!Box Fon WLAN 7390
2018-11-01 17:34:24.662 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: AVM Berlin - FRITZ!Box Fon WLAN 7390
2018-11-01 17:34:25.027 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: AVM Berlin - FRITZ!Box Fon WLAN 7390
2018-11-01 17:34:25.137 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: AVM Berlin - FRITZ!Box Fon WLAN 7390
2018-11-01 17:34:25.141 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: AVM Berlin - FRITZ!Box Fon WLAN 7390
2018-11-01 17:34:25.539 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: Huawei Technologies Co.,Ltd - dms_tpb

markus7017 · November 1, 2018, 5:21pm

ok, I see
dms_tpb - this is the MR400
dmr_tpb - this should be the MR200

Model is added. I need to complete some testing, expect a new build within the next hour.

weralthoff · November 1, 2018, 5:42pm

in your “show properties menu” they both have the same name.
Namely dmr_tpb

markus7017 · November 1, 2018, 5:54pm

ok, i see that both report dms_tpr and dmr_tpr
yoi should get a thing
does it get initialized? does the thing gets online?
how does the log look like?

weralthoff · November 1, 2018, 6:03pm

Both are online.
Here is a new LOG.
At the first trace I had activated as desired only the THING of the MR200

org.openhab.binding.entertaintv
2018-11-01 17:34:15.235 [DEBUG] [very.EntertainTVDiscoveryParticipant] - EntertainTV: HandlerFactory bound to EntertainTVDiscoveryParticipant
2018-11-01 17:34:15.236 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Activate UpnpDiscovery, configurarion (servicesentertaintv.cfg):
2018-11-01 17:34:22.069 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: Synology - DS213j
2018-11-01 17:34:22.070 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: Synology - DS213j
2018-11-01 17:34:22.368 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: Samsung Electronics - UE40F6400
2018-11-01 17:34:22.377 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: Samsung Electronics - UE40F6400
2018-11-01 17:34:22.393 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: Royal Philips Electronics - Philips hue bridge 2015
2018-11-01 17:34:22.846 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: Huawei Technologies Co.,Ltd - dmr_tpb
2018-11-01 17:34:22.847 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: Samsung Electronics - UE40F6400
2018-11-01 17:34:23.467 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: Huawei Technologies Co.,Ltd - dmr_tpb
2018-11-01 17:34:23.497 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: Samsung Electronics - UE40F6400
2018-11-01 17:34:23.808 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: Sonos, Inc. - Sonos Play:5
2018-11-01 17:34:24.280 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: Sonos, Inc. - Sonos Play:5
2018-11-01 17:34:24.355 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: Sonos, Inc. - Sonos Play:5
2018-11-01 17:34:24.474 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: Huawei Technologies Co.,Ltd - dms_tpb
2018-11-01 17:34:24.475 [DEBUG] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Discovered an EntertainTV Receiver ‘DMS_172.17.2.153’, UDN: ‘bb5e21ce-2222-11b2-f918-AC6FBB3A0B98’, Model dms_tpb.1.1
2018-11-01 17:34:24.475 [DEBUG] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Create Thing for device ‘DMS_172.17.2.153’ with UDN ‘bb5e21ce-2222-11b2-f918-AC6FBB3A0B98, Model’dms_tpb’
2018-11-01 17:34:24.586 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: Sonos, Inc. - Sonos Play:5
2018-11-01 17:34:24.660 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: AVM Berlin - FRITZ!Box Fon WLAN 7390
2018-11-01 17:34:24.662 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: AVM Berlin - FRITZ!Box Fon WLAN 7390
2018-11-01 17:34:25.027 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: AVM Berlin - FRITZ!Box Fon WLAN 7390
2018-11-01 17:34:25.137 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: AVM Berlin - FRITZ!Box Fon WLAN 7390
2018-11-01 17:34:25.141 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: AVM Berlin - FRITZ!Box Fon WLAN 7390
2018-11-01 17:34:25.539 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: Huawei Technologies Co.,Ltd - dms_tpb
2018-11-01 17:34:25.540 [DEBUG] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Discovered an EntertainTV Receiver ‘DMS_172.17.2.152’, UDN: ‘bb5e21ce-2222-11b2-f918-AC6FBB3E1151’, Model dms_tpb.1.1

markus7017 · November 1, 2018, 6:08pm

please try first onl with the MR200. the binding does currentl don’snsupport more than 1 thing (to be analyzed).
remove the mr400 and restart oh
leave the mr400 in the inbox if it gets re-discovered
then check if thing is online
try to send some keys (eg channel-up)

weralthoff · November 1, 2018, 6:56pm

OK. Only the MR200 is online. Have been with the remote control some commands.

2018-11-01 19:39:36.657 [TRACE] [ertaintv.internal.EntertainTVNetwork] - EntertainTVNetwork: POST ’ s:encodingStyle=“http://schemas.xmlsoap.org/soap/encoding/”><s:Body>
2018-11-01 19:39:36.690 [TRACE] [tv.internal.EntertainTVNotifyServlet] - EntertainTVServlet: Reqeust from 172.17.2.153:45839/entertaintv/notify (172.17.2.153, HTTP/1.1)
2018-11-01 19:39:36.691 [TRACE] [tv.internal.EntertainTVNotifyServlet] - EntertainTV.Notify: Pairing code ‘B773A113’ received for deviceID ‘C31289A920EB3FB5A22FD2CB6C5CF4AD’
2018-11-01 19:39:37.962 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: Synology - DS213j
2018-11-01 19:39:37.963 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: Synology - DS213j
2018-11-01 19:39:38.268 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: Royal Philips Electronics - Philips hue bridge 2015
2018-11-01 19:39:38.489 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: Samsung Electronics - UE40F6400
2018-11-01 19:39:38.533 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: Samsung Electronics - UE40F6400
2018-11-01 19:39:38.597 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: Samsung Electronics - UE40F6400
2018-11-01 19:39:38.904 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: Samsung Electronics - UE40F6400
2018-11-01 19:39:39.130 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: AVM Berlin - FRITZ!Box Fon WLAN 7390
2018-11-01 19:39:39.131 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: AVM Berlin - FRITZ!Box Fon WLAN 7390
2018-11-01 19:39:39.844 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: Sonos, Inc. - Sonos Play:5
2018-11-01 19:39:40.072 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: Sonos, Inc. - Sonos Play:5
2018-11-01 19:39:40.154 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: Huawei Technologies Co.,Ltd - dmr_tpb
2018-11-01 19:39:40.207 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: Sonos, Inc. - Sonos Play:5
2018-11-01 19:39:40.573 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: Huawei Technologies Co.,Ltd - dmr_tpb
2018-11-01 19:39:40.629 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: Sonos, Inc. - Sonos Play:5
2018-11-01 19:39:40.635 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: Huawei Technologies Co.,Ltd - dms_tpb
2018-11-01 19:39:40.970 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: Huawei Technologies Co.,Ltd - dms_tpb
2018-11-01 19:39:41.033 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: AVM Berlin - FRITZ!Box Fon WLAN 7390
2018-11-01 19:39:41.081 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: AVM Berlin - FRITZ!Box Fon WLAN 7390
2018-11-01 19:39:41.087 [TRACE] [very.EntertainTVDiscoveryParticipant] - EntertainTV: Device discovered: AVM Berlin - FRITZ!Box Fon WLAN 7390

018-11-01 19:48:09.129 [TRACE] [tv.internal.EntertainTVNotifyServlet] - EntertainTVServlet: Reqeust from 172.17.2.153:47284/entertaintv/notify (172.17.2.153, HTTP/1.1)
2018-11-01 19:48:09.130 [TRACE] [tv.internal.EntertainTVNotifyServlet] - EntertainTV.Notify: STB status:
2018-11-01 19:48:09.931 [TRACE] [tv.internal.EntertainTVNotifyServlet] - EntertainTVServlet: Reqeust from 172.17.2.153:47286/entertaintv/notify (172.17.2.153, HTTP/1.1)
2018-11-01 19:48:09.932 [TRACE] [tv.internal.EntertainTVNotifyServlet] - EntertainTV.Notify: STB status:
2018-11-01 19:48:10.013 [TRACE] [tv.internal.EntertainTVNotifyServlet] - EntertainTVServlet: Reqeust from 172.17.2.153:47289/entertaintv/notify (172.17.2.153, HTTP/1.1)
2018-11-01 19:48:10.014 [TRACE] [tv.internal.EntertainTVNotifyServlet] - EntertainTV.Notify: STB status:
2018-11-01 19:48:13.223 [TRACE] [tv.internal.EntertainTVNotifyServlet] - EntertainTVServlet: Reqeust from 172.17.2.153:47301/entertaintv/notify (172.17.2.153, HTTP/1.1)
2018-11-01 19:48:13.224 [TRACE] [tv.internal.EntertainTVNotifyServlet] - EntertainTV.Notify: STB status:
2018-11-01 19:48:13.248 [TRACE] [tv.internal.EntertainTVNotifyServlet] - EntertainTVServlet: Reqeust from 172.17.2.153:47304/entertaintv/notify (172.17.2.153, HTTP/1.1)
2018-11-01 19:48:13.248 [TRACE] [tv.internal.EntertainTVNotifyServlet] - EntertainTV.Notify: STB status:
2018-11-01 19:48:31.413 [TRACE] [tv.internal.EntertainTVNotifyServlet] - EntertainTVServlet: Reqeust from 172.17.2.153:47350/entertaintv/notify (172.17.2.153, HTTP/1.1)
2018-11-01 19:48:31.414 [TRACE] [tv.internal.EntertainTVNotifyServlet] - EntertainTV.Notify: STB status:
2018-11-01 19:48:31.517 [TRACE] [tv.internal.EntertainTVNotifyServlet] - EntertainTVServlet: Reqeust from 172.17.2.153:47353/entertaintv/notify (172.17.2.153, HTTP/1.1)
2018-11-01 19:48:31.519 [TRACE] [tv.internal.EntertainTVNotifyServlet] - EntertainTV.Notify: STB status:

018-11-01 19:43:18.079 [INFO ] [ertaintv.internal.EntertainTVControl] - EntertainTVControl: Send Key ‘VOLDOWN’ (keyCode=‘0x0104’)
2018-11-01 19:43:18.079 [TRACE] [ertaintv.internal.EntertainTVControl] - EntertainTV: sendKey keyCode=‘0x0104’, terminalid=‘C31289A920EB3FB5A22FD2CB6C5CF4AD’, pairingCode=‘B773A113’, verificationCode=‘56015BE7F069DE67A54626F4C6ABFB99’, userId=F596BE6D59771930308A9F5D4879DB85’
2018-11-01 19:43:18.943 [INFO ] [ertaintv.internal.EntertainTVControl] - EntertainTVControl: Send Key ‘VOLDOWN’ (keyCode=‘0x0104’)
2018-11-01 19:43:18.944 [TRACE] [ertaintv.internal.EntertainTVControl] - EntertainTV: sendKey keyCode=‘0x0104’, terminalid=‘C31289A920EB3FB5A22FD2CB6C5CF4AD’, pairingCode=‘B773A113’, verificationCode=‘56015BE7F069DE67A54626F4C6ABFB99’, userId=F596BE6D59771930308A9F5D4879DB85’
2018-11-01 19:43:23.352 [INFO ] [ertaintv.internal.EntertainTVControl] - EntertainTVControl: Send Key ‘EPG’ (keyCode=‘0x0111’)
2018-11-01 19:43:23.352 [TRACE] [ertaintv.internal.EntertainTVControl] - EntertainTV: sendKey keyCode=‘0x0111’, terminalid=‘C31289A920EB3FB5A22FD2CB6C5CF4AD’, pairingCode=‘B773A113’, verificationCode=‘56015BE7F069DE67A54626F4C6ABFB99’, userId=F596BE6D59771930308A9F5D4879DB85’
2018-11-01 19:45:36.570 [TRACE] [ertaintv.internal.EntertainTVNetwork] - EntertainTVNetwork: Sending data to ‘172.17.2.153:49152’: 'SUBSCRIBE /upnp/service/X-CTC_RemotePairing/Event HTTP/1.1
2018-11-01 19:50:37.070 [TRACE] [ertaintv.internal.EntertainTVNetwork] - EntertainTVNetwork: Sending data to ‘172.17.2.153:49152’: 'SUBSCRIBE /upnp/service/X-CTC_RemotePairing/Event HTTP/1.1
2018-11-01 19:50:37.580 [INFO ] [ertaintv.internal.EntertainTVControl] - EntertainTVControl: Send Pairing Request (firendlyName=‘PAD:openHAB’, deviceID=‘C31289A920EB3FB5A22FD2CB6C5CF4AD’, userID=‘F596BE6D59771930308A9F5D4879DB85’)

markus7017 · November 1, 2018, 7:06pm

an updated build is online
https://github.com/markus7017/org.openhab.binding.entertaintv/blob/beta1/target/org.openhab.binding.entertaintv-2.4.0-SNAPSHOT.jar

json fix for mr201
set User-Agent on http POSTs

UdoJR · November 1, 2018, 8:29pm

As mentioned in my previous post under What I tried so far I already cleared the openHAB cache.

Any other idea?

hmerk · November 1, 2018, 9:09pm

As I wrote earlier, you can not use this Binding with Media Receivers other than 4xx series. Communication protocol with the old receiver is completely different.
AFAIK, EntertainRC app does not support MR4xx series.

weralthoff · November 1, 2018, 10:14pm

Great, looks a lot better.
Unfortunately, I still can not switch anything.

markus7017 · November 1, 2018, 11:46pm

We still have a problem with the MR400 and I also think MR200. From the trace the pairing looks good, but we noticed that the MR400 doesn’t display a connected message when the binding was started, whereas it does when the App connects. So something must be wrong at the end of pairing. Therefore the subsequent SendKey are sent, but not executed,

UdoJR · November 2, 2018, 2:01am

Ahhh got it, ok, thank you.