Another option is to attempt to set up the Receiver using Net::UDAP.
Results 11 to 20 of 21
Thread: Duet set up
-
2020-06-21, 04:30 #11
-
2020-06-21, 05:13 #12
- Join Date
- Oct 2009
- Location
- Western & Northern New York
- Posts
- 415
LMS has lost my receivers many times for various reasons and I always reset the controller and receiver, and bring them up together. You do not have to factory reset your receiver (if I am recalling correctly). I think all of my controller color, menu order, etc remain in tact. I outlined the process in post #2 of this thread:
https://forums.slimdevices.com/showt...ng-for-players
I have found over the years and frustrations that connection issues with receivers are related to wifi strength and stability. My ethernet connected ones are rock solid. I have one on wifi in a location on the fringes of wifi range and it is always troublesome.
good luck;
Jim
-
2020-06-21, 12:36 #13
- Join Date
- Dec 2008
- Location
- Sweden (only country where the clouds are interesting)
- Posts
- 646
Success, finally!
OK, guys, my Duet is up and running again! Thanks for all the help.
Indeed, I had to reset also the controller. How annoying. All my customization has to be redone and I have now idea how I did some of those long ago...
One strange thing: even though it was factory reset, the controller still remembered that it was registered with my account on MySB.com. Surprising, but it simplified things as I am not sure about the password
So, now I only have to figure out how to set the controller to use a static IP-address. If that is at all necessary, that was a consequence of the old router; the controller was slow to wake up and setting a fixed IP address made it wake up significantly faster. Maybe it is not necessary anymore, I'll see.// OppfinnarJocke
SqueezeBox Duet, Controller FW 7.7.3 r16662, Player FW 77
Main use: Deezer and Radio Paradise through MySB.com
-
2020-06-21, 12:58 #14
- Join Date
- Oct 2009
- Location
- Western & Northern New York
- Posts
- 415
You success lead to me learning something...my controller wake up is notoriously slow, to the point of me muttering "why?". So much I seldom keep them out of the cradle. Maybe a static IP would have helped me. Thanks! However, while I still like the controllers, I use/like them primarily as a "now playing" screen, because there are so many options for phone, PC control (I use material, sqeeeze cntrl) that the only time I use the controller is if I am in the same room that a controller is, and remove it, and return it to the cradle.
I don't have a controller at this location but I am surprised that you had to do a factory reset. I guess I didn't pay that much attention. I always tough the '+' pwr combo was a bit of a soft reset...
cheers
Jim
-
2020-06-27, 23:39 #15
- Join Date
- Mar 2016
- Posts
- 37
-
2020-07-07, 07:59 #16
- Join Date
- Apr 2008
- Posts
- 1,447
Setting static IP in Controller
From a long time ago if you can ssh in to the controller to set a static IP. User Root PW 1234 File Protocol SCP. Hope this helps.
If you know how to mess around in a Linux prompt, you can edit the file
/etc/network/interfaces on the controller to give it a static IP.
Change this section:
iface <name of your wifi network> inet dhcp
script /etc/network/udhcpc_action
to:
iface <name of your wifi network> inet static
address 192.168.2.50
netmask 255.255.255.0
network 192.168.2.0
broadcast 192.168.2.255
gateway 192.168.2.1
Ofcourse you should use the correct IP addresses/netmasks that goes for
your system - you can use /sbin/ifconfig to get the info needed. You
might also have to edit /etc/resolv.conf, but I guess it'll already have
the correct value (name server) if you're running DHCP now.
Howard
-
2020-07-07, 12:27 #17
- Join Date
- Aug 2007
- Posts
- 12
-
2020-10-04, 09:07 #18
Stuck on blue...
I have a similar situation, so I tried to reset the player, fast red, then slow red, appears on my network as a device, and I can select it in the controller.
I get to the connecting to network part, and the light goes yellow, green, blue in rapid order.
Blue should mean waiting to connect to server, which is fine as the 5 other players are all listed there and the server is responding to them all.
Then the controller gives up and says could not connect, and try skip or try again.
Skip does nothing, try again repeats the above.
Then the player is not seen be the controller.
Even when I reboot controller, player not seen, I have to reset the player too.
Then all the above just repeats.
Any ideas?2 x Booms, 2 x Players, 2 x Touch, 4 x Joggler, LMS 7.7.6-113 running on Synology D712+
-
2020-10-05, 04:20 #19
- Join Date
- Oct 2009
- Location
- Western & Northern New York
- Posts
- 415
As I mentioned in post #12, my controller receiver issues have always been due to wifi (strength, interference, ??). I have a couple seldom used receivers and when they were connected via wifi, I would come back after say a month or so and I often had to reset them. Try connecting with an ethernet cable. The receivers I have connected via ethernet have no more issues, even after sitting idle.
I have had alot of troublesome experience with receivers over years that I don't have with other players, and have come to the conclusion it's something unique to their wifi.
I also always reset both the controller and receiver (see my post #12 for the link to the process) and brought them up "together". The discovery process where the controller says "choose your player" seems to complete the process, for me at least.
Jim
-
2020-10-05, 14:36 #20