Z-Wave factfile Fibaro FGBS-001 Universal Binary Sensor

Information about specific Z-Wave devices
Post Reply
User avatar
Domosapiens
Posts: 371
Joined: Wednesday 20 August 2014 12:08
Target OS: Windows
Domoticz version: V3.5981
Location: NL
Contact:

Z-Wave factfile Fibaro FGBS-001 Universal Binary Sensor

Post by Domosapiens » Friday 11 December 2015 12:35

Supplier:
Fibaro

Website:
http://www.fibaro.com/uk/support#

Function:
Universal Binary Sensor for 4 temperature probes DS18B20 and 2 discrete inputs

Z-Wave5
No
Superseded (?) by FGBS-321 version 1.2 and 2.1-2.3 (not sure of that! Not avail in NL?) Not sure if that one is Gen5.

Rebranding:
unknown, never seen

Device Library from http://www.pepper1.net
http://www.pepper1.net/zwavedb/device/514

Manuals from manuals.zwaveeurope.com and doc.eedomus.com:
manuals.zwaveeurope.com: PDF
doc.eedomus.com User doc PDF

DS18B20 sensor
Datasheet
Search the Chinese webshops for chip or wired versions. Less then 1.50 Euro (1 fail in a sample of 24).
DS18B20

All DS18B20 sensors do have an unique ID, therefor the DS18B20 sensors must be connected before Inclusion.
Replacing or adding a DS18B20? Exclude and Include again!

I have one working with 10 meter CAT5 cable, with remaining leads connected to Earth.

Hint: use aluminum tape to connect them with pipes.
Absolute accuracy reasonable, relative accuracy good (+/- 0.3C): adapt them in Domoticz.
Hint: tape them together for 24hr and correct step by step.
Resolution is great, 0.1C

Domoticz experience
Hardware:
Fibaro FGBS-001 population.JPG
Fibaro FGBS-001 population.JPG (51.52 KiB) Viewed 7964 times
Remarks:
6 operational. For temperature no polling needed. For discretes: not sure, currently with polling.
(on my to do list to investigate: will feed 2 units with the same signal. With and without polling)
Polling results in OZW_log errors: Node005, ERROR: Dropping command, expected response not received after 1 attempt(s) ....in average 3x per hour
In the last 2 year they never lost their ID.
They give an average contribution to the Z-Wave network.

Configuration:
Fibaro FGBS-001 configuration_small.jpg
Fibaro FGBS-001 configuration_small.jpg (333.19 KiB) Viewed 7964 times
Devices
Fibaro FGBS-001 devices.jpg
Fibaro FGBS-001 devices.jpg (56.84 KiB) Viewed 7964 times
zwcfg_0xaaaaaaa.xml sample:

