--MeshTalk-- used to be displayed.

Describe the bug
Crashes when viewing nodes

To Reproduce
Open meshwatch, press N to view nodes

Screenshots

  karl@mini  ~  130  python3 meshtastic/meshwatch/meshwatch.py


--------------------------------------------------------------
ERROR - Function ( Clear ) has encountered an error.
prefresh() returned ERR


TRACE
Traceback (most recent call last):
  File "meshtastic/meshwatch/meshwatch.py", line 431, in Clear
    self.TextPad.refresh(0,0,self.y1,self.x1,self.y1 + self.rows,self.x1 + self.columns)
_curses.error: prefresh() returned ERR



Additonal info: erasing textpad


--------------------------------------------------------------


Good by for now...

Desktop (please complete the following information):
meshtastic version: 1.2.80
meshwatch version: latest:

commit a0f856c (HEAD -> main, origin/main, origin/HEAD)
Author: riddick [email protected]
Date: Tue Dec 28 21:56:15 2021 +0100

Update meshwatch.py

fix for recent meshtastic version, tested with 1.2.46

Hi, is it possible to receive on a much smaller screen using just the messages "window" screen?
I'm building a device like beepberry that'll be connected throught USB to meshtastic station G1. The code is working through SSH but the screen size of the device is way to small to show all the info. Preferably I'd like to use just the message feature (receive - decode - print on a screen) and send message.

MyNodeInfo in the packet display does not show the parent name

When connection to the device breaks, error messages leak over the interface from the Debug window position (cursor), covering the Messages window and any existing text.

Possible solutions:

• relocate the prompt to the bottom of the screen before the API call;
• or contain the error message within the Extended Information window;
• or relocate de Debug window to the bottom of the screen, in a way that errors don't cover sensitive information.

Example:

Sendmessage crashes now that we are using curses.
Make sure the main function area skips the curses section when sending a message from the command line. Simply send, report, exit.

Pressing 'L' to Show Logs gives an error in the Extended Information window:
Could not open /var/log/kern.log.

Mac OS 14.2.1

No run with upgrade of Meshtastic from 1.2 to 1.3

Always was run very well with my TTGO with firmware Meshtastic 1.2. I put firmware 1.3 ...

Nothing run.

ERROR - Function ( main ) has encountered an error.
Timed out waiting for connection completion

TRACE
Traceback (most recent call last):
File "/home/admin/meshtalk/meshwatch.py", line 1621, in main
interface = meshtastic.serial_interface.SerialInterface()
File "/usr/local/lib/python3.9/dist-packages/meshtastic/serial_interface.py", line 55, in init
StreamInterface.init(self, debugOut=debugOut, noProto=noProto, connectNow=connectNow)
File "/usr/local/lib/python3.9/dist-packages/meshtastic/stream_interface.py", line 48, in init
self.connect()
File "/usr/local/lib/python3.9/dist-packages/meshtastic/stream_interface.py", line 72, in connect
self._waitConnected()
File "/usr/local/lib/python3.9/dist-packages/meshtastic/mesh_interface.py", line 401, in _waitConnected
raise Exception("Timed out waiting for connection completion")
Exception: Timed out waiting for connection completion

Additonal info: Main function

Good by for now...
1

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

Status indicator has stopped functioning. Make sure it is updated when the device responds to requests or receives packets.

Build better documentation.

Describe the bug

Users reported that while running in a terminal window N and I functions result in error:

ERROR - Function ( Clear ) has encountered an error.
prefresh() returned ERR

TRACE
Traceback (most recent call last):
File "./meshwatch.py", line 430, in Clear
self.TextPad.refresh(0,0,self.y1,self.x1,self.y1 + self.rows,self.x1 + self.columns)
_curses.error: prefresh() returned ERR

Additonal info: erasing textpad

Note from another user regarding curses:
ksamson
2d
For those having stability issues, I happened to trip over this:
curses — Terminal handling for character-cell displays — Python 3.10.0 documentation 2
A bug in ncurses, the backend for this Python module, can cause SegFaults when resizing windows. This is fixed in ncurses-6.1-20190511. If you are stuck with an earlier ncurses, you can avoid triggering this if you do not call addstr() with a str that has embedded newlines. Instead, call addstr() separately for each line.

Would be great to connect via TCP/IP interface over WiFi, besides Serial.

Seems to work replacing code line 1482: interface = meshtastic.SerialInterface()
with: interface = meshtastic.TCPInterface("192.168.1.X")

Hope it is a good start for others interested in doing the same.