-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error when starting with plugin enabled #16
Comments
Could you start homebridge in debug mode using |
@DoctorNSA I did that, but saw there was a plugin update so updated to the latest version and that seems to have resolved it as homebridge has now started successfully and my receiver has now appeared within the accessories view and I can see it's pulling things in fine in the logs. Not sure what the issue was. |
The issue might have been defining the input type tuner as it is just a group of inputs and won't work properly. Please replace tuner with am, fm or dab |
Hi,
I've tried for a while to get this plugin to work; it took me a while to get my json formatted correctly in a way in which it would be accepted but I get this error in my logs on startup which sends homebridge in a loop.
Here is my config
{
"accessory": "MusicCastTV",
"name": "Yamaha Stereo",
"ip": "192.168.1.187",
"model": "RN-803D",
"inputs": {
"tuner": "Tuner",
"server": "Server",
"phono": "Phono",
"line_cd": "CD",
"optical2": "TV",
"line1": "PC",
"line2": "Tape",
"spotify": "Spotify",
"net_radio": "Net Radio",
"tidal": "Tidal",
"airplay": "Airplay",
"bluetooth": "Bluetooth"
}
}
Have you got any ideas?
Output from my receiver's api below also
The text was updated successfully, but these errors were encountered: