I am a proud owner of a new Flukso v3 for my office and struggle with using it the same way as at home where I successfully installed the local visualisations on a v2 Flukso like described here: https://github.com/gebhardm/flmlocal/tree/flm03
Or is it just not working on firmware version 380 as of yet?
Maby thanks for any hint in advance
Erik
Sorry, I did not have any time yet to adapt to v380, but from the change history there may be some evidence on what to do. I always start(ed) with a copy of the /www/-folder from the FLM and did a local compare...
Thanks for the quick response.
Please let me know if you have any plans to do it or what I can do to help with this task.
Regards
Erik
Just had a look; I indeed prepared myself for an update; see https://github.com/gebhardm/flm03/tree/master/revisions/www - corresponding to the diffs of the v378 (here with flmlocal installed) to the v380 (plain after update) the flmlocal visualization should also work out of the box with v380 and following the description in https://github.com/gebhardm/flmlocal/blob/master/README.md - at own risk as I currently don't plan an update; my FLM03 is offline due to personal changes...
Upfront you may perform a backup of your settings using
scp -r root@<flm_ip address>:/www/ .to whereever you want to save it - remember: no backup, no mercy.I am afraid I need some help as I probably ruined the content of my www/ directory, and sorry Gebhardm, I screwed up my backup also :( Can I download the original content somewhere or is a way to make a factory reset?
Thanks for any help
https://www.flukso.net/files/docs/en/fluksometer.html#button
Thanks Gehardm, that helped :) and its running fine again!
Lelek62 - did you get the visualisations working on V3?
For the records: v380 and v378 are from the viewpoint of UI identical. As such also the v378 intended flmlocal implementation works right out of the box.
The only adapted files are
/www/index.html,/www/scripts/app.jsand/etc/init.d/flukso.So, follow the instructions as for v378 and enjoy.
https://github.com/gebhardm/flmlocal
@VK2HIM
Sorry, I only read your message now. No, I did not get it to work so far, but will try again next week :)
Did you get it to work with Gebhardm hints above?
I still have the version 2 however it just died so I might need to buy a V3 - so it would be good to know if visualisations work on v3
I doubt it died. Keep if off power for a while and power on again; then check the connections - be kind to your little electronic helpers. And yes, the visualizations work on the FLM03 as well.
Thanks Gebhardm - I've had it off overnight so I will try when I get home from work - with fingers crossed I hope I can re-flash the firmware! Good to know your visualisations work on FLM03 as a fall back in case I have to buy a new one. I haven't seen anything in the Solar market that matches the powerful real-time information your visualisations offer - sure there's devices that show you what happened 15 minutes ago, but that's no comparison to knowing whats happening right now.
I tried without much luck recently (because i know very little about programming lol) to get your visualisations working in a unix/MACOS environment not on the FLM - my thoughts were to cover this sort of situation where the FLM dies - I might then be able to attach to another mqtt steam of another device ..
That is a "piece of cake" ;-) A Raspberry Pi Zero will do with an installed webserver (e.g. NGINX or even the simplest http server set up on node.js), then the www-folder of the FLM can be copied and it works "rather" out of the box (except for the TMPO part, of course, as this is FLM local)... See https://github.com/gebhardm/energyhacks/tree/master/Flukso
Thanks Gebhardm - your suggestion worked! I left if off overnight and I have now re-flashed and it is back to life!!!! Great help thanks!
I seem to be having the same issue now though as HERO is describing in this other thread https://www.flukso.net/content/flukso-update-problem-after-bricked
I have clicked and requested an upgrade in firmware from the current 214 to 250 via my user account and it is queued to do the upgrade at the next heartbeat:
FL0300xxxx 250** 121 20 Feb 2020 19:12:36 0d 0h
My problem is that after the next heartbeat the firmware stays on 214 and never gets the current 250.
I'll continue this on the other thread.