This weekend I got round to putting the EmonTx / base / EmonTh (x6) equipment that i purchased into service. Had a few challenges along the way, but now have everything up and running, showings as nodes, and feeds setup based on selected inputs. Thumbs up all round.
Almost, but Not quite.
So when i get to look at the logged data in detail, i notice that i’m getting lots of data dropouts (values show as NAN when i view CSV of graphs) on all my nodes. But there seem to be different reasons depending on on the node.
What happens here, is that everything seems to log ok for about 20-30 minutes, and then i get a data gap of about 20-30 mins. When i inspect the debug log it appears that the data is still be received & processed (RFM2Pi shows frame data, timestamp, values etc) and appears to be published (MQTT publishing for all values), however no data appears to being logged and there are gaps in the plotted data sets. Whilst writing this, i went to check and another gap had appeared. I then viewed the log; changed log mode to Error, then back to debug - and when I went back to my graphs, data was being logged again. Any ideas on what is happening or why ?
I have 10 feeds setup to track P1, P2, P3, kWh for the same, Vrms, and daily max / min for Vrms and daily min for P1. Scans are setup for every 5sec.
The dropouts here seem to be being caused by transmission dropouts. Whereas for the EmonTx i get an rssi of ~ -65, those for the EmonTh are closer to -78 to -85. My thinking here is that the issue is with signal strength more than anything else. Given that the max (linear) distance from the base unit to a 'Th is about 6m I am surprised. Certainly for some of the 'Th units, the lack of data corresponds to there being no RMF2Pi data for that node in the log. Any suggestions on how to improve the signal strenght from the 'Th’s ?
I am logging Temp / humidity from each 'Th at an interval of 30 sec.