Fibaro Smart Implant

You need to use Device Actions->Light/Appliances Control->Turn On (or Turn Off) and the Fibaro Smart Implant will show on the list of available devices./

Thanks for the tip but I did try that and even included an Auto-off so the relay would open again (as shown in the attached screenshot) and got the error I mentioned in my previous post.
Here it is again...

9 Feb 2020 at 19:04:06
Action Group Open Gate
Z-Wave Error device "Gate Open/Close" does not support on command
Schedule _auto_off_Gate Open/Close
Z-Wave Error device "Gate Open/Close" does not support off command

It seems the device type is not fully coded in Indigo. Is this the case Matt, Jay?

Cheers,

Chris
--

[matt (support)]

Re-Sync the device in Indigo again and see if the Turn On/Turn Off work. If they don't copy/paste the Event Log results showing the sync and failed on/off into a reply for me.

Good day,

I can confirm that I had no problem setting up a new Action Group to turn on/turn off my Fibaro Smart Implant Relay 1 and/or Relay 2, as per my previous post. Both on and off work as expected.

@CBowles

This device includes several different functions in a single physical device. Each function (exposed in the GUI as different tabs) has it's own set of capabilities. Therefore, you will only be able to switch on/of Relay 1 and/or Relay 2 capabilities. Analog1, Analog2, Binary1, Binary2 and Temperature will not allow turning on/off.

I suggest you name each of the above mentioned tabs accordingly, which would make it easier to identify each capability on the Action Group screens. Please refer to attached screen grabs so you may better understand what I meant above.

Re-Sync the device in Indigo again and see if the Turn On/Turn Off work. If they don't copy/paste the Event Log results showing the sync and failed on/off into a reply for me.

Hi Matt,

Thanks for your offer of help on this. I had added the Smart Implant device prior to upgrading to 7.4.1 but since updating I deleted the main and all the sub devices that were created as part of the device and re-synced.
Below is the Event Log output after a further sync and trying to switch on the relay device via the Indigo UI.

10 Feb 2020 at 15:01:13
Z-Wave Syncing - started for "Gate Button"
Z-Wave Syncing - retrieved module neighbors list: 3, 7, 8, 9, 10, 12, 13, 19, 20
Z-Wave Syncing - assigning return route to "021 - Gate Button"
Z-Wave Syncing - assigned return route
Z-Wave Syncing - retrieved manufacture and model names: Fibaro System - 010F, Smart Implant (FGBS222) - 05021000
Z-Wave Syncing - retrieved protocol version 6.02, app version 5.01

10 Feb 2020 at 15:01:38
Z-Wave Syncing - retrieved class hierarchy: Routing Slave : Notification Sensor : Notification Sensor (04 : 07 : 01, base 00)
Z-Wave Syncing - retrieved command classes: 85v1 86v1 8Ev1 98v1 9Fv1 20v1 22v1 25v1 31v11 55v1 56v1 59v1 5Av1 5Bv1 5Ev1 60v4 6Cv1 70v1 71v1 72v1 73v1 75v1 7Av1
Z-Wave Syncing - retrieved encrypt commands: 85 86 8E 59 5A 5B 60 25 31 70 71 72 73 75 7A
Z-Wave Syncing - retrieved capabilities: routing, beaming, security

10 Feb 2020 at 15:02:36
Z-Wave Syncing - retrieved multi-endpoint types: 1:(07 : 01), 2:(07 : 01), 3:(21 : 01), 4:(21 : 01), 5:(10 : 01), 6:(10 : 01), 7:(21 : 01)
Z-Wave Syncing - retrieved multi-endpoint classes: 1:[5E 6C 22 98 9F], 2:[5E 6C 22 98 9F], 3:[5E 6C 22 98 9F], 4:[5E 6C 22 98 9F], 5:[5E 6C 22 98 9F], 6:[5E 6C 22 98 9F], 7:[5E 6C 22 98 9F]

