Fibaro FGBS222 Smart Implant
Moderator: leecollings
-
- Posts: 31
- Joined: Friday 08 February 2019 8:35
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 4.9700
- Location: France
- Contact:
Fibaro FGBS222 Smart Implant
Hi !
I wanted to buy this hardware to get in one two entries and two relays.
But I'm not sure of the fully interoperability with Domoticz.
The reseller told me that the two entries are not included in Domoticz, even with the last beta version 4.10525.
Does anyone have one ?
Will Domoticz get improved to be able to fully use this device ?
Many thanks !
I wanted to buy this hardware to get in one two entries and two relays.
But I'm not sure of the fully interoperability with Domoticz.
The reseller told me that the two entries are not included in Domoticz, even with the last beta version 4.10525.
Does anyone have one ?
Will Domoticz get improved to be able to fully use this device ?
Many thanks !
-
- Posts: 4
- Joined: Saturday 25 August 2018 10:48
- Target OS: Linux
- Domoticz version:
- Location: Corsica
- Contact:
Re: Fibaro FGBS222 Smart Implant
Hi,
I replied to your question on the reseller site but they didnt validate it.
I bought a FGBS222 at the same place last week and did the required changes for openzwave support: https://github.com/OpenZWave/open-zwave/pull/1727
You just have to add the fgbs222.xml in your fibaro folder and add the required line in manufacturer_specific.xml
As you can see in comments of the pull request, for now you will have to enable polling on the device so it wont be reactive to get the status of the two entries. You can lower the polling time to increase the polling frequency.
There is also an alternative, using the central scene, but you may have to change 2 lines of code in domoticz and compile it.
Let me know if you need more help.
I replied to your question on the reseller site but they didnt validate it.
I bought a FGBS222 at the same place last week and did the required changes for openzwave support: https://github.com/OpenZWave/open-zwave/pull/1727
You just have to add the fgbs222.xml in your fibaro folder and add the required line in manufacturer_specific.xml
As you can see in comments of the pull request, for now you will have to enable polling on the device so it wont be reactive to get the status of the two entries. You can lower the polling time to increase the polling frequency.
There is also an alternative, using the central scene, but you may have to change 2 lines of code in domoticz and compile it.
Let me know if you need more help.
-
- Posts: 31
- Joined: Friday 08 February 2019 8:35
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 4.9700
- Location: France
- Contact:
Re: Fibaro FGBS222 Smart Implant
OK, sounds good for me.
I don't need it immediatly, maybe next month.
But with the polling way, it should be OK for me !
I don't need it immediatly, maybe next month.
But with the polling way, it should be OK for me !
-
- Posts: 68
- Joined: Monday 11 December 2017 22:57
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Fibaro FGBS222 Smart Implant
Hi,
I just installed the Smart Implant. I added the xml and added the line in the manifest. The implant is recognized and the configuration is available (which wasn't the case before the XML patch).
I noticed the following issues:
- It seems I can't read the state of switch inputs, they never switch, even when polling.
- The only way I have found to read one input was to switch it to "Alarm Normally Open/Closed" mode. Then the corresponding alarm level device changes, and I have a "burglar" switch which responds, and is updated, without even polling. On the other hand, the second alarm level is never updated, and I don't have a second burglar device.
- In analog mode, I have only one "voltage" device visible in Domoticz. In the openzwave control panel, I can see two voltages and they update properly when refreshing.
- I have set the outputs to auto switch off after one second (the garage door I'm commanding uses inpulses). When using an output, it properly pulses for one second, but the device state in Domoticz never goes back to "Off".
It seems there is still a lot of things to fix before we can fully use this module.
I just installed the Smart Implant. I added the xml and added the line in the manifest. The implant is recognized and the configuration is available (which wasn't the case before the XML patch).
I noticed the following issues:
- It seems I can't read the state of switch inputs, they never switch, even when polling.
- The only way I have found to read one input was to switch it to "Alarm Normally Open/Closed" mode. Then the corresponding alarm level device changes, and I have a "burglar" switch which responds, and is updated, without even polling. On the other hand, the second alarm level is never updated, and I don't have a second burglar device.
- In analog mode, I have only one "voltage" device visible in Domoticz. In the openzwave control panel, I can see two voltages and they update properly when refreshing.
- I have set the outputs to auto switch off after one second (the garage door I'm commanding uses inpulses). When using an output, it properly pulses for one second, but the device state in Domoticz never goes back to "Off".
It seems there is still a lot of things to fix before we can fully use this module.
-
- Posts: 338
- Joined: Friday 17 August 2018 14:03
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Fibaro FGBS222 Smart Implant
Hi,
i probably should have read this thread before i bought the Smart Implant. This would have saved me a lot of work.
I got the sensor working by adjusting the xml according to the instructions above before including, which resulted in the sensor being recognized and a lot of devices being included after adding.
The problem is: i can only control output 1 and i get only notifications on input 1 (only when configured as alarm). For me it is enough to use it for my purposes.
However it would be nice though to get it fully working, so did anyone manage to get this sensor fully working in domoticz? Does anyone have experiences on this sensor which might be handy?
KR Arnold
i probably should have read this thread before i bought the Smart Implant. This would have saved me a lot of work.
I got the sensor working by adjusting the xml according to the instructions above before including, which resulted in the sensor being recognized and a lot of devices being included after adding.
The problem is: i can only control output 1 and i get only notifications on input 1 (only when configured as alarm). For me it is enough to use it for my purposes.
However it would be nice though to get it fully working, so did anyone manage to get this sensor fully working in domoticz? Does anyone have experiences on this sensor which might be handy?
KR Arnold
-
- Posts: 338
- Joined: Friday 17 August 2018 14:03
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Fibaro FGBS222 Smart Implant
I created an issue on the issuelist for this device a few days ago. https://github.com/domoticz/domoticz/issues/3337
based on the feedback by a developer and then doing some testing, i noticed that
-under OZW 1.4 without security it seems to work as designed (which is sometimes quite fuzzy btw: The only way to get notifications is using alarms)
- under OZW 1.4 with security the functionality is very limited (like written in the thread here)
- under OZW1.6 without security i can only switch 2 outputs. notifications don't work
- under OZW 1.6 with security nothing works..
my advice for now. Only use this device in latest stable for domoticz (so OZW 1.4) without security until the issues are fixed.
based on the feedback by a developer and then doing some testing, i noticed that
-under OZW 1.4 without security it seems to work as designed (which is sometimes quite fuzzy btw: The only way to get notifications is using alarms)
- under OZW 1.4 with security the functionality is very limited (like written in the thread here)
- under OZW1.6 without security i can only switch 2 outputs. notifications don't work
- under OZW 1.6 with security nothing works..
my advice for now. Only use this device in latest stable for domoticz (so OZW 1.4) without security until the issues are fixed.
-
- Posts: 14
- Joined: Tuesday 15 November 2016 17:39
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Fibaro FGBS222 Smart Implant
I'm using Domoticz 4.97 and am trying to include the smart implant. Including doesn't work for me.
Can anyone tell me if this can be caused by my missing configuration around the xml and open z-wave part? Or should including always work?
The manual states there is a color led on the device, but for me no light is visible at all. Should there be a green led when powered on?
Can anyone tell me if this can be caused by my missing configuration around the xml and open z-wave part? Or should including always work?
The manual states there is a color led on the device, but for me no light is visible at all. Should there be a green led when powered on?
-
- Posts: 141
- Joined: Tuesday 31 January 2017 20:34
- Target OS: -
- Domoticz version:
- Contact:
Re: Fibaro FGBS222 Smart Implant
Hi, i just bought one of these implants and ran into trouble..
now im stuck ad reading forums that its one big mess with these sensors..
how can ik fix it to get this to work or do i have to return it to the reseller?
i dont get it what to do with a xml thing???
i cant find it and i dont get it what to do with it..
please help.
now im stuck ad reading forums that its one big mess with these sensors..
how can ik fix it to get this to work or do i have to return it to the reseller?
i dont get it what to do with a xml thing???
i cant find it and i dont get it what to do with it..
please help.
how to do this?add the required line in manufacturer_specific.xml
-
- Posts: 141
- Joined: Tuesday 31 January 2017 20:34
- Target OS: -
- Domoticz version:
- Contact:
Re: Fibaro FGBS222 Smart Implant
Now I managed to copy some files it gets now recognized by the correct name. But nothing more. Can somebody please help me?
-
- Posts: 616
- Joined: Thursday 10 November 2016 9:30
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Fibaro FGBS222 Smart Implant
Sending back the device to the seller if still possible may be the best advice! Planned to buy one several weeks ago, but checked the forums before... No-one managed to make it work as advertised.
If this is a buggy device firmware, even if Fibaro build a fix someday you'll not be able to use it not using their controller.
We'll miss the previous (z-wave not +) version.
-
- Posts: 1
- Joined: Tuesday 08 October 2019 19:39
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Fibaro FGBS222 Smart Implant
Hi guys! I’m unable to add the fibaro fgbs222. I’ve followed the instructions but I can’t find the file with the mk extension.
I’ve to upgrade open zwave? How? Thank you!!!
I’ve to upgrade open zwave? How? Thank you!!!
-
- Posts: 12
- Joined: Sunday 12 May 2019 14:09
- Target OS: Raspberry Pi / ODroid
- Domoticz version: Latest
- Location: Netherlands
- Contact:
Re: Fibaro FGBS222 Smart Implant
Hi All,
I have the old one, a FGBS001 and after a lot of frustations I managed to get the digital inputs to work more or less reliable with polling enabled, Domoticz version 4.9983. The polling introduced an average of 10/day OpenZWave: Received timeout notification from HomeID... errors!
The FGBS001 is in use with a keypad to arm and disarm my home build alarm system.
When I switched to the latest beta my blockly event that arms an disarms the alarm system is not working anymore as it should so I returned to 4.9983.
My advice is, do not use the FGBS001 or FGBS222 when you are in need for digital inputs. I think Openzwave/Domoticz is not handling these devices properly.
Update: last week I replaced my two "Kaku/CoCo" dimmers with two Aeotec nano dimmers and a couple of Aeotec wallmotes in order to get rid of my rflink interface. One of the dimmers is at a distance of 20 cm to the keypad with the FGBS001 and the other is somewhere between the Aeotec Z stick gen 5 and the first one. After a couple of days I decided to turn off the polling for the FGBS001 to see if the strengthening of the zwave network made a difference for the behaviour of the FGBS001 and the answer is yes!!!, no more timeout notifications from the FGBS001 and it switches every time like it should and it not once got stuck in the wrong state.
Conclusion: I have to review my advice for these devices, embed them in a strong zwave network, preferably with a powered node nearby.
I have the old one, a FGBS001 and after a lot of frustations I managed to get the digital inputs to work more or less reliable with polling enabled, Domoticz version 4.9983. The polling introduced an average of 10/day OpenZWave: Received timeout notification from HomeID... errors!
The FGBS001 is in use with a keypad to arm and disarm my home build alarm system.
When I switched to the latest beta my blockly event that arms an disarms the alarm system is not working anymore as it should so I returned to 4.9983.
My advice is, do not use the FGBS001 or FGBS222 when you are in need for digital inputs. I think Openzwave/Domoticz is not handling these devices properly.
Update: last week I replaced my two "Kaku/CoCo" dimmers with two Aeotec nano dimmers and a couple of Aeotec wallmotes in order to get rid of my rflink interface. One of the dimmers is at a distance of 20 cm to the keypad with the FGBS001 and the other is somewhere between the Aeotec Z stick gen 5 and the first one. After a couple of days I decided to turn off the polling for the FGBS001 to see if the strengthening of the zwave network made a difference for the behaviour of the FGBS001 and the answer is yes!!!, no more timeout notifications from the FGBS001 and it switches every time like it should and it not once got stuck in the wrong state.
Conclusion: I have to review my advice for these devices, embed them in a strong zwave network, preferably with a powered node nearby.
Last edited by Jofre on Wednesday 18 December 2019 9:35, edited 1 time in total.
-
- Posts: 67
- Joined: Tuesday 27 March 2018 17:42
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Fibaro FGBS222 Smart Implant
Using very latest beta, (Version: 4.11550) the config file is present but had to edit manufacturer_specific.xml and change the id from 1000 to 2000 for it to be recognized properly.
<Product config="fibaro/fgbs222.xml" id="2000" name="FGBS222 Smart Implant" type="0502"/>
Something not right here .....
<Product config="fibaro/fgbs222.xml" id="2000" name="FGBS222 Smart Implant" type="0502"/>
Something not right here .....
Last edited by fargle on Monday 09 December 2019 15:45, edited 1 time in total.
-
- Posts: 67
- Joined: Tuesday 27 March 2018 17:42
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Fibaro FGBS222 Smart Implant
It actually works the same as most ZWave relay devices, the In1 and In2 inputs are "hardwired" to switch the outputs. So if the input is on, or has been triggered on, the output will be on. Still playing with this, but relay switching at least is normal.
-
- Posts: 67
- Joined: Tuesday 27 March 2018 17:42
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Fibaro FGBS222 Smart Implant
Another upgrade brought the original, faulty settings back, as normal.
Maybe will put this device back on the shelf for a while and wait for an update. It would be a handy device if it worked properly.
Maybe will put this device back on the shelf for a while and wait for an update. It would be a handy device if it worked properly.
-
- Posts: 141
- Joined: Tuesday 31 January 2017 20:34
- Target OS: -
- Domoticz version:
- Contact:
Re: Fibaro FGBS222 Smart Implant
Hi picked up the motivation to get my smart implant to get working in domoticz.
my findings until now is that switching monostable works. input switches output directly.
but i want that info to trigger a scene/switch... but in domoticz the smart implant switch delays for a minute or so..
so input switches my output to on mode.. (my hardwired test light connected to output 1 goes on) but in domoticz the switch is still off..
wait for a minute, or 2..(to long for me) and domoticz gets updated to on status...
how to debug this or fix it?
running on stable version of domoticz and got smart implant working as described in this thread.
greets marco
my findings until now is that switching monostable works. input switches output directly.
but i want that info to trigger a scene/switch... but in domoticz the smart implant switch delays for a minute or so..
so input switches my output to on mode.. (my hardwired test light connected to output 1 goes on) but in domoticz the switch is still off..
wait for a minute, or 2..(to long for me) and domoticz gets updated to on status...
how to debug this or fix it?
running on stable version of domoticz and got smart implant working as described in this thread.
greets marco
-
- Posts: 347
- Joined: Friday 03 April 2015 17:09
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Fibaro FGBS222 Smart Implant
Did you ever resolved this issue? How do you get the input from the smart implant into Domoticz?astrapowerrr wrote: ↑Monday 13 January 2020 11:24 Hi picked up the motivation to get my smart implant to get working in domoticz.
my findings until now is that switching monostable works. input switches output directly.
but i want that info to trigger a scene/switch... but in domoticz the smart implant switch delays for a minute or so..
so input switches my output to on mode.. (my hardwired test light connected to output 1 goes on) but in domoticz the switch is still off..
wait for a minute, or 2..(to long for me) and domoticz gets updated to on status...
how to debug this or fix it?
running on stable version of domoticz and got smart implant working as described in this thread.
greets marco
Also when I shortcut the input wires the output is not triggered? Why not? I like this behavior but it is not according to the spec.
I want to trigger a doorbel, so when the input is triggered the doorbel needs to switch on. I can control the output from a script but then I still need a trigger from the input. How can i achieve this?
I’m running Open Zwave Version: 1.6-1033-g3661f170.
These are the options/switches in Domoticz for the Smart Implant:
-
- Posts: 347
- Joined: Friday 03 April 2015 17:09
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Fibaro FGBS222 Smart Implant
I was able to finally get this working. The input 1 and 2 are set to "Normally Open alarm input". With this configuration I was able to catch the user trigger on the input into the dzvents script. From the script I was able to control the output, either 1 or 2 (Deurbel 1 or Deurbel 2 in the above picture). So i can decide if I use input 1 or 2, one of the input directly controls the doorbell while the other I need to trigger the bell from the script. The second one is what I prefer as I then can disable the bell for example at night. So it looks like I've a working solution now.
-
- Posts: 40
- Joined: Tuesday 01 December 2015 8:47
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 2022.1
- Location: Netherlands
- Contact:
Re: Fibaro FGBS222 Smart Implant
Can please share your script? I am struggling.
Did you update that file? Where to download that file?
Did you update that file? Where to download that file?
Version 3.9639
Platform: Jessie lite
Hardware: Raspberry pi 3B; RFXCOM; Weather Underground; Dummy; OpenZwave USB; Fritzbox Callmonitor via LAN interface; System Alive Checker (Ping); Philips Hue Bridge; Atag One Thermostat
Platform: Jessie lite
Hardware: Raspberry pi 3B; RFXCOM; Weather Underground; Dummy; OpenZwave USB; Fritzbox Callmonitor via LAN interface; System Alive Checker (Ping); Philips Hue Bridge; Atag One Thermostat
-
- Posts: 347
- Joined: Friday 03 April 2015 17:09
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Fibaro FGBS222 Smart Implant
Below the overview of how I've configured the smart implant.
The simplified script I'm using is:Code: Select all
return {
logging = {
level = domoticz.LOG_ERROR, --DEBUG, -- switch to domoticz.LOG_ERROR when all OK
marker = 'ControlDeurBel'
},
on = {
devices = {
'Deurbel Input 1'
}
},
execute = function(domoticz, device)
-- If the Doorbell is pressed, take action and ring the bell.
if (device.name == 'Deurbel Input 1') and (device.state == 'On') then
local deurBelOut = domoticz.devices('Deurbel Output 2')
local IsLightOutside = domoticz.devices('IsLightOutside')
local DeubelAanUit = domoticz.devices('Deubel Aan Uit')
local DateTimePressed = os.date("%X %d/%m/%Y")
-- Log information to the debug window
domoticz.log(DateTimePressed .. ' Doorbell was pressed, lets ring the bell!', domoticz.LOG_INFO)
-- Send a message to Telegram that the doorbell was pressed.
domoticz.notify("HoekHuis Deurbel", "Doorbell was pressed at " .. DateTimePressed .. ".", domoticz.PRIORITY_HIGH, nil, nil, domoticz.NSS_TELEGRAM)
-- Check if the Doorbell ringer needs to be enabled.
if (DeubelAanUit.state == 'On') then
-- Enable the doorbell, smart implant output.
-- Smart implant is configured to switch off the output automatically.
deurBelOut.switchOn()
-- Say something on Sonos.
domoticz.openURL({ url = 'http://192.168.0.100:5005/say/ding%20dong%20ding%20dong%20ding%20dong%20Please%20open%20de%20door', method = 'GET' })
end
-- Enable the gang door light
local VoorDeurGangLight = domoticz.devices('Lamp Hal Voordeur')
domoticz.log('Switch on the gang front door lamp.', domoticz.LOG_DEBUG)
VoorDeurGangLight.switchOn()
VoorDeurGangLight.switchOff().afterSec(600)
end
end
}
Who is online
Users browsing this forum: Google [Bot] and 1 guest