Duet Issues, e.g. actively streaming while flashing Red?

[rockhopper]

To finish up what bpa started...

No need to ethernet connect the receiver,

Factory reset receiver - long push front button untill fast red blink. Then release button, it will drop back to slow red blink.

Factory reset the controller.

Set up controller per what it tells you on the screen. When it gets to the part of selecting a receiver your receiver should show by its MAC address. Select it.

What that does is the controller transfers your wifi login credentials to the receiver (this is the only time the controller actually talks directly to the receiver). You should see the light on the receiver turn green, then blue when it gets an IP from the router and if your LMS host is running the light should end up as dull white. Every once in a while the receiver will finish up and go to the dull white and the controller will say the setup failed... It's a lie!

You're done except for things like maybe change the wallpaper on the controller and I also set the not playing screen saver to the analog clock.

I will say there was one time in the over ten years I've had a receiver that I couldn't make it through setup with the controller and ended up having to use Net::UDAP to get the receiver setup completely. Other than that one time the standard setup has always worked. I do run my LMS server on a reserved IP so it's always at the same address on my network.

As I've said, the Duet does not respond to a long push of its button in the proscribed way. All it will display is the 6 rapid blinks of red, followed by a short pause , then repeated. It does not change to slow red blinks or anything else for that matter.
I'm not sure how else to perform a factory reset.

Regarding the Controller factory reset: That works fine but will only find the Duet if Ethernet connected.
There is no evidence of credentials transferring to the receiver via the coloured lights sequence.
Does this mean there is no transfer happening?
Do you know if WiFi credentials retained by the receiver when it is powered off?
Or perhaps the h/w condition represented by the 6 red blinks overrides the credential transfer/coloured light process?

BTW, I've not noticed anything common about the occasions when the setup is lost.

The Net::UDAP tool mentioned is currently sounding like my best bet to get to the bottom of this, but I know nothing about that and I'll have to look into it.

Thank you for your help.

[rockhopper]

AFAICT - you have not reset the Receiver (i.e. you did not push the button and get slow blink Red) so this is a "Normal" Receiver operation finding LMS.
Receiver can only find LMS after Receiver powers up and broadcasts a UDP request for all LMS on the LAN segment to reply. If the Receiver is not on the same LAN segment (i.e. network mask) then Receiver will not see the LMS replies to the broadcast messages. This might explain why you have to connect Receiver direct to PC - to ensure Receiver in on the the right LAN segment.

I still think looking at Receiver setting with Net::UDAP tool might clarify things - it'll tell you what IP address the receiver actually think is the current LMS

If the LED is fast flashing red ("Factory Reset and Xilinx update in progress") and not purple - then perhaps a Factory & Xilinx reset might help but then you'll have to go through a full Receiver setup (assuming Receiver is OK after a reset).
According to another post "Pressing and holding SBRs button about 6 seconds until the LED flashes red fast does a factory reset and reprograms the xilinx chip. "

I'll look into this Net::UDAP tool you recommend when I get plenty of spare time.
The IP addresses all match in terms of what my Router says and what LMS settings and logs say, as far as I can tell, but I'm not sure about the other LAN data you mention.

I was under the impression I was doing a full Receiver set-up each time, especially if Controller displays receiver name subscripted with last 6 digits of its MAC address, rather than the name I renamed it to.

The Duet does not respond to the proscribed procedure for a reset via its button. I'm not sure how else to perform a factory reset.
BTW I have previously opened it up to check its physical operation and the microswitch appears healthy, chip seated securely, no signs of dry joints etc.
The same behaviour is seen with both my old and replacement Duet receivers.

Thank you once again for your help.

[w3wilkes]

To finish up what bpa started...

No need to ethernet connect the receiver,

Factory reset receiver - long push front button untill fast red blink. Then release button, it will drop back to slow red blink.

Factory reset the controller.

Set up controller per what it tells you on the screen. When it gets to the part of selecting a receiver your receiver should show by its MAC address. Select it.

