The dash page shows nothing and even no timeout message, while all LEDs are lit up on the box.
However I can see the device and the sensors displayed on the corresponding tabs.
I have a similar issue. I have my gas-meter (Schlumberger G4RF1) connected on port 5. My sensor for gas consumption is showing up in My Account > Sensors with the correct id and according to syslog, data seem to be sent on flukso.net :
Oct 14 04:34:02 flukso-be877a user.info heartbeat[13256]: POST https://api.flukso.net/device/be877a1c72086a8715a53a39de7871cb: 200
Oct 14 04:45:01 flukso-be877a cron.info crond[673]: crond: USER root pid 13290 cmd /usr/bin/fcheck
Oct 14 05:00:01 flukso-be877a cron.info crond[673]: crond: USER root pid 13335 cmd /usr/bin/fcheck
Oct 14 05:15:01 flukso-be877a cron.info crond[673]: crond: USER root pid 13380 cmd /usr/bin/fcheck
Oct 14 05:30:01 flukso-be877a cron.info crond[673]: crond: USER root pid 13451 cmd /usr/bin/fcheck
Oct 14 05:34:01 flukso-be877a cron.info crond[673]: crond: USER root pid 13472 cmd /usr/bin/heartbeat 0
Oct 14 05:34:03 flukso-be877a user.info heartbeat[13473]: POST https://api.flukso.net/device/be877a1c72086a8715a53a39de7871cb: 200
However, I have a blank page when I click on Dash > Gas. I also see nan values when I check the raw data with the REST API...
The strange thing is that I see two sensors listed for gas in My Account > Sensors: gas consumption (the one with correct sensor id) and smart-main (that I didn't enable anywhere).
"Port 6 can now be used to read out the local data port, a.k.a. P1 port, of a Dutch smart meter. All you need is a data cable with an RJ11 connector. Connect the Rj11 pins as follows: pin 2 > 6a, pin 3 > 5-, pin 4 > free, pin 5 > 6b. Pin numbering is from left to right when the RJ11 connector has its lip pointing downwards. Once the FLM02B is physically connected to the smart meter, it should automatically start registering its readings. The corresponding sensors will be called 'smart-main' for both electricity and gas on the Flukso dash."
I have a similar issue. I have my gas-meter (Schlumberger G4RF1) connected on port 5. My sensor for gas consumption is showing up in My Account > Sensors with the correct id and according to syslog, data seem to be sent on flukso.net :
Oct 14 04:34:02 flukso-be877a user.info heartbeat[13256]: POST https://api.flukso.net/device/be877a1c72086a8715a53a39de7871cb: 200
Oct 14 04:45:01 flukso-be877a cron.info crond[673]: crond: USER root pid 13290 cmd /usr/bin/fcheck
Oct 14 05:00:01 flukso-be877a cron.info crond[673]: crond: USER root pid 13335 cmd /usr/bin/fcheck
Oct 14 05:15:01 flukso-be877a cron.info crond[673]: crond: USER root pid 13380 cmd /usr/bin/fcheck
Oct 14 05:30:01 flukso-be877a cron.info crond[673]: crond: USER root pid 13451 cmd /usr/bin/fcheck
Oct 14 05:34:01 flukso-be877a cron.info crond[673]: crond: USER root pid 13472 cmd /usr/bin/heartbeat 0
Oct 14 05:34:03 flukso-be877a user.info heartbeat[13473]: POST https://api.flukso.net/device/be877a1c72086a8715a53a39de7871cb: 200
However, I have a blank page when I click on Dash > Gas. I also see nan values when I check the raw data with the REST API...
The strange thing is that I see two sensors listed for gas in My Account > Sensors: gas consumption (the one with correct sensor id) and smart-main (that I didn't enable anywhere).
Any idea?
Thanks,
Greg
FYI: "Smart main" reflects the capability to read out a Dutch smart meter on port 6; ref to https://www.flukso.net/content/fluksometer-v2b
"Port 6 can now be used to read out the local data port, a.k.a. P1 port, of a Dutch smart meter. All you need is a data cable with an RJ11 connector. Connect the Rj11 pins as follows: pin 2 > 6a, pin 3 > 5-, pin 4 > free, pin 5 > 6b. Pin numbering is from left to right when the RJ11 connector has its lip pointing downwards. Once the FLM02B is physically connected to the smart meter, it should automatically start registering its readings. The corresponding sensors will be called 'smart-main' for both electricity and gas on the Flukso dash."
and https://www.flukso.net/content/uninstalled-smart-main-sensors-reason-non... on how to disable this.