[APP][PRO] Yamaha AV & MusicCast Receiver

Apps
,
161

Hi thanks for your quick answer. I removed the instance and installed again, now 100% sure I used the AV receiver, but have the same error. The code of the diagnostic report is C5FD9513. Thank you for your help, Robert

162

It seems you sent a report to Athom. Please sens the report from the app detail page.

Some ideasā€¦

  • is your receiver switched on?
  • is network standby activated to turn on from Homey?
163

Hi i can switch the receiver on from the Yamaha app, and i get the same error when the receiver is on.
Managed to create a diagnostic report, hope it has the info you needā€¦
This is the code:
59930b43-bc88-426a-b4ce-9dedf3ca459b

164

I can only see the message that itā€™s not possible to read device details. But no details.

Can you please check this URL (MusicCast) with your receiver IP?
Just to check if this is working.
http://{IP}/YamahaExtendedControl/v1/system/getDeviceInfo

If yes, you can add it as MusicCast device.
If notā€¦I have no idea at the momentā€¦

165

Hi Ronny,

The URL gives no response, so probably something wrong with the local setup. Still strange that the app works flawlessly.

Regards
Robert

166

I searched a lot but could not find any details about the used API.
Only this page with an old app only supporting a few models.

Which app are you using: The app from the link or one of these?

Screenshot_20240722_230943_Google Play Store
Screenshot_20240722_230943_Google Play Store1080Ɨ424 83 KB

If you want to test the API used by the Homey AV-Receiver, you need a http tool that can send POST requests. Easiest way is a browser add on like ā€œRESTEDā€ Firefox add on.
Use this URL:
http://192.168.1.33/YamahaRemoteControl/ctrl
and use this body:

<YAMAHA_AV cmd="PUT"><Main_Zone><Power_Control><Power>On</Power></Power_Control></Main_Zone></YAMAHA_AV>

grafik
grafik1053Ɨ730 22.3 KB

If your device does not turn on, it doesnā€™t support the Yamaha XML API or REST/MusicCast API.

Edit: I found an example where someone used the XML API with such a receiver. So AV-Receiver device should work. Perhaps the device does not support all functions like providing device details.

167

Hi Ronny it is the app from the link

Thanks
Robert

168

Hm, then I think this app has a undocumented API.

I added further logging to the app. You can try the testversion. After the app is installed and running, you can send me a log. But I think it will only show a simple http error (device not responding).

Yamaha | Homey

169

Hi Ronny

Thanks for your effortā€¦ Here is the new diagnostic reportā€¦
8ac2ff7e-b03d-4671-b97d-83530345222e

BTW, during installation, system DOES recognize the model number, after that, it failsā€¦

Regards
Robert

170

The SSDP discovery is working and reading basic device details is working. So is basically supports the XML API.
But reading device details fails with a http400 error.

Does your Yamaha show device details (tuner, volume, title)? Or does it only allow some basic controls/commands like an IR remote?

Are you able to do some test with a REST client shown in the screenshtos above to test what features/commands are supported?

PS: The receiver firmware is up to date?

PS2: The system data response from your device (XML) is similar to AV/XML API only in parts (device name) but different in other data (features). And I miss a zone definition. Iā€™m not sure if itā€™s an earlier/deprecated API version or a special variant for only some devices.

171

Hi Ronny

Not sure what you mean by ā€˜device detailsā€™, but the display on the receiver show things like volume, title etc.
I tested with the REST client and also this resulted in a 400 error.
Server details were >> Server: AV_Receiver/3.1 (CRX-N560)

Regards
Robert