Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Issue trying to get the Dialog with the 2.14 firmware via the web API
#1
I'm seeing an issue trying to get the Dialog with the API?
Has anyone gotten the dialog to respond to the new API?
All devices are running firmware 2.14

Sample implementation
1) Discover devices = static IPs, i have 5 static v4 IPs. 
Two Phantoms stereo systems 1 pair of golds, 1 pair of silvers and, 1 Dialog.
I also see IPV6 IPs but not planning to use them.

2. Iterate over all discovered devices:  static IP inputs used with client to request devices/current on IPs.

a. Perform /devices/current call on each device.  - this mostly works except on the DIALOG.

b. For each device, memorize its system and group ids, and (optionally) their firmware version and serial numbers.

If i cant enumerate the dialog i have to go through an elimination process using return values from the phantoms. YUCK!!!

*BUGBUG** c. For accessories only, memorize their names.

Attempting to enumerate a dialog returns 502 Bad Gateway.

http://192.168.0.15:80/ipcontrol/v1/devices/current

            client1 = new RestClient("http://192.168.0.15:80/ipcontrol/v1/");
            resultJson = await client1.Resource("devices/current").Get();

<html>
<head><title>502 Bad Gateway</title></head>
<body>
<center><h1>502 Bad Gateway</h1></center>
<hr><center>nginx/1.15.7</center>
</body>
</html>

the device enumeration works fine on Phantoms but not on the dialog.

I see the dialog in the list of sources returned by systems and groups but have to find the dialog by memorizing all of the devices and then go through a process of by elimination of known device/system ids.???

The docs say memorize the name, would love to but cant find a way to get the dialog to respond directly?

The dialog works fine with the Devialet app.

Anyone gotten the Dialog to work with the Remote IP Control API??


regards
scott-
Reply
#2
Got an update from Devialet support and confirmed the Dialog does not work directly with the API in 2.14 but should in a future update.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)