Recently the data quality posted to Emoncms.org fell from 100% to 91%.
All i have changed is that the board now has M-BUS working @ 2400 baud to a Kamstrup 403 heat meter.
Also, the EmonTxV3 is no longer transmitting data to the heatpump board.
you can see some missing packets around 3:30pm, my heatpump board has an RSSI of -80 its on the edge of WiFi range… I also rebooted my Pi several times yesterday
Interesting, so i took a look and my RSSI is -51.
Similar to my EmonTxV3 @ -48, which is working fine.
I just noticed, when logged into the EmonESP, it suggests packet success is 99.9%.
Could that mean that the board is not generating the messages when required?
Could the newly added comms over M-Bus be interfering with the process in any way?
Is that the sending end or the receiving end, or both?
For a while, it’s been considered a “good idea” to send the data a little more frequently than the database is set to receive it. If the rates are exactly matched, and the data arrives in the middle of its time slot (for the PHPFINA database), all is well. But if it sent at a slightly slower rate - because the timebase isn’t perfect - it will slowly creep towards the trailing end of its slot and then fall into the next one, leaving an empty slot. On the other hand, if it’s sent slightly faster, it will creep forwards and eventually fall into a slot that still contains the previous value. That gets overwritten, you lose it but there aren’t any gaps in the data. I suspect what you’re seeing could be explained in this way.
If it’s the repetition rate, it’s probably OK. If it’s the time between doing its thing (therefore you add the time for that), it may well not be, depending on what it’s doing. I don’t know that software, I’d need to find it and check.
Check the emonhub logs and see if it is actually sending the data within the time slots you expect it to. I noted an issue where by my EmonTH was sending data just (less than half a second) before the EmonTX but that was enough for the data to miss it’s time slot.
Ah, I just noticed you use an EmonESP directly from the heatpump to EmonCMS. Limited scope to debug that I fear.
Is that an EmonESP log or Emoncms log (I do not use either)?
If EmonESP, it shows that the data is not being generated at a regular interval. @glyn.hudson or @TrystanLea will be your best help.
That is the success of the sent messages. If the EmonESP is not generating the message, it will not be measured as a failure.
No it should be regular. My personal suspicion is the ESP module. I have had countless problems with ESPs and Wi-Fi over that last few weeks. My conclusion is that the current Wi-Fi implementation for ESPs is unreliable. You can find a fair bit of chat on this out there.