emonTx data disappeared

[pb66 (Paul)]

@djh

One thing I did notice were three new unknown nodes on the input page, but I’ve no idea when they were generated since I don’t normally look at that page. Incidentally, it’s very tedious deleting each input one at a time until eventually the node winks out of existence. Is there any way to delete the entire spurious node more simply?

Phantom (and duplicate) inputs can be dealt with the same way, using the “clean” input api

@pb66

If you need to, you can use the emoncms/input/clean api to remove all duplicate inputs in one go, to facilitate that option I always make sure I have at least one process on any valid inputs, even if it’s not used as the api call deletes all inputs without a processlist. Unfortunately this isn’t a cure as you still need to be a aware the duplication has occurred (eg feeds stop updating) to alert you to use the api (or automate it via nodered etc)

the api can be called eg by daily cron and any inputs without a processlist will be deleted, so put a redundant process in any legitimate but unused inputs to keep things tidy eg “reset to original” will effective have no effect other than to save an input from deletion.