Cannot receive message

[Lentrave]

I know the problem is describes as a know issue in the node-red module page. It said to increase the fetch interval but it dont work . i can send message but cannot receive. Try update the fetch to 10000ms with no improvment. Any way to make it work ?

[danpeig]

Connect using the device web interface and if it is working, disconnect and try again. Ensure you don't have any other device connected to Meshtastic radio like the mobile phone app.

[Lentrave]

i try using Wifi and serial ans same problem. i can connect to the web interface using serial and wifi. Also try different device, Helvec V3 and Rak 4631.

[danpeig]

In the example flow, there is one node that does the log output. Enable it and go to the debug tab to see if the device is receiving other packets...

[Lentrave]

edit: I run a seperate nodered in a docker and now it dont crash with the test flow, but same problem, i can send message but no message can be received and nothing came in debug from the log flow.

it dont work, it is even worst. each time the node reveive a message nodered crash. i erase all the flow i made to run only the test flow .

[danpeig]

I am working on version 3.1 that should catch Meshtastic Web errors without crashing Node-RED. Please give me a couple days to finish it.

[Lentrave]

I made some progress. I think all of that is cause by high memory use on the ESP-32 (Heltec V3) with the WiFi and Bluetooth activated. With both enable and the client open it peak to 95%. Disabling Bluetooth save around 15-20% of memory use. Now I connect the Node-Red Flow, I open a web client and close it and now I can send and receive using Node-Red. I keep the fetch at 5 seconds because it seem to work, if I see high usage again I will increase it. The Node-Red crash is still present (with the instance running on a Raspberry Pi) but work without crash with Docker on Windows.

[danpeig]

Great news! I see my ESP32 devices struggling with TLS encryption as well.

Working on the crashes...

[danpeig]

OK, version 3.1 is out...
I tried to catch all errors that could cause Node-RED to crash.

There is very little I can do regarding the Lora devices firmware. Hopefully they get optimized and leaner...

[danpeig]

Did you mapped the ports when creating the container? If the ports are not properly mapped and with the correct permissions you can't use them.

[Lentrave]

Did you mapped the ports when creating the container? If the ports are not properly mapped and with the correct permissions you can't use them.

i remove the comment because i just mistype the path of the port. It's not on docker , on the raspberry pi. I have no more error but cannot use it on raspberry Pi anyway. I must open a serial client before i can send message using nodered, but was unable to install meshtastic python cli, no desktop environment, and text base web broser dont support javascripr so i'm stuck.

[Lentrave]

I have a question for you @danpeig. Is it possible to extract all the data from the packet like hopLimit, gatewayId and things like that? thanks

[danpeig]

I have a question for you @danpeig. Is it possible to extract all the data from the packet like hopLimit, gatewayId and things like that? thanks

Yes. Some packets are decoded by Meshtastic Web and will come out as JSON objects. Others will be delivered encoded and you will have to do some post-processing.

[Lentrave]

I have a question for you @danpeig. Is it possible to extract all the data from the packet like hopLimit, gatewayId and things like that? thanks

Yes. Some packets are decoded by Meshtastic Web and will come out as JSON objects. Others will be delivered encoded and you will have to do some post-processing.

so for message packet we cannot exrtract those value?

[danpeig]

Message packets are fully decoded, the node will output full JSON data if needed.