This will make the temp reporting work again - I can confirm this. I had to run my script anyway, since digital inputs are still mapped in the wrong way, but at least the device is now fully usable. thanks to @mcv.bogdanf for the tip!
Guys I really need your help. I am doing exactly as you describe, by adding fgb-223from wizard using pc, and i can See only one difference the external temp sensor does’t report. The Rest unchanged ( generic IO x2, appliance module x2, GET_LANG x 4). What am i doing wrong?
- Login on home.getvera.com
- Connect with my vera controller (vera g100) software version 1.7.1040
- Clicking Devices menu
- Add device
- Search and click fgs-223
- Next-next until i See countdown. Then triple clicking fgbs 222
- Fgbs-222 green Led is on, and timer still countdown until it reaches 0
- Next is Page with name of device
And that’s it (generic IO x2, appliance module x2, GET_LANG x 4, temp sensor x 1 but does’t report, and named device)
I’m on FW 7.30, and I’m experiencing problems with pairing, maybe related to this, maybe related to this FW.
Anyway, I can only map temp sensors (binary sensore are not working) and I found that it’s impossible for me to set device parameters (it’s stuck on “Getting secure classes”).
I’ll probably go back to a previous backup later tomorrow. Unfortunately this device is not properly supported, even if it’s not very new to the market.
So, I was finally able to get it working 100% (at least binary inputs + temp sensors).
Just pair as generic, because if pairing as FGS 223, temp sensors will work, but binary sensors will not.
Then, run the updated scripts in the other thread, to fix missing variables and configuration. Just issue a luup.reload() and you’ll be done. Device will be paired secure and inputs will work.
@mcv.bogdanf I found that temperature reports are not working, unless I manually poll the device. Is there anything special I can configure to avoid a scene running a polling every now and then? Thanks.
First post from me guys, so bear with me. I have one of these fgs-222 devices and am trying to add 4 external temp sensors (DS18B20)
I have tried adding as fgs-223, and see some external temp sensors among other devices as discussed above. Getting the ext sensors to check for temp every 60 secs is my issue.
I also tried deleting, then pairing as generic, as ‘therealdb’ suggested, where I don’t see the ext devices as temp but instead as generic, due to the xml they are using.
My question is, following that other thread, I tried to add a new implementation xml file (pasted from the code and edited my IP) under Apps -> Develop Apps -> Luup files… Then I created a new device using the implementation file I created and D_TemperaruteSensor1 as the xml file (which was referred to in the implementation file). I get a new device displayed. What do I do now? How do I associate that with the generic master device created earlier? OR how do I get the external devices to use this? Do I add the parent ID for the new device into all the ext sensors?
I’ve also tried the luup reload (http://:3480/data_request?id=reload.
no need to change the implementation file. the script should be run one time only. I adapted it to use 4 endpoints, if you need more, just change to code. My sensors are reporting OK and everything is working as it should.
Great thanks. Makes more sense now.
Hello, is there anyone who knows when this device will be introduced in Vera database in order to add simple and correctly inmediately?
I soupose Vera team reads this threads, this Smart Implant FGBS-222 it is already selling buy fibaro long time ago, sin april!!!
happy new year
is the module fully recognized (v5.1) ?
are the outputs controllable separately from the inputs ?
Hi there. Am running 7.4x here and am trying to use the FGBS-222 to sense an open or close on a dry contact. I’ve joined it using the ‘generic’ z-wave device. Where is the script that you are referring to ? I can’t seem to find another thread where it is. Thanks
it’s in the 3rd post of this thread: