The old CPU speed on the oled display has been replaced with “ChUtil” or channel utilization. This will show how much traffic there is on your channel, both from your mesh and any other lora traffic that may interfere (other meshes, helium, lorawan, etc).
I made a post yesterday about Tbeam FW 1.2.50 not found in Android 7 mestastic APP from 1.2.45 to 1.2.50 / 51. Remove the post hour later because it solved. This morning upgrade to latest FW and APK Tbeam FW 1.2.50 + meshtastic 1.2.52 trouble is back and not fantastic
Android 7.0 pair BT Tbeam and APP meshtastic APP 1.2.52 also see device, but not give access to Tbeam device some reason not clear
Same as yesterday after upgrade to mestastic APP from 1.2.45 to 1.2.50 / 51.
I solve it yesterday to roll back FW Tbeam to early versions and upgrade every version from start but i think not the way.
How do i ADD pictures to post?
Ever since updating to 1.2.50 when using the python cli, most commands return the below posted output. Checking Version or such work, however it reports 1.2.48 instead of 1.2.50.
$ meshtastic --port COM5 --nodes
Traceback (most recent call last):
File “C:\Users\Mark\AppData\Local\Programs\Python\Python310\Scripts\meshtastic-script.py”, line 33, in
sys.exit(load_entry_point(‘meshtastic==1.2.48’, ‘console_scripts’, ‘meshtastic’)())
File “C:\Users\Mark\AppData\Local\Programs\Python\Python310\lib\site-packages\meshtastic_main_.py”, line 833, in main
common()
File “C:\Users\Mark\AppData\Local\Programs\Python\Python310\lib\site-packages\meshtastic_main_.py”, line 635, in common
client = meshtastic.serial_interface.SerialInterface(
File “C:\Users\Mark\AppData\Local\Programs\Python\Python310\lib\site-packages\meshtastic\serial_interface.py”, line 52, in init
self.stream = serial.Serial(devPath, 921600, exclusive=True, timeout=0.5, write_timeout=0)
File “C:\Users\Mark\AppData\Local\Programs\Python\Python310\lib\site-packages\serial\serialwin32.py”, line 33, in init
super(Serial, self).init(*args, **kwargs)
File “C:\Users\Mark\AppData\Local\Programs\Python\Python310\lib\site-packages\serial\serialutil.py”, line 244, in init
self.open()
File “C:\Users\Mark\AppData\Local\Programs\Python\Python310\lib\site-packages\serial\serialwin32.py”, line 64, in open
raise SerialException(“could not open port {!r}: {!r}”.format(self.portstr, ctypes.WinError()))
serial.serialutil.SerialException: could not open port ‘COM5’: FileNotFoundError(2, ‘The system cannot find the file specified.’, None, 2)
I found some ‘bugs’ in firmware-1.2.50 when I activate the node as WiFiAP.
The node is a LilyGo T3-1.6.
Sometimes the webserverIP is 192.168.4.1 but mostly it is 192.168.42.1
(Maybe because I have a ESP8266 device that also use 192.168.4.1 for configuration?)
Sometimes, just after activating the WiFi AP, the node get very slow and even can reset itself, the node will then come back as IP 0.0.0.0 and needs a push-reset-button.
Getting in WiFi mode on a Android(8.0) phone or on a Win10 tablet is slow and difficult (maybe browser issues)
On a linux laptop in Chromium it works best for me, the connection stays stable.
On the UI:
When I choose the ‘nodes’ button nothing happens, blank screen, need to go to previus page.
In the message screen the time stamp always is the same 01:00 AM.
Hi,
I see that the ChUtil is varying a lot even after some power on time ( from 0…22%). Is it calculated only for the last minute or so? If yes, wouldn’t it be better to have a longer time average?
Just a thought…
Thanks.
There’s nothing in the code that would make it listen to 192.168.4.1.
We picked 42 because that’s to the answer to life the universe and everything.
In AP mode, try going to 192.168.42.1/json/report on your device. That’s an internal page served by the web server. If you can get to that, then you know the device is functioning normally.
