Hi,
I would like to know when firmware 244 will be released, I'm also curious if mosquitto 1.4 with websocket support will be installed by default?
Openwrt has support for mosquitto 1.4 with websockets, just compiled it yesterday and after using mqtt bridges this feels much cleaner.
Firmware r24x is currently in beta, with r245 just made available for testing. Let me know if you'd like your FLM upgraded to r245.
Any release notes available? :-)
Hi Icarus,
Please feel free to upgrade, would like to beta test new things.
And release notes ftw :)
@cdr Your FLM is scheduled for an upgrade to a r245 beta release within the hour. Release notes will be published once we get to an official r24x release. In the mean time you can parse the git commit log to inspect all code changes.
Thanks. :-)
@Bart - could you please add the few lines of MQTT-config-publishing to the fluksod as I guess old FLMs will not be switched to the wwd... Thanks.
willing to test. what whould we look for?
Thanks for the update, everything is running smooth here; I like the gauge and meters created by @GEBHARDM, this should be installed by default IMO.
I noticed a lot of messages published in topic daemon/tmpod/check, why is this? It's eating my websocket bandwidth :)
@CDR - thanks for the flowers :-) Bart promised to have a look for firmware v2.5.x, so let's wait and see...
Corresponding to the tmpod.lua code the daemon topics are created by the
-- mqtt connection servicingin the tmpo's main loop with the current source code version; maybe this is intentional to make the FLM behave like a "nasty little kid" that wants continuous attention ;-) (I did not experience any errors without it in the v2.4.4)@cdr One user reported that a tmpod disconnect from the mosquitto broker had gone unnoticed to the daemon. If this happens, no tmpo blocks will be generated or published. So in commit b53c65 I added error checking to every mqtt call and I'm sending an empty mqtt message on
/daemon/tmpod/checkevery second.If you're only interested in sensor data, just subscribe to
/sensor/#and you'll not be spammed with messages on the/daemon/#topics.@Jaap Your FLM is scheduled for an upgrade to r245 within the hour.
My flukso 2B is still on 232, when should I upgrade to newer version.... Everything is working without problems, just asking...
Hey Bart,
Would love to get r245 a test, if possible :)
Currently on 241 according to the flukso dash
cheers
adam
@ICARUS75 thanxs, I see the new version but something is wrong with timestamp.
on flukso I see "Incorrect system time"
I cant get it correct, tried reboot and setting time via ntp but syntax seems to be incorrect.
Tried to enable ntpd but it does not help the ntp servers are accesable via network on pc.
Also correcting /etc/config/system as on wiki http://wiki.openwrt.org/doc/uci/system
did not help
Maybe a reinstall, several reboots did not work, gui still gives errors after last reboot a lot of :
"/usr/lib/lua/luci/sauth.lua:80: Security Exception: Session ID is invalid! stack traceback: [C]: in function 'assert' /usr/lib/lua/luci/sauth.lua:80: in function 'read' /usr/lib/lua/luci/controller/rpc.lua:28: in function 'authen' /usr/lib/lua/luci/dispatcher.lua:370: in function 'dispatch' /usr/lib/lua/luci/dispatcher.lua:195: in function "
Did you clear your browser cache?
I cleared browser cache and tried other browsers but stil incorrect system time. On other browsers/computer I do not get the ..lua/luci error .
but system just rebooted.... @icarus75 Bart are you doing the upgrade again?
I cleared browser cache and tried other browsers but stil incorrect system time. On other browsers/computer I do not get the ..lua/luci error .
but system just rebooted.... @icarus75 Bart are you doing the upgrade again?
Maybe upfront try to use the "factory refresh" (this actually does a complete reinstall from a "save" partition on the FLM) - this may be an indicator if the whole update went wrong:
"Restore firrmware - Keep the button pressed for between 60 and 120 seconds to restore the Fluksometer's stock firmware and reboot. You will have to reconfigure all network and sensor settings. Connect to the local web interface after the heartbeat LED starts blinking again."
@voogt Can you keep your FLM powered and connected to the net? Then I can have a remote peek to see what's going on. Did you modify any internal settings via ssh?
No only change was another wifi network but changed it back to old one. On ssh I only tried to enable ntpd.
this you can see via history..... S..t there is no histroy on the box.. only session based I think.
Issue is I think related to not working op time synchro so how to enable ntp or because ther was no issue with old firmware...
I will not do a factory reset yet, wait for Bart is there a easy way to save config?
Keybord not working.... I cannot edit my post.... so again
No only change was another wifi network but changed it back to old one. On ssh I only tried to enable ntpd.
this you can see via history..... S..t there is no history on the box.. Only session based I think.
Issue is I think related too not working op time synchronisation, so how to enable ntp or because there was no issue with old firmware...??
I will not do a factory reset yet and wait for Bart (he is analysing the box) is there a easy way to save config I saved config info from gui but is it also written to a config or xml file??
Look for the flukso.uci file using ssh; ref to https://github.com/flukso/flm02/tree/develop/openwrt/package/flukso/config
Configuration is also provided (for firmware versions v24x with tweak) also on MQTT topic
/device/<device id>/config/sensor- see https://www.flukso.net/content/obtain-flm-configuration-mqttI got the date and time changed after paying around for correct syntax.
via ssh:
$ date -s '2015.07.03-19:35'
Only there is no time synchro so after a reboot, time is incorrect again. But for now it works
@Icarus Bart do you have any Idea why time synchro is not working?
Now data is also loaded again, @Icarus75 this is a bug for 245 beta? Only issue was time sync not working anymore.
Tempory solution is to set time manualy (via ssh as ROOT date -s '2015.07.03-19:35').
But then after every reboot or summer/wintertime change time has to me changed. Also I do not know how acurate the hardware clock is. I can test it again on my box if necessary a restart wil show issue but I think it has to do with the time synchronisation .
Small update on graphs, it only shows stange figures on Flukso site/dash pvoutput show correct readings... (no flatliners for some sensors).
See this forum post for a reply. Putting a lock on this one.