John Walicki
Good point, I often use `miniterm` and `screen` but agree that the dialout group permissions are necessary. I'll add some words about it.
I've been seeing random panics on an ESP32 as well. Running PubSubClient and MQTT to Watson IoT Platform. It will run for many hours or just a few minutes. Then...
My ESP32 was panicking because of a faulty PCB board that was causing random brown outs. It wasn't an issue with PubSubClient or MQTT
@chughts For your consideration and review.
This discourse conversation was also a clue. https://discourse.nodered.org/t/stuck-with-text-to-speech-watson-node/81211
The rabbit hole was deep as I tried to determine why axios versions were affecting node-red-node-watson (which doesn't have a direct dependency on axios) https://github.com/axios/axios/issues/5072
The final clue was a comment here https://stackoverflow.com/questions/75642251/using-require-axios-and-vrchat-i-get-error-err-package-path-not-exported-pa which said: ``` This error usually occurs when there is a mismatch between the version of the axios package and the version...
Thanks @chughts for the review. FWIW - the `ibm-watson` axios dependency was bumped in [ibm-cloud-sdk-core](https://github.com/IBM/node-sdk-core/releases) a few months ago.
Thanks @chughts - The new release looks good.
This is a real problem and is not solved. I recommend this issue should be re-opened.