gebhardm/flmdisplay

by sebastien.otten on Wed, 12/11/2014 - 16:40

Hi Gebhardm,

I installed the flmdisplay/combined/raspi_setup.mdon Rpi and I got this error at running, but the page is open and not data.

The difference between raspi_setup.mdon and my Rpi is that I installed RASPBIAN 2014-09-09 instead of the 2014-06-20 that is not available.

~/node_modules/thing-client$ node test.js
*** WARNING *** The program 'node' uses the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see

Many thanks for your help.

sebastien.otten | Wed, 12/11/2014 - 16:50

All the message:

*** WARNING *** The program 'node' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see
Database flm successfully connected
Create/connect to table successful...

gebhardm | Wed, 12/11/2014 - 19:49

As it says, it is a warning as there is a potential incompatibility between Apple's implementation and the avahi-version; this can be neglected as far as I can check this (for my scripts).
As I updated my RasPi always via apt-get upgrade/update I experienced no issues, also on a fresh install.
There might (sic) be also an issue with the node version - I use v0.10.29 (as v0.10.30++ did not compile)
After the Create/connect table statement there shall be a "detected:flmip:1883" - if this is not given, then the FLM was not detected (why so ever - I did not experience any issue on RasPi nor Mac nor PC)
Use the mDNS example to see whether you detect your FLM - if not, only local check can help (sorry...): https://github.com/agnat/node_mdns

gebhardm | Wed, 12/11/2014 - 21:44

I bet there is an issue with the Bonjour detection - please refer to https://www.flukso.net/content/multiple-flm-discovery and check the test scripts there; only if this is working, the combined persist and panel script with detection will work...

sebastien.otten | Mon, 17/11/2014 - 09:40

Hi,

I will try to re-install all again. I could not find out if it detect the FLM.

sebastien.otten | Mon, 17/11/2014 - 10:56

Do I need to install something else?

gebhardm | Mon, 17/11/2014 - 13:46

Beside https://github.com/gebhardm/flmdisplay/blob/master/combined/raspi_setup.md nothing needs to be done for the gauge/persistence application
BUT, as written, your FLM was not recognized via Bonjour, so you need to check this first; follow https://www.flukso.net/content/multiple-flm-discovery
With node.js installed you need to install the multicast DNS service "mdns" via npm and use the code from the first block as a simple discovery method... - only if that is working, the flmdisplay will work (if not switching to the manual code - again as described)

sebastien.otten | Mon, 17/11/2014 - 17:25

I started to install again.

Is it normal this message "ignoring input and appending output to `nohup.out'"? After command nohup make &

Thanks

gebhardm | Mon, 17/11/2014 - 18:43

Yes it is - "nohup" read "no hang-up" and "&" sends a process into background; so you can log off from the RasPi without the make to stop (all "screen" output of make then can be read from nohub.out)... Get yourself an unix intro ;-)
tail nohup.out shows you where the make process currently is - I use this as I use a headless RasPi in the basement near the PV-inverter and switch box.

sebastien.otten | Thu, 20/11/2014 - 12:57

after tail nohup.out is done I need to do "sudo make install"

How can I know that "nohup make &" finished?

gebhardm | Thu, 20/11/2014 - 13:33

As far as I remember after all the compile steps there was some copying step that was "obviously" the end of the process; otherwise you'll recognize that the file is not increasing in size any longer; alternative is looking at the process overview... (ps ax)
Feel free to use your imagination and also www.giyf.com

sebastien.otten | Thu, 20/11/2014 - 14:04

It finished but there are errors.

"/out/Release/mksnapshot.arm' failed
make[1]: *** [/home/pi/node/out/Release/mksnapshot.arm] Error 1
make[1]: Leaving directory '/home/pi/node/out'
Makefile:45: recipe for target 'node' failed
make: *** [node] Error 2"

Are they important?

sebastien.otten | Thu, 20/11/2014 - 14:28

deps/v8/tools/gyp/mksnapshot.arm.target.mk:129: recipe for target '/home/pi/node/out/Release/mksnapshot.arm' failed
make[1]: *** [/home/pi/node/out/Release/mksnapshot.arm] Error 1
make[1]: Leaving directory '/home/pi/node/out'
Makefile:45: recipe for target 'node' failed
make: *** [node] Error 2
make -C out BUILDTYPE=Release V=1
make[1]: Entering directory '/home/pi/node/out'
make[1]: Nothing to be done for 'all'.
make[1]: Leaving directory '/home/pi/node/out'
ln -fs out/Release/node node

gebhardm | Sat, 22/11/2014 - 18:47

I just did a fresh install on a RasPi model B with the current Raspbian distro (2014-09-09) - if you EXACTLY follow the RasPi install description there shall be no issue; make sure to READ and FOLLOW every line, especially the git checkout and ./configure advice on node.js installation - everything else is beyond my scope.