Code: Select all

	<Node id="3" name="Temp_A" location="" basic="4" generic="32" specific="1" type="Routing Binary Sensor" listening="true" frequentListening="false" beaming="true" routing="true" max_baud_rate="40000" version="4" query_stage="Complete">
		<Manufacturer id="010f" name="FIBARO System">
			<Product type="0501" id="1002" name="FGBS001 Universal Binary Sensor" />
		</Manufacturer>
		<CommandClasses>
			<CommandClass id="32" name="COMMAND_CLASS_BASIC" version="1" request_flags="5" after_mark="true" mapping="48" setasreport="true">
				<Instance index="1" endpoint="1" />
			</CommandClass>
			<CommandClass id="43" name="COMMAND_CLASS_SCENE_ACTIVATION" version="1" request_flags="5" after_mark="true">
				<Instance index="1" />
			</CommandClass>
			<CommandClass id="48" name="COMMAND_CLASS_SENSOR_BINARY" version="1" request_flags="5">
				<Instance index="1" endpoint="1" />
				<Instance index="2" endpoint="2" />
				<Value type="bool" genre="user" instance="1" index="0" label="Sensor" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="False" />
				<Value type="bool" genre="user" instance="2" index="0" label="Sensor" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="False" />
				<SensorMap index="0" type="80" />
				<SensorMap index="0" type="83" />
				<SensorMap index="0" type="172" />
				<SensorMap index="0" type="175" />
			</CommandClass>
			<CommandClass id="49" name="COMMAND_CLASS_SENSOR_MULTILEVEL" version="1">
				<Instance index="1" endpoint="3" />
				<Instance index="2" endpoint="4" />
				<Instance index="3" endpoint="5" />
				<Instance index="4" endpoint="6" />
				<Value type="decimal" genre="user" instance="1" index="1" label="Temperature" units="C" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="46.12" />
				<Value type="decimal" genre="user" instance="2" index="1" label="Temperature" units="C" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="47.62" />
				<Value type="decimal" genre="user" instance="3" index="1" label="Temperature" units="C" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="30.18" />
				<Value type="decimal" genre="user" instance="4" index="1" label="Temperature" units="C" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="28.62" />
			</CommandClass>
			<CommandClass id="96" name="COMMAND_CLASS_MULTI_INSTANCE/CHANNEL" version="2" request_flags="1" mapping="endpoints">
				<Instance index="1" />
			</CommandClass>
			<CommandClass id="112" name="COMMAND_CLASS_CONFIGURATION" version="1" request_flags="5">
				<Instance index="1" />
				<Value type="short" genre="config" instance="1" index="1" label="IN1 Alarm Cancellation Delay" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="65535" value="0">
					<Help>Input I alarm cancellation delay. Additional delay after an alarm from input IN1 has ceased. The parameter allows you to specify additional time, after which the input no. 1 alarm is cancelled once its violation has ceased. Default 0.</Help>
				</Value>
				<Value type="short" genre="config" instance="1" index="2" label="IN2 Alarm Cancellation Delay" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="65535" value="0">
					<Help>Input II alarm cancellation delay. Additional delay after an alarm from input IN1 has ceased. The parameter allows you to specify additional time, after which the input no. 1 alarm is cancelled once its violation has ceased. Default 0.</Help>
				</Value>
				<Value type="list" genre="config" instance="1" index="3" label="Type of input no. 1" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" vindex="1" size="1">
					<Help>Type of input no. 1, what the input 1 will report if no contact is made. Default 1.</Help>
					<Item label="Input NO (Normal Open)" value="0" />
					<Item label="Input NC (Normal Close)" value="1" />
					<Item label="Input MONOSTABLE" value="2" />
					<Item label="Input BISTABLE" value="3" />
				</Value>
				<Value type="list" genre="config" instance="1" index="4" label="Type of input no. 2" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" vindex="1" size="1">
					<Help>Type of input no. 2, what the input 2 will report if no contact is made. Default 1.</Help>
					<Item label="Input NO (Normal Open)" value="0" />
					<Item label="Input NC (Normal Close)" value="1" />
					<Item label="Input MONOSTABLE" value="2" />
					<Item label="Input BISTABLE" value="3" />
				</Value>
				<Value type="list" genre="config" instance="1" index="5" label="Type of transmitted control frame for association group 1" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" vindex="6" size="1">
					<Help>Type of transmitted control frame for association group 1, activated via input IN1. The parameter allows to specify the type of alarm frame or to force transmission of control commands (BASIC_SET). Default 255 - BASIC SET.</Help>
					<Item label="ALARM GENERIC" value="0" />
					<Item label="ALARM SMOKE" value="1" />
					<Item label="ALARM CO" value="2" />
					<Item label="ALARM CO2" value="3" />
					<Item label="ALARM HEAT" value="4" />
					<Item label="ALARM WATER" value="5" />
					<Item label="BASIC_SET" value="255" />
				</Value>
				<Value type="list" genre="config" instance="1" index="6" label="Type of transmitted control frame for association group 2" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" vindex="6" size="1">
					<Help>Type of transmitted control frame for association group 2, activated via input IN1. The parameter allows to specify the type of alarm frame or to force transmission of control commands (BASIC_SET). Default 255 - BASIC SET.</Help>
					<Item label="ALARM GENERIC" value="0" />
					<Item label="ALARM SMOKE" value="1" />
					<Item label="ALARM CO" value="2" />
					<Item label="ALARM CO2" value="3" />
					<Item label="ALARM HEAT" value="4" />
					<Item label="ALARM WATER" value="5" />
					<Item label="BASIC_SET" value="255" />
				</Value>
				<Value type="byte" genre="config" instance="1" index="7" label="Forced Level of Dimming group 1" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="1" max="255" value="255">
					<Help>Value of the parameter specifying the forced level of dimming / opening sun blinds when comes "switch on" / "open" command to devices from association group no. 1. In the case of alarm frames the alarm priority is specified. Possible parameter settings: (1 – 99) and 255. Value of 255 makes it possible to activate the device when using the Dimmer module it means activating the device and setting it to the previous stored condition, e.g. when Dimmer is set to 30%, then deactivated, and then reactivated using command 255, it will automatically be set to the previous condition, i.e. 30%. Default 255.</Help>
				</Value>
				<Value type="byte" genre="config" instance="1" index="8" label="Forced Level of Dimming group 2" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="1" max="255" value="255">
					<Help>Value of the parameter specifying the forced level of dimming / opening sun blinds when comes "switch on" / "open" command to devices from association group no. 2. In the case of alarm frames the alarm priority is specified. Possible parameter settings: (1 – 99) and 255. Value of 255 makes it possible to activate the device when using the Dimmer module it means activating the device and setting it to the previous stored condition, e.g. when Dimmer is set to 30%, then deactivated, and then reactivated using command 255, it will automatically be set to the previous condition, i.e. 30%. Default 255.</Help>
				</Value>
				<Value type="list" genre="config" instance="1" index="9" label="Deactivate transmission of frame cancelling alarm" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" vindex="0" size="1">
					<Help>Deactivating transmission of the frame cancelling the alarm or the control frame deactivating the device (Basic). It allows for disabling the deactivation function or the alarm cancellation function for devices associated with the appropriate input of the Fibaro Sensor. NOTE: Information concerning alarm violation or activation commands for devices from association groups are always sent. Default 0. ATTENTION: Information alarm triggered or command enabled for devices with associative groups are always sent. NOTE: Value "Group 1 not sent, Group 2 not sent" is only available in version 2.1 and up</Help>
					<Item label="Groups 1 and 2 sent" value="0" />
					<Item label="Group 1 sent, Group 2 not sent." value="1" />
					<Item label="Group 1 not sent, Group 2 sent." value="2" />
					<Item label="Group 1 not sent, Group 2 not sent." value="3" />
				</Value>
				<Value type="byte" genre="config" instance="1" index="10" label="Interval between successive readings of temperature sensors" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="1" max="255" value="30">
					<Help>Interval between successive readings of temperature from all sensors connected to the device in seconds. Possible parameter settings: (1 – 255). Default 20. ATTENTION: taking temperature readings from the sensor does not result in sending a temperature condition report to the central hub.</Help>
				</Value>
				<Value type="byte" genre="config" instance="1" index="11" label="Interval between forcing to send report concerning the temperature conditions" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="255" value="60">
					<Help>Interval between forcing to send report concerning the temperature conditions. The forced report is sent immediately after the next reading of temperature from the sensor, irrespective of the settings of parameter no. 12. Value 0 = Deactivates the function. Default 200. ATTENTION: Frequent sending of temperature condition reports is reasonable when the sensor is located somewhere where can occure rapid changes of ambient temperature. In other cases it is recommended to leave the parameter set to the default value.</Help>
				</Value>
				<Value type="byte" genre="config" instance="1" index="12" label="Insensitiveness to temperature changes." units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="255" value="8">
					<Help>Insensitiveness to temperature changes. This is the maximum acceptable difference between the last reported temperature and the current temperature taken from the sensor. If the temperatures differ by the set value or more, then a report with the current temperature value is sent to the device assigned to association group no. 3. Intervals between taking readings from sensors are specified by parameter no. 10. Possible parameter settings:0 – 255 [0oC to 16oC] [0 oF – 28.8oF] In order to set the appropriate value of the parameter, the following formula should be used: x = delta T x 16 - for Celsius x = delta T x 80 / 9 - for Fahrenheit x – parameter value delta T – maximum acceptable temperature gradient in Celsius or Fahrenheit If the value is set to 0, then information about the temperature will be sent every time, immediately once the readings have been taken from the sensor. Default 8.</Help>
				</Value>
				<Value type="list" genre="config" instance="1" index="13" label="Transmitting the alarm or control frame broadcast mode" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" vindex="0" size="1">
					<Help>Transmitting the alarm or control frame in "broadcast" mode (i.e. to all devices within range), information sent in this mode is not repeated by the mesh network. Default 0. ATTENTION: If the broadcast mode of information transmission is activated for a given channel, then transmission of information in singlecast mode to devices assigned to the association group of this channel is deactivated.</Help>
					<Item label="Sensor 1 and 2 Broadcast inactive" value="0" />
					<Item label="Sensor 1 broadcast mode active, Sensor 2 broadcast mode inactive" value="1" />
					<Item label="Sensor 1 broadcast mode inactive, Sensor 2 broadcast mode active" value="2" />
					<Item label="Sensor 1 and 2 broadcast mode active" value="3" />
				</Value>
				<Value type="list" genre="config" instance="1" index="14" label="Scene activation" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" vindex="0" size="1">
					<Help>Enable/Disable scene functionality. The device offers the possibility of sending commands compatible with Command class scene activation. Information is sent to devices assigned to association group no. 3. Default 0.</Help>
					<Item label="Scenes disabled" value="0" />
					<Item label="Scenes enabled" value="1" />
				</Value>
			</CommandClass>
			<CommandClass id="114" name="COMMAND_CLASS_MANUFACTURER_SPECIFIC" version="1" request_flags="5">
				<Instance index="1" />
			</CommandClass>
			<CommandClass id="133" name="COMMAND_CLASS_ASSOCIATION" version="1" request_flags="5">
				<Instance index="1" />
				<Associations num_groups="3">
					<Group index="1" max_associations="5" label="Input IN1" auto="true" multiInstance="true">
						<Node id="1" />
					</Group>
					<Group index="2" max_associations="5" label="Input IN2" auto="true">
						<Node id="1" />
					</Group>
					<Group index="3" max_associations="1" label="Temperature Sensor(s)" auto="true">
						<Node id="1" />
					</Group>
				</Associations>
			</CommandClass>
			<CommandClass id="134" name="COMMAND_CLASS_VERSION" version="1" request_flags="5">
				<Instance index="1" />
				<Value type="string" genre="system" instance="1" index="0" label="Library Version" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="3" />
				<Value type="string" genre="system" instance="1" index="1" label="Protocol Version" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="3.52" />
				<Value type="string" genre="system" instance="1" index="2" label="Application Version" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="2.01" />
			</CommandClass>
			<CommandClass id="142" name="COMMAND_CLASS_MULTI_INSTANCE_ASSOCIATION" version="1" request_flags="5">
				<Instance index="1" />
				<Associations num_groups="0">
					<Group index="1" max_associations="5" label="Input IN1" auto="true" multiInstance="true">
						<Node id="1" />
					</Group>
					<Group index="2" max_associations="5" label="Input IN2" auto="true">
						<Node id="1" />
					</Group>
					<Group index="3" max_associations="1" label="Temperature Sensor(s)" auto="true">
						<Node id="1" />
					</Group>
				</Associations>
			</CommandClass>
			<CommandClass id="156" name="COMMAND_CLASS_SENSOR_ALARM" version="1" request_flags="2">
				<Instance index="1" endpoint="1" />
				<Instance index="2" endpoint="2" />
			</CommandClass>
		</CommandClasses>
	</Node>