10 Feb 2020 at 15:02:51
Z-Wave Syncing - retrieved group 1 associations: []
Z-Wave Syncing - retrieved group 2 associations: []
Z-Wave Syncing - retrieved group 3 associations: []
Z-Wave Syncing - added group 1 multi association to interface
Z-Wave Syncing - retrieved parameter 20 "Input 1 type" is 1 "Normally Open"
Z-Wave Syncing - retrieved parameter 40 "Input 1 scene sending" is 0 "None"
Z-Wave Syncing - retrieved parameter 21 "Input 2 type" is 1 "Normally Open"
Z-Wave Syncing - retrieved parameter 41 "Input 2 scene sending" is 0 "None"
Z-Wave Syncing - retrieved parameter 24 "Swap inputs (IN1 and IN2)" is false
Z-Wave Syncing - retrieved parameter 154 "Output 1 type" is 0 "Normally Open"
Z-Wave Syncing - retrieved parameter 156 "Output 1 delayed off" is 50 * 0.1 seconds
Z-Wave Syncing - retrieved parameter 155 "Output 2 type" is 0 "Normally Open"
Z-Wave Syncing - retrieved parameter 157 "Output 2 delayed off" is 0 * 0.1 seconds
Z-Wave Syncing - retrieved parameter 25 "Swap outputs (OUT1 and OUT2)" is false
Z-Wave Syncing - retrieved parameter 66 "Internal temperature interval" is 0 seconds
Z-Wave Syncing - retrieved parameter 65 "Internal temperature sensitivity" is 5 * 0.1°C
Z-Wave Syncing - retrieved parameter 64 "Analog input interval" is 0 seconds
Z-Wave Syncing - retrieved parameter 63 "Analog input sensitivity" is 5 * 0.1 V
Z-Wave Syncing - retrieved parameter 150 "Analog IN1 debounce" is 10 milliseconds
Z-Wave Syncing - retrieved parameter 151 "Analog IN2 debounce" is 10 milliseconds
Z-Wave Syncing - retrieved parameter 68 "External sensor interval" is 0 seconds
Z-Wave Syncing - retrieved parameter 67 "External sensor sensitivity" is 5 * 0.1
Z-Wave Syncing - complete
Z-Wave sent "Gate Button" status request
Z-Wave sent "021 - Analog IN1" status request
Z-Wave received "021 - Analog IN1" sensor update to 10.41 V
Z-Wave sent "021 - Binary IN2" status request
Z-Wave sent "021 - Analog IN2" status request
Z-Wave received "021 - Analog IN2" sensor update to 10.41 V
Z-Wave sent "Gate Open/Close" status request
Z-Wave sent "021 - Relay 2" status request
Z-Wave sent "Gate Control Box Temperature" status request

10 Feb 2020 at 15:13:11
Z-Wave received "Gate Control Box Temperature" sensor update to 31.1 °C

10 Feb 2020 at 15:13:41
Z-Wave received "Gate Control Box Temperature" sensor update to 31.7 °C

10 Feb 2020 at 15:32:17
Z-Wave Error device "Gate Open/Close" does not support on command

I can confirm that closing the Binary IN1 input (named Gate Button in my case) DOES result in relay 1 (named Gate Open/Close in my case) going to the On position and this is reflected in the Indigo UI. However, I don't seem to be able to get Indigo to set the relay to On.
Any ideas?

Many thanks,

Chris
--

Did you set the parameters accordingly, as per item 6 below (excerpt from Smart Implant operating manual)?

Link to manual: https://manuals.fibaro.com/fgbs2-man

===============================================================================
4.9: Connection with gate opener
Smart Implant can be connected to different devices to control them. In this example it is connected to gate opener with im- pulse input (every impulse will start and stop the gate motor, alternately opening/closing)
1. Disconnect power.
2. Connect with the diagram below:

<NOTE: Diagram did not paste, refer to above link for more info>

3. Verify correctness of connection.
4. Power the device.
5. Add the device to the Z-Wave network.
6. Change values of parameters:
• Connected to IN1 and OUT1:
» Change parameter 20 to 2 (monostable button)
» Change parameter 156 to 1 (0.1s)
• Connected to IN2 and OUT2:
» Change parameter 21 to 2 (monostable button)
» Change parameter 157 to 1 (0.1s)
===============================================================================

[matt (support)]