What that does is the controller transfers your wifi login credentials to the receiver (this is the only time the controller actually talks directly to the receiver). You should see the light on the receiver turn green, then blue when it gets an IP from the router and if your LMS host is running the light should end up as dull white. Every once in a while the receiver will finish up and go to the dull white and the controller will say the setup failed... It's a lie!

You're done except for things like maybe change the wallpaper on the controller and I also set the not playing screen saver to the analog clock.

I will say there was one time in the over ten years I've had a receiver that I couldn't make it through setup with the controller and ended up having to use Net::UDAP to get the receiver setup completely. Other than that one time the standard setup has always worked. I do run my LMS server on a reserved IP so it's always at the same address on my network.

[bpa]

Many thanks for your continued interest, bpa.

The procedure I follow for re-setup is:
Stop LMS and cut power to Duet and Router
Connect Duet to PC laptop (hosting LMS & music library) with temporary Ethernet cable.
Power up Router and Duet.
Start LMS.
Use Controller / Select Player to point it to the Duet (as opposed to my fully functional Boom), choose wireless & point it to my WiFi network, then my music library, all while Ethernet still plugged in.
(pointing to mysqueezebox.com never works).
Once working, unplug Ethernet and continue.

Prior to this repeated problem, I was able to use the Duet's button to re-setup, with it cycling through the various colours until ultimately displaying bright white once music library found/playing.
This procedure no longer works - the Duet's lights permanently display the 6 blinking reds.

AFAICT - you have not reset the Receiver (i.e. you did not push the button and get slow blink Red) so this is a "Normal" Receiver operation finding LMS.
Receiver can only find LMS after Receiver powers up and broadcasts a UDP request for all LMS on the LAN segment to reply. If the Receiver is not on the same LAN segment (i.e. network mask) then Receiver will not see the LMS replies to the broadcast messages. This might explain why you have to connect Receiver direct to PC - to ensure Receiver in on the the right LAN segment.

I still think looking at Receiver setting with Net::UDAP tool might clarify things - it'll tell you what IP address the receiver actually think is the current LMS

If the LED is fast flashing red ("Factory Reset and Xilinx update in progress") and not purple - then perhaps a Factory & Xilinx reset might help but then you'll have to go through a full Receiver setup (assuming Receiver is OK after a reset).
According to another post "Pressing and holding SBRs button about 6 seconds until the LED flashes red fast does a factory reset and reprograms the xilinx chip. "

[rockhopper]

If LMS server IP address doesn't change, what needs to be setup in Receiver each time ?

It may be worth looking at Net::UDP tool to see which setting gets "lost" although the tool can be a pain to setup.

Many thanks for your continued interest, bpa.

The procedure I follow for re-setup is:
Stop LMS and cut power to Duet and Router
Connect Duet to PC laptop (hosting LMS & music library) with temporary Ethernet cable.
Power up Router and Duet.
Start LMS.
Use Controller / Select Player to point it to the Duet (as opposed to my fully functional Boom), choose wireless & point it to my WiFi network, then my music library, all while Ethernet still plugged in.
(pointing to mysqueezebox.com never works).
Once working, unplug Ethernet and continue.

Prior to this repeated problem, I was able to use the Duet's button to re-setup, with it cycling through the various colours until ultimately displaying bright white once music library found/playing.
This procedure no longer works - the Duet's lights permanently display the 6 blinking reds.

[bpa]

By DHCP. I believe it's possible to use static IPs with my router. I haven't tried tbh.
However, I note the same dynamic IP address is always being used each time a re-setup is required, in my case 192.168.0.14 for the LMS host.

If LMS server IP address doesn't change, what needs to be setup in Receiver each time ?

It may be worth looking at Net::UDP tool to see which setting gets "lost" although the tool can be a pain to setup.

[rockhopper]

Dhcp

Is the LMS host IP address statics or allocated by DHCP ?

If allocated by DHCP - can you reserve in router the MAC address so that it is always allocated same IP address

By DHCP. I believe it's possible to use static IPs with my router. I haven't tried tbh.
However, I note the same dynamic IP address is always being used each time a re-setup is required, in my case 192.168.0.14 for the LMS host.

[bpa]

My real concern is the frequency with which my set-up loses the Duet, necessitating re-set-up via an Ethernet connection between the Duet and my PC laptop (LMS host).