Conclusion
Unique and extreme small sensor capability.
Consumed input current not specified, but I have 3 running on one 12V 1.2A power supply.
I suspect that they are sensitive for ripple on the power supply (use an Elco!)
The weaker signal causes sometimes new strange values (like UV sensor data??). I think this is caused by the weak error recovering from Z-Wave.
This can cause pollution in the zwcfg_0xaaaaaaa.xml. In that case remove the node from the zwcfg_0xaaaaaaa.xml and let Domoticz re-discover it.
Not sure if polling is needed for IN1 and IN2 discrete inputs. Maybe Association Groups can do it better.
OUT1 and OUT2 are not controlled by Z-Wave! Only by IN1 and IN2.
They need to be embedded in a strong network.
Because of it's unique features: recommended.
But ... Superseded (???) by FGBS-321 version 1.2 and 2.1-2.3 (subsequent versions... that sounds like problems ??). Not seen avail. in NL.

Hope this helps
Domosapiens

[Edit: sanitized zwcfg_0xaaaaaaa.xml sample]
Last edited by Domosapiens on Wednesday 23 December 2015 23:59, edited 3 times in total.
Win Vista&7; 1#Aeon Z-Stick S2; 1#Aeotec Z-Sick Gen5, 6#Fib.FGBS001; 24#DS18B20; 8#Everspr.AN158-2; 3#Philio PAN04; 1#Philio PAN06, 1#YouLess El; 1#Fib.FGWPE; 1#ZME_RC2; 2#FAK_ZWS230, 2#Quib.ZMNHCDx, 1#Quib.ZMNHDD1, 7#EM6555

User avatar
Domosapiens
Posts: 371
Joined: Wednesday 20 August 2014 12:08
Target OS: Windows
Domoticz version: V3.5981
Location: NL
Contact:

Re: Z-Wave factfile Fibaro FGBS-001 Universal Binary Sensor

Post by Domosapiens » Wednesday 16 December 2015 19:20

Not sure if polling is needed for IN1 and IN2 discrete inputs. Maybe Association Groups can do it better
According to Pepper1:
Association Groups Capture.JPG
Association Groups Capture.JPG (34.67 KiB) Viewed 7878 times
The Z-wave Controller must be connected to Group 3 for it's "life line". In contrast to most other devices, that need a Controller connection with Group 1.
Adding a connection between the Controller and Group 1 gives the status of input IN1.
Group 2 can do the same for input IN2.

Devices - Node Management - Groups & Networks, shows this:
Connected to 3 groups.JPG
Connected to 3 groups.JPG (14.13 KiB) Viewed 7878 times
The + sign can be used to add the Controller (1) or other devices.
Press F5 to update.
Additional devices can be connected here (without Domoticz control) in a simple way.
F.i. if you sens the pump of the heater with IN1, you could add a floor heating pump to Group1 to synchronize both.
Did a test with 2 FGBS-001: both with all 3 Groups connected to the Controller (1).
One with polling, one without polling.
Both results are the same.
The rumor that the FGBS-001 needs polling comes in my opinion from not connecting the Controller to Group 3.
A recent OpenZwave update, incorporated in Domoticz after release 2.3799 could make some differences in the "not" auto inclusion of node 1 in Group 3.
In previous OpenZwave releases there was the assumption that the Controller needed standard connection to Group 1 for the "life line".
But I have not tested that version yet.

Wrap up for FGBS-001:
- always connect the Controller to Group3
- connect the Controller to Group 1 in case of use of IN1
- connect the Controller to Group 2 in case of use of IN2
- other devices can be synchronized with Group 1 or 2 by adding them to one of the Groups

Hope this helps
Domosapiens

Edit: No polling needed ? I'm not so sure anymore. Experimentation with a production system is not that smart ... :oops:
See quoted parts ... this needs more testing
Win Vista&7; 1#Aeon Z-Stick S2; 1#Aeotec Z-Sick Gen5, 6#Fib.FGBS001; 24#DS18B20; 8#Everspr.AN158-2; 3#Philio PAN04; 1#Philio PAN06, 1#YouLess El; 1#Fib.FGWPE; 1#ZME_RC2; 2#FAK_ZWS230, 2#Quib.ZMNHCDx, 1#Quib.ZMNHDD1, 7#EM6555

User avatar
Domosapiens
Posts: 371
Joined: Wednesday 20 August 2014 12:08
Target OS: Windows
Domoticz version: V3.5981
Location: NL
Contact:

Re: Z-Wave factfile Fibaro FGBS-001 Universal Binary Sensor

Post by Domosapiens » Saturday 19 December 2015 18:00

Some eye candy
Universal Sensor - Fibaro thumb.jpg
Universal Sensor - Fibaro thumb.jpg (22.29 KiB) Viewed 7825 times
Universal Sensor - Fibaro.png
Universal Sensor - Fibaro.png (69.67 KiB) Viewed 7825 times
FBUSWiringSensors.png
FBUSWiringSensors.png (22.25 KiB) Viewed 7825 times
Win Vista&7; 1#Aeon Z-Stick S2; 1#Aeotec Z-Sick Gen5, 6#Fib.FGBS001; 24#DS18B20; 8#Everspr.AN158-2; 3#Philio PAN04; 1#Philio PAN06, 1#YouLess El; 1#Fib.FGWPE; 1#ZME_RC2; 2#FAK_ZWS230, 2#Quib.ZMNHCDx, 1#Quib.ZMNHDD1, 7#EM6555

User avatar
mbliek
Posts: 826
Joined: Friday 12 July 2013 14:08
Target OS: Raspberry Pi
Domoticz version: beta
Location: the Netherlands
Contact:

Re: Z-Wave factfile Fibaro FGBS-001 Universal Binary Sensor

Post by mbliek » Sunday 20 December 2015 1:07

The FGBS-321 is the old one. Google gives result from 2012 when googling for that sensor.

User avatar
Domosapiens
Posts: 371
Joined: Wednesday 20 August 2014 12:08
Target OS: Windows
Domoticz version: V3.5981
Location: NL
Contact:

Re: Z-Wave factfile Fibaro FGBS-001 Universal Binary Sensor

Post by Domosapiens » Sunday 27 December 2015 23:44

@mbliek,
The FGBS-321 is the old one.
if so,
Why shows the Fibaro site the FGBS-321 and not the FGBS-001?
http://www.fibaro.com/uk/node/2484

In France it seems to be the common one.

Don't understand,
Domosapiens
Win Vista&7; 1#Aeon Z-Stick S2; 1#Aeotec Z-Sick Gen5, 6#Fib.FGBS001; 24#DS18B20; 8#Everspr.AN158-2; 3#Philio PAN04; 1#Philio PAN06, 1#YouLess El; 1#Fib.FGWPE; 1#ZME_RC2; 2#FAK_ZWS230, 2#Quib.ZMNHCDx, 1#Quib.ZMNHDD1, 7#EM6555

User avatar
mbliek
Posts: 826
Joined: Friday 12 July 2013 14:08
Target OS: Raspberry Pi
Domoticz version: beta
Location: the Netherlands
Contact:

Re: Z-Wave factfile Fibaro FGBS-001 Universal Binary Sensor

Post by mbliek » Monday 28 December 2015 20:42

Weird, I can get Fibaro from 3 different suppliers.
One in the Netherlands, one in France and one in Germany.
All are only offering the 001.

User avatar
Domosapiens
Posts: 371
Joined: Wednesday 20 August 2014 12:08
Target OS: Windows
Domoticz version: V3.5981
Location: NL
Contact:

No polling needed for IN1 and IN2

Post by Domosapiens » Saturday 24 September 2016 1:23

Summary:
No polling needed for IN1 and IN2 of the Fibaro FGBS-001 by using Multi Channel Association plus a Blockly for edge detection.

Provocative:

Currently I'm migrating from Aeotech Z-stick GEN-2 to GEN-5 and that was a good reason to try to eliminate the polling issue of the IN1 and IN2 inputs.
When a short reaction time is needed, a high polling frequency is mandatory. For the FGBS-001 as a negative side-effect, this high frequency is also applied for the connected temperature sensors.
When I started with the FGBS-001 there was no Multi Channel Association implemented (in Z-wave or Domoticz?) so the only way to use those inputs was polling.
For this migration I use Domoticz Version V3.5114

Guidance:
To clean-up:
Exclude the FGBS-001 by pushing 3x the FGBS-001 button while your stick is in Exclusion mode (long press for the Aeotech Z-stick).
The Aeotech Z-stick reacts with a fast flashing, that means your FGBS-001 is excluded.
Remove the power from the FGBS-001.
Reset the FGBS-001 by restore the power while pushing the FGBS-001 button for at least 10 seconds (at this moment your potential temperature sensors must be connected).
Include the FGBS-001 by pushing 3x the FGBS-001 button while your stick is in Inclusion mode (short press for the Aeotech Z-stick).
At the restart of Domoticz ( or Z-wave) a new Device: FIBARO System FGBS001 Universal Binary Sensor is shown (check the Log).

