It's one thing that is holding me back from upgrading my FLM: the prospect of potentially lost/discontinued data. I asked about this before but never got a clear answer...
icarus75 |
There is a primitive way to merge your data graphically by keeping your old and new FLM associated with your account. The lines will have different colours when crossing the replacement timestamp. But they should nevertheless both be visible.
petur |
I know the server part is a free service from you, but :(
bazzle |
Can you explain how to show both accounts please. I cant seem to get it to work.
gebhardm |
Bart, if you keep an "old" FLM associated with an account you rather cannot sell it to assign it to a new account and in the same time keep data. So, indeed it would be a nice feature to allow migration.
By TMPO I bet this would even be an option for a user service - download complete TMPO data, optionally transform content to different sensor IDs (the "new" sensors), upload the TMPO data to another account (or the own FLM - to be checked for memory sufficiency, of course).
As a workaround, FLM local TMPO data at least may be saved locally, using scp or WinSCP and archiving all content of /usr/share/tmpo/sensor/ - which, of course, leaves out any data previous to v2.4.x... (but maybe you, Bart, have migrated all db content to the TMPO format and allow this to be taken from the server via REST)
bazzle |
OK. Adding my old "broken" flm number worked.
As above though maybe just allowing to change a flm number to add an suffix (x) would allow a serviceable unit to be resold.
Bart
Is there a merge function available please?
Baz
It's one thing that is holding me back from upgrading my FLM: the prospect of potentially lost/discontinued data. I asked about this before but never got a clear answer...
There is a primitive way to merge your data graphically by keeping your old and new FLM associated with your account. The lines will have different colours when crossing the replacement timestamp. But they should nevertheless both be visible.
I know the server part is a free service from you, but :(
Can you explain how to show both accounts please. I cant seem to get it to work.
Bart, if you keep an "old" FLM associated with an account you rather cannot sell it to assign it to a new account and in the same time keep data. So, indeed it would be a nice feature to allow migration.
By TMPO I bet this would even be an option for a user service - download complete TMPO data, optionally transform content to different sensor IDs (the "new" sensors), upload the TMPO data to another account (or the own FLM - to be checked for memory sufficiency, of course).
As a workaround, FLM local TMPO data at least may be saved locally, using
scporWinSCPand archiving all content of/usr/share/tmpo/sensor/- which, of course, leaves out any data previous to v2.4.x... (but maybe you, Bart, have migrated all db content to the TMPO format and allow this to be taken from the server via REST)OK. Adding my old "broken" flm number worked.
As above though maybe just allowing to change a flm number to add an suffix (x) would allow a serviceable unit to be resold.