[ST Edge] Driver for FIBARO Smart Implant (beta)

I’ve released an edge driver for the Fibaro Smart Implant FBGS-222. At the moment it supports the contact capability.

The driver treat the second input as a different device and not as a component :slight_smile:

Of course if you need only a single contact sensor, you can remove the second one (the one with “B” in the name)

Join my channel here:
https://bestow-regional.api.smartthings.com/invite/qWjBA1gkPQly

Should you encounter any problem, please show me the logs taken with the following command:
smartthings edge:drivers:logcat b8d5ea82-6cd6-49bb-9833-fcab65bb5c8a --hub-address=IP_HUB_SMARTTHINGS

5 Likes

Added support for motion sensor:


Hi,

Does your driver support the outputs or the temperature funcrions?

Thanks.

The driver shows the temperature of the device but still does not support the outputs.

Great work mate,

Have you got any plans to add any remaining functionality?

@Recon yes but before I’d like to integrate the “basic version” of all my devices

Perfect! Thanks again

Hello Daniele, how do you install the 2 devices that fulfill the function of the inputs?
At the moment I can only see the temperature on the main device.
Should 3 devices have been installed in total?

(Please finish the driver to be able to handle outputs as soon as you have some time to give to the community :wink: :slight_smile:

Thank you!!!

Hi

Are you planning to add the ability to use external temp sensors if and when you have the time?

Thanks

You have to open the settings and select the operating modes. The 2 sensors will appear then.

I have the plan to improve the driver in order to support other capabilities :slight_smile:

Hello Daniel, good afternoon, correct,

I can’t see the inputs from the parent device or create new child devices.

Once the inputs are configured, should new devices be created automatically? (As previously happened with the custom Groovy DTH)

Thanks!!


Hello @matiasjg, can you please debug with logcat (see my first post) and show me the debugging result?

Hello @Daniele_Ratti
Yes, thanks!

@Daniele_Ratti

Do you have the code available to the public? (to gossip)

BR.

Great, are you able to show me that output in the exact moment after you change the sensor type from “normally open” to “normally closed” or vice versa (in the settings)?

It is that the moment in which I create the device :slight_smile:

Of course, I will release the source code after my drivers will become more stable (eg. resolving eventual issues like yours).

Hello Daniele,

Coincidentally my capture is from this exact moment. I made 1 change to each of the inputs.

Otherwise I did not receive any type of log.

I’ve just published an update with more log verbosity. Please allow 12hrs to get the update and retry to do the same thing. Then send me the log :slight_smile: