Hi flukso community,
I joined you yesterday with my FLM in the mail and eagerly tried to set it up.
So it was not problem connecting it to the wireless network, and seeing the device and sensors beeing connected online. As access to the fusebox is a bit constarained in my case I tried to simulate the setup by putting the clamps around my laptops powercord. I was hoping to see at least some readings on the dashboard page. But now after 16 hours of uptime there is still only a blank screen.
So I started to play around with the sensor settings and disabled all of them: what is puzzling me that there are still two sensor active, which are the
electricity smart-main
gas smart-main
sensors.
Any idea whats going wrong or whether simulating the flukso as I did just doesn´t create any out put?
Thanks for any hint
Erik
Putting a current clamp around a power chord that contains Line and Neutral does not work as the magnetic field which shall be detected then is wiped out; the only way to "simulate" the FLM's readings is either shortening a pulse port or using a clamp around a power cable where it can be clamped to either Line or Neutral alone (thus "single conductor")... Have a search on the principle of current clamps...
Thanks Gebhardm, and understood.
I was also not expecting any reasonable reading but just wanted to see whether the whole thing works.
Would the flukso system display anything in case of a zero reading from the clamps?
Erik
No. As the FLM internally counts pulses for Wh it will display nothing as long as there has been no reading...
So now I connected a DIN meter with S0 and 3 clamps for more than an hour and still no display. Any idea what can cause this?
Connect via a MQTT client and see what happens... See https://www.flukso.net/content/mqtt-mq-telemetry-transport As an alternative consult the manual for the "nobrainers" (LAN connection, Global LED, ...) ;-)
* Install a MQTT client on your computer - use for example http://mosquitto.org/download/
* Having done that, you have a MQTT client, for example mosquitto_sub from mosquitto.org
* Call your FLM using the command line: mosquitto_sub -h "your FLM's local IP address" -p 1883 -v -t /sensor/# - for example: mosquitto_sub -h 192.168.0.50 -p 1883 -v -t /sensor/#
* The # denotes a wildcard that will show all your sensors' topics, so gauge and counter on each sensor-ID, -v is used to show which sensor sent what data...
* Enjoy!
I am seeing lots of pulses being detected and posted.
But there is still no sign of a graph or anything on the dash page.
This is a sample output on the syslog page:
Dec 15 15:51:32 flukso-2b466a daemon.info fluksod[878]: processed pulse 56ce0f185d219206e29e481224b719c1:1387122692:319
Dec 15 15:51:44 flukso-2b466a daemon.info fluksod[878]: processed pulse 56ce0f185d219206e29e481224b719c1:1387122704:320
Dec 15 15:51:57 flukso-2b466a daemon.info fluksod[878]: processed pulse 56ce0f185d219206e29e481224b719c1:1387122717:321
Dec 15 15:52:10 flukso-2b466a daemon.info fluksod[878]: processed pulse 56ce0f185d219206e29e481224b719c1:1387122730:322
Dec 15 15:52:22 flukso-2b466a daemon.info fluksod[878]: processed pulse 56ce0f185d219206e29e481224b719c1:1387122742:323
Dec 15 15:52:35 flukso-2b466a daemon.info fluksod[878]: processed pulse 56ce0f185d219206e29e481224b719c1:1387122755:324
Dec 15 15:52:48 flukso-2b466a daemon.info fluksod[878]: processed pulse 56ce0f185d219206e29e481224b719c1:1387122768:325
Dec 15 15:53:00 flukso-2b466a daemon.info fluksod[878]: POST https://api.flukso.net/sensor/56ce0f185d219206e29e481224b719c1: 200
Dec 15 15:53:01 flukso-2b466a daemon.info fluksod[878]: processed pulse 56ce0f185d219206e29e481224b719c1:1387122781:326
Dec 15 15:53:13 flukso-2b466a daemon.info fluksod[878]: processed pulse 56ce0f185d219206e29e481224b719c1:1387122793:327
Dec 15 15:53:26 flukso-2b466a daemon.info fluksod[878]: processed pulse 56ce0f185d219206e29e481224b719c1:1387122806:328
Dec 15 15:53:39 flukso-2b466a daemon.info fluksod[878]: processed pulse 56ce0f185d219206e29e481224b719c1:1387122819:329
I am desperate now, why is nothing showing up?
Erik
You seem to use two accounts: On which is you FLM registered? Is the devices correctly shown in "settings --> Devices", are the sensors registeres under "settings --> Sensors"; get back into the local FLM configuration, what is the status? Is the Sensor config synchronization current? Save again...
I tried everything I can think of and so I created a second account to check whether that changes anything, which it didn´t.
Its all up to date, I don't see any error messages in the syslog, so I start thinking its a problem with the webservice at flukso.net.
Is anybody seeing similar issues?
Erik
Erik,
I have similar issues, see my post of 6 hours ago.
I also have the successfull pulse processed messages in my syslog and I only have minute values in the Dash, hourly or daily values are not working. This is for my water sensor, my gas sensor works fine.
Do you have any minute values ?
Did you try to look at the content of the sensor files ?
/var/run/fluksod/sensor/***
If you see pulses being logged to syslog but no charts being plotted on the dash, then this is most likely because the FLM hasn't properly synchronised its sensor settings with the Flukso server. Just point your browser to the local sensor configuration page again and save the settings (no need to make any changes) while the FLM is connected to the internet. This should result in a successful synchronisation. You will then see data points on the chart appearing within 5mins.
The smart-main sensors have been pre-configured on the FLM02B for smart meter readout. Ignore them when using clamps or pulse inputs.
@tdullers
No, I don´t have any minute values either. It keeps saying I am probably not on the same network which I think I am.
@icarus75
I saved the sensor configuration on the local settings a couple of times now. Still no success. Lots of pulses have been detected and posted. So I am giving up for now, spent many hours trying to solve that problem, and still don´t have a clue why there is no dash display.
Erik
@Lelek62 @tdullers This Saturday we had a service outage due to a full server disk. This caused the provisioning for some of your sensors to fail. Your issue should be fixed now and your FLM's sensor readings should render properly in the dash. Please confirm.
Hi Icarus75,
yes, I can confirm its working fine now. Thanks a lot for resolving this!
I only have onle last question that I read about a lot here and that is how to make the minute tab work for realtime data. I still get the
"Error - The call for sensor smart-main experienced a timeout. You are probably not in the same local network as the FLM."
on Chrome. On Safari (Iphone) and IE it just doens´t display anyting, but also no error message.
Is there a workarounf for this other than installing the Android App on windows?
Erik
@Icarus75: Everything came in correctly, so it works as a charm!
I spent quite so;e ti;ethos weekend wondering why it did not work, but learned a lot,
setup Openhab and the MQTT binding and have all meter values from the Flukso now also in Openhab.
Thanks
@LELEK62:
- For the minute values i tested the following:
MACOSX: Safari -> Works fine , Chro;e does not work
On IPHONE Safari -> Works fine
On Windows 7 IE -> Works fine if you disable the ;iced content restrictions
Thank you for your feedback. Glad to see this issue resolved. I'm locking this thread as the minute tab discussion is off-topic.