WiFi restart makes my Raspberry Pi3 device go offline until reboot

Project help
,
49

Thanks for sharing back your findings :+1:

52

Hi All,

Resurrecting the discussion:
I’m running a simple RPi3, downloaded the image, loaded up node-red and in a matter of hours or days it goes offline, without coming back.
I’m running 2.36.0+rev2.

I was wondering if the problem has been addressed in a definitive way and if it is known why the device at random goes out of the WLAN?

Thanks for the great support.

53

Hi @mvargasevans,
Can you share a few extra details about your setup.
What WiFi dongle are you using?
Do you have the same issue on more than one devices?
Could it be a connectivity issue? Does the device loose connectivity when using ethernet?

54

Could you also grant us support access to that device and share its dashboard url with us so that we can pull some logs from it?

56

Hi Thodoris

Thanks for the quick response.

It is actually connected to wifi via the on-chip hardware, no dongle.

I am testing a BalenaFin now, I can come back with those results later.

I have tried it out in different locations (home, work, etc) and I’m not able to pinpoint when it happens.

What I can add is that if it goes offline, it never comes back.

Not sure if it is a connectivity issue, but the signal is strong if that is the question.

It seems to me it is only the network manager which seems to get disconnected and never come back.

Someone mentioned in another post, somewhere, that it seems like it cannot find the network.

What I am testing now is the first suggestion, to remove the [hidden] = true.

Since I saw a couple of work arounds and updates, I wanted to know if it is a resolved issue from your side or are there other people still reporting this.

Regards

59

Hi Thodoris

I saw this a couple of hours later.
I will grant access tomorrow and dashboard.
Unfortunately the device shut down on its own again, (hidden=true) didnt work.
The device is sitting in the same network as a BalenaFin, and that one is active.

67

@mvargasevans this sounds a bit like this issue https://github.com/balena-os/meta-balena/issues/1473 , but that is still being investigated. The best way to help us narrow down the issue is to set up a .dev balenaOS device with a serial cable attached to it and when the device fails, use the serial console to grab the networkManager logs using journalctl -u NetworkManager --no-pager