First part of the solution:
Check Devices - and find the Device number
Go to Node Management - Groups & Network
Add 1.1 to Group 1 and Group 2
TempF groups Capture.PNG
TempF groups Capture.PNG (5.52 KiB) Viewed 6358 times
Restart Domoticz or Z-wave.
After that, when the IN1 and/or IN2 goes from Low to High or High to Low, new Devices will appear.
Depending on Parameter 3&4: Normally Open, Normally Closed, Mono-stable, Bi-stable, new devices with new numbers will appear (check the Log)

Example:
My FGBS-001 sensor is 015, that means 0F in hex.
Temperature sensors are then 0F01, 0F02, 0F03, 0F04 (trailing numbering)
The polled IN1 and IN2 are 00000F00 and 00000F02

When using for Parameter 3&4 Normally Open:
For IN1 there are 2 new devices 000A0F00 and 000B0F00
For IN2 there are 2 new devices 00140F00 and 00150F00 (leading numbering)

Playing around, other choices for Parameter 3&4 give other Device numbers (f.i. 00170F00 for the Mono-stable)
Normally Closed gives also 2 new devices but I did not check/name them
TempF devices naming.PNG
TempF devices naming.PNG (127.61 KiB) Viewed 6337 times
The devices 000A0F00 , 000B0F00 and 00140F00 , 00150F00 are always ON in Domoticz.
Always ON but .... they contain a trigger Edge.

How to catch the Edge

How to catch the Edge with Blockly will be my next post.
Blockly ... yes Real men use Blockly (programming is sooooo 1985)

[Edit: replaced the Devices picture by a more recent one]
Win Vista&7; 1#Aeon Z-Stick S2; 1#Aeotec Z-Sick Gen5, 6#Fib.FGBS001; 24#DS18B20; 8#Everspr.AN158-2; 3#Philio PAN04; 1#Philio PAN06, 1#YouLess El; 1#Fib.FGWPE; 1#ZME_RC2; 2#FAK_ZWS230, 2#Quib.ZMNHCDx, 1#Quib.ZMNHDD1, 7#EM6555

User avatar
Domosapiens
Posts: 371
Joined: Wednesday 20 August 2014 12:08
Target OS: Windows
Domoticz version: V3.5981
Location: NL
Contact:

Real men use Blockly

Post by Domosapiens » Saturday 24 September 2016 11:18

So there are 4 new sensors. For each input 2.

For IN1 (the yellow lead) called here Sens_F1_NO_OFFpulse and Sens_F1_NO_ONpulse.
Define a binary (integer) Variable: here called SensF_IN1_State.
Make the initial value 0 because it is a NO (Normal Open) contact
Define a Dummy Variable: here called Dummy2_Geel_IN1_pulsed.

Create a Device controlled Blockly
Blockly detection Capture.PNG
Blockly detection Capture.PNG (27.93 KiB) Viewed 6335 times
The Dummy variable Dummy2_Geel_IN1_pulsed reflects the state of IN1 for further use.
After the Sens_F1_NO_OFFpulse the Variable and Dummy are 0.
If both are out-off-sync after a restart, one edge of IN1 is enough to sync them.

For IN2 create a comparable Blockly.
In case of Normally Closed, Mono-stable, Bi-stable, you have to find the correct Device numbers yourself

Next post: the Parameter configuration of the FGBS-001 that I use
Hope this helps
Domosapiens
Win Vista&7; 1#Aeon Z-Stick S2; 1#Aeotec Z-Sick Gen5, 6#Fib.FGBS001; 24#DS18B20; 8#Everspr.AN158-2; 3#Philio PAN04; 1#Philio PAN06, 1#YouLess El; 1#Fib.FGWPE; 1#ZME_RC2; 2#FAK_ZWS230, 2#Quib.ZMNHCDx, 1#Quib.ZMNHDD1, 7#EM6555

User avatar
Domosapiens
Posts: 371
Joined: Wednesday 20 August 2014 12:08
Target OS: Windows
Domoticz version: V3.5981
Location: NL
Contact:

FGBS-001 parameters

Post by Domosapiens » Saturday 24 September 2016 11:37

The FGBS-001 parameters:
TempF param1 Capture.JPG
TempF param1 Capture.JPG (118 KiB) Viewed 6335 times
TempF param2 Capture.JPG
TempF param2 Capture.JPG (203.34 KiB) Viewed 6335 times
TempF param3 Capture.JPG
TempF param3 Capture.JPG (56.05 KiB) Viewed 6335 times
Next post: a zwcfg_0xaaaaaaa.xml sample
Last edited by Domosapiens on Saturday 24 September 2016 11:41, edited 2 times in total.
Win Vista&7; 1#Aeon Z-Stick S2; 1#Aeotec Z-Sick Gen5, 6#Fib.FGBS001; 24#DS18B20; 8#Everspr.AN158-2; 3#Philio PAN04; 1#Philio PAN06, 1#YouLess El; 1#Fib.FGWPE; 1#ZME_RC2; 2#FAK_ZWS230, 2#Quib.ZMNHCDx, 1#Quib.ZMNHDD1, 7#EM6555

User avatar
Domosapiens
Posts: 371
Joined: Wednesday 20 August 2014 12:08
Target OS: Windows
Domoticz version: V3.5981
Location: NL
Contact:

FGBS-001 zwcfg_0xaaaaaaa.xml

Post by Domosapiens » Saturday 24 September 2016 11:41

The zwcfg_0xaaaaaaa.xml code related to the FGBS-001

