Fibaro Smart Implant

Posted on
Wed Oct 23, 2019 4:47 pm
howartp offline
Posts: 4092
Joined: Jan 09, 2014
Location: West Yorkshire, UK

Re: Fibaro Smart Implant

Right, 2 hours of testing later...

I've sent Matt a full 300 line debug file with running commentary.

In brief, the Smart Implant is doing exactly what we thought.

NO / NC inputs are sending Home Security reports when opened/closed or vice-versa, which Indigo is currently ignoring. Therefore the Binary IN1/IN2 inputs never change state in the UI.

Push Buttons (and Toggle Buttons) are sending Central Scene 1 or 2 (for button 1 or 2) to IN1 (always IN1). They have a key states of Tapped, Double-Tapped, Triple-Tapped, Held or Released. If you configure Param 40/41 ("Input 1 scene sending:") to Single & Double Tap, then you will only receive Single and Double Tapped notifications - you won't get Triple or Held notifications. If you configure it to Single Tap, you will equally only get Single Tap notifications. If you configure it to All Scenes, you will get all varieties of Single, Double, Triple, Held and Released.

Regardless of P20/P21 setting ("Input 1/2 Type:") the internal relay still fires by default whenever you press a button, and thus sends Binary Reports which change the UI state for the relays.

McJohn, I'm seeing no delays with firing commands on NO/NC. If your detection beam is NO and goes Closed you will instantly see the 71 05 .... 07 02 in the log. I've created a trigger on Binary IN1 with:

* 0x71 0x05 * 0x07 0x02 * and it works instantly.

You will never get Scenes sent when you have NO/NC configured, so you can't use "Button 1 pressed" etc, which I think you've already understood.

You DO get a 3 second delay when set to "Push Button" and "Held Down/Released" because by the nature of "Held down" it has to wait internally to realise whether you're holding the button down, or just have slow motor control in your hands/arms and are trying to tap or double-tap with it.

Peter

Posted on
Wed Oct 23, 2019 7:57 pm
matt (support) offline
Site Admin
User avatar
Posts: 20016
Joined: Jan 27, 2003
Location: Texas

Re: Fibaro Smart Implant

GlennNZ wrote:
Another Smart Implant - another model ID.

We'll make sure that one gets added.

Image

Posted on
Mon Oct 28, 2019 4:36 am
McJohn offline
User avatar
Posts: 470
Joined: Dec 18, 2012
Location: The Netherlands

Re: Fibaro Smart Implant

Thanks for your report and time Peter.

For now it's working with the code * 0x71 0x05 * 0x07 0x02 * at "Any Device" Trigger.
Does it work at your site with only the selected Smart Implant device?

And what are your experiences with the temperature sensor?

John

Posted on
Fri Nov 01, 2019 5:11 am
Nick offline
Posts: 17
Joined: Nov 06, 2018

Re: Fibaro Smart Implant

This is a great device. And thanks for the support in Indigo. I can now add my 0-10v lux and wind sensor to my Indigo system.

It only does not seems to update value changes. Changed the parameters but no luck......Any suggestions..


https://smarterhome.sk/en/weather-stati ... t-599.html

Servodan Lichtsensor 24VDC/0-10V 4 ranges 3..60K lux ip20 - 43-197

Posted on
Tue Jan 14, 2020 8:50 am
cesarvog offline
User avatar
Posts: 57
Joined: Aug 13, 2016
Location: Brazil

Re: Fibaro Smart Implant

Hello everyone,

I have two units of the Fibaro Smart Implant coming my way (will be here tomorrow) and have been reading this thread with great interest.
I understand that it seems there are at least three variants of this device currently in the wild: Model ID: 05021000, Model ID: 05022000 and Model ID: 05023000, and that Indigo 7.4 has added support to the first afore mentioned Model ID only.
Matt has also stated that the 2000 and 3000 variants will be added to Indigo 7.4.1.

So, assuming I end up getting one of the latter Model IDs, how can I get hold of Indigo 7.4.1?

TIA
Cesar

PS: Will report back with Model IDs when I get them delivered.

Posted on
Tue Jan 14, 2020 9:30 am
jay (support) offline
Site Admin
User avatar
Posts: 16264
Joined: Mar 19, 2008
Location: Austin, Texas

Re: Fibaro Smart Implant

cesarvog wrote:
So, assuming I end up getting one of the latter Model IDs, how can I get hold of Indigo 7.4.1?


Still in progress, but we're getting pretty close to release I think.

Jay (Indigo Support)
Twitter | Facebook | LinkedIn

Posted on
Tue Jan 14, 2020 9:54 am
cesarvog offline
User avatar
Posts: 57
Joined: Aug 13, 2016
Location: Brazil

Re: Fibaro Smart Implant

Thank you for the fast reply, Jay.
Best regards

Posted on
Wed Jan 15, 2020 1:56 pm
cesarvog offline
User avatar
Posts: 57
Joined: Aug 13, 2016
Location: Brazil

Re: Fibaro Smart Implant

Ok, it seems the units I got are of Model ID 05022000. Looks like I will have to wait for 7.4.1 to be released.

See below for information collected when including the first of the two units I bought:

15 Jan 2020 16:50:33
Z-Wave controller included module: 094 - Notification Sensor
Z-Wave stopped controller inclusion mode

15 Jan 2020 16:52:34
Z-Wave Syncing - started for "094 - Notification Sensor"
Z-Wave Syncing - retrieved module neighbors list: 1, 4, 5, 20, 43, 44, 49, 51, 55, 57, 60, 62, 63, 64, 66, 68, 69, 72, 73, 75, 93
Z-Wave Syncing - assigning return route to "094 - Notification Sensor"
Z-Wave Syncing - assigned return route
Z-Wave Syncing - retrieved manufacture and model names: Fibaro System - 010F, Notification Sensor - 05022000
Z-Wave Syncing - retrieved protocol version 6.02, app version 5.01
Z-Wave Syncing - retrieved class hierarchy: Routing Slave : Notification Sensor : Notification Sensor (04 : 07 : 01, base 00)
Z-Wave Syncing - retrieved command classes: 20v1 85v1 86v1 8Ev1 55v1 56v1 98v1 59v1 5Av1 5Bv1 5Ev1 9Fv1 60v4 22v1 25v1 31v11 6Cv1 70v1 71v1 72v1 73v1 75v1 7Av1
Z-Wave Syncing - retrieved encrypt commands: - none -
Z-Wave Syncing - retrieved capabilities: routing, beaming, security
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 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]
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 association to interface
Z-Wave Syncing - created device "094 - Notification Sensor"
Z-Wave Syncing - created device "094 - Notification Sensor 2"
Z-Wave Syncing - created device "094 - Multilevel Sensor"
Z-Wave Syncing - created device "094 - Multilevel Sensor 2"
Z-Wave Syncing - created device "094 - Relay Switch"
Z-Wave Syncing - created device "094 - Relay Switch 2"
Z-Wave Syncing - created device "094 - Multilevel Sensor 3"
Z-Wave Syncing - complete
Z-Wave sent "094 - Notification Sensor" status request
Z-Wave sent "094 - Notification Sensor 2" status request
Z-Wave sent "094 - Multilevel Sensor" status request
Z-Wave received "094 - Multilevel Sensor" sensor update to 10.41 V
Z-Wave received "094 - Multilevel Sensor" units changed to V
Z-Wave sent "094 - Multilevel Sensor 2" status request
Z-Wave received "094 - Multilevel Sensor 2" sensor update to 10.36 V
Z-Wave received "094 - Multilevel Sensor 2" units changed to V
Z-Wave sent "094 - Relay Switch" status request
Z-Wave received "094 - Relay Switch" status update is on
Z-Wave sent "094 - Relay Switch 2" status request
Z-Wave received "094 - Relay Switch 2" status update is on
Z-Wave sent "094 - Multilevel Sensor 3" status request

Posted on
Thu Jan 16, 2020 3:26 am
McJohn offline
User avatar
Posts: 470
Joined: Dec 18, 2012
Location: The Netherlands

Re: Fibaro Smart Implant

Thanks for your contribution.

I’m sorry to say but also the first one (model ID 05021000) isn’t supported at the moment.
It only works with the Trigger “Match Raw package” and selection of "Any Device"
Last edited by McJohn on Thu Jan 16, 2020 7:19 am, edited 1 time in total.

Posted on
Thu Jan 16, 2020 3:28 am
howartp offline
Posts: 4092
Joined: Jan 09, 2014
Location: West Yorkshire, UK

Re: Fibaro Smart Implant

Have you tried with Zwave Scene Controller plugin?

It should accept most of the behaviours from memory, albeit maybe not the most intuitively.


Sent from my iPhone using Tapatalk Pro

Posted on
Thu Jan 16, 2020 3:36 am
McJohn offline
User avatar
Posts: 470
Joined: Dec 18, 2012
Location: The Netherlands

Re: Fibaro Smart Implant

Thanks for the fast reply,
It 's working a couple of months now (very fast) with the named Match Raw package trigger and we are satisfied with this temporary solution. :D
(The former Fibaro Binary sensor gives sometimes no reaction, this one always!)

Posted on
Thu Jan 16, 2020 6:01 am
cesarvog offline
User avatar
Posts: 57
Joined: Aug 13, 2016
Location: Brazil

Re: Fibaro Smart Implant

Thanks @McJohn and @howartp for your input.

I guess it won't be long now for full support to show up in 7.4.1. I guess the only difference between model IDs is the z-wave frequency, 05021000 being Europe, 05022000 US and 05023000 AU/NZ.
Once @Matt adds support to IN1 / IN2 and 2000 and 3000 variants, most likely everything will work as intended. This is a very capable device and it would be a shame to have it partially supported in Indigo.

Posted on
Thu Jan 16, 2020 1:08 pm
matt (support) offline
Site Admin
User avatar
Posts: 20016
Joined: Jan 27, 2003
Location: Texas

Re: Fibaro Smart Implant

cesarvog wrote:
I guess it won't be long now for full support to show up in 7.4.1.

Yep, new version coming soon.

Image

Posted on
Thu Jan 16, 2020 1:30 pm
cesarvog offline
User avatar
Posts: 57
Joined: Aug 13, 2016
Location: Brazil

Re: Fibaro Smart Implant

Thanks @Matt, it's reassuring.

Now, contrary to @McJohn's results ("For now it's working with the code * 0x71 0x05 * 0x07 0x02 * at "Any Device" Trigger."), I was able to get the * 0x71 0x05 * 0x07 0x02 * working by selecting either "Any Device" or "(Notification Sensor of each specific FGBS222 device)" in my raw z-wave command triggers. Thanks for your input, @howartp !!!

I originally defined a single raw z-wave command received trigger with Any Device and it worked as experienced by others above.

Then I tried defining one trigger pointing to "Notification Sensor" of the first Smart Implant and another pointing to "Notification Sensor" of the second Smart Implant that I received yesterday, as I supposed "Notification Sensor" refers to IN1 and "Notification Sensor 2" refers to IN2.

Both triggers work separately whenever I connect the yellow wire (IN1) to the blue wire (ground) of each Smart Implant. I have them set to record to the Log.
As reported by others above, Indigo shows no change in it's GUI. The State column Icon remains grey with "off" to the right.

Parameter 20 was manually changed using "Modify Configuration Parameter" from the default 2 (Monostable button - Central Scene) to 0 (Normally Closed) on both Smart Implants.

Sorry if explanation above is difficult to understand. English is not my native language.

Posted on
Thu Jan 16, 2020 1:59 pm
McJohn offline
User avatar
Posts: 470
Joined: Dec 18, 2012
Location: The Netherlands

Re: Fibaro Smart Implant

It's right that there are no changes in the GUI with the Match Raw package trigger.
So, for the time being you have to deal with this solution.

And when Matt says "the time is right", it's no far away anymore.

Kind regards,

John

Page 5 of 10 1, 2, 3, 4, 5, 6, 7, 8 ... 10

Who is online

Users browsing this forum: jalves and 1 guest