@Wobblyman 

Thanks for the suggestions - 

I was comparing more to the current 1.3.2 to earlier versions. 

Only one has the WAN connection - never set it before. Will look into it. However, it was the other DECO's experiencing the problem.

I do'nt want to reboot every day - I've got SONOS and over 60+ wifi devices that will need to go through the discovery process again and realign. Shouldn't need to be done.. Maybe once a month at best. Also the light show they give off when booting up (even with lights set to off) looks like a disco when it's happening (especially in a dark room). 

All my devices are on reservations via DHCP - i've got a split IOT and internal network. 

This behaviour wasn't happening before.. Seems that the physical layer is brought up and working (hence i can see devices in the app physically connected to the deco), but the device is still flashing red. 

A few more reboots later, they come good.. Waited about 20 mins while it was flashing red - so not sure what is preventing it from going green.. And nothing changes (other than the stage the other DECO's. were in when it finally come good). 

Cheers

  @Wobblyman 

Thanks for your email. 

Yes, they are directly connected to each other via ethernet. no switches inbetween, wan > deco1 > deco2 > deco3 >>> wifi >>> deco 4 (be25 in garage). 

I'm in Wifi mode. 

I'll try to remove the ethernet cable next reboot.. I'm not game enough at the moment to loose the connection again.

Keen to see if anyone else has this experience with the new FW. 

Cheers

Greg.

  @Wobblyman Hi Greg, You wanted to know if anyone else had had a bad experience on the BE65 v1.3.x firmware, I just wanted to let you know that I did just to add one to the count! I tested it during the beta phase when it was 1.3.0 . My BE65 V2 devices would connect and work for a very short period of time, and then the light would go red on the main node and that would be the end of that. I was very surprised as usually the beta firmwares work well, I tried it at the very end of the beta process thinking it would be stable. I mentioned my negative experience in the beta thread and I ended up rolling back all three nodes to 1.2.0 using a PC I had spare and that resolved the issue. I'm in Australia, on TPG as an ISP, a PPTP connection and this ISP requires a VLAN ID of 2. Since then I did upgrade to 1.2.10 - I had to download this from the USA site although it does support AU, as 1.2.10 final was not offered as an update in Australia. I am still on this firmware and it is great. I have turned off Auto update on the devices, and sure enough I have been offered the 1.3.2 as a firmware upgrade, I am not going to take it! I'll stay on 1.2.10 as I have learned my lesson. I'm sure that this firmware 1.3.2 must be working fine for most as it is on auto update here in Australia, but there is something subtle stopping it working for all and I'm not going to take the chance yet!

Cheers.