DLNA Player and Media Render warning message

michael.l.nelson · July 16, 2019, 11:39pm

Broken code or working as intended...
I get this warning in my logs :
> sys:12019-07-16 06:45:01.203 pm warnReceived data from 192.168.1.36, no matching device found for 192.168.1.36, C0A80124:C676, 00226C88AEF6 or C0A80124.

sys:12019-07-16 06:45:01.176 pm warnReceived data from 192.168.1.36, no matching device found for 192.168.1.36, C0A80124:C675, 00226C88AEF6 or C0A80124.
sys:12019-07-16 06:45:00.713 pm warnReceived data from 192.168.1.22, no matching device found for 192.168.1.22, C0A80116:CA38, 00226C88C78A or C0A80116.
sys:12019-07-16 06:45:00.651 pm warnReceived data from 192.168.1.22, no matching device found for 192.168.1.22, C0A80116:CA37, 00226C88C78A or C0A80116.

The addresses stated line up with the Eufy speakers I use.

The warning is generated by the hub so I'm not sure there's even anything to be done. If anyone has any thoughts they will be appreciated.

mike.maxwell · July 17, 2019, 12:28am

It would seem that your speakers have taken on a different ip address...

michael.l.nelson · July 17, 2019, 12:55am

You would think that was it, I guess I should have pointed out that they have not. At least as far as my router is concerned. As soon as I set these up I reserved the address in my router.

The address matches in the device page too.

24 hex = 36 dec
16 hex = 22 dec

And the devices work for TTS and so-so as media players.

mike.maxwell · July 17, 2019, 12:59am

The port changed, or isn't correct.
Dni says c000, devices all say something different.

michael.l.nelson · July 17, 2019, 12:35pm

Yup, definitely the port causing the issue. Since it shows two ports per IP in the log I tried deleting the port information from the dni. The devices worked but the warnings became errors. So then I tried changing the dni to one of the address + ports from the log. Now I get two different port/warnings.

I've been assuming this is something with media render. These devices are also Alexa enabled speakers. Maybe that's the app I should be investigating.

mike.maxwell · July 17, 2019, 12:39pm

Well now they are using yet another set of ports...
I don't have any answers for you here.

michael.l.nelson · July 17, 2019, 5:10pm

Probably the Chinese army's back door trying to probe the hub thinking it's a server. /sarcasm

They're just warnings, I guess I'll deal with it with silent resentment and scathing looks whenever I look at the logs.

csteele · July 17, 2019, 5:19pm

I have always needed a name for that when I do it!! Perfect, well done.

cybrmage · August 1, 2019, 12:58am

These error have to do with the implementation of some DLNA Media Players....

What is happening is the the App discovers a player, and adds a device for it, using IP:PORT as the DeviceNetworkId...

When the HE receive data from a DLNA player, it tries to match it with the correct device... by matching the DeviceNetworkId against:

the IP:PORT of the device that sent the data
the MAC address of the device that sent the data
the IP address of the device that sent the data

If none of these three match a the DeviceNetworkId of an installed device, then the error is thrown...

The problem is... Many DLNA devices do NOT send data from the same port that is reported in the SSDP discovery response... So the device driver sends commands to IpAdress:49152, but the response data comes back from IpAddress:56789... and is dropped by the system...
(I have seen this behavior with an LG WebOS TV and a Jam Audio WiFi speaker)

So... I have been experimenting.... I modified the connect App and driver so that it uses the MAC address as the DeviceNetworkId... And the driver now receives all data sent from the player...

I'm still fighting with an issue that the parse routines do not parse the data from the LG TV properly... But that is a separate issue...

dman2306 · August 1, 2019, 2:44am

Any chance you can share your Mac address based version? My HEOS speakers exhibit the same behavior

cybrmage · August 1, 2019, 3:35am

I intend to share, after getting permission of the original author... and after I've had time to sort out the parsing routines...

cybrmage · August 2, 2019, 2:35am

Ok... I have the driver and app to a point that they no longer throw errors and seem to work well...

The files are available here: OLD VERSION REMOVED see THIS post.

When you initially upload the files to your HE, any existing DLNA devices you have will probably freak out and generate errors... this should be considered normal... You should then run the Mediarenderer (Connect) appand rediscover your devices. This will (should) regenerate your devices with their new DeviceNetworkID. If you have issues, you should delete the App (which will also delete the child devices) and add it again.

Major changes:

DLNA Device MAC address used as DeviceNetworkId (eliminates the sys:1 no matching device error
Captures and processes all data sent to HE by the DLNA device
Adds functions and adjustments to emulate/fix functions used in the original ST code that is not present in the HE
Fixes track data processing so that track data is available as events

Be aware that not all exposed functions/commands work with all DLNA devices...
IE: The "speak"/"playText" functions do not work (using the build in TTS engine) with an LG WebOS TV, but does work with a Jam Audio Rythm speaker. The correct commands are sent, but no speech is emited by the device. (This is due to the mp3 format produced by the built-in TTS engine being rejected by the WebOS TV)

If you find anything that is not right, let me know and i'll try to get it working.

aguileramekin · August 2, 2019, 11:04pm

cybrmage, I installed the Driver and the App.
The App discovered 4 devices:

3 Samsung TVs
1 WD TV Media Player

But (using the commands in the Device Screen) anything appear to work (volumen, play, OFF, ON, or similar actions)

Am I doing something wrong?

michael.l.nelson · August 3, 2019, 2:41am

Thank you. My Eufy speakers are doing TTS like champs without the logged errors. No more silent resentment or scathing looks at my log files.

StephenH · August 3, 2019, 3:05am

Would this DLNA player work with a Phorus PS5 speaker?

leeonestop · September 15, 2019, 2:05am

If it using DLNA don't see why not.

deanturner39 · October 11, 2019, 5:45pm

I just update mine to your version @cybrmage but getting the below error now any idea?
2019-10-11 18:44:00.120 errorjava.lang.NullPointerException: Cannot invoke method getAt() on null object on line 1015

deanturner39 · October 23, 2019, 3:29pm

well i did have working! after the the above post but noticed i wasn't getting voice on jam symphony now. checked logs getting below error.

2019-10-23 15:48:00.351 errorgroovy.lang.MissingMethodException: No signature of method: static java.lang.Math.round() is applicable for argument types: (com.hubitat.hub.domain.State) values: [com.hubitat.hub.domain.State(2019-10-20 11:53:00.461, null, level, null, 50, NUMBER)] Possible solutions: round(float), round(double), find(), rint(double), find(groovy.lang.Closure), random() on line 563 (playTextAndRestore)

deanturner39 · October 24, 2019, 6:37pm

gone back to old scottma61 versions and i've got voice announcements working again with no error, so don't know what the issue is.

Ryan780 · October 24, 2019, 6:48pm

The problem is the way that the volume is being set. I can see a problem in line 563 of the driver. Try replacing lines 562-564 with these lines and see if it works instead:

def setVolume(val) {
	mediaRendererAction("SetVolume", "RenderingControl", getDataValue("rccurl") , [InstanceID:0, Channel:"Master", DesiredVolume:val.toInteger()])
}