Up2Stream HD DAC HTTP API Not Working

Hi,
I have an HD DAC that I am trying to control via the HTTP API, but cURL doesn’t seem to be able to connect.
Here’s a few variations I’ve tried:

$ curl -k http://10.0.1.220/httpapi.asp?command=getStatusEx
curl: (7) Failed to connect to 10.0.1.220 port 80 after 9 ms: Connection refused
$ curl -k https://10.0.1.220/httpapi.asp?command=getStatusEx
curl: (56) LibreSSL SSL_read: error:1404C45C:SSL routines:ST_OK:reason(1116), errno 0
$ curl -k https://10.0.1.220:443/httpapi.asp?command=getStatusEx
curl: (56) LibreSSL SSL_read: error:1404C45C:SSL routines:ST_OK:reason(1116), errno 0
$ curl -k https://10.0.1.220:4443/httpapi.asp?command=getStatusEx
curl: (7) Failed to connect to 10.0.1.220 port 4443 after 9 ms: Connection refused

UPnP seems to work fine:

$ curl -H 'Content-Type: text/xml; charset=utf-8' \                                               ⏎
  -H 'SOAPAction: "urn:schemas-upnp-org:service:AVTransport:1#GetInfoEx"' \
  -d '<?xml version="1.0" encoding="utf-8"?><s:Envelope s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"><s:Body><u:GetInfoEx xmlns:u="urn:schemas-upnp-org:service:AVTransport:1"><InstanceID>0</InstanceID></u:GetInfoEx></s:Body></s:Envelope>' \
  'http://10.0.1.220:49152/upnp/control/rendertransport1'
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body>
<u:GetInfoExResponse xmlns:u="urn:schemas-upnp-org:service:AVTransport:1">
<CurrentTransportState>PLAYING</CurrentTransportState>
<CurrentTransportStatus>OK</CurrentTransportStatus>
<CurrentSpeed>1</CurrentSpeed>
<Track>0</Track>
<TrackDuration>00:03:31</TrackDuration>
<TrackMetaData>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
&lt;DIDL-Lite xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:upnp=&quot;urn:schemas-upnp-org:metadata-1-0/upnp/&quot; xmlns:song=&quot;www.wiimu.com/song/&quot; xmlns=&quot;urn:schemas-upnp-org:metadata-1-0/DIDL-Lite/&quot;&gt;
&lt;upnp:class&gt;object.item.audioItem.musicTrack&lt;/upnp:class&gt;
&lt;item id=&quot;0&quot;&gt;
&lt;song:subid&gt;&lt;/song:subid&gt;
&lt;song:description&gt;un_known&lt;/song:description&gt;
&lt;song:skiplimit&gt;0&lt;/song:skiplimit&gt;
&lt;song:id&gt;0&lt;/song:id&gt;
&lt;song:like&gt;0&lt;/song:like&gt;
&lt;song:singerid&gt;0&lt;/song:singerid&gt;
&lt;song:albumid&gt;0&lt;/song:albumid&gt;
&lt;res protocolInfo=&quot;http-get:*:audio/mpeg:DLNA.ORG_PN=MP3;DLNA.ORG_OP=01;&quot; duration=&quot;00:00:00.000&quot;&gt;wiimu_airplay&lt;/res&gt;
&lt;dc:title&gt;Blast Ya (feat. Barrington Levy)&lt;/dc:title&gt;
&lt;dc:creator&gt;Borgore&lt;/dc:creator&gt;
&lt;upnp:artist&gt;Borgore&lt;/upnp:artist&gt;
&lt;upnp:album&gt;Blast Ya (feat. Barrington Levy) - Single&lt;/upnp:album&gt;
&lt;upnp:albumArtURI&gt;&lt;/upnp:albumArtURI&gt;
&lt;/item&gt;
&lt;/DIDL-Lite&gt;
</TrackMetaData>
<TrackURI>wiimu_airplay</TrackURI>
<RelTime>00:03:21</RelTime>
<AbsTime>NOT_IMPLEMENTED</AbsTime>
<RelCount>2147483647</RelCount>
<AbsCount>2147483647</AbsCount>
<CurrentVolume>25</CurrentVolume>
<CurrentChannel>0</CurrentChannel>
<LoopMode>0</LoopMode>
<PlayType>1</PlayType>
<SlaveFlag>0</SlaveFlag>
<MasterUUID></MasterUUID>
<SlaveList>{ &quot;slaves&quot;: 0, &quot;wmrm_version&quot;: &quot;4.2&quot; }</SlaveList>
<PlayMedium>AIRPLAY</PlayMedium>
<TrackSource></TrackSource>
<InternetAccess>1</InternetAccess>
<VerUpdateFlag>0</VerUpdateFlag>
<VerUpdateStatus>20</VerUpdateStatus>
<BatteryFlag>0</BatteryFlag>
<BatteryPercent>0</BatteryPercent>
<AlarmFlag>0</AlarmFlag>
<TimeStamp>80024298</TimeStamp>
<SubNum>0</SubNum>
<SpotifyActive>0</SpotifyActive>
</u:GetInfoExResponse>
</s:Body> </s:Envelope>

Is there something I am missing or is this a bug?

Hi, is not supported in DAC HD.

Regards.

Thank you. Are there any plans to support it in the future or offer workarounds to access functions that require the HTTP API?

Hi i do not know, arylic is not work in this device.

$250 to the garbage, with one rasp and a DAC all work fine.

Of course the HTTP API is supported. It would be very strange not to have it implemented in the much costly and better board!
Guess you only need a different firmware. You can buy one or develop one and upload it via the 4 non-cased black headerpins ( classic 2.5 mm style), which have subscripts: GPIO0, B0, B1 and GND. GPIO0 is for getting in boot mode during powerup. B0 and B1 are likeley RX and TX.