Fibaro Smart Implant

I added one today - came up as 05022000 and since it is not supported yet Indigo found the sensor but not the two DS temp probes (DS18B20).

Here is some data from Indigo, Happy to supply more if needed, just let me know.

PS - these have very very tiny wires (read, PITA to hook up) - just FYI in case anyone is thinking of adding one to their system.

Code: Select all

controller included module: 063 - Notification Sensor
   Z-Wave                          stopped controller inclusion mode
   Z-Wave                          Syncing - started for "063 - Notification Sensor"
   Z-Wave                          Syncing - retrieved module neighbors list: 2, 3, 4, 5, 6, 7, 8, 9, 12, 13, 14, 18, 19, 20, 21, 22, 25, 26, 31, 32, 33, 34, 37, 46, 47, 48, 61
   Z-Wave                          Syncing - assigning return route to "063 - 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), 8:(21 : 01), 9:(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], 8:[5E 85 8E 59 31 71 6C 22 98 9F], 9:[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 "063 - Notification Sensor"
   SQL Logger                      creating table device_history_69642674 for "063 - Notification Sensor"
   Z-Wave                          Syncing - created device "063 - Notification Sensor 2"
   SQL Logger                      creating table device_history_1326343618 for "063 - Notification Sensor 2"
   Z-Wave                          Syncing - created device "063 - Multilevel Sensor"
   SQL Logger                      creating table device_history_203783329 for "063 - Multilevel Sensor"
   SQL Logger                      adding column "sensorvalue" to table device_history_203783329 ("063 - Multilevel Sensor")
   Z-Wave                          Syncing - created device "063 - Multilevel Sensor 2"
   SQL Logger                      adding column "sensorvalue_ui" to table device_history_203783329 ("063 - Multilevel Sensor")
   SQL Logger                      creating table device_history_1301354066 for "063 - Multilevel Sensor 2"
   Z-Wave                          Syncing - created device "063 - Relay Switch"
   SQL Logger                      adding column "sensorvalue" to table device_history_1301354066 ("063 - Multilevel Sensor 2")
   Z-Wave                          Syncing - created device "063 - Relay Switch 2"
   SQL Logger                      adding column "sensorvalue_ui" to table device_history_1301354066 ("063 - Multilevel Sensor 2")
   Z-Wave                          Syncing - created device "063 - Multilevel Sensor 3"
   SQL Logger                      creating table device_history_1370263103 for "063 - Relay Switch"
   SQL Logger                      creating table device_history_1053796962 for "063 - Relay Switch 2"
   Z-Wave                          Syncing - created device "063 - Multilevel Sensor 4"
   SQL Logger                      creating table device_history_467823861 for "063 - Multilevel Sensor 3"
   Z-Wave                          Syncing - created device "063 - Multilevel Sensor 5"
   SQL Logger                      adding column "sensorvalue" to table device_history_467823861 ("063 - Multilevel Sensor 3")
   SQL Logger                      adding column "sensorvalue_ui" to table device_history_467823861 ("063 - Multilevel Sensor 3")
   Z-Wave                          Syncing - complete
   SQL Logger                      creating table device_history_1836324467 for "063 - Multilevel Sensor 4"
   SQL Logger                      adding column "sensorvalue" to table device_history_1836324467 ("063 - Multilevel Sensor 4")
   SQL Logger                      adding column "sensorvalue_ui" to table device_history_1836324467 ("063 - Multilevel Sensor 4")
   SQL Logger                      creating table device_history_1783730525 for "063 - Multilevel Sensor 5"
   SQL Logger                      adding column "sensorvalue" to table device_history_1783730525 ("063 - Multilevel Sensor 5")
   SQL Logger                      adding column "sensorvalue_ui" to table device_history_1783730525 ("063 - Multilevel Sensor 5")
   Z-Wave                          sent "063 - Notification Sensor" status request
   Z-Wave                          sent "063 - Notification Sensor 2" status request
   Z-Wave                          sent "063 - Multilevel Sensor" status request
   Z-Wave                          received "063 - Multilevel Sensor" sensor update to 11.73 V
   Z-Wave                          received "063 - Multilevel Sensor" units changed to V
   Z-Wave                          sent "063 - Multilevel Sensor 2" status request
   Z-Wave                          received "063 - Multilevel Sensor 2" sensor update to 11.60 V
   Z-Wave                          received "063 - Multilevel Sensor 2" units changed to V
   Z-Wave                          sent "063 - Relay Switch" status request
   Z-Wave                          sent "063 - Relay Switch 2" status request
   Z-Wave                          sent "063 - Multilevel Sensor 3" status request
   Z-Wave                          sent "063 - Multilevel Sensor 4" status request
   Z-Wave                          sent "063 - Multilevel Sensor 5" status request

Code: Select all

Jan 19, 2020 at 2:19:47 PM
   Z-Wave                          Indigo Device "Temp Sensor 2 Probe 063 - Notification Sensor" Z-Wave Properties:
Indigo Z-Wave Version: 7.4.0
Node ID: 63
Model: Notification Sensor
Model ID: 05022000
Manufacturer: Fibaro System
Manufacturer ID: 010F
Protocol Version: 6.02
Application Version: 5.01
Model Definition Version: 0
Library Type: 3
Class Name: Notification Sensor
Class Hierarchy: 04 : 07 : 01
Command Class Base: 00
Command Versions: 20v1 85v1 86v1 8Ev1 55v1 56v1 98v1 59v1 5Av1 5Bv1 5Ev1 9Fv1 60v4 22v1 25v1 31v11 6Cv1 70v1 71v1 72v1 73v1 75v1 7Av1
Encryption Status: Supported but not Enabled
Multi-Endpoint Types: 1:(07 : 01), 2:(07 : 01), 3:(21 : 01), 4:(21 : 01), 5:(10 : 01), 6:(10 : 01), 7:(21 : 01), 8:(21 : 01), 9:(21 : 01)
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], 8:[5E 85 8E 59 31 71 6C 22 98 9F], 9:[5E 85 8E 59 31 71 6C 22 98 9F]
Multi-Instance Counts: - none -
Features: routing, beaming, security
Neighbors: 2, 3, 4, 5, 6, 7, 8, 9, 12, 13, 14, 18, 19, 20, 21, 22, 25, 26, 31, 32, 33, 34, 37, 46, 47, 48, 61
Associations: 1:[1] 2:[] 3:[]
Config Values: - none -

I wonder if anyone has experienced similar behaviour with Implants.

I have one attached to my house water meter since New Year's eve and I'm counting impulses with it and it works 99% time just fine. But couple of windy days with short power outages (f.ex. lights go out for 0.1 secs) Implant has become unresponsive and I have to resync it to get it online. After syncing it functions just as before.

I already have it monitored by Device Extensions plugin so I know when it goes offline but I wonder can I automate the resync via Python code? I havent seen any scripts which can sync device before so Matt/Jay is it possible?

But couple of windy days with short power outages (f.ex. lights go out for 0.1 secs)

Most of electronic products don't like it to have no power... and again etc.

Is it possible to connect the Implant to an UPS or 12V PowerBank?

In our case the Implant works perfect and faster than the Fibaro Binary Sensor.
We discovered when it is placed too low to the floor, the connection is unstable, so we connect it ~ 2 meter above the ground and now it's working very good.

But couple of windy days with short power outages (f.ex. lights go out for 0.1 secs)

Most of electronic products don't like it to have no power... and again etc.

Is it possible to connect the Implant to an UPS or 12V PowerBank?

Yeah, its understandable. It seems that those short blinks are worst ones. If I take PSU off for 5...10s Implant reboots just fine and no resync needed.

UPS was my plan too, didnt think about the powerbank though. I havent played with those before - can I have it plugged in to mains and same time connected to 12V?

The best way is:
220V -> PowerBank 12V -> Smart Implant
(don't connect 2 x 12V at the same time/connecters at the Smart Implant)

The best way is:
220V -> PowerBank 12V -> Smart Implant
(don't connect 2 x 12V at the same time/connecters at the Smart Implant)

Sorry, didnt mean to have 2x12V connected! Have to take closer look to powerbanks and try it out.

But still like to know if resync via python script is possible?

[matt (support)]

Unfortunately that isn't currently possible via the python API but it is on the request list.

The resync question is for Matt

Personally I think it's an "emergency bandage".
You better make a good basic solution with 100% power.

Unfortunately that isn't currently possible via the python API but it is on the request list.

Bummer, that would've been great bandage for those nightime outages I just simply hate it when these happen at nighttime and couple UPS's sing a duet at 3am.

A good way to power these and the universal sensor is via wired security alarms (which I think was their original intended usage.. within PIRs).. most security systems run at 12v and have a solid stable connection with a battery backup.

That is exactly what I did. Turned two of my outside movement sensors wireless by adding the Smart Implant, powered by the older system via the original 12Vdc cabling. As a proof of concept it has worked very well. Intend to buy another 8 Smart Implants to convert all of the outside sensors.

[matt (support)]

Indigo 7.4.1 is now available and includes the new model ID for the Smart Implant.

Thanks @Matt and @Jay.

Got the 7.4.1 update installed, resynchronized all my Smart Implants and am glad to inform that everything is working as expected, including status update on Indigo's GUI when Binary IN1 is switched.

Good Job!

Also from Europe: many thanks for all the hard work; Smart Implant is now working perfect!
(We are looking forward for nice projects with the analog inputs )

And also thanks for the new/smaller font into the Log; more info to read.
(May added into the Indigo 7.4.1 Release Notes)

Cheers!

Hi Chaps,

I've just got one of these great little devices (well two actually) to use as a gate opener and the other as a IR break beam sensor.
In reading the burb, I was under the impression that as well as being triggered by the inputs, I would be able to switch the relays from Indigo to open and close the gate.
I've attached a screenshot to show where I'd expect to see this in the UI (Input/Output Controls) but there's no device listed for the Smart Implant there.
Alternatively, could I send a command to turn the Binary input on/off that would result in the relay switching?
When I try to turn on the Output relays via the UI (screenshot attached), it says:

9 Feb 2020 at 18:13:43
Z-Wave Error device "Gate Open/Close" does not support on command

So in summary, I'd like to be able to switch the relays using device actions. Is this possible?
Shout if you need more info/details.

Cheers,

Chris
--