cesarvog is correct that you may not have parameters 20, 21, 156, 157 set correctly (shown in the UI as: Input 1 type, Input 2 type, Output 1 delayed off, Output 2 delayed off) but I think there is something else going wrong as well. It is very odd that the Gate Open/Close (Relay 1) is not responding to the ON/OFF commands. From your sync I can see why that would occur, but it looks like your module is either in a bad state or malfunctioned. Based on the documentation Endpoint 5 (which Indigo maps to Relay 1) should support COMMAND_CLASS_SWITCH_BINARY [0x25], yet we can see from your Sync that it does not report that:

Z-Wave Syncing - retrieved multi-endpoint classes: 1:[5E 6C 22 98 9F], 2:[5E 6C 22 98 9F], 3:[5E 6C 22 98 9F], 4:[5E 6C 22 98 9F], 5:[5E 6C 22 98 9F], 6:[5E 6C 22 98 9F], 7:[5E 6C 22 98 9F]

Looking through this forum thread I see an example of another user (McJohn) that has an identical firmware version Implant as yours but notice the endpoint classes supported are reporting differently:

Multi-Endpoint Classes: 1:[5E 85 8E 59 71 6C 22 98 9F], 2:[5E 85 8E 59 71 6C 22 98 9F], 3:[5E 85 8E 59 31 6C 22 98 9F], 4:[5E 85 8E 59 31 6C 22 98 9F], 5:[5E 25 85 8E 59 75 6C 22 98 9F], 6:[5E 25 85 8E 59 75 6C 22 98 9F], 7:[5E 85 8E 59 31 71 6C 22 98 9F]

In his case his module is reporting it supports the 0x25 (Switch Binary) command class. I have no idea why yours is reporting different values – you'll need to contact Fibaro to see if they can shed some light on that. It isn't a firmware version difference though, as McJohn has the same version you do.

Oh wait, I see in your log you are including it with encryption enabled. I suspect the module isn't reporting the correct information to Indigo when encryption is enabled. Try excluding it and re-including it without encryption and I'll be it works as expected.

Hey Matt,

Many thanks for the tip!
I'll try removal and re-adding without encryption tomorrow when I get home and let you know how I get on!

Cheers!

It's not a big problem but does the temperature reporting of the Smart Implant work at your sites?
In our case it keeps staying at the same temperature and it's not updating (despite of changing the report interval and sensitivity).

It's not a big problem but does the temperature reporting of the Smart Implant work at your sites?
In our case it keeps staying at the same temperature and it's not updating (despite of changing the report interval and sensitivity).

Did you have your implant powered by ups/powerbank? Just asking since my implant stopped reporting temperature and relay inputs after power spike!

No, we haven't connect a UPS to the Smart Implant but it can handle a wide power input: from the manual: 9-30V DC ±10%.
So, I don't think your problem has to do with a power peak.

No, we haven't connect a UPS to the Smart Implant but it can handle a wide power input: from the manual: 9-30V DC ±10%.
So, I don't think your problem has to do with a power peak.

well, spike or peak or low voltage messed my implant for sure yesterday: strong wind made lamps in our house dim/brighten and UPS's on my computer beeped. And implant (+12V PSU) didn't report anything after that although it was reachable from Indigo. After I resynced it, it was back in business. From my short (4 weeks) experience with implant in production (pulse counting & temperature reporting), it seems to be quite sensitive about the power.

So give resync a go and see if it helps.

@McJohn
Now that you mentioned, my Smart Implants also don't seem to update temperature (which is way off the correct temperature, by the way).
I DO have them powered by the previous alarm system, which of course has battery backup, so I don't think power fluctuations are to blame.

@juntta
Resync DID change the previous temperature value, but I doubt it will change over time. Will report back at the end of the day.

Hmm, have you checked what is the internal temp sensor reporting interval (param 66) set at? Its default is disabled. Try to change that and see if that helps.

Hmm, have you checked what is the internal temp sensor reporting interval (param 66) set at? Its default is disabled. Try to change that and see if that helps.

Correct. It was indeed left at it's default value of 0 (disabled). Changed to 60 seconds and parameter 65 to 1 (1 * 0,1C), to verify if anything changes over time.
Thanks for pointing that out.