Hello community,
working with the TMPO charting I started the corresponding query daemon on my FLM (still v244) some while ago; and it runs and runs and runs; no dump, no break... Anybody else gained experience so far? If nobody experiences any issues (if so, please report as github issue) we might convince Bart to integrate it into the tmpo-daemon with firmware v25x already...
Thanks for your feedback
Markus
P.S.: If somebody can tell me, why the heck the input fields do not provide full text height, please give me a hint also! (css oddity between the two bootstrap stylesheets, of course)
P.P.S.: To get an understanding what this is all about, read my corresponding blog article.
Hello Markus,
I'll be having a deeper look at your local charting code after r24x is out. With no major showstoppers, r24x should be released by the end of the month.
Cheers
/Bart
I have FluksoChart running AOK in FF and Chrome OSX 10.10. Safari doesn't show text in the input fields (probably local problem), Chrome is fastest.
http://gysenbergs.info/data/fluksochart.png
Still have to figure out this topic: .. payload: .. thing. If a day had 36 hours ...
Looks quite OK. The weird squares in the solar graph are caused by the averaging; I changed this with the current code version of chart.js. I would be interested in the water/gas graph, please check the scaling as I currently just go for Wh... - you'll get that with the topic, it's straight forward, no magic...
To provide an MQTT metaphor:
MQTT topics are like the titles and chapter headlines of a continuously updated essay book (might be called "blog" these days); you can subscribe to either of the chapters in which you are interested - subscription is explicit; only messages on named topics are passed on to you; this you can do explicit by exact chapter name "/sports/biathlon" or by wildcards /sports/# - the complete sub-chapter hierarchy of "sports" (here for example "biathlon" and "biathlon/Norway") and /sports/+ - exactly the first level of sub-chapters of "sports", thus only "biathlon" neglecting "Norway"; /sports/+/+ the first and second sub-level and to forth...
MQTT payload then denotes the actual content in the subscribed topics - this is the stuff to check, compute, recognize.
I enhanced the chart.js by a different handling of electricity and water/gas (I don't have that type of sensors attached, so I am dependent on your testing) - download the "raw" file from Github if you haven't cloned the complete repository to pull and "scp" just that into the respective FLM folder; this is actually also a method to play with different settings if you don't want to use the vi on the FLM directly... After a refresh on the browser this lets you test and debug the presentation; poor man's IDE ;-)
Thanks very much for clarification and effort. This is what a mere mortal like me needs (after all, I'm more of an art scientist than an ICT person). Now, where is my thinking cap ...
Meanwhile, here are some screenshots. These clearly illustrate Flukso's measurements in a comprehensive format:
http://gysenbergs.info/data/fluksochart
New chart.js version available that should show the actual water and gas consumption as liters occuring in a certain time interval like the electricity wattage. Please test.
On Safari 8.0.3: This version throws CSS-errors already on loading the FLM's landing page and fails to instantiate any JS file; so I would name this simply "Safari sucks"...
Update - the messy input on the chart indeed was an incompatibility with bootstrap v3, which I now removed; now all visualizations should work in all browsers... (I "love" web programming)
But again the question on the TMPO daemon ;-)
Nice!
http://gysenbergs.info/data/fluksochart/FluksoChart150315.png from Chrome Version 39.0.2159.4 dev (64-bit)
Jos, you should "update" to "v3.2", then is also works with Safari (make sure to clear browser cache or reload the pages) :-) - https://github.com/gebhardm/flmlocal/releases/tag/v3.2
Works AOK now in Safari. Again, thanks!
FYI - the query daemon has been placed in a pull request with included startup capability, so no need for manual activity. See https://github.com/flukso/flm02/pull/7
It is running fine on mine too - no problems seen :)
i get this issue trying to run it
Jan 1 00:01:14 flukso-a5cda6 daemon.info queryd[699]: Sucessfully started with DEAMON=queryd and DAEMON_PATH=/var/run/queryd
May 3 12:00:04 flukso-a5cda6 daemon.err queryd[699]: /usr/sbin/queryd.lua:51: attempt to concatenate a nil value
May 3 12:00:05 flukso-a5cda6 daemon.err queryd[699]: 10 restarts within a 60 sec window
May 3 12:00:05 flukso-a5cda6 daemon.info queryd[699]: Exiting...
all other flm local works fine
downloaded and reinstalled latest FLM02 flm local www/ folder
installed new etc/init.d/flukso file
re added /usr/sbin/queryd.lua and linked it
now lost all graphs on the flukso and still non working tmpo
Note: The flmlocal installation does not alter any FLM inherent data; it is just static content; so nothing lost until a factory reset... if you stay with the description it "should" all work straight forward. As an alternative, try the tmpo access via Python as described in https://github.com/flukso/tmpo-py
And, of course, you have to start the new daemon
/usr/sbin/queryd -u flukso
Check withps
to see the running workers. There must be an entry likei ran
/usr/sbin/queryd -u flukso
and this is what syslog on flukso showsunsure what you mean with the check with ps for a running worker
on another note the other flm local is working except the gauges
Hello B-Man,
with
ps
I refer to the commandps
that just shows the running processes of the system like on any Unix machine. But from the syslog I see that queryd is successfully started. What irritates is the following bunch of errors on queryd. Here in line 51 of the lua script the path is set where tmpo stores its values; this seems to not exist on your FLM, why so ever. Please check the content of your queryd.lua file; if line 51 contains uci:get("flukso", "tmpo", "root") then you are using the FLM03 version instead of the FLM02 version; in the FLM03 the storage directory is set by configuration, not hard coded; and on the FLM02 exactly this configuration does not yet exist...Regards, Markus
ah my mistake, got confused with the flm03 serial vs the flm02b model i did have the wrong version.
ps
all appears to be working!
thanks
Yes, that looks fine now :-) Enjoy!