Hi
I hope some one can help me, I have installed a FLM about six weeks ago and have not been able to see any graphs on the Flukso Dash, the only one that works is the minute one which tells me that the sensors are working fine. the FLM has the heartbeat and globe light light and I can see in the sys log data is being posted, also when I log in to the Flukso web into my account I can see the sensors and the latest heartbeats being received. Is there a problem with the Flukso servers? or have I purchased a faulty unit.
Any help appreciated.
I'm a flukso newbie and can testify that perseverance pays off!
Are you actually seeing a line>0 being drawn on the minute graph? Perhaps best to post the last (20-30) lines from your log here. Hopefully these reveals some clues what might be happening.
Hi BELLYF
Thanks for the reply, I was beginning to become a little disheartened as any attempt to seek help by using the contact option on the Flukso web was met with silence, any how I will try to get this unit working, here is a sample of my sys log, any ideas?
Jan 20 09:11:42 flukso-85906d daemon.info fluksod[5512]: processed pulse 23a6455729ba4ee3085d4a54c0beb0ee:1421745102:945913
Jan 20 09:12:38 flukso-85906d daemon.info fluksod[5512]: processed pulse 23a6455729ba4ee3085d4a54c0beb0ee:1421745158:945914
Jan 20 09:13:39 flukso-85906d daemon.info fluksod[5512]: processed pulse 23a6455729ba4ee3085d4a54c0beb0ee:1421745219:945915
Jan 20 09:13:52 flukso-85906d daemon.info fluksod[5512]: POST https://api.flukso.net/sensor/23a6455729ba4ee3085d4a54c0beb0ee: 200
Jan 20 09:14:44 flukso-85906d daemon.info fluksod[5512]: processed pulse 23a6455729ba4ee3085d4a54c0beb0ee:1421745284:945916
Jan 20 09:15:01 flukso-85906d cron.info crond[659]: crond: USER root pid 22938 cmd /usr/bin/fcheck
Jan 20 09:15:55 flukso-85906d daemon.info fluksod[5512]: processed pulse 23a6455729ba4ee3085d4a54c0beb0ee:1421745355:945917
Jan 20 09:17:12 flukso-85906d daemon.info fluksod[5512]: processed pulse 23a6455729ba4ee3085d4a54c0beb0ee:1421745432:945918
Jan 20 09:18:52 flukso-85906d kern.info kernel: [3275519.920000] wlan0: deauthenticated from 00:04:ed:3e:ab:bd (Reason: 3)
Jan 20 09:18:52 flukso-85906d daemon.info supd[5506]: Received event DISCONNECTED for wlan0
Jan 20 09:18:53 flukso-85906d kern.info kernel: [3275520.850000] wlan0: authenticate with 00:04:ed:3e:ab:bd
Jan 20 09:18:53 flukso-85906d kern.info kernel: [3275520.870000] wlan0: send auth to 00:04:ed:3e:ab:bd (try 1/3)
Jan 20 09:18:53 flukso-85906d kern.info kernel: [3275520.870000] wlan0: authenticated
Jan 20 09:18:53 flukso-85906d kern.info kernel: [3275520.900000] wlan0: associate with 00:04:ed:3e:ab:bd (try 1/3)
Jan 20 09:18:53 flukso-85906d kern.info kernel: [3275520.900000] wlan0: RX AssocResp from 00:04:ed:3e:ab:bd (capab=0x411 status=0 aid=1)
Jan 20 09:18:53 flukso-85906d kern.info kernel: [3275520.900000] wlan0: associated
Jan 20 09:18:57 flukso-85906d daemon.info supd[5506]: Received event CONNECTED for wlan0
Jan 20 09:19:03 flukso-85906d daemon.info fluksod[5512]: POST https://api.flukso.net/sensor/23a6455729ba4ee3085d4a54c0beb0ee: 200
Jan 20 09:19:03 flukso-85906d daemon.info fluksod[5512]: processed pulse 23a6455729ba4ee3085d4a54c0beb0ee:1421745533:945919
Jan 20 09:22:19 flukso-85906d daemon.info fluksod[5512]: processed pulse 23a6455729ba4ee3085d4a54c0beb0ee:1421745739:945920
Jan 20 09:24:07 flukso-85906d daemon.info fluksod[5512]: POST https://api.flukso.net/sensor/23a6455729ba4ee3085d4a54c0beb0ee: 200
Jan 20 09:26:15 flukso-85906d daemon.info fluksod[5512]: processed pulse 23a6455729ba4ee3085d4a54c0beb0ee:1421745975:945921
Jan 20 09:29:11 flukso-85906d daemon.info fluksod[5512]: POST https://api.flukso.net/sensor/23a6455729ba4ee3085d4a54c0beb0ee: 200
Jan 20 09:29:45 flukso-85906d daemon.info fluksod[5512]: processed pulse 23a6455729ba4ee3085d4a54c0beb0ee:1421746185:945922
Jan 20 09:30:01 flukso-85906d cron.info crond[659]: crond: USER root pid 23015 cmd /usr/bin/fcheck
Jan 20 09:34:15 flukso-85906d daemon.info fluksod[5512]: POST https://api.flukso.net/sensor/23a6455729ba4ee3085d4a54c0beb0ee: 200
Jan 20 09:37:48 flukso-85906d daemon.info fluksod[5512]: processed pulse 23a6455729ba4ee3085d4a54c0beb0ee:1421746668:945923
Jan 20 09:39:19 flukso-85906d daemon.info fluksod[5512]: POST https://api.flukso.net/sensor/23a6455729ba4ee3085d4a54c0beb0ee: 200
Jan 20 09:44:21 flukso-85906d kern.info kernel: [3277049.220000] wlan0: deauthenticated from 00:04:ed:3e:ab:bd (Reason: 3)
Jan 20 09:44:21 flukso-85906d daemon.info supd[5506]: Received event DISCONNECTED for wlan0
Jan 20 09:44:22 flukso-85906d kern.info kernel: [3277050.190000] wlan0: authenticate with 00:04:ed:3e:ab:bd
Jan 20 09:44:22 flukso-85906d kern.info kernel: [3277050.210000] wlan0: send auth to 00:04:ed:3e:ab
It looks like FLM is processing the pulses woithout error messages. I can't judge the Wifi messages as I have my FLM hardwired to the router. You could try this also.
Next step is to see whether you can retrieve any stored data from the Flukso server. Login to your flm (default userid/pw= root/root) and use the
curlcommand described in chapter 3 of the FLM manual to retrieve timeseries from the server. The curl command should return a series of tuples consisting of a timestamp and a measured value. If you only see 'nan' returned for all measured values no data is stored on the server. If not (ie at least some of the measured values are integers) there is something else wrong (and I'm afraid my knowledge stops there).Success.
Thanks for the reply,
I will try to get hold of a lan cable first and try that, might take a week or so to get one long enough, as for linux I am a newbie and have been around before computers were invented, so I struggle with using anything more than a mouse, I hope option one works
You may want to try to access the FLM internals already (although I don't know whether this works over Wifi).
1) If you use Windows install Putty to be able to access your FLM (you can search in this forum for more info on Putty)
2) if you use a Mac you can use Terminal
3) Login to your FLM
amend the following CURL statement to suit your sensor and token parameters:
Replace <your token> with the token associated with sensor "23a6455729ba4ee3085d4a54c0beb0ee". I have already added your sensor from the log above.
Paste the above statement on a single line (ie no carriage returns) in the Puty window and press return.
If it works you should get a number of statements ending with something like
[[1421746668,100],[1421746678,120], ...]Hi BELLYF
I apologise for not getting back to you sooner, yes I have now sorted out the problem and it is working well.
Changing the connection type from wifi to Ethernet did not fix it, and there was no difference. As I had absolutely no support from flukso (they would not even answer my emails) I decided to return the unit to the place I bought it from as it should have worked out of the box and I considered it to be faulty. I am impressed at the level of service I received from Amy at rowetel she immediately and quickly exchanged my FLM and hey presto I have a working unit.
Thanks for your help