No more readings without any changes

by jghaanstra on

Two nights ago my Flukso 02B suddenly stopped sending data to the Flukso dashboard (and therefor PVOutput.org). It has been running fine for more then a year and I havent touched it during this time. It stopped working in the middle of the night while I was asleep so it has to be some external cause. The Flukso is connected to the P1 port of my Smart Meter. I can access it through the webinterface and SSH fine. In the webinterface the status looks fine as well (wifi connected and ping to flukso succesfull). I rebooted the Flukso in the hope this would fix it but it hasnt. Below is the last part of the syslog, can someone help me indentify the cause and preferably come up with a solution.

  1. Jan  1 00:00:51 flukso-eb6e6c daemon.notice netifd: wan (676): Lease of 192.168.0.124 obtained, lease time 268435455
  2. Jan  1 00:00:52 flukso-eb6e6c daemon.notice netifd: Interface 'wan' is now up
  3. Jan  1 00:00:54 flukso-eb6e6c user.notice firewall: Reloading firewall due to ifup of wan (wlan0)
  4. Jan  1 00:00:55 flukso-eb6e6c authpriv.info dropbear[716]: Running in background
  5. Jan  1 00:01:01 flukso-eb6e6c cron.info crond[667]: crond: USER root pid 738 cmd /usr/bin/heartbeat 0
  6. Jan  1 00:01:06 flukso-eb6e6c user.notice dnsmasq: DNS rebinding protection is active, will discard upstream RFC1918 responses!
  7. Jan  1 00:01:06 flukso-eb6e6c user.notice dnsmasq: Allowing 127.0.0.0/8 responses
  8. Jan  1 00:01:07 flukso-eb6e6c user.info heartbeat[739]: POST <a href="https://api.flukso.net/device/eb6e6cc5e66aa2f06f74d89448c50dfc:" title="https://api.flukso.net/device/eb6e6cc5e66aa2f06f74d89448c50dfc:">https://api.flukso.net/device/eb6e6cc5e66aa2f06f74d89448c50dfc:</a> 200
  9. Jan  1 00:01:10 flukso-eb6e6c daemon.info dnsmasq[769]: started, version 2.66 cachesize 150
  10. Jan  1 00:01:10 flukso-eb6e6c daemon.info dnsmasq[769]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth
  11. Jan  1 00:01:10 flukso-eb6e6c daemon.info dnsmasq-dhcp[769]: DHCP, IP range 192.168.255.100 -- 192.168.255.249, lease time 12h
  12. Jan  1 00:01:10 flukso-eb6e6c daemon.info dnsmasq[769]: using local addresses only for domain lan
  13. Jan  1 00:01:10 flukso-eb6e6c daemon.info dnsmasq[769]: reading /tmp/resolv.conf.auto
  14. Jan  1 00:01:10 flukso-eb6e6c daemon.info dnsmasq[769]: using nameserver 8.8.4.4#53
  15. Jan  1 00:01:10 flukso-eb6e6c daemon.info dnsmasq[769]: using nameserver 8.8.8.8#53
  16. Jan  1 00:01:10 flukso-eb6e6c daemon.info dnsmasq[769]: using local addresses only for domain lan
  17. Jan  1 00:01:10 flukso-eb6e6c daemon.info dnsmasq[769]: read /etc/hosts - 1 addresses
  18. Jan  1 00:01:10 flukso-eb6e6c daemon.info dnsmasq-dhcp[769]: read /etc/ethers - 0 addresses
  19. Jan  1 00:01:12 flukso-eb6e6c daemon.info avahi-daemon[775]: Found user 'nobody' (UID 65534) and group 'nogroup' (GID 65534).
  20. Jan  1 00:01:12 flukso-eb6e6c daemon.info avahi-daemon[775]: Successfully dropped root privileges.
  21. Jan  1 00:01:12 flukso-eb6e6c daemon.info avahi-daemon[775]: avahi-daemon 0.6.31 starting up.
  22. Jan  1 00:01:12 flukso-eb6e6c daemon.warn avahi-daemon[775]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
  23. Jan  1 00:01:12 flukso-eb6e6c daemon.info avahi-daemon[775]: Loading service file /etc/avahi/services/flukso.service.
  24. Jan  1 00:01:12 flukso-eb6e6c daemon.info avahi-daemon[775]: Loading service file /etc/avahi/services/http.service.
  25. Jan  1 00:01:12 flukso-eb6e6c daemon.info avahi-daemon[775]: Loading service file /etc/avahi/services/mqtt.service.
  26. Jan  1 00:01:12 flukso-eb6e6c daemon.info avahi-daemon[775]: Loading service file /etc/avahi/services/ssh.service.
  27. Jan  1 00:01:12 flukso-eb6e6c daemon.info avahi-daemon[775]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.124.
  28. Jan  1 00:01:12 flukso-eb6e6c daemon.info avahi-daemon[775]: New relevant interface wlan0.IPv4 for mDNS.
  29. Jan  1 00:01:12 flukso-eb6e6c daemon.info avahi-daemon[775]: Joining mDNS multicast group on interface br-lan.IPv4 with address 192.168.255.1.
  30. Jan  1 00:01:12 flukso-eb6e6c daemon.info avahi-daemon[775]: New relevant interface br-lan.IPv4 for mDNS.
  31. Jan  1 00:01:12 flukso-eb6e6c daemon.info avahi-daemon[775]: Network interface enumeration completed.
  32. Jan  1 00:01:12 flukso-eb6e6c daemon.info avahi-daemon[775]: Registering new address record for 192.168.0.124 on wlan0.IPv4.
  33. Jan  1 00:01:12 flukso-eb6e6c daemon.info avahi-daemon[775]: Registering new address record for 192.168.255.1 on br-lan.IPv4.
  34. Jan  1 00:01:12 flukso-eb6e6c daemon.info avahi-daemon[775]: Registering HINFO record with values 'MIPS'/'LINUX'.
  35. Jan  1 00:01:14 flukso-eb6e6c daemon.info avahi-daemon[775]: Server startup complete. Host name is flukso-eb6e6c.local. Local service cookie is 3748380999.
  36. Jan  1 00:01:15 flukso-eb6e6c user.info sysinit: setting up led wlan
  37. Jan  1 00:01:16 flukso-eb6e6c daemon.info avahi-daemon[775]: Service "Secure Shell on flukso-eb6e6c" (/etc/avahi/services/ssh.service) successfully established.
  38. Jan  1 00:01:16 flukso-eb6e6c daemon.info avahi-daemon[775]: Service "MQTT Broker on flukso-eb6e6c" (/etc/avahi/services/mqtt.service) successfully established.
  39. Jan  1 00:01:17 flukso-eb6e6c daemon.info avahi-daemon[775]: Service "Web Server on flukso-eb6e6c" (/etc/avahi/services/http.service) successfully established.
  40. Jan  1 00:01:18 flukso-eb6e6c daemon.info avahi-daemon[775]: Service "Flukso RESTful API on flukso-eb6e6c" (/etc/avahi/services/flukso.service) successfully established.
  41. Jan  1 00:01:18 flukso-eb6e6c user.info sysinit: Daemon returned 0 as return value.
  42. Jan  1 00:01:18 flukso-eb6e6c daemon.info supd[793]: Sucessfully started with DEAMON=supd and DAEMON_PATH=/var/run/supd
  43. Jan  1 00:01:19 flukso-eb6e6c daemon.info spid[796]: Sucessfully started with DEAMON=spid and DAEMON_PATH=/var/run/spid
  44. Jan  1 00:01:19 flukso-eb6e6c user.info sysinit: Daemon returned 0 as return value.
  45. Jan  1 00:01:19 flukso-eb6e6c daemon.info fluksod[799]: Sucessfully started with DEAMON=fluksod and DAEMON_PATH=/var/run/fluksod
  46. Jan  1 00:01:19 flukso-eb6e6c user.info sysinit: Daemon returned 0 as return value.
  47. Jan  1 00:01:19 flukso-eb6e6c user.info sysinit: Daemon returned 0 as return value.
  48. Jan  1 00:01:19 flukso-eb6e6c daemon.info parsed[804]: Sucessfully started with DEAMON=parsed and DAEMON_PATH=/var/run/parsed
  49. Jan  1 00:01:24 flukso-eb6e6c user.info heartbeat[809]: POST <a href="https://api.flukso.net/device/eb6e6cc5e66aa2f06f74d89448c50dfc:" title="https://api.flukso.net/device/eb6e6cc5e66aa2f06f74d89448c50dfc:">https://api.flukso.net/device/eb6e6cc5e66aa2f06f74d89448c50dfc:</a> 200
  50. Jan  1 00:01:25 flukso-eb6e6c daemon.info supd[793]: Received event START for ntp
  51. Dec 10 11:20:06 flukso-eb6e6c cron.err crond[667]: time disparity of 23636838 minutes detected
  52. Dec 10 11:30:01 flukso-eb6e6c cron.info crond[667]: crond: USER root pid 883 cmd /usr/bin/fcheck