Is the LMS host IP address statics or allocated by DHCP ?

If allocated by DHCP - can you reserve in router the MAC address so that it is always allocated same IP address

[rockhopper]

MAC address OK

The Wiki is written by a user so peerhaps they are mistaken.

Check the MAC address is the same as label on bottom - WebUI Settings/Information

Wiki errors are always possible, sadly. Let's see if anyone can verify..?
The MAC address is the same.

PS. I can live with red blinks, if they cannot be diagnosed.
My real concern is the frequency with which my set-up loses the Duet, necessitating re-set-up via an Ethernet connection between the Duet and my PC laptop (LMS host).
Please see original post for details, if interested.
Many thanks for your input.

[bpa]

Hi bpa.
I misread the Wikipedia table and was too quick seeing the hard error codes, not to notice they are associated with purple blinks. Sorry for the confusion.

My blinks are definitely red. I've seen purple with previous problems.

I do get 6 red blinks. It would be great to know what that denotes.

I recall seeing a subset of the Mac address in the name of the device when first set up via the controller. Also the Mac address is shown (non-zero) as seen in the list of IP devices in my Router config.
So I think the 6 purple blinks meaning is a red herring (of my making).

The Wiki is written by a user so peerhaps they are mistaken.

Check the MAC address is the same as label on bottom - WebUI Settings/Information

[rockhopper]

Oops! Red not Purple

You are certain the LED colour is actually purplish and not red........

Hi bpa.
I misread the Wikipedia table and was too quick seeing the hard error codes, not to notice they are associated with purple blinks. Sorry for the confusion.

My blinks are definitely red. I've seen purple with previous problems.

I do get 6 red blinks. It would be great to know what that denotes.

I recall seeing a subset of the Mac address in the name of the device when first set up via the controller. Also the Mac address is shown (non-zero) as seen in the list of IP devices in my Router config.
So I think the 6 purple blinks meaning is a red herring (of my making).

[rockhopper]

Power supply?

A failing power supply can cause all sorts of issues.........

Thank you for your post w3wilkes.
I tried swapping the power supplies but it had no effect.
My use of SB kit is effectively plug & play, but having read yours and many other posts which describe building components to improve setups I will have to look into how involved that is.
However, thank you for your comments.

[bpa]

Thank you for your post, bpa.
Yes, my light sequence of 6 red blinks is there, denoting a Hard Error code meaning "UUID not set/all zeros".
Unfortunately I have no idea of the significance of this.
Clearly it's not stopping configuration of the Duet and I assume whatever the trigger is, it supersedes the usual colour sequence during set-up through to white when connected and playing.

You are certain the LED colour is actually purplish and not red.

The UUID is used to identify the player uniquely to LMS - usually it is the MAC address.
MAC addresses have been known to be reset to zero on older SB players.

Is the MAC address of your receiver all zeroes ?

You may have use NET::UDAP to configure receiver (see https://forums.slimdevices.com/showt...iguration-tool )


edit:

The MAC address for a player is shown in the LMS WebGUI Settings/Information tab

[rockhopper]

Blinking Red x6

Can you find your light sequence amongst the list in this wiki entry ?

http://wiki.slimdevices.com/index.ph...button_and_LED

Thank you for your post, bpa.
Yes, my light sequence of 6 red blinks is there, denoting a Hard Error code meaning "UUID not set/all zeros".
Unfortunately I have no idea of the significance of this.
Clearly it's not stopping configuration of the Duet and I assume whatever the trigger is, it supersedes the usual colour sequence during set-up through to white when connected and playing.

[w3wilkes]

A failing power supply can cause all sorts of issues. I also had a wifi card fail and was able to find a replacement. I've seen the light on the receiver do strange things and also the music will cut and start over. I bought a generic power supply with output rated to support up to 2 Amps, set the voltage to what the receiver expected and the receiver now works fine. When I needed a 3rd receiver I just built a PiCore player with a HiFiBerry DAC+ and have found it to be way more reliable than the logitech receivers. Next time I have a receiver problem I'll just build another PiCore player, easy peezy.