Before you rip out the 3b, which I ran on util a thunderstorm took it out, might try writing the PI module to the sd card again, set it to it’s default IP and try again?
I will give it a go
Not sure what else to suggest at this point. It’s low cost and doesn’t take much time…
Good luck
Thanks anyway… New image does not work , same issue. I am 99% sure the Pi is ok, i am leaning towards firewall, but i will need the developers to tell me if the software requires a specific port to communicate with the PI.
As far as I know it’s just another device hanging off your lan. Nothing special anything needs to know.
I’ve had an Amazon $12 bridge, 3b and now a 4 and have had no issues. Just shows up as another device on the local network.
I’m out of ideas myself. The big guns will be around tomorrow and @adammhaile knows these intimately…
Hang in there.
Sorry, no. I’ve been out of pocket for the last couple of days. Will try to get to this in the next couple of days.
If you have a firewall configured, can you disable entirely to test functionality? That would definitively indicate root cause and make a fix easier.
Unfortunately I don’t have control over the firewall…
Is the firewall running on your computer or is it applied network wide?
The connection between the Pi and the Ruida is pretty dumb. It’s basic TCP and it’s all hard coded IP’s. You MUST configure the IP of your Ruida to be 10.0.3.3 as described here: LightBurn Bridge - LightBurn Software Documentation
There is no amount of configuration on the “other” side of the communications (wifi from the bridge to your LightBurn computer) such as firewalls which will affect that. If you connect a monitor to your Pi you can see a console dashboard that will tell you if the Bridge can see the Ruida.
Though it looks like you can already access the web dashboard and from that I’m seeing that the Bridge IS connected to the Ruida. So the fact that LightBurn is saying it’s not is suspect…
Please send me both the network log and relay log from that dashboard.
Network_Log.txt (11.7 KB)
Relay_Log.txt (2.0 KB)
Both Logs attached
Network Firewall, I might setup a small network out with the company one and see if I can get it to work.
Not the Network 
I setup up an isolated network, Just an Access Point and got the same result.
Is it worth updating the ruida firmware?
To confirm, computer and Bridge wifi are on the isolated network. And Bridge to Ruida is direct connect, correct? And wifi and ruida are on different subnets?
To confirm, computer and Bridge wifi are on the isolated network. And Bridge to Ruida is direct connect, correct? And wifi and ruida are on different subnets?
Yes confirmed…
ok, so it looks like it is the Ruida itself (6445S), even though i can ping it and the lan looks ok. I tried my own Ruida from home (6442s) and it works.
Any ideas? worth Firmware update? or try and get an exchange?
I say never update firmware unless there is a specific reason to think it will solve an issue…
If the controller isn’t working, and you’re going to toss it, then it can’t hurt anything.
Always save a copy of the configuration Edit → Machine Settings → Save. That vendor data won’t survive a factory reset and you’ll need it for the replacement.
Then I’d do a factory reset, reload the configuration and see if it will walk, talk and chew gum… before I bought another one.
Wish I had a better suggestion. These have so many options, some of which are only available for access through a specific version of RDWorks… I always wonder…
In the same network environment or different network environment?
Same Network Environment
Wow. Wouldn’t have expected that. This isn’t a common fault scenario. There may be one other situation where the controller could be pinged but wouldn’t otherwise connect.
One thing to try before you upgrade the firmware, check that the storage is not full on the controller. If there are existing files, try removing them all before throwing in the towel.
I like to keep things interesting 
No luck clearing the files or factory resetting… Time for a new controller.