|
|
Post by Greg on Mar 24, 2021 6:54:18 GMT -8
When SGSConfigure scans the IP Address of the wireless extender, it flashes white and sends json to the terminal. However, the w.e. does not appear in the GUI.
Any help much appreciated!
|
|
|
|
Post by SDL on Mar 24, 2021 8:52:16 GMT -8
Have you configured your Wireless Extender to talk to your Access Point? Go back through the manual and make sure you did that.
If you Extender is not connected to the network, SGSConfigure will not find the extender.
BP
|
|
|
|
Post by Greg on Mar 24, 2021 16:13:44 GMT -8
Hey BP, thanks for the fast response! Excited to be up and running soon. I believe I did configure the wireless extender to talk to the access point as per the instructions ~ p28-30 www.switchdoc.com/wp-content/uploads/2020/09/SmartGardenSystemAssemblyAndTestManual1.4.pdf. When SGSConfigure scans the ip address on my wireless extender, the command line prints: JSON= {'return_value': 0, 'id': '151', 'name': '', 'ipaddress': '192.168.1.11', 'hardware': 'esp32', 'return_string': '151,1,1,1,1,025', 'connected': True} and the wireless extender flashes white. But, nothing comes up on the configure GUI. Not sure how to troubleshoot this further. Thanks, Greg PS- in case this is a hint- when I run SGS2.py I get the following error: Traceback (most recent call last): File "SGS2.py", line 43, in <module> import pixelDriver File "/home/pi/Adafruit_Python_GPIO/SDL_Pi_SmartGardenSystem2/pixelDriver.py", line 28, in <module> LED_STRIP = ws.SK6812_STRIP_RGBW NameError: name 'ws' is not defined |
|
|
|
Post by SDL on Mar 24, 2021 16:48:03 GMT -8
Hmm That sounds right. Let me do some debugging.
Delete your .JSON files and try again. Something may be hosed up. PM the JSON files before you delete them.
You aren't using our SDCard?
You are starting it with "sudo python3" right?
BP
|
|
greg
New Member
Posts: 3
|
Post by greg on Mar 25, 2021 3:17:44 GMT -8
Just sent the JSON in a PM. Deleting the files doesn't fix it, unfortunately.
I'm not using your SDCard- I cloned the repositories.
Yes, starting with sudo python3.
Thanks
|
|
|
|
Post by SDL on Mar 27, 2021 7:49:41 GMT -8
OK. Doesn't fix what? You have two problems. To fix the pixel problem, you have to install the pixel drivers. Download: github.com/switchdoclabs/SDL_Pi_8PixelStripAnd follow all the instructions in the multiple README.md's in the file. Including the one under the Python directory. BP |
|
|
|
Post by SDL on Mar 27, 2021 7:54:26 GMT -8
Greg,
Looked at your JSON. SGS is not picking up the wireless as you suspected. I just wanted to make sure something wasn't corrupted.
Can you tell me what the OLED display is showing on power up on the extender? Video it if you can and post it here.
BP
|
|
greg
New Member
Posts: 3
|
Post by greg on Mar 29, 2021 16:07:02 GMT -8
Hey BP, photos.app.goo.gl/5nSDE7uE6n1STcCF6There's a link to a video of the OLED on start up. In case that's hard to see, after the Smart Garden page, it's followed by: SGS2WExt Connected IP Address 192.... SGS2WExt Boot Ver: 025 Thanks! |
|
|
|
Post by SDL on Mar 30, 2021 18:04:32 GMT -8
Hmm. What is going on here. Could you reset your SGS Extender back to default values and set it up again? And then scan it.
I wonder if something else is on that IP #. Just guessing here.
BP
|
|
greg
New Member
Posts: 3
|
Post by greg on Apr 1, 2021 4:53:07 GMT -8
Tried setting to default and reconnecting everything on the extender but it still uses 192.168.1.11.
Perhaps this might help-
With the extender unplugged, I ran:
pi@raspberrypi:~ $ ping 192.168.1.11
which yielded:
PING 192.168.1.11 (192.168.1.11) 56(84) bytes of data.
From 192.168.1.10 icmp_seq=1 Destination Host Unreachable
From 192.168.1.10 icmp_seq=2 Destination Host Unreachable
... and so on continuing the sequence on 192.168.1.10
|
|
|
|
Post by SDL on Apr 1, 2021 14:40:12 GMT -8
Now that's pretty weird.
That looks like some kind of problem with your router. You ping 192.168.1.11 and it responsds with that? Do you have anything on 192.168.1.10?
BP
|
|