‹ Maximum length analog clamp wire no reading from P1 kamstrup ›
threma's picture
threma |

I have the same problem since december 2. I send a mail to info@flukso.net. I'm still waiting for an answer.

jghaanstra's picture
jghaanstra |

I have the same problem since december 2. I send a mail to info@flukso.net. I'm still waiting for an answer.
Did you recieve any response, my issue continues to exist.

Fluc's picture
Fluc |

Is the heartbeat led blinking on the Flukso ?
If not, perhaps you can do a reset of the device and hope it will working again.

jghaanstra's picture
jghaanstra |

The heartbeat led is still blinking and the log is showing the heartbeat as well. Strange thing is though that it seems to reboot very often. Uptime is never longer then 2 - 3 hours.

  1. Dec 16 17:09:26 flukso-eb6e6c cron.err crond[667]: time disparity of 23645828 minutes detected
  2. Dec 16 17:15:01 flukso-eb6e6c cron.info crond[667]: crond: USER root pid 838 cmd /usr/bin/fcheck
  3. Dec 16 17:30:01 flukso-eb6e6c cron.info crond[667]: crond: USER root pid 871 cmd /usr/bin/fcheck
  4. Dec 16 17:45:01 flukso-eb6e6c cron.info crond[667]: crond: USER root pid 904 cmd /usr/bin/fcheck
  5. Dec 16 18:00:01 flukso-eb6e6c cron.info crond[667]: crond: USER root pid 939 cmd /usr/bin/fcheck
  6. Dec 16 18:01:01 flukso-eb6e6c cron.info crond[667]: crond: USER root pid 954 cmd /usr/bin/heartbeat 0
  7. Dec 16 18:01:07 flukso-eb6e6c user.info heartbeat[955]: POST <a href="https://api.flukso.net/device/eb6e6cc5e66aa2f06f74d89448c50dfc:" title="https://api.flukso.net/device/eb6e6cc5e66aa2f06f74d89448c50dfc:">https://api.flukso.net/device/eb6e6cc5e66aa2f06f74d89448c50dfc:</a> 200
  8. Dec 16 18:15:01 flukso-eb6e6c cron.info crond[667]: crond: USER root pid 985 cmd /usr/bin/fcheck
  9. Dec 16 18:30:01 flukso-eb6e6c cron.info crond[667]: crond: USER root pid 1026 cmd /usr/bin/fcheck
  10. Dec 16 18:45:01 flukso-eb6e6c cron.info crond[667]: crond: USER root pid 1061 cmd /usr/bin/fcheck

