Emoncms version low-write 9.8.28 Stable was installed, after pressing the EmonBase update button and restarting, the following error has now occurred: Inputs Nodes Value only rssi
an old Image Backup with Emoncms version low-write 9.8.7 works,
after the update to Emoncms version low-write 9.8.28 Stable the error returns.
about help I would be grateful
Server Information
Oh dear, there’s a couple of issues I can see in addition to the obvious problem of the Mosquitto service failing.
For some reason all the mqtt data is being published at a per key topic level but all the power and voltage data is being published to the rssi topic. This is why you are not seeing any other input data in emoncms and most likely the reason you are seeing inputs with numeric keys created by the per node level mqtt. I’m not sure these should both be used in parallel if they are both being processed in emoncms.
Additionally I can see there are transmissions being sent out via the RFM2Pi, there is not enough log to see what they are, but I can see a couple of “ack” confirmations, is your system configured to send data out over the RFM network? eg emonGLCD (not that those packets use ack’s). More log would be useful, please attach or copy in-lne the text rather than pictures of text.
Apologies @Luiflm2, I missed the issue you highlighted there with the rssi advancing across several inputs. I’ve implemented a fix which is now available via emonpi update.
@TrystanLea, after the update today the error has been fixed.
but now a new error has been added, under Node-Red the EMONCMS flows are no longer working.
Yes, I think that would be a good move, none of the above addresses the “confirmed sent packet size: → ack” entries in the log snippets either.
I think that partially depends on which button you use, the “update emonpi” button will install/update node-red-node-emoncms via npn, where as the “update rfm69pi” button won’t. (see Update EmonPi Button or Update EmonBase Button? - #15 by pb66). So as I expect the “update emonpi” to have been used, I now wonder why a change would be pulled in on the last update when the previous update was only on Monday. Has the node-red stuff changed again since then?
sorry for my late answer, node-red-node-emoncms was actually updated from version 0.0.15 to 0.1.0, it behaves differently.
Data Type must be changed if necessary
all errors have been fixed.
Thanks for your fast help, you are great!
@Luiflm2 - I’m still intrigued by the “confirmed sent packet size: → ack” entries in the log snippets. Can you please confirm if these still exist and/or if they were expected, ie do you knowingly have data transmitted over RFM from the emonPi/emonBase?
@pb66 Paul, some used sensors are replicas of nathan chantrell TinyTX3, they ask as far as I can remember if the data package arrived. RFM69Pi V3 on my EmonBase confirms the received package.
Have these sensors been running for over 4,5 years now.
Ahh ok! that makes sense. So they are just confirmations that the ack’s to received packets have been sent by the RFM. The message text could do with some editing in that case. The current log message is derived from seeing the “send” confirmations being in the format of “4b” to tell us a frame of 4 bytes was sent so “confirmed sent packet size: → 4b” made sense, apparently less so for an ack confirmation.
[this is another note to self, i can revise the messages if I know the full range of utilization]
In theory, it should, by default, work the same but offer different functionality. Can you tell me what it defaulted to and what you needed to do to make it work please?
The Emoncms node is preset to Data Type Legacy Processing, it didn’t fit on every flow, I had overlooked the fact that it was a new version.
after I had the hint from you the settings could be done with little effort.
I can only repeat, you guys are really great.