Code: Select all

    <Node id="15" name="Temp_F" location="" basic="4" generic="32" specific="1" type="Routing Slave" listening="true" frequentListening="false" beaming="true" routing="true" max_baud_rate="40000" version="4" query_stage="Complete">
        <Manufacturer id="10f" name="FIBARO System">
            <Product type="501" id="1002" name="FGBS001 Universal Binary Sensor" />
        </Manufacturer>
        <CommandClasses>
            <CommandClass id="32" name="COMMAND_CLASS_BASIC" version="1" setasreport="true">
                <Instance index="1" />
            </CommandClass>
            <CommandClass id="43" name="COMMAND_CLASS_SCENE_ACTIVATION" version="1" request_flags="5" after_mark="true" innif="true">
                <Instance index="1" />
            </CommandClass>
            <CommandClass id="48" name="COMMAND_CLASS_SENSOR_BINARY" version="1" request_flags="5" innif="true">
                <Instance index="1" endpoint="1" />
                <Instance index="2" endpoint="2" />
                <Value type="bool" genre="user" instance="1" index="0" label="Sensor" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="True" />
                <Value type="bool" genre="user" instance="2" index="0" label="Sensor" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="False" />
                <SensorMap index="0" type="92" />
                <SensorMap index="0" type="95" />
                <SensorMap index="0" type="160" />
                <SensorMap index="0" type="163" />
            </CommandClass>
            <CommandClass id="49" name="COMMAND_CLASS_SENSOR_MULTILEVEL" version="1">
                <Instance index="1" endpoint="3" />
                <Instance index="2" endpoint="4" />
                <Instance index="3" endpoint="5" />
                <Instance index="4" endpoint="6" />
                <Value type="decimal" genre="user" instance="1" index="1" label="Temperature" units="C" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="0.00" />
                <Value type="decimal" genre="user" instance="2" index="1" label="Temperature" units="C" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="0.00" />
                <Value type="decimal" genre="user" instance="3" index="1" label="Temperature" units="C" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="0.00" />
                <Value type="decimal" genre="user" instance="4" index="1" label="Temperature" units="C" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="0.00" />
            </CommandClass>
            <CommandClass id="96" name="COMMAND_CLASS_MULTI_INSTANCE/CHANNEL" version="2" request_flags="1" innif="true" mapping="endpoints">
                <Instance index="1" />
            </CommandClass>
            <CommandClass id="112" name="COMMAND_CLASS_CONFIGURATION" version="1" request_flags="5" innif="true">
                <Instance index="1" />
                <Value type="short" genre="config" instance="1" index="1" label="IN1 Alarm Cancellation Delay" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="65535" value="0">
                    <Help>Input I alarm cancellation delay. Additional delay after an alarm from input IN1 has ceased. The parameter allows you to specify additional time, after which the input no. 1 alarm is cancelled once its violation has ceased. Default 0.</Help>
                </Value>
                <Value type="short" genre="config" instance="1" index="2" label="IN2 Alarm Cancellation Delay" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="65535" value="0">
                    <Help>Input II alarm cancellation delay. Additional delay after an alarm from input IN1 has ceased. The parameter allows you to specify additional time, after which the input no. 1 alarm is cancelled once its violation has ceased. Default 0.</Help>
                </Value>
                <Value type="list" genre="config" instance="1" index="3" label="Type of input no. 1" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" vindex="0" size="1">
                    <Help>Type of input no. 1, what the input 1 will report if no contact is made. Default 1.</Help>
                    <Item label="Input NO (Normal Open)" value="0" />
                    <Item label="Input NC (Normal Close)" value="1" />
                    <Item label="Input MONOSTABLE" value="2" />
                    <Item label="Input BISTABLE" value="3" />
                </Value>
                <Value type="list" genre="config" instance="1" index="4" label="Type of input no. 2" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" vindex="0" size="1">
                    <Help>Type of input no. 2, what the input 2 will report if no contact is made. Default 1.</Help>
                    <Item label="Input NO (Normal Open)" value="0" />
                    <Item label="Input NC (Normal Close)" value="1" />
                    <Item label="Input MONOSTABLE" value="2" />
                    <Item label="Input BISTABLE" value="3" />
                </Value>
                <Value type="list" genre="config" instance="1" index="5" label="Type of transmitted control frame for association group 1" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" vindex="6" size="1">
                    <Help>Type of transmitted control frame for association group 1, activated via input IN1. The parameter allows to specify the type of alarm frame or to force transmission of control commands (BASIC_SET). Default 255 - BASIC SET.</Help>
                    <Item label="ALARM GENERIC" value="0" />
                    <Item label="ALARM SMOKE" value="1" />
                    <Item label="ALARM CO" value="2" />
                    <Item label="ALARM CO2" value="3" />
                    <Item label="ALARM HEAT" value="4" />
                    <Item label="ALARM WATER" value="5" />
                    <Item label="BASIC_SET" value="255" />
                </Value>
                <Value type="list" genre="config" instance="1" index="6" label="Type of transmitted control frame for association group 2" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" vindex="6" size="1">
                    <Help>Type of transmitted control frame for association group 2, activated via input IN1. The parameter allows to specify the type of alarm frame or to force transmission of control commands (BASIC_SET). Default 255 - BASIC SET.</Help>
                    <Item label="ALARM GENERIC" value="0" />
                    <Item label="ALARM SMOKE" value="1" />
                    <Item label="ALARM CO" value="2" />
                    <Item label="ALARM CO2" value="3" />
                    <Item label="ALARM HEAT" value="4" />
                    <Item label="ALARM WATER" value="5" />
                    <Item label="BASIC_SET" value="255" />
                </Value>
                <Value type="byte" genre="config" instance="1" index="7" label="Forced Level of Dimming group 1" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="1" max="255" value="255">
                    <Help>Value of the parameter specifying the forced level of dimming / opening sun blinds when comes "switch on" / "open" command to devices from association group no. 1. In the case of alarm frames the alarm priority is specified. Possible parameter settings: (1 – 99) and 255. Value of 255 makes it possible to activate the device when using the Dimmer module it means activating the device and setting it to the previous stored condition, e.g. when Dimmer is set to 30%, then deactivated, and then reactivated using command 255, it will automatically be set to the previous condition, i.e. 30%. Default 255.</Help>
                </Value>
                <Value type="byte" genre="config" instance="1" index="8" label="Forced Level of Dimming group 2" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="1" max="255" value="255">
                    <Help>Value of the parameter specifying the forced level of dimming / opening sun blinds when comes "switch on" / "open" command to devices from association group no. 2. In the case of alarm frames the alarm priority is specified. Possible parameter settings: (1 – 99) and 255. Value of 255 makes it possible to activate the device when using the Dimmer module it means activating the device and setting it to the previous stored condition, e.g. when Dimmer is set to 30%, then deactivated, and then reactivated using command 255, it will automatically be set to the previous condition, i.e. 30%. Default 255.</Help>
                </Value>
                <Value type="list" genre="config" instance="1" index="9" label="Deactivate transmission of frame cancelling alarm" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" vindex="0" size="1">
                    <Help>Deactivating transmission of the frame cancelling the alarm or the control frame deactivating the device (Basic). It allows for disabling the deactivation function or the alarm cancellation function for devices associated with the appropriate input of the Fibaro Sensor. NOTE: Information concerning alarm violation or activation commands for devices from association groups are always sent. Default 0. ATTENTION: Information alarm triggered or command enabled for devices with associative groups are always sent. NOTE: Value "Group 1 not sent, Group 2 not sent" is only available in version 2.1 and up</Help>
                    <Item label="Groups 1 and 2 sent" value="0" />
                    <Item label="Group 1 sent, Group 2 not sent." value="1" />
                    <Item label="Group 1 not sent, Group 2 sent." value="2" />
                    <Item label="Group 1 not sent, Group 2 not sent." value="3" />
                </Value>
                <Value type="byte" genre="config" instance="1" index="10" label="Interval between successive readings of temperature sensors" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="1" max="255" value="60">
                    <Help>Interval between successive readings of temperature from all sensors connected to the device in seconds. Possible parameter settings: (1 – 255). Default 20. ATTENTION: taking temperature readings from the sensor does not result in sending a temperature condition report to the central hub.</Help>
                </Value>
                <Value type="byte" genre="config" instance="1" index="11" label="Interval between forcing to send report concerning the temperature conditions" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="255" value="60">
                    <Help>Interval between forcing to send report concerning the temperature conditions. The forced report is sent immediately after the next reading of temperature from the sensor, irrespective of the settings of parameter no. 12. Value 0 = Deactivates the function. Default 200. ATTENTION: Frequent sending of temperature condition reports is reasonable when the sensor is located somewhere where can occure rapid changes of ambient temperature. In other cases it is recommended to leave the parameter set to the default value.</Help>
                </Value>
                <Value type="byte" genre="config" instance="1" index="12" label="Insensitiveness to temperature changes." units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="255" value="8">
                    <Help>Insensitiveness to temperature changes. This is the maximum acceptable difference between the last reported temperature and the current temperature taken from the sensor. If the temperatures differ by the set value or more, then a report with the current temperature value is sent to the device assigned to association group no. 3. Intervals between taking readings from sensors are specified by parameter no. 10. Possible parameter settings:0 – 255 [0oC to 16oC] [0 oF – 28.8oF] In order to set the appropriate value of the parameter, the following formula should be used: x = delta T x 16 - for Celsius x = delta T x 80 / 9 - for Fahrenheit x – parameter value delta T – maximum acceptable temperature gradient in Celsius or Fahrenheit If the value is set to 0, then information about the temperature will be sent every time, immediately once the readings have been taken from the sensor. Default 8.</Help>
                </Value>
                <Value type="list" genre="config" instance="1" index="13" label="Transmitting the alarm or control frame broadcast mode" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" vindex="0" size="1">
                    <Help>Transmitting the alarm or control frame in "broadcast" mode (i.e. to all devices within range), information sent in this mode is not repeated by the mesh network. Default 0. ATTENTION: If the broadcast mode of information transmission is activated for a given channel, then transmission of information in singlecast mode to devices assigned to the association group of this channel is deactivated.</Help>
                    <Item label="Sensor 1 and 2 Broadcast inactive" value="0" />
                    <Item label="Sensor 1 broadcast mode active, Sensor 2 broadcast mode inactive" value="1" />
                    <Item label="Sensor 1 broadcast mode inactive, Sensor 2 broadcast mode active" value="2" />
                    <Item label="Sensor 1 and 2 broadcast mode active" value="3" />
                </Value>
                <Value type="list" genre="config" instance="1" index="14" label="Scene activation" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" vindex="1" size="1">
                    <Help>Enable/Disable scene functionality. The device offers the possibility of sending commands compatible with Command class scene activation. Information is sent to devices assigned to association group no. 3. Default 0.</Help>
                    <Item label="Scenes disabled" value="0" />
                    <Item label="Scenes enabled" value="1" />
                </Value>
            </CommandClass>
            <CommandClass id="114" name="COMMAND_CLASS_MANUFACTURER_SPECIFIC" version="1" request_flags="5" innif="true">
                <Instance index="1" />
            </CommandClass>
            <CommandClass id="133" name="COMMAND_CLASS_ASSOCIATION" version="1" request_flags="5" innif="true">
                <Instance index="1" />
                <Associations num_groups="3">
                    <Group index="1" max_associations="5" label="Input IN1" auto="true" multiInstance="true">
                        <Node id="1" />
                        <Node id="1" instance="1" />
                    </Group>
                    <Group index="2" max_associations="5" label="Input IN2" auto="true" multiInstance="true">
                        <Node id="1" />
                        <Node id="1" instance="1" />
                    </Group>
                    <Group index="3" max_associations="1" label="Temperature Sensor(s)" auto="true">
                        <Node id="1" />
                    </Group>
                </Associations>
            </CommandClass>
            <CommandClass id="134" name="COMMAND_CLASS_VERSION" version="1" request_flags="5" innif="true">
                <Instance index="1" />
                <Value type="string" genre="system" instance="1" index="0" label="Library Version" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="3" />
                <Value type="string" genre="system" instance="1" index="1" label="Protocol Version" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="3.52" />
                <Value type="string" genre="system" instance="1" index="2" label="Application Version" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="2.01" />
            </CommandClass>
            <CommandClass id="142" name="COMMAND_CLASS_MULTI_INSTANCE_ASSOCIATION" version="1" request_flags="5" innif="true">
                <Instance index="1" />
                <Associations num_groups="2">
                    <Group index="1" max_associations="5" label="Input IN1" auto="true" multiInstance="true">
                        <Node id="1" />
                        <Node id="1" instance="1" />
                    </Group>
                    <Group index="2" max_associations="5" label="Input IN2" auto="true" multiInstance="true">
                        <Node id="1" />
                        <Node id="1" instance="1" />
                    </Group>
                    <Group index="3" max_associations="1" label="Temperature Sensor(s)" auto="true">
                        <Node id="1" />
                    </Group>
                </Associations>
            </CommandClass>
            <CommandClass id="156" name="COMMAND_CLASS_SENSOR_ALARM" version="1" request_flags="2">
                <Instance index="1" endpoint="1" />
                <Instance index="2" endpoint="2" />
            </CommandClass>
        </CommandClasses>
    </Node>
