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?
restart ?
Did that!
When I type "http://local-ip:8080/sensor/7b44c557bf2b593019e0479cb3b7ff36?version=1.0&interval=minute&unit=watt&callback=realtime", I get a normal response from FLM for the solar sensor. So this works. It seems to me that the minute display function doesn't contact my local FLM. What's wrong?
Have you checked in the config that the json api is on?
Of course you have, otherwise the direct call wouldn't have been possible; nevertheless, maybe 'resync' the config...
Thanx, I've done all that.
Do you have any extra Fluksonians on your chart?
Maybe its their minute data that it is unable to get?
I am not at my home network to test what happens normally if you have one or more additional Fluksonians data showing on your chart and you try to display the minute chart. I would imagine it will only show your own data but i can't remember actually trying it.
Just a thought.
Yes, I have extra Fluksonians. But even removing them doesn't help.
I get the same error if I log in from a site not on my local network at home . ie. at work :(
Might be a clue there?
Bazzle
That's rather strange. Do you mean the minute tab used to work before, but from 04/08 onwards just stopped working?
The dash will try to find your FLM at 192.168.2.2 in your LAN. I'm assuming that your computer is indeed in the same LAN segment since you've tried out the API call manually.
Did you check your browser's console/net output? It should list the HTTP call with all its request and response parameters when hitting the minute tab. What browser type/version are you using?
My minute tab works fine with my IPhone in the same WLAN, but it has stopped working on my laptop (also wifi). Says that it's probably not in the same network but I can see them all on my router's status page. I am using the latest Chrome browser and I have tried IE9 as well on the laptop.
I've just tried this out in Chrome. When hitting the minute tab, the error is indeed shown. On the top of the page, there's a pop-up saying 'This page has insecure content'. That's because the page itself is fetched from the server using https while local access to the FLM's API is via plain http. So select the 'Load Anyway' button to allow this mix of protocols. IE9 will have a similar behaviour I guess.
If this does not solve the issue in Chrome, reload the Flukso dash page and hit Shift+Ctrl+I to open the developer tools. Now go to the minute tab on the dash page. Go back to the developer tools window and check both the console and network tabs. If you're not getting a 200 status code for the GET request, click on the request and copy/past the contents in a forum comment.
I have noticed the warning on the top of the page and selected "Load Anyway". Perhaps I have pushed the wrong button once because I get 200 status code for all GET requests in the network tab and the console tab shows the following:
Port error: Could not establish connection. Receiving end does not exist. miscellaneous_bindings:232
chromeHidden.Port.dispatchOnDisconnect miscellaneous_bindings:232
[blocked] The page at https://flukso.net/dash#electricity/day ran insecure content from http://192.168.2.7:8080/sensor/e09d8d41a1afb385bf96ef05fb7bf277?callback....
[blocked] The page at https://flukso.net/dash#electricity/minute ran insecure content from http://192.168.2.7:8080/sensor/e09d8d41a1afb385bf96ef05fb7bf277?callback....
[blocked] The page at https://flukso.net/dash#electricity/minute ran insecure content from http://192.168.2.7:8080/sensor/e09d8d41a1afb385bf96ef05fb7bf277?callback....
[blocked] The page at https://flukso.net/dash#electricity/minute ran insecure content from http://192.168.2.7:8080/sensor/e09d8d41a1afb385bf96ef05fb7bf277?callback....
Clearing the cache (Ctrl+F5) normally is a solution but it doesn't solve the blocked situation.
Hmm. Just reloading the dash page works for me in Chrome. You could try opening the page in another tab as well.
Now it works on IE9 on the laptop but still not with Chrome. Got the same question in IE9 that I previously got in Chrome. How can I recover the same 'insecure content' in Chrome, because I don't even get the question anymore? Next step is reinstallation of Chrome...
Cracked it! Right click your Chrome icon, choose properties and add "--allow-running-insecure-content" (without quotes) after the target ending with ...chrome.exe
I had the same problem. With the "--allow-running-insecure-content" it works
Now I'm back from holiday I tried all suggestions. My version of Chrome (21.0.1180.89) never displays the pop-up saying 'This page has insecure content'
The developer tools report:
[blocked] The page at https://www.flukso.net/dash#electricity/minute ran insecure content from http://192.168.2.2:8080/sensor/7b44c557bf2b593019e0479cb3b7ff36?callback....
etc.
My Internet Explorer works fine.
Add me to the list. Linux user here. Does not work with firefox.chrome/chromium. Going to try using konqueror with compatibility mode turned on.
Hmmm. Firefox on Linux never gave me any issues. Do you see any error in the Firebug console output?
Icarus,
Ill report when I get back home from work.
Thanks.
So "Minute Display" at home with Internet Explorer 8 works OK. With Chrome it definitely does not.
When I move my laptop to another site and log in to the corresponding flukso-account "Minute Display" does not work with IE8. There is a normal reponse to "http://local-ip:8080/sensor/7b44c557bf2b593019e0479cb3b7ff36?version=1.0&interval=minute&unit=watt&callback=realtime".
I have started my Chrome browser with the "--allow-running-insecure-content" option, but now it tells me this:
Error - Real-time charting is not available on this Fluksometer. If you have an FLM02, then please upgrade to the latest firmware release on the my account -> devices page.
But I see nowhere on that page, how I could upgrade my firmware. All I have is a "remove" link next to my device :-/
@Automatronic
I received the same error the other day, not in Chrome but in Firefox. I was going round and round in circles until i realised that i wasn't logged in. The data i was seeing must have been from a default/demo account. Doh.
Logged in and the minute chart worked again.
Thought i would mention it as sometimes its easy to overlook the simple things.
@fusionpower,
Not the case for me. I am logged in and the minute display does not work for me at all.
Chrome/Firefox/Konqueror
@fusionpower
If I wasn't logged in, I wouldn't be able to see the "remove" link next to my device !
@patlem If you're using chrome, reload the Flukso dash page and hit Shift+Ctrl+I to open the developer tools. Now go to the minute tab on the dash page. Go back to the developer tools window and check both the console and network tabs. If you're not getting a 200 status code for the GET request, click on the request and copy/past the contents in a forum comment.
When I execute Chrome without the "--allow-running-insecure-content" switch I get this message in the developer console:
[Blocked] The page at https://www.flukso.net/dash#electricity/minute ran insecure content from http://192.168.100.191:8080/sensor/blablabla
When I execute Chrome with the "--allow-running-insecure-content" switch I get this message in the developer console:
The page at https://www.flukso.net/dash#electricity/minute ran insecure content from http://192.168.100.191:8080/sensor/blablabla
The only difference is the [Blocked] at the beginning.
And of course, if I open the link to the fluksometer in an new tab, it works just fine.
With IE9, I get a popup at the bottom of the page asking me if I want to allow insecure content, but allowing it just give me the page with a blank square instead of the graph.
When I execute Chrome with the "--allow-running-insecure-content" switch I get this message in the developer console:
The page at https://www.flukso.net/dash#electricity/minute ran insecure content from http://192.168.0.122:8080/sensor/100468e06087fc66c109b7cbbb622174?callba....
It shows no minute display however.
Strange! Todays everythings works fine. IE and Firefox are working now. @Icarus75: Did you do something to make this work?