Wismesh Pocket - Critical Fault #3

Hi,

I got my Wismesh Pocket a couple of weeks ago, and it was working without issues until the beginning of the week when I noticed it stopped and saw on the screen “Critical Fault #3.” I did some searching here and followed the advice to use the web flasher and to make sure to also erase the flash.

After erasing the flash and reinstalling the firmware, the unit is now “deaf” it does not see any other nodes. I tried to use another device to the messages and it worked fine, but it is like the Wismesh pocket sensitivity now is really low for some reason. But even leaving the node on my window, where it was working, it no longer receives anything.

Is there anything else I can do to further troubleshoot without specialized equipment?

I have the normal equipment, serial cables, programmers, Jtag adapters, soldering irons, and other things that may be a little bit more useful, like a hackrf and a nanovna.

I also have a tigard (Tigard | Crowd Supply) that I can use to hook to the board if necessary, but I’m not sure what else to do now.

I would appreciate any suggestions!

Thanks in advance!

Hi, Not sure if this is exactly what’s going with yours but 2 things cometo mind. The first is easy. Navigate to the LoRa settings and in “Frequency Slot” put in the number for the frequency slot of your country rather than the default value.
If that doesn’t seem to be working, there is a difference with firmware that puts channels somewhere else. I haven’t had time to run it down but if you connect 2 nodes to a MQTT broker, I’d be willing to bet you’d see one of them publishing to a topic c/LongFast and the other will be e/LongFast. This would also translate to something different on the RF side I’m sure but I have not had the time to run it down. The way I’ve been able to fix this is by flashing all the nodes with the same firmware version and be mindful of the “stable” and “Alpha” versions. This will get them all on either E or C and they should talk to each other. Hope this helps.

Critical Fault #3 has absolutely nothing to do with MQTT.