</Driver>
Win Vista&7; 1#Aeon Z-Stick S2; 1#Aeotec Z-Sick Gen5, 6#Fib.FGBS001; 24#DS18B20; 8#Everspr.AN158-2; 3#Philio PAN04; 1#Philio PAN06, 1#YouLess El; 1#Fib.FGWPE; 1#ZME_RC2; 2#FAK_ZWS230, 2#Quib.ZMNHCDx, 1#Quib.ZMNHDD1, 7#EM6555

DomoJev
Posts: 27
Joined: Friday 16 June 2017 23:40
Target OS: Raspberry Pi
Domoticz version:
Contact:

Re: Z-Wave factfile Fibaro FGBS-001 Universal Binary Sensor

Post by DomoJev » Monday 31 July 2017 10:52

I got me one of these for hooking up to 3 temperature sensors. Didn't get around to checking it on the hardware itself, but does anyone have information on the power consumption of this sensor? I would like to power it from a 9V/500mAh battery block unless that means swapping batteries every month...

User avatar
robpow
Posts: 84
Joined: Friday 19 July 2013 19:28
Target OS: Raspberry Pi
Domoticz version: Beta :)
Location: .se
Contact:

Re: Z-Wave factfile Fibaro FGBS-001 Universal Binary Sensor

Post by robpow » Monday 31 July 2017 16:51

