@mike.maxwell @mluck. I officially didn’t try it but I should work any serial to telnet adaptor or the Pi with Python scrip telnet2serial should do the trick I will strongly recommend to try the official driver my is a little bit choppy generate to much logs and probably overloading your hub. I’m not a real programmer and just do this when is not other choice.
1 Like
I've been using the custom driver for awhile without any issue. Today I tried the official driver using the same IP and same port. After saving the new device, it shows up as OFFLINE and upon initializing generates "telnet connect error: connection refused" in the log. Any ideas? Could it be because I didn't delete the old custom device first? I'm hoping not to delete the old until I get the new version working.
@mluck I just try it and it work on point no problem, I have both my drive and the official driver at the same time and both are working, do you have the tcp/ip tp serial adapter or the raspberry pi??? I will say start triple checking the IP and port.
1 Like
Your driver still works great. I’m using a serial adapter. I used the same IP and same port in the official driver and it doesn’t work.
Are you using a raspberry pi?
not any more -- just using a serial adapter. It works great with your driver.
I got no idea why is not working
if you are going to satay on my driver update the child driver from the github the driver is generating unnecessary logs
line 61 should be change from "log.debug NewData" to "if (logEnable) log.debug NewData"
and turn off logging on the Childs devices
1 Like
I really need to switch to the official driver. Been trying everything without luck so far. Jorge, do you think this could be my problem?
In your device driver, I entered the IP address as well as the port of the serial controller. This works great.
In the official driver, it looks like the below, but the port defaults to 8080. I changed 8080 to 23, which the port previously setup on the serial adapter. Any reason this would be wrong?
No matter what I try, I get "Offline" status using the official driver. And the logs show a telnet connection error. Is it possible I need to charge other parameters on the serial adapter?
@mike.maxwell, any suggestions. I'm trying to use the new Monoprice 6 Audio driver without luck so far. Granted, I'm using the amp not the pre-amp, so...
I would verify that you can connect to the amp on that ip port combo using a separate telnet client first.
Jorge, doesn't the custom driver use telnet also? I thought so. Mike, the OP's driver works for me fine -- same IP and port.
(FWIW there are feature/function and performance downsides which is why I want to move to the "official" driver.)
I tried using PuTTy and it won't connect. Weird because this driver works like a charm. Maybe it's not using telnet?
The driver use telnet too can you send an screen shot of the telenet to serial configuration screen?
Try to change the port on the serial to telnet adapter to 8080 that is what I have set on my.
Thanks Jorge. I’ll try the 8080 port. In the meantime, here are the main configuration screens from the serial adapter. Let me know your thoughts. Thank you!
For anyone who follows me....
Turns out the official driver will work if you set the port to 8080, as @martinez.mp3 suggested. Thank you Jorge! Of course, I'm using the Monoprice 6 Amp not Preamp; that could be a difference, not sure. When my serial adapter was set to port 23, and I put 23 in the driver, the device was always offline. As soon as I used port 8080 in both places, everything worked (with one caveat below). Not sure why, but hopefully the tip helps others who are trying to make it work.
Note one issue with the official driver that isn't a problem with the custom driver. For some reason, you can't adjust the media source (AKA, input source) by way of a standard music player tile in a dashboard (like you can with the custom driver). @mike.maxwell, is this fixable?
I'm sure it is
You took me very literally 
Is there something I can do to make it happen?
i think the dashboard is looking for a speaker, not a preamp/receiver, as such it will require a change to the dashboard app me thinks, so there's nothing really for you to do per se.
Thanks for all of your work.
Can someone guide me on how to rename the sources to what they are (instead or RCA 1, to have it display as "Sonos" or "Chromecast"). I'm having trouble on my 3rd zone that I added to rename those sources.
If you go to the parent device, on the device details page, you’ll see a command called “Edit Input Name”. You can name your inputs there. It looks like this:
1 Like
Thanks for the reply.
I tried this, but cant get it to work.
Is there a specific naming system I'm getting wrong.
For example, the 3rd zone on my 3rd unit, is that zone 15, or is zone 33 .. i've tried both without success. Thanks so much for the reply.. I'll keep at it, but if you know the correct form, I'd appreciate it.
