UdoJR
(Udo Weber)
October 31, 2018, 8:31pm
183
The permission are the same as for the amazonechocontrol
-rw-rw-r-- 1 openhabian openhabian 72929 Oct 18 16:37 org.eclipse.smarthome.binding.bosesoundtouch-0.10.0-SNAPSHOT.jar
-rw-r--r-- 1 openhabian openhabian 458251 Oct 21 00:41 org.openhab.binding.amazonechocontrol_2.4.0.201808261949.jar
-rw-r--r-- 1 openhabian openhabian 53183 Oct 31 11:35 org.openhab.binding.entertaintv-2.4.0-SNAPSHOT.jar
-rw-rw-r-- 1 openhabian openhabian 49992 Oct 18 16:37 org.openhab.binding.network-2.4.0-SNAPSHOT.jar
-rw-rw-r-- 1 openhab openhab 70 May 28 10:33 README
But the binding is not loaded.
Checked it in karaf console with
bundle:list | grep entertain
bundle:list | grep tv
bundle:list | grep telekom
bundle:list | grep magenta
...
also with a first capital letterā¦ what is the name of the EntertainTV/MagentaTV binding in the bundle list by the way?
ibot1989
(Tobias)
October 31, 2018, 8:37pm
184
At the moment, the Binding is in the bundle:list:
227 ā Active ā 80 ā 2.4.0.201810311857 ā EntertainTV Binding
UdoJR
(Udo Weber)
October 31, 2018, 8:40pm
185
Thanks, then it is not loading at all
ibot1989
(Tobias)
October 31, 2018, 8:45pm
186
Is this the content of /usr/share/openhab2/addons/ ?
You have restart OpenHAB?
UdoJR
(Udo Weber)
October 31, 2018, 9:49pm
187
Exactly, just to show permission are right.
And yes I restarted the openHab service w/o success and afterwards the raspberry w/o success also.
markus7017
(Markus Michels)
October 31, 2018, 11:46pm
188
enter log:set TRACE org.openhab.binding.entertaintv innthe console
try bundle:start org.openhab.binding.entertaintv, maybe a dependecy is missing.
you could also try
open the OH console, enter log:tail
delete the jar from the addons folder
download the lagest one (I updated last night)
cop the jar into addons while viewing the log
within 10s you should see that the bundle gets started
once the bundle gets loaded I need the UPnP model numbers from the logfile so I could add those to the discovery process.
hmerk
(Hans-Jƶrg Merk)
November 1, 2018, 8:20am
189
If You are still Using MR300 / MR102B, You are not Using the actual EntertainTV/MagentaTV (aka NGTV) but the old āEntertainā, therefore you canāt use this Binding.
weralthoff
(W. Althoff)
November 1, 2018, 12:37pm
190
Hallo
What is the problem here.
I can not switch anything.
and the only thing that is displayed is when the recorder is recording a recording.
markus7017
(Markus Michels)
November 1, 2018, 2:45pm
191
that problem will be fixed tonight. depending on the MR model the JSON format is slightly different, MR401:channel_num is a string, MR201: channel num is an int
now Iām checking for string and otherwise use getInt()
which model are you using?
weralthoff
(W. Althoff)
November 1, 2018, 3:09pm
193
I have an MR400 and as a second device an MR200
excuse my short sentences, but my English is not so good
markus7017
(Markus Michels)
November 1, 2018, 3:22pm
194
we still have problems with the MR400, Iām working with @ibot1989 on this.
does the MR200 works?
weralthoff
(W. Althoff)
November 1, 2018, 3:35pm
195
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
(Udo Weber)
November 1, 2018, 3:43pm
196
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
(Udo Weber)
November 1, 2018, 3:45pm
197
Mmm ok, thought it works like the Android EntertainRC App, which worked for my old receivers too.
markus7017
(Markus Michels)
November 1, 2018, 3:50pm
198
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
(Markus Michels)
November 1, 2018, 4:08pm
199
fyi: the binding for new has a problem to deal with more than one MR / thing. Iām awaiting logs to analyse
markus7017
(Markus Michels)
November 1, 2018, 4:11pm
200
clearing the OH cache:
Often when one encounters a problem with OH, particularly after an update, OH will refuse to run or certain parts of OH stop working. Some reported errors include:
500 or 404 errors when accessing the UIs
lots of exceptions from Jetty or other core components in openhab.log
OH refuses to start at all
The first step in debugging the problem is to clear the tmp and cache.
Installed OH
If you are running an installed OH (openHABian, installed using apt or yum):
openhab-cli stop
openhab-clā¦
please note: reatarting OH could take some minutes after cache was clears
markus7017
(Markus Michels)
November 1, 2018, 4:17pm
201
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
(W. Althoff)
November 1, 2018, 4:45pm
202
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
(Markus Michels)
November 1, 2018, 5:21pm
203
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.