10/18/2023 Map Stopped Working?
Visit this post for the fix
This appeared when I rebooted... The LEDs appear to have quit during the screen wipe.
builtins.AttributeError
AttributeError: 'NoneType' object has no attribute 'split'
Traceback (most recent call last)
-
File "/usr/lib/python3/dist-packages/flask/app.py", line 2309, in
__call__return self.wsgi_app(environ, start_response)
-
File "/usr/lib/python3/dist-packages/flask/app.py", line 2295, in
wsgi_appresponse = self.handle_exception(e)
-
File "/usr/lib/python3/dist-packages/flask/app.py", line 1741, in
handle_exceptionreraise(exc_type, exc_value, tb)
-
File "/usr/lib/python3/dist-packages/flask/_compat.py", line 35, in
reraiseraise value
-
File "/usr/lib/python3/dist-packages/flask/app.py", line 2292, in
wsgi_appresponse = self.full_dispatch_request()
-
File "/usr/lib/python3/dist-packages/flask/app.py", line 1815, in
full_dispatch_requestrv = self.handle_user_exception(e)
-
File "/usr/lib/python3/dist-packages/flask/app.py", line 1718, in
handle_user_exceptionreraise(exc_type, exc_value, tb)
-
File "/usr/lib/python3/dist-packages/flask/_compat.py", line 35, in
reraise
raise value -
File "/usr/lib/python3/dist-packages/flask/app.py", line 1813, in
full_dispatch_requestrv = self.dispatch_request()
-
File "/usr/lib/python3/dist-packages/flask/app.py", line 1799, in
dispatch_requestreturn self.view_functions[rule.endpoint](**req.view_args)
-
File "/NeoSectional/webapp.py", line 892, in
startup1temp = url.split('/')
AttributeError: 'NoneType' object has no attribute 'split'
To switch between the interactive traceback and the plaintext one, you can click on the "Traceback" headline. From the text traceback you can also create a paste of it. For code execution mouse-over the frame you want to debug and click on the console icon on the right side.
You can execute arbitrary Python code in the stack frames and there are some extra helpers available for introspection:
dump()shows all variables in the framedump(obj)dumps all that's known about the object
Hi Steve, this will happen if you try to re-run the web interface using the last URL in the address bar after reboot. When you reboot the connection is lost but the URL in the browser will still show something like; http://192.189.2.3:5000/reboot.
If you remove the 'reboot' part of the URL before refreshing the browser, all will be well.
I went back in to see if there was another way to keep this from happening and I believe I found an answer. I'll have to test this a bit and it will be part of the next update. - Mark
I'm leaving a note here (and other help threads where I've been frustrated) in case it helps someone. I re-did all of the electronics and now appear to have solid reliability and consistent operation. I strongly believe that the basic jumper set had very poor crimped connections and this made for some intermittent and weak connections. I shortened all wire runs and used solid core wire for many components. For those situations where using the jumpers remained beneficial, I took off the black shielding with a needle and touched a tiny bit of solder to each wire connection and replaced the shielding. Any connection that didn't FEEL solid, got a light squeeze with a crimper before pressing onto the terminal. I also had an unnecessarily-long run for the LED data line, and this seemed to create a host of issues. Shortened and tightened and all appears well! Bottom line, TIGHT and short connections are very necessary for a bulletproof project.
Thanks Steve, that's great advice. - Mark
