For now I’m concentrating on achieving reliability with MQTT using the original library and C – and interfacing it to the likes of the Raspberry Pi 2, but it came to my attention for those of you using Lua right now that there seems to be a problem with the new built-in MQTT? Might want to check this out.
4 thoughts on “NodeMCU Broken?”
Comments are closed.
I’ve not tested personally, but apparently this is fixed by upgrading the MQTT broker to 3.1.1
For Mosquito this was done in the latest version 1.4 released on Feb 18 – http://mosquitto.org/
Im using thingbox ( thanks to the heads up from Pete ) its running mosquito 1.3.4 ..so will work out how to update mosquito on it… cmd shell here i come!!!
https://github.com/nodemcu/nodemcu-firmware/issues/237
Seriously broken and generally unstable, wasted my weekend on it. Rolled back to the pre_build 20150212 last night and now all my lua codes runs fine and I dont need to constantly re-flash on the smallest error.
Well, I backed away from it when I realised that they are never going to get past the shortage of RAM. However, stranger things have happened.
The node modules make it o so easy and MQTT a good alternative to exploring other protocols for reliable communication for multi IoTs plus it can be secure. Firing up my Arduino Yun as broker, seeing that MQTT runs on OpenWrt. Not that keen on Linux stuff myself. One can beat the ESP price performance, hopefully they stick more RAM into in in future models.