By the way, this is the board I made for my application!

/C

Yes, only one 4.7 kOhm from 3.3 to GPIO/dataline at the Rasberry connector. The 100 Ohm is only if you have problems with impedance mismatch, and in your case should not be a problem with that. With your topography but with much longer cables and having problem, I would try 100 Ohm at the start of ...

I have 9 sensors, length appr.15 m and weigth appr. 35 m with 4.7 kOhm pull-up and in parasitic mode with no problems. (Using Raspberry GPIO and kernel support). I have a second installation close to a compressor and in that case it is only 4 m length and 2 sensor, was force to go to 1.2 kOhm pull ...

You need to have information on how your alarm is connected and function. One way is with Fibaro Universal Sensor, install it between your PIR and the alarm control unit:
http://www.fibaro.com/manuals/en/FGBS-3 ... -v1.01.pdf

/C

Hi, I found the same errors with using XLMSpears app. A corrected file is in my previous post.

I used that page as information while writing the config file, it is above my linux skills and I have not submitted a pull request to OZW.

/C

XMLSpear rapported 4 errors, corrected in this file:
Thanks Domosapiens!

1. Documentation says 1A but box and label on unit says 1B

2. No special checks. Done editing on Fraise.app and did not rapport any errors. Do you have any suggestion for a OSX xlm-editor?

3. Thanks!

/C

The only way in LUA that I know is to go via a file (but I am not a LUA expert):

os.execute('curl "http://192.168.1.2/cgi . . . (your cgi command) . . ." > /home/pi/xxx.txt')

then in LUA open the file and read what you need.

/C

jackfagner, yes I did!

Here it is:

Totof: There is a way to change resolution from a Raspberry Pi! I have tested and it is working. Found a program Raspberry forum, courtesy of Daniel Perron, modified to work on Pi2 and now I can change resolution on sensor. Found it here: https://www.raspberrypi.org/forums/viewtopic.php?f=37&t=77611 ...

And also if Fibaro could make a change in the Config options so one could define the resolution of the temp. sensors, that would be even better! I am leaving the FGBS-001 as a 1-wire interface, will use kernel support (w1-gpio/w1-therm modules) and with my own script to update User Variables from ...

I will answer myself on the temperature question: The logs from OpenZWave show that FGBS-001 was reporting temperature and always with last byte = 0: ... Node013, Received: 0x01, 0x12, 0x00, 0x04, 0x00, 0x0d, 0x0c, 0x60, 0x0d, 0x03, 0x01, 0x31, 0x05, 0x01, 0x44, 0x00, 0x00, 0x55, 0xf0 , 0x72 ...

Hi, Have same problem, my sensor is giving 160-200 degree readings. (Raspberry Pi 2 / Razberry / Domoticz / openZwave / FGBS-001) Have an idea that it could be resolution setting, 9 bit to expected 12 because reading divided by 8 would give me almost correct values. Tested sensor by making a simple ...

Hi folks, Got a new Philio PAN06-01B, it did include OK but had no configuration options. (This is tested on Domoticz on Raspberry/Razberry and OpenZwave.) I do have an PAN06-1B but the included manual and the only spec’s I could find in the internet are for the PAN06-1A and therefore labeled this f ...