Since today, I get this "Error - The call for sensor solar experienced a timeout. You are probably not in the same local network as the FLM.". The FLM is definitely in my network and it has worked before. In my opinion nothing has changed since last time. At this time, The solar sensor reports every second in the syslog. Any suggestion?
YaY! Working for me too :D
Bart,
I have installed the latest fluksometer we ordered and the minute graph works like charm in Firefox and Chrome without any tweaking (v216).
The only difference I see with the setup I have in the office which doesn't work is the software version (v215).
@automatronic
1/ Are you using the same laptop for accessing these two setups?
2/ Are you sure you've enabled the local REST API on both FLM's?
3/ Can you report which version of chrome/ff you're running?
@Icarus75
1 & 3) I use 2 different computers but both running Win7 & Firefox (15.0.1) / Chrome (21.0.1180.89 m).
2) Yes and tested manually (by copy/pasting the url in the browser).
Could you let me know the serials of both your FLMs via email? I'll have a look for any differences between them.
What do the Chrome and FF consoles report when the real-time charting does not work?
At my friend's installation (FL02000375) "minute display" (MD) does not work with either Chrome, IE, or Firefox. At my home (FL02000242) MD works fine on my laptop (Chrome --allow-running-insecure-content). When I take my laptop to his site and log in to his account: no response for MD. Local REST API is enabled.
I've seen this behaviour now on two different sites. At the first site (FL02000303) MD spontaneously started to work after a few days.
Any suggestions?
Could your friend try loading the minute display again in IE/FF/Chrome and report on the result?
@DriekdeGadgetfreak I've found the root cause of your issues with the minute display. You seem to have enabled sensors 2 & 3 with the FLM set to 3-phase mode. This will ripple through the system and make the browser client think that it needs to fetch data for sensor 2 and 3 as well. Sensor 2 and 3 will never publish any data (the three clamp ports map to a single sensor, i.e. sensor 1) thus causing time-outs for the HTTP calls to the FLM.
So, in the short term, do not enable ports that have no chance of generating data (including pulse ports that will not register pulses). I'll have a peek at the code to see how we can prevent this from happening altogether.
Thanks for the diligence on this topic!
@icarus75: can I conclude: There is no minute display during the time my solar panels generate no output (at night)?
If you measure your panels through one of the pulse inputs you will:
1/ not see any solar panel readings at night since they're not generating any pulses
2/ minute readings for your consumption should work once your panels have at least generated one Wh after startup of the FLM.
I don't consider the second point to be 'normal' behaviour. It should work right after boot. This will be fixed in the next firmware release.
We (Bart and I) found out the following (Chrome users):
1. You can start Chrome in the "allow insecure content" mode by using the "chrome --allow-running-insecure-content" command.
2. However: you'll need start a new instance ONLY after you've closed all other Chrome screens...
3. For ease of use, you might consider creating a shortcut with the following command line: "C:\Users\xxx\Application\chrome.exe --allow-running-insecure-content www.flukso.net/dash#electricity/minute" (replace the xxx with the location where windows can find your Chrome.exe.
Good luck.
For Mac users:
You can create an AppleScript application in the AppleScript Editor with following contents
do shell script "'/Applications/Google Chrome.app/Contents/MacOS/Google Chrome' --allow-running-insecure-content www.flukso.net/dash#electricity/minute > /dev/null 2>&1 &"
Cant you guys put some sort of self signed SSL certificate on the device?
Is the minute display now active in the FLM 2B ?
Is this also passed towards the Flukso webspace or only locally on the Flukso itself?
Is there a how to on an Linux machine with Firefox or Chrome to see the minute tab working ?
@ICARUS75
Any updates on this problem?
It looks like i'm not the only one with this problem...
For Firefox users see this link to unblock Insecure content. :)
Minute Tab working fine now.
https://support.mozilla.org/en-US/kb/mixed-content-blocking-firefox
Thanks, but it worked for almost a year by me now on Firefox by disabling the smart main sensors for elec and gas on the Flukso v2b. https://www.flukso.net/content/uninstalled-smart-main-sensors-reason-non...
Of course the above tip to unblock insecure content must also be done.
Hey FLUC
I have the FLM02A any idea if Bart's tweak will work for me?
FLM02A has no smart-main sensor as it is not capable to read P1 telegrams (different hardware setup)... An option is using the MQTT messages sent by the FLM; see the many threads on this topic - https://www.google.com/search?q=site:flukso.net+mqtt&ie=utf-8&oe=utf-8