Running a command will eventually result in a error

[RRplofkip]

Whenever I run the command meshcli -D, it will always result in an error saying:

DEBUG:meshcore:Sending device query command
DEBUG:meshcore:Sending raw data: 1603
DEBUG:meshcore:Waiting for events [<EventType.DEVICE_INFO: 'device_info'>, <EventType.ERROR: 'command_error'>], timeout=5.0
ERROR:meshcore:Error while querying device: Event(type=<EventType.ERROR: 'command_error'>, payload={'reason': 'no_event_received'}, attributes={})

I know for sure the device is connect, because the terminal says that the device is connected succesfully. I have tested the node with the web client AND the ios app and those both work.

What is causing this problem and how can I fix it, or is it a fault in the code?

[fdlamotte]

I'd need more context to help you ...

what OS are you on ? is that a nrf or esp device ? which version of meshcore-cli, of meshcore_py ? could you give me the whole trace (especially the part where it says it's connected) ?

device info is the second command issued, so it would be interesting to know how appstart resulted ...

Here is the log of a T114 while pairing and issuing first commands, so you can spot any difference ...

DEBUG:meshcore:Connecting with client: None, address: C2:2B:A1:D5:3E:B6, device: None
DEBUG:meshcore:Connecting using provided address
DEBUG:meshcore:Attempting BLE pairing with PIN
INFO:meshcore:BLE pairing successful
INFO:meshcore:BLE Connection started
DEBUG:meshcore:Connected successfully: C2:2B:A1:D5:3E:B6
DEBUG:meshcore:Sending appstart command
DEBUG:meshcore:Sending raw data: bytearray(b'\x01\x03      mccli')
DEBUG:meshcore:Dispatching event: EventType.CONNECTED, {'connection_info': 'C2:2B:A1:D5:3E:B6'}, {}
DEBUG:meshcore:Waiting for events [<EventType.SELF_INFO: 'self_info'>], timeout=5.0
DEBUG:meshcore:Received data: 05011616098674bee7421d4c2fb8fa2ff0c5b0f1f7734210a80a7c17b96d6c4321d77edd000000000000000000000000f2440d0024f40000080746313134
DEBUG:meshcore:Dispatching event: EventType.SELF_INFO, {'adv_type': 1, 'tx_power': 22, 'max_tx_power': 22, 'public_key': '098674bee7421d4c2fb8fa2ff0c5b0f1f7734210a80a7c17b96d6c4321d77edd', 'adv_lat': 0.0, 'adv_lon': 0.0, 'multi_acks': 0, 'adv_loc_policy': 0, 'telemetry_mode_env': 0, 'telemetry_mode_loc': 0, 'telemetry_mode_base': 0, 'manual_add_contacts': False, 'radio_freq': 869.618, 'radio_bw': 62.5, 'radio_sf': 8, 'radio_cr': 7, 'name': 'F114'}, {}
DEBUG:meshcore:Sending device query command
DEBUG:meshcore:Sending raw data: 1603
DEBUG:meshcore:Waiting for events [<EventType.DEVICE_INFO: 'device_info'>, <EventType.ERROR: 'command_error'>], timeout=5.0
DEBUG:meshcore:Received data: 0d08af0a0000000032204f63742032303235000048656c7465632054313134000000000000000000000000000000000000000000000000000000000076312e392e310000000000000000000000000000
DEBUG:meshcore:Dispatching event: EventType.DEVICE_INFO, {'fw ver': 8, 'max_contacts': 350, 'max_channels': 10, 'ble_pin': 0, 'fw_build': '2 Oct 2025', 'model': 'Heltec T114', 'ver': 'v1.9.1'}, {}
INFO:meshcore:Connected to F114 running on a v1.9.1 fw.```

[RRplofkip]

I am on Windows 11 version 25H2 and I am using VScode. The device is a Heltec V3.2 LoRa module (this one) so it is a esp device. The meshcore-cli version is v1.2.7 it says (when executing: meshcli -v), although on github the latest version is v.1.2.0, I am not exactely sure what the meshcore_py version is but I downloaded the latest one so it must be v2.0.0.

The complete log when executing the command meshcli -D is:

INFO:meshcore:Searching first MC BLE device
INFO:meshcore:Found device MeshCore-1C479EEC 10:20:BA:62:04:ED
DEBUG:meshcore:Connecting with client: None, address: 10:20:BA:62:04:ED, device: 10:20:BA:62:04:ED: MeshCore-1C479EEC
DEBUG:meshcore:Directly using a passed device.
INFO:meshcore:BLE Connection started
DEBUG:meshcore:Connected successfully: 10:20:BA:62:04:ED
DEBUG:meshcore:Sending appstart command
DEBUG:meshcore:Sending raw data: bytearray(b'\x01\x03 mccli')
DEBUG:meshcore:Dispatching event: EventType.CONNECTED, {'connection_info': '10:20:BA:62:04:ED'}, {}
DEBUG:meshcore:Waiting for events [<EventType.SELF_INFO: 'self_info'>], timeout=5.0
DEBUG:meshcore:Sending device query command
DEBUG:meshcore:Sending raw data: 1603
DEBUG:meshcore:Waiting for events [<EventType.DEVICE_INFO: 'device_info'>, <EventType.ERROR: 'command_error'>], timeout=5.0
ERROR:meshcore:Error while querying device: Event(type=<EventType.ERROR: 'command_error'>, payload={'reason': 'no_event_received'}, attributes={})

An appstart results in:

INFO:meshcore:Scanning BLE for device matching
INFO:meshcore:Found device MeshCore-1C479EEC 10:20:BA:62:04:ED
INFO:meshcore:BLE Connection started
ERROR:meshcore:Error while querying device: Event(type=<EventType.ERROR: 'command_error'>, payload={'reason': 'no_event_received'}, attributes={})

Maybe the problem lies by me because I am just starting out with meshcore and the cli version written in python so it could be that I overlooked something.

[fdlamotte]

The versions are ok, pip versions are ahead of github releases (I release often on pip to deploy on my own machines, but not so much on github ;)). I'm at 1.2.14 but 1.2.7 should be ok.

I can't guarantee anything on windows as I don't have machines with that os (I have more testers on macs), from what I've read it works better using WSL, I also know some people manage to use it directly on windows.

From your trace it seems there is no data passing between the firmware and mccli. Is everything ok with pairing ? I have absolutely no idea how it is handled on windows and how it should behave, sorry for that ...

[fdlamotte]

Don't hesitate to come on the dedicated channel on the meshcore discord to discuss this kind of issue

https://discord.com/channels/1343693475589263471/1355633129385099404

There might be some windows users there which had the same issue ...

[fdlamotte]

I was thinking about your issue ...

And you state you use v2.0 of meshcore_py ... that's a very old version (from july 19) as I do my releases on pip (and last version there is 2.1.24 ...

I strongly advise to use pip or pipx to install meshcore_py and meshcore_cli, as they take care of the dependencies from the pyproject.toml files.

If you're on an old version of the lib, I'm really surprised that you can even launch meshcore-cli ... that's why I didn't give any credits to that trail...

I've just draft a release for 2.1.24 and I'd advise you to use both 2.1.24 for meshcore_py and 1.2.14 for meshcore-cli (1.3 will be released shortly, it will be very close to 1.2.14). You can also use the git versions of both projects as they are normally in sync

[RRplofkip]

O okay, that could have been it but I was running in the wrong installation since I have installed it both from github and from pip. I have now tested mesh_cli with te pip version so the meshcore_py is also up to date. However I get the same error so I will ask it on the meshcore discord page.
Thank you for the quick reactions!

[sillevl]

I think I might have been experiencing the same problem...
I am using meshcli v1.3.3
Tested this on at least 4 differen Heltec V3 boards. I have the exact same results on Windows 11 as on Linux (Debian13). I tried different USB ports, with or without an USB hub. Different cables,...

Sometimes it works great after flashing the firmware, with erase all (not sure if this has an impact on the results). But as soon as i reboot the node, even without making any configuration changes, it just stops working.

meshcli -s /dev/ttyUSB0 -b 115200 -D
DEBUG:meshcore:port opened
INFO:meshcore:Serial Connection started
DEBUG:meshcore:Connected successfully: /dev/ttyUSB0
DEBUG:meshcore:Sending appstart command
DEBUG:meshcore:Sending raw data: bytearray(b'\x01\x03      mccli')
DEBUG:meshcore:sending pkt : b'<\r\x00\x01\x03      mccli'
DEBUG:meshcore:Waiting for events [<EventType.SELF_INFO: 'self_info'>], timeout=5.0
DEBUG:meshcore:Dispatching event: EventType.CONNECTED, {'connection_info': '/dev/ttyUSB0'}, {}
DEBUG:meshcore:Sending device query command
DEBUG:meshcore:Sending raw data: 1603
DEBUG:meshcore:sending pkt : b'<\x02\x00\x16\x03'
DEBUG:meshcore:Waiting for events [<EventType.DEVICE_INFO: 'device_info'>, <EventType.ERROR: 'command_error'>], timeout=5.0
ERROR:meshcore:Error while querying device: Event(type=<EventType.ERROR: 'command_error'>, payload={'reason': 'no_event_received'}, attributes={})

[fdlamotte]

@sillevl

The original issue is about a connexion issue on a BLE companion

But you are connecting through USB and if you're using linux this should be a lot more straightforward than ble

From your log I see that meshcli tries to query the device but there is no response. The first idea that comes to mind in this case (as there is no ble involved) is that you don't have a serial firmware on your heltec (maybe a ble one ?). I get the exact same log when I use an USB/TTL converter with nothing at the end ...

What puzzles me is you say it works until a reboot ... in which conditions ? does it work with the web client (you should be able to connect to serial node via web client) ?

Maybe the nodes keeps using the same serial port used for flashing when the fw starts after flashing and changes at reboot (and wait on Serial1 or Serial2 instead of the normal Serial ?) in this case it is an issue on the firmware side, but I've never seen this kind of behaviour

[fdlamotte]

I've ran into issues as my bleak version upgraded to 2.0

I've forced to use version < 2.0, but I'll have to deal with that

Maybe that's the same issue, some incompatibility with newer versions of bleak ?