Hi,
I am trying to implement a 433mhz to MQTT gateway for an OpenHab system that I have had running for many years. I am experiencing a few issues.
The gateway is built on a TTGO Lora32 board and I have installed LilyGo 433RTL on the board … all good. The setup was easy and it all went smoothly.
Issues:
The board restarts about every 50 minutes - I have watched freemem and freestck - these both see quite stable. About every 2 days, the gateway just locks up requiring a power cycle. I have reflashed the board after a full erase AND tried the latest dev version - all with the same result.
Every few minutes, the gateway publishes some ‘rubbish’ to one of the topics I use for monitoring temperature sensors. This generates an error in OpenHab due to a failed JSONPATH transform.
Message example
Executing the JSONPATH-transformation failed: Invalid path ‘$.battery_ok’ in ‘{“model”:“Springfield-Soil”,“Soil”:5,“channel”:113,“nnel”:1,“tery_ok”:1,“nsmit”:25.9,“emperature_C”:67,“e_C”:0,“sture”:“ton”," Moisture":-65,“ture”:1154000}’
The topic is actually Conrad-S3318P (that the gateway decodes correctly most times). I also see lots of strange topics for devices that I do not have and can find no source for (eg Rain gauges, smoke detectors etc). The payload sometimes looks valid - other times it is corrupted (like the above).
I have tried everything I can think of - so any suggestions would be appreciated very much.
Thanks
Will do.
I’m just trying another board (exactly the same type) and it seems different - it is reporting different sensor types - they actually make more sense. I’ll see if it is stable and report back. I’m running it in parallel on a different base topic.
If you this issue relates to the hardware I selected, what hardware would you recommend for best stability and range? I’m happy to purchase whatever will work best.
I haven’t tried putting the development version into the production environment where OpenHAB is subscribed to its topics.
I did however put version 1.6 on my testing board to monitor stability (in my RF environment) and found that it too randomly restarts about every 3000 to 6000 seconds and then after some time (overnight ) goes unresponsive.
Just a little more info on this issue. I have just noticed that when I have two boards running (one on version 1.6 and one on v1.7) - they both reboot that the same time (within about 5 seconds). This suggests that the issues relates to some 433mhz RF signal that they are both receiving. Unfortunately, I have no way of knowing what that signal is or from where it originates. There are about 45 different 433mhz sources within my environment.
This is a screen shot from MQTT Explorer, Note the highlighted line - published to a Esperanza-EWS topic. It contains data from a Conrad-S3318P device (that I do have). Could this point to an issue?
I have installed the dev version and had it running for about 6 hours. I have not seen any corruption in the MQTT topics so far, but it has published a lot of topics for devices I don’t have, and the LilyGo has rebooted 12 times.
I have had the dev version running for some time now. I have not seen any corrupt data, but the board still re-boots at least every hour (sometimes 5 or 6 times within a few minutes) and locks up every couple of hours. I still see lots of MQTT topics for devices I don’t have.
Of course, you have several possibilities to get the serial logs (from the easiest):
With your board connected by USB
ESP Tool
Select 115200 as baudrate, connect and start the console. You will see the logs.
Arduino IDE Tools-> Serial Monitor (select 115200)
PlatformIO, even if PIO is easier for developing or building , regarding the serial monitoring it involves a few more steps than the solution above, so this is why I add it as the last option
Download VSC visual studio code
Add PlatformIO extension
Click on the serial button
Once your board is connected and sharing serial logs, the goal is to capture and share a restart.
Note the first solution may not be ideal if the reboot occurs after several hours; I haven’t tested it for a long time.
Just an update on this - sorry it has been a few days, I have been away.
I have installed the latest dev version (7a3fae) on a second board (so I can keep it close to a serial port). It has been up for 4 hours with no issues.
I will report back again tomorrow.