Open radic00l opened 3 years ago
Thanks for a very detailed issue
A couple of comments
1 - Without have access to the physical device, adding and troubleshooting support issues is close to impossible. If you want to submit a pull request resolving the issue, I can merge it.
2 - Device Discovery - Yeah that is a bit of a wacky experience, and your correct the plugin does not handle the exclusion use case. In this scenario you could just not add/pair the duplicates, or put them is a 'closet'. And after looking at the code, am wondering if you could disable the discovery by setting the discovery timeout to a really low value, ie 1 or .1
Hey...
1 - Not sure this would actually work out
2 - Give it a try and see what happens. I'm thinking a really small value like 1 or .1
I'm getting an error that is preventing an older (pre-MusicCast) device from being added, i.e. 1/13/2021, 10:38:28 AM Unhandled rejection TypeError: Cannot read property '0' of undefined
My config is as follows
To give you more information:
For reference, here is the full extract from the logs for your plugin. You'll see the RX-A3060 being added successfully, but the error thrown for the Z7...
Separately (apologies for combining items, but while I have your attention)... Would it not make sense that if a person specifies manual_addresses, the plugin doesn't attempt to scan the network to index devices itself. This would allow a person to control which Yamaha devices are added, by specifying IP for devices to include and leaving out IP for devices they don't want added. Of course, by default, a person could leave blank and search for all devices.