One of my inputs has not updated since 2.3 days (since Saturday noonish). I can see emonesp sending updates as well as I can see my local emonbase reading updates for that sensor. Its CT4 (EV charging), CV1,2,3 as well as temperature etc update emoncms.org normally. Also updating inputs list takes quite some time even after deleting many of the inputs…
Is something going on with Emoncms.org or where to look for an explanation?
Here is what emonesp sends out:
2021-06-01T16:53:35.002Z {“ct1”:328,“ct2”:121,“ct3”:688,“ct4”:11,“vrms”:520,“pulse”:0,“t0”:163,“freeram”:28016,“srssi”:-86,“psent”:5560,“psuccess”:5187}
Hello @PetriK I cant see anything specifically out of place but I have restarted the input processors just in case it’s got caught in the limiter. Has that made any difference?
Thanks Trystan,
Unfortunately it did not help. I think this is an issue after input processor as I can read the updated value from emoncms.org using the API. I am OK for you to have a look at my data if you wish.
Ok great to hear, I did just push a fix a couple of days ago that should have sorted the device already exists error but it looks like it may not have worked yet, there’s another thread here discussing the same thing "device already exists" ajax async errors perhaps? - #6 by TrystanLea would you be able to check the script timing I mentioned in my reply in that thread?
Hello @PetriK I’ve removed the duplicate inputs on your account and setup some extra logging to see if I can catch what is causing this issue. If you can remind me here when you next see an issue on your account that would be really useful.
Edit looks like it happened immediately after your fix as my log says 3 days ago @TrystanLea
This is emontx and emonesp to emoncms. I am also sending data to homeassigant using mqtt and dont see anything particular there so the serial line seems to be working.
Thanks @PetriK I can see the entries here in the log, I will look into why EmonESP is passing these through. Which version of EmonESP do you have there?