Did you guys find out what is going on in this case? I am facing the same situation, the binding gets stuck
while “Initializing”, but from what I can see there are no upstream problems. The binding is loaded, the MediaReceiver thing gets detected, the “login” was done and there is a username reported in the thing.
it‘s pure Java so should run. There might be a problem with detecting the local ip address. Did you selected the default ip interface in the OH system settings?
Open PaperUI -> Configuration. Under Network Settings you’ll find the option to select the default network interface. The binding needs to detect the local IP address to reach the receiver to generate a callback link receiving the Pairing response.
Depending von the environment this may fail (Java is a little bit inconsistent how this works on different platforms and nobody verified the Synology environment so far. The preferred handling is to get the local IP from the OH system setting. If this is not successful the binding will try to different ways.
If you see a message like
TelekomTV.Network: Local IP address=‘x.x.x.x’, Local MAC address = ‘xx:xx:xx:xx:xx:xx
it’s all good and couldn’t be the problem,
Dieter send me another log and it might be a timing issue, because I see that the pairing request is send first before the Notification handler gets startet.
But I do not see a message that looks like the one you mentioned, “…Local IP address=‘x.x.x.x’, ….”.
Nevertheless the device gets discovered (“TelekomTV: Discovered an Telekom Media Receiver…” followed by
“TelekomTV: Create Thing for device…”) and then almost immediately “TelekomTV.Factory: Unable to process discovered device,…, null (class java.lang.NullPointerException)”
"*Unable to process discovered device, UDN=’ means that an exception happened
I see the message in your post, but not in the log, so it can’t be the complete log
stop OH and remove the bundle from the addon folder
start OH, wait until is fully initialized
empty the openhab.log (not deleting it)
copy the bundle to the addons folder -> this will cause the bundle to load
wait 5 min
cut out relevant section from the logfile and post it here
If we are able to reproduce it, I could add some additional debug messages to narrow the problem.
This is how this log was generated. I only put the two lines that I thought to be interesting on top. So the log at the end plus the two lines that I highlighted are the full log.
Maybe we switch to more direct conversation.
I had a look at the code as well. There should really be some more debugging statements in order to identify which part of information could not be dectected during the initialisation. I would be more than happy if I could help finding the problem and support my local open source developer .