jghaanstra's picture
jghaanstra |

Something I did notice which might be related. When updating the sensor config I got the following error (I thought I'd toggle it since I have no clue on how to actually troubleshoot this and there is no support).

  1. Saving sensor parameters: ......
  2. Committing changes: true
  3. Syncing configuration: gh 3 0 .. ok
  4. Hardware check (major: 3, minor: 0) .. nok
  5. Error. Major version does not match.
  6. Use -f to override this check at your own peril.
  7.  
  8. Restarting the Flukso daemon: ok

jghaanstra's picture
jghaanstra |

And the corresponding log:

  1. Dec 22 09:01:04 flukso-eb6e6c user.info heartbeat[922]: POST <a href="https://api.flukso.net/device/eb6e6cc5e66aa2f06f74d89448c50dfc:" title="https://api.flukso.net/device/eb6e6cc5e66aa2f06f74d89448c50dfc:">https://api.flukso.net/device/eb6e6cc5e66aa2f06f74d89448c50dfc:</a> 200
  2. Dec 22 09:15:01 flukso-eb6e6c cron.info crond[667]: crond: USER root pid 946 cmd /usr/bin/fcheck
  3. Dec 22 09:30:01 flukso-eb6e6c cron.info crond[667]: crond: USER root pid 1005 cmd /usr/bin/fcheck
  4. Dec 22 09:34:32 flukso-eb6e6c user.err fsync[1056]: fsync exit status: 4, sensor board hardware compatibility check failed
  5. Dec 22 09:34:33 flukso-eb6e6c daemon.info parsed[804]: Caught a SIGTERM. Exiting...
  6. Dec 22 09:34:33 flukso-eb6e6c daemon.info fluksod[799]: Caught a SIGTERM. Exiting...
  7. Dec 22 09:34:34 flukso-eb6e6c daemon.info spid[796]: Caught a SIGTERM. Exiting...
  8. Dec 22 09:34:35 flukso-eb6e6c daemon.info supd[793]: Caught a SIGTERM. Exiting...
  9. Dec 22 09:34:36 flukso-eb6e6c daemon.info supd[1075]: Sucessfully started with DEAMON=supd and DAEMON_PATH=/var/run/supd
  10. Dec 22 09:34:36 flukso-eb6e6c daemon.info spid[1078]: Sucessfully started with DEAMON=spid and DAEMON_PATH=/var/run/spid
  11. Dec 22 09:34:37 flukso-eb6e6c daemon.info fluksod[1081]: Sucessfully started with DEAMON=fluksod and DAEMON_PATH=/var/run/fluksod
  12. Dec 22 09:34:37 flukso-eb6e6c daemon.info parsed[1086]: Sucessfully started with DEAMON=parsed and DAEMON_PATH=/var/run/parsed
  13. Dec 22 09:34:40 flukso-eb6e6c user.info heartbeat[1089]: POST <a href="https://api.flukso.net/device/eb6e6cc5e66aa2f06f74d89448c50dfc:" title="https://api.flukso.net/device/eb6e6cc5e66aa2f06f74d89448c50dfc:">https://api.flukso.net/device/eb6e6cc5e66aa2f06f74d89448c50dfc:</a> 200

gebhardm's picture
gebhardm |

Hardware check (major: 3, minor: 0) .. nok
This message is sent by fsync.lua and should report what is stored in the sensor board's controller eeprom; so there seems to be a hickup; maybe a master reset helps (following Dogbert's tech advice)