"You need a power-supply to power it (any voltage between 9V and 30V DC); its power consumption is too high for a 9V battery to last even 1-2 days (we measured around 160mW @16V DC input with one DS18B20 temperature sensor connected and with very strong Z-wave controller signal strength)"

https://homeautomationfordummies.wordpr ... -fgbs-321/

DomoJev
Posts: 27
Joined: Friday 16 June 2017 23:40
Target OS: Raspberry Pi
Domoticz version:
Contact:

Re: Z-Wave factfile Fibaro FGBS-001 Universal Binary Sensor

Post by DomoJev » Monday 31 July 2017 22:49

Thanks for the link Rob!

Anyway, a continuous 160 mW @ 16V? Damn... that's pretty outrageous! I'll have to rethink my strategy than - being used to uA territory (a Nordic nRF52 series featuring BLE takes 48 uA @ 3.3V per 100 ms bursts) IMHO anything this thirsty is really really really bad design :o .

Mario25
Posts: 1
Joined: Sunday 17 September 2017 18:23
Target OS: NAS (Synology & others)
Domoticz version:
Contact:

Re: Z-Wave factfile Fibaro FGBS-001 Universal Binary Sensor

Post by Mario25 » Sunday 17 September 2017 18:26

Regarding discussion on difference between FGBS321 and FGBS-001: I just read that they are one single product. In fact, Fibaro changed its reference just after launch and suddenly some dealers still use both part numbers.

nizaga
Posts: 110
Joined: Monday 30 November 2015 12:36
Target OS: Raspberry Pi
Domoticz version:
Contact:

Re: Z-Wave factfile Fibaro FGBS-001 Universal Binary Sensor

Post by nizaga » Wednesday 28 March 2018 18:42

hello,

I can't iclude my FGBS-001 Universal Binary Sensor in my zwave network.

I am running latest stable domoticz on RPI 2 + Razberry (more than 30 zwave devices).

I am using a DC12V - 200mA charger, tested with a led strip (works fine), but i can't include the FGBS-001.

I have tried GND + P and viceversa. Attached a picture.

Could someone help?

Thanks in advance,

nim
Attachments
IMG_5576.JPG
IMG_5576.JPG (97.67 KiB) Viewed 2006 times

User avatar
Domosapiens
Posts: 371
Joined: Wednesday 20 August 2014 12:08
Target OS: Windows
Domoticz version: V3.5981
Location: NL
Contact:

Re: Z-Wave factfile Fibaro FGBS-001 Universal Binary Sensor

Post by Domosapiens » Saturday 14 April 2018 22:09

I am using a DC12V - 200mA charger
I think 200 mA is to weak.
Look for 500ma.
Win Vista&7; 1#Aeon Z-Stick S2; 1#Aeotec Z-Sick Gen5, 6#Fib.FGBS001; 24#DS18B20; 8#Everspr.AN158-2; 3#Philio PAN04; 1#Philio PAN06, 1#YouLess El; 1#Fib.FGWPE; 1#ZME_RC2; 2#FAK_ZWS230, 2#Quib.ZMNHCDx, 1#Quib.ZMNHDD1, 7#EM6555

User avatar
robpow
Posts: 84
Joined: Friday 19 July 2013 19:28
Target OS: Raspberry Pi
Domoticz version: Beta :)
Location: .se
Contact:

Re: Z-Wave factfile Fibaro FGBS-001 Universal Binary Sensor

Post by robpow » Sunday 15 April 2018 9:38

nizaga wrote:
Wednesday 28 March 2018 18:42
hello,

I can't iclude my FGBS-001 Universal Binary Sensor in my zwave network.

I am running latest stable domoticz on RPI 2 + Razberry (more than 30 zwave devices).

I am using a DC12V - 200mA charger, tested with a led strip (works fine), but i can't include the FGBS-001.

I have tried GND + P and viceversa. Attached a picture.

Could someone help?

Thanks in advance,

nim
Try do a factory reset if you haven’t already. If the device thinks it’s already included to another controller it won’t pair to a new one.

Matt

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest