For the PicoBrew ZSeries. I'm using a Raspberry Pi Zero W following the regular setup instructions and release beta3. I have pointed the Pi at an extender as well as the primary xfinity 2.4 networks.
I can attach to the Pi hotspot with a laptop and reach the internet without issue, and I can reach the Pi through the WiFi network it is connected to and view recipes I have copied to the SMB shares.
On a rare occasion, The Z can spin up properly and display recipes from the Pi, but usually I am met with an initial ERROR HTTP GET, and after that, screens that display ErrorWifiNoInternet.
I have checked that the firmware version is 0.0.116 on the Z, and that proper .py file is also at 116 (ref "pinned firmware" discussion in issue #41).
The only thing that seems to help is if I reset the xfinity modem and cascade down to the Z. Even though, not usually for very long.
At any point I can select the xfinity or extender network from the Z WiFi screen and return to normal when hitting the PB servers.
I have moved the Pi physically around to be sure there isn't a range or crowded channel issue causing these problems.
Is there any debugging I can do to help resolve this? I don't see anything on the Pi output screen to indicate errors when any of this occurs.
chiefwigms
commented
4 years ago
For the PicoBrew ZSeries. I'm using a Raspberry Pi Zero W following the regular setup instructions and release beta3. I have pointed the Pi at an extender as well as the primary xfinity 2.4 networks.
I can attach to the Pi hotspot with a laptop and reach the internet without issue, and I can reach the Pi through the WiFi network it is connected to and view recipes I have copied to the SMB shares.
On a rare occasion, The Z can spin up properly and display recipes from the Pi, but usually I am met with an initial ERROR HTTP GET, and after that, screens that display ErrorWifiNoInternet.
I have checked that the firmware version is 0.0.116 on the Z, and that proper .py file is also at 116 (ref "pinned firmware" discussion in issue #41).
The only thing that seems to help is if I reset the xfinity modem and cascade down to the Z. Even though, not usually for very long.
At any point I can select the xfinity or extender network from the Z WiFi screen and return to normal when hitting the PB servers.
I have moved the Pi physically around to be sure there isn't a range or crowded channel issue causing these problems.
Is there any debugging I can do to help resolve this? I don't see anything on the Pi output screen to indicate errors when any of this occurs.