threma's picture
threma |

I solved my problem. There were two things wrong. First I forgot to save the sensors after reinstalling.
And second there is sometimes a disconnecting between the P1 port and the RJ11 jacket. Moving the jacket a little solve this problem.

Wpatrick's picture
Wpatrick |

He,

Here Belgium Leuven, i have the same problem, Flukso does'nt send anymore

started the same periode about start of december,...... i can read the dashboard but no reception by my account at PVOUTPUT ????

what is the trubble?? can someone help

Patrick Wauters - Dalkia - Veolia Energiecel.

jghaanstra's picture
jghaanstra |

I did:
- a hard reset
- change the connection from wifi to ethernet just to make sure
- saved the sensor config again
- physically checked the data cable

All didnt matter, still no data. Can someone tell me how I can check if the P1 port sensors have been registered.

threma's picture
threma |

You can check in your account the sensors and see something like this:
Sensor Token Type Function
7a2f25436c6fb337940b64347732f5b3 d832056a155dd2ea38f8997a19d4015c electricity smart-main
4b57efa9481ba616995d145a0f137feb d56c27d70072c8448f413496a0deef78 gas smart-main

Another problem can be a corrupt P1 port. Or in my case the wires in the connector to the Flukso meter were not fitted well.

gebhardm's picture
gebhardm |

@jghaanstra - does the syslog still show the hardware check error? If yes, icarus75 has to deal (and potentially send a nice letter to China)

jghaanstra's picture
jghaanstra |

@threma, the sensors are showing in my account but they where registered when my Flukso was still working so it doesnt really say anything.

