On one side, I have the Sonos plugin with its D_Sonos1.json and D_Sonos1.js files.
On the other side, I have my DLNA plugin with its D_DLNAMediaController1.json and D_DLNAMediaController1.js files.
Here is what happen.
It happens only in one direction.
It is systematic: as soon as I open one Sonos device, then the DLNA device is “corrupted”.
The behaviour is the same whatever the WEB browser.
The only workaround to restore the right tabs is to clear the cache of the browser (Ctrl+F5).
I have received a report of my ecobee thermostat plugin’s JSON information replacing what should appear for a Z-Wave thermostat in the dashboard, and my suspicion is that I use the UPnP standard device type for my thermostat device, and something in the system is assuming its use is unique per plugin. My understanding is that your plugin can use standard device types without creating conflicts with other plugins or the built-in Z-Wave support, but this report contradicts that.
Do you use standard device types in a way that could be exposing the same bug?
Yes, Sonos is historically using a standard device type. But yesterday I tried to assign to it a new device type and it does not help.
I see two possible recommendations:
Regarding the second point, I will check it but I think I can probably move a lot of my global functions to sub-functions of the main functions (the functions defined in the JSON file). In this case, I could probably keep common names.
I don’t know if it is a known problem. If not, I am surprised anyone already discovered it.