Hi,
Just updated the sensor-config on my Flukso (among others, I changed a pulsecounter from electricity to water, where I also changed the constant to 0.5).
The new sensor is working (checked via the local realtime API).
** questions:
- when/how often is the sensorinformation on the Fluksowebsite updated - after 3 days I still see that pulsecounter as electricity & not water
thanks
Does anyone have an idea how I can update the sensors on the flukso website in my account according to the sensors I have configured on the Flusko's themselves?
It does not seem to update automatically...
thanks
Bart is on vacation to the end of this week i think and only he can change the data on the website.
On the other hand, did you check the syslog on the FLM locally ?
With the new firmware r247 you can also check the MQTT values on a new tab locally on the FLM.
See this tread : https://www.flukso.net/content/new-firmware-and-upgrade-descriptions-dum...
Ok - I've tested everything, there are 3 issues, here's the status:
** Configuration: 2 flukso's:
- on both the 1st 3 are A-clamps
- the 1st Flukso has the last 2 inputs as counters from kWh-meters
- the 2nd Flukso has the 4th port configured as water-gauge (constant=0.5); the last as gas-gauge (constant=10)
** Status of local readout via API
(via http://:8080/sensor/?version=1.0&interval=minute&unit=watt&jsonp_callback=realtime)
All OK, except the gas-port; all (9) other give output like this, which is as it should:
realtime([[1439548437,242],... ...,[1439548496,247]]);
ISSUE 1: The last port on The 2nd device shows just this: []
Possibly I did not place the gas probe correctly? :-) See picture: http://hofmans.be/gassensor.jpg - I tried positioning in in every corner in every possible orientation - same results.
** MQTT readout
When I check via MQTT (either locally on the local browser or via my Raspberry) the output for the 1st Flukso works perfectly.
ISSUE 2: When I do same for the 2nd Flukso, it doens't work.
Via the browser, I get the following error(s): ""AMQJSC0001E Connect timed out". and sometimes "AMQJS0007E Socket error:undefined."
On my Raspberry I get the following: ""Error: Connection refused"
I configured the 2nd Flukso the same as the 1st one - is there a conflict somewhere because there are 2 Flukso's in the same network?
** config of sensors on Flukso website
I reconfigured my sensors a week or 2 ago.
ISSUE 3: The changed names, and the water- and gas-gauge don't show on the Flukso website. The water-sensor, which was previously configured as kWh-pulse-reader, still reads as 'electricity'. The gas-gauge doesn't show up. I thought this was automatically, that as soon as you change the config on the Flukso itself, it is uploaded to the Flukso website. What am I doing wrong?
Thanks in advance for the help!
Hi - sorry to ask again, but does anybody have an answer for me - I have several problems with my Flukso installation.
Thanks !!
Perhaps a Fluksonian will try to help you at your home ?
In what town or village do you live ?
If someone lives nearby, one can help, but for details like phone and/or street address, best is to communicate by email or so.
Issue 1: The gas probe should be installed on the right side of the cavity with the markings facing down. To test the proper functioning of the port you can short the + and - inputs a couple of times and check the mqtt logs. The gas probe can be triggered by holding a magnet close to the probe.
Issue 2: Do you access both FLM MQTT interfaces over wifi or ethernet? Did you make any specific config changes, especially via the FLM's shell? Can you pass me the serial of the FLM having MQTT issues?
Issue 3: Configuration changes are now synced with flukso.net via MQTT. So this could be related to issue 2. Can you confirm that the sensor config change was made to FLM #2?
Hi Bart,
Thanks for taking some time for this!
issue 1: I positioned the sensor like you said - working now!
issue 2: I access both FLMs over wifi (after changing the internal FW).
The only config-changes I made are fixed IP, DNS, NTP & firewall (to allow wifi) - the rest I didn't touch.
Serial of working FLM: FL02000010
Serial of FLM with MQTT issues: FL02000051
issue 3: indeed, when I do sensor changes on FLM1, they get sync'd to flukso.net, on FLM2 they do not, so it boils down to a MQTT issue on FLM2.
on FLM2: I see a discrepancy between the hostname configured in /etc/config/system (which reads as 'flukso-466605') and the hostname printed on the cli, which just reads as 'flukso'. On FLM1 these match.
Perhaps this is an issue?
If you could check, would be much appreciated! Thanks!!
Something seems to have gone awry during the migration to r247. I have to dig a bit deeper into this. Please leave your FLM running as is. I'll report back when I've finished the investigation.
I have found a bug in the r247 migration script. The bug only manifested itself when upgrading from a version < 230. Do you remember which version your FLMs were running prior to the upgrade? Could FL02000010 have been on a version > 230 while FL02000051 was on a version < 230?
I have manually patched FL02000051. So these issues should be gone now.
Thanks for reporting the problem
/Bart.
SUPER! While I'm not sure, it's indeed quite possible that the 51 was on <230 prior and the 10 was not.
thanks very much!