@gebhardm, the hardware error seems to be gone. I was able to submit the sensor config without any errors. Below is the log.

  1. Saving sensor parameters: ......
  2. Committing changes: true
  3. Syncing configuration: gh 2 2 .. ok
  4. Hardware check (major: 2, minor: 2) .. ok
  5. se 0 0 .. ok
  6. se 1 0 .. ok
  7. se 2 0 .. ok
  8. se 3 0 .. ok
  9. se 4 0 .. ok
  10. se 5 0 .. ok
  11. sk 0 0 0 .. ok
  12. sp 0 1 2 3 4 5 .. ok
  13. sm 0 5163 .. ok
  14. sf 0 0 .. ok
  15. sm 1 0 .. ok
  16. sf 1 0 .. ok
  17. sm 2 0 .. ok
  18. sf 2 0 .. ok
  19. sm 3 1 .. ok
  20. sf 3 0 .. ok
  21. sm 4 1 .. ok
  22. sf 4 0 .. ok
  23. sm 5 0 .. ok
  24. sf 5 0 .. ok
  25. ct .. ok
  26. generating a new /etc/avahi/services/flukso.service
  27. /usr/bin/fsync completed successfully. Bye!
  28.  
  29. Restarting the Flukso daemon: ok

jghaanstra's picture
jghaanstra |

I also checked the output from cat /dev/ttyS0 which is supposed to show the pulses from the P1 port and this is the jibberish that comes out. Obviously something is wrong.

  1. root@flukso-eb6e6c:~# cat /dev/ttyS0
  2. m,f'=m,'f'=m,'f4=lrm-=,'4fvVV6vV66=lr-mrR222Rdvvvmvmlr+9=m2$,=lr4o9(
  3. eYfv=m,''/6VvvvV6$'i,mZmrII
  4. 'i,mmr6mRE'ilmZmve
  5. 'ilmm24IE=m,'4mvv'i,4mvvv-'il4mvvvmv=m,mmm,,v=(
  6. eYfv=m,''/6VvvvV6$'i,mZmrII
  7. 'i,mmr6m2E'ilmZmve
  8. 'ilmm24IE=m,'4mvv'i,4mvvv-'il4mvvvmv=m,mmm,,v=(
  9. eYfv=m,''/6VvvvV6$'i,mZmrII
  10. 'i,mmr6mE'ilmZmve
  11. 'ilmm24IE=m,'4mvv'i,4mvvv-'il4mvvvmv=m,mmm,,v=m,f'=m,'f'=m,'f4=lrm-=,'4fvVV6vV66                        =Mlr-mrR222Rdvvvmvmlr+9=m2$,=lr4o9(
  12. eYfv=m,''/6VvvvV6$'i,mZmrII
  13. 'i,mmr6mrE'ilmZmve
  14. 'ilmm24IE=m,'4mvv'i,4mvvv-'il4mvvvmv=m,mmm,,v=m,f'=m,'f'=m,'f4=lrm-=,'4fvVV6vV66                        =lr-mrR222Rdvvvmvmlr+9=m2$,=lr4o9(
  15. eYfv=m,''/6VvvvV6$'i,mZmrII
  16. 'i,mmr6mE'ilmZmve

gebhardm's picture
gebhardm |

...that looks rather like the baudrate is not fitting...

jghaanstra's picture
jghaanstra |

Not a single responsive from Flukso itself, not even after sending an email. My Flukso is useless now, just lame.

What would a non-fitting baud rate mean Gebhardm? Is there anyway to fix it an why would it all of a sudden change without any interaction?

jghaanstra's picture
jghaanstra |

Well, seems like I fixed it myself by running the command "fp1". My guess is that my Fluksometer somehow reset himself and this command needed to be run to register the virtual sensors for the smart meter again.

threma's picture
threma |

Congratulations JG Haanstra. After 25 days you fixed it yourself! Flukso is a good school to learn by try-and-error to solve problems with their products. But how many people have the patience and knowledge to graduate at the Flukso university? I think most people say "F*** Flukso" and threw the Flukso meter in the garbage can!

rswennen's picture
rswennen |

I have the same problem on port 3, how do I run this command.

vringer's picture
vringer |

download putty.exe
run it
connet to your FLM by typing the IP adress
you will get a commandline (like DOS...)
FLM will ask to login (type: root )
FLM will ask to give the password (type: root
You will get more lines that you are'in'.
Then type fp1