Fibaro Smart Implant

Posted on
Sat Feb 22, 2020 5:19 am
howartp offline
Posts: 4559
Joined: Jan 09, 2014
Location: West Yorkshire, UK

Re: Fibaro Smart Implant

Ok, my IN1 and IN2 are working perfectly.

Indigo 7.4.1, resynced device before I started.

Both set to NO (as i'm using bare wires, easier than NC).

Association Group 1: Node 1 ZWave
Association Groups 2+3: No devices

IN1 and IN2 are reporting correctly what I'm doing with the wires.

I've sent debug log direct to Matt.

Peter

Posted on
Sat Feb 22, 2020 5:24 am
howartp offline
Posts: 4559
Joined: Jan 09, 2014
Location: West Yorkshire, UK

Re: Fibaro Smart Implant

I’ve just had a thought which is a further benefit to my Zwave Watcher plugin that I haven’t realised or pushed before.

If you browse to the Indigo install folder > Logs/Zwave Watcher folder, that debug log will be clean of non-interesting traffic so we can focus in on the matter at hand.


Sent from my iPhone using Tapatalk Pro

Posted on
Sat Feb 22, 2020 8:13 am
cesarvog offline
User avatar
Posts: 155
Joined: Aug 13, 2016
Location: Brazil

Re: Fibaro Smart Implant

howartp wrote:
I’ve just had a thought which is a further benefit to my Zwave Watcher plugin that I haven’t realised or pushed before.

If you browse to the Indigo install folder > Logs/Zwave Watcher folder, that debug log will be clean of non-interesting traffic so we can focus in on the matter at hand.

o


Ok. I have created two Zwave Watcher devices referencing IN1 and IN2 of Fibaro Smart Implant (device 104). How should I proceed now?
Should I do the a) Switch IN1, b) Switch IN2, c) Remove Association, d) Resync, e) Switch IN1, f) Switch IN2 routine again and then collect the Log from the above referenced folder and post it here?

Thanks for your continued support.

UPDATE : Superseded, please see the following post for updated info on this.
=======
Attachments
Screen Shot 2020-02-22 at 11.10.09.png
Screen Shot 2020-02-22 at 11.10.09.png (32.66 KiB) Viewed 2451 times
Last edited by cesarvog on Sat Feb 22, 2020 10:17 am, edited 1 time in total.

Posted on
Sat Feb 22, 2020 9:43 am
cesarvog offline
User avatar
Posts: 155
Joined: Aug 13, 2016
Location: Brazil

Re: Fibaro Smart Implant

Hello Everyone,

I don't know what happened, but it seems with the zwave watcher plugin on, both IN1 and IN2 correctly show when switched. Don't know what to say at this time. I'm quite sure IN2 it wasn't being received before...

Here is the zwave watcher log:

2020-02-22 11:02:11.328 DEBUG Plugin.debugLog: startup called
2020-02-22 11:25:56.505 DEBUG Plugin.debugLog: Raw command received (Node 104 Endpoint 7): 01 0C 00 04 10 68 06 31 05 01 22 01 6C FF
2020-02-22 11:25:56.505 DEBUG Plugin.debugLog: Raw command received (Node 104): 01 10 00 04 10 68 0A 60 0D 07 01 31 05 01 22 01 6C 88
2020-02-22 11:25:56.574 DEBUG Plugin.debugLog: Raw command received (Node 104 Endpoint 7): 01 0C 00 04 10 68 06 31 05 01 22 01 6C FF
2020-02-22 11:25:56.575 DEBUG Plugin.debugLog: Raw command received (Node 104): 01 10 00 04 10 68 0A 60 0D 07 01 31 05 01 22 01 6C 88
2020-02-22 11:25:56.576 DEBUG Plugin.debugLog: Raw command received (Node 104 Endpoint 7): 01 0C 00 04 10 68 06 31 05 01 22 01 6C FF
2020-02-22 11:25:56.576 DEBUG Plugin.debugLog: Raw command received (Node 104): 01 10 00 04 10 68 0A 60 0D 07 01 31 05 01 22 01 6C 88
2020-02-22 11:25:56.643 DEBUG Plugin.debugLog: Raw command received (Node 104 Endpoint 7): 01 0C 00 04 10 68 06 31 05 01 22 01 6C FF
2020-02-22 11:25:56.644 DEBUG Plugin.debugLog: Raw command received (Node 104): 01 10 00 04 10 68 0A 60 0D 07 01 31 05 01 22 01 6C 88
2020-02-22 11:25:56.646 DEBUG Plugin.debugLog: Raw command received (Node 104 Endpoint 7): 01 0C 00 04 10 68 06 31 05 01 22 01 6C FF
2020-02-22 11:25:56.646 DEBUG Plugin.debugLog: Raw command received (Node 104): 01 10 00 04 10 68 0A 60 0D 07 01 31 05 01 22 01 6C 88
2020-02-22 11:25:56.665 DEBUG Plugin.debugLog: Raw command received (Node 104 Endpoint 7): 01 0C 00 04 10 68 06 31 05 01 22 01 6C FF
2020-02-22 11:25:56.665 DEBUG Plugin.debugLog: Raw command received (Node 104): 01 10 00 04 10 68 0A 60 0D 07 01 31 05 01 22 01 6C 88
2020-02-22 11:25:56.894 DEBUG Plugin.debugLog: Raw command received (Node 104 Endpoint 7): 01 0C 00 04 10 68 06 31 05 01 22 01 6C FF
2020-02-22 11:25:56.894 DEBUG Plugin.debugLog: Raw command received (Node 104): 01 10 00 04 10 68 0A 60 0D 07 01 31 05 01 22 01 6C 88
2020-02-22 11:25:57.020 DEBUG Plugin.debugLog: Raw command received (Node 104 Endpoint 7): 01 0C 00 04 10 68 06 31 05 01 22 01 6C FF
2020-02-22 11:25:57.020 DEBUG Plugin.debugLog: Raw command received (Node 104): 01 10 00 04 10 68 0A 60 0D 07 01 31 05 01 22 01 6C 88
2020-02-22 12:37:50.718 DEBUG Plugin.debugLog: Raw command received (Node 104 Endpoint 5): 01 09 00 04 00 68 03 25 03 FF FF
2020-02-22 12:37:50.719 DEBUG Plugin.debugLog: Raw command received (Node 104): 01 0D 00 04 00 68 07 60 0D 05 01 25 03 FF 29
2020-02-22 12:37:50.736 DEBUG Plugin.debugLog: Raw command received (Node 104 Endpoint 1): 01 0F 00 04 00 68 09 71 05 00 00 00 FF 07 00 00 FF
2020-02-22 12:37:50.736 DEBUG Plugin.debugLog: Raw command received (Node 104): 01 13 00 04 00 68 0D 60 0D 01 01 71 05 00 00 00 FF 07 00 00 6C
2020-02-22 12:37:51.540 DEBUG Plugin.debugLog: Raw command received (Node 104 Endpoint 5): 01 09 00 04 00 68 03 25 03 00 FF
2020-02-22 12:37:51.541 DEBUG Plugin.debugLog: Raw command received (Node 104): 01 0D 00 04 00 68 07 60 0D 05 01 25 03 00 D6
2020-02-22 12:37:51.612 DEBUG Plugin.debugLog: Raw command received (Node 104 Endpoint 1): 01 0F 00 04 00 68 09 71 05 00 00 00 FF 07 02 00 FF
2020-02-22 12:37:51.612 DEBUG Plugin.debugLog: Raw command received (Node 104): 01 13 00 04 00 68 0D 60 0D 01 01 71 05 00 00 00 FF 07 02 00 6E
2020-02-22 12:38:18.307 DEBUG Plugin.debugLog: Raw command received (Node 104 Endpoint 6): 01 09 00 04 00 68 03 25 03 FF FF
2020-02-22 12:38:18.307 DEBUG Plugin.debugLog: Raw command received (Node 104): 01 0D 00 04 00 68 07 60 0D 06 01 25 03 FF 2A
2020-02-22 12:38:18.326 DEBUG Plugin.debugLog: Raw command received (Node 104 Endpoint 2): 01 0F 00 04 00 68 09 71 05 00 00 00 FF 07 00 00 FF
2020-02-22 12:38:18.327 DEBUG Plugin.debugLog: Raw command received (Node 104): 01 13 00 04 00 68 0D 60 0D 02 01 71 05 00 00 00 FF 07 00 00 6F
2020-02-22 12:38:19.197 DEBUG Plugin.debugLog: Raw command received (Node 104 Endpoint 6): 01 09 00 04 00 68 03 25 03 00 FF
2020-02-22 12:38:19.197 DEBUG Plugin.debugLog: Raw command received (Node 104): 01 0D 00 04 00 68 07 60 0D 06 01 25 03 00 D5
2020-02-22 12:38:19.373 DEBUG Plugin.debugLog: Raw command received (Node 104 Endpoint 2): 01 0F 00 04 00 68 09 71 05 00 00 00 FF 07 02 00 FF
2020-02-22 12:38:19.374 DEBUG Plugin.debugLog: Raw command received (Node 104): 01 13 00 04 00 68 0D 60 0D 02 01 71 05 00 00 00 FF 07 02 00 6D

Here is Indigo 7.4.1 log (not from the same capture, as I have unwillingly cleared the Indigo log after I got the above):

2 Feb 2020 12:42:41
Z-Wave received "Sensor Novo Piscina - Relay 1" status update is on
Z-Wave Watcher Debug Raw command received (Node 104 Endpoint 5): 01 09 00 04 00 68 03 25 03 FF FF
Z-Wave Watcher Debug Raw command received (Node 104): 01 0D 00 04 00 68 07 60 0D 05 01 25 03 FF 29
Z-Wave received "Sensor Novo Piscina - Binary IN1" status update is off
Z-Wave Watcher Debug Raw command received (Node 104 Endpoint 1): 01 0F 00 04 00 68 09 71 05 00 00 00 FF 07 00 00 FF
Z-Wave Watcher Debug Raw command received (Node 104): 01 13 00 04 00 68 0D 60 0D 01 01 71 05 00 00 00 FF 07 00 00 6C
Z-Wave received "Sensor Novo Piscina - Relay 1" status update is off
Z-Wave Watcher Debug Raw command received (Node 104 Endpoint 5): 01 09 00 04 00 68 03 25 03 00 FF
Z-Wave Watcher Debug Raw command received (Node 104): 01 0D 00 04 00 68 07 60 0D 05 01 25 03 00 D6
Z-Wave received "Sensor Novo Piscina - Binary IN1" status update is on
Z-Wave Watcher Debug Raw command received (Node 104 Endpoint 1): 01 0F 00 04 00 68 09 71 05 00 00 00 FF 07 02 00 FF
Z-Wave Watcher Debug Raw command received (Node 104): 01 13 00 04 00 68 0D 60 0D 01 01 71 05 00 00 00 FF 07 02 00 6E
Z-Wave received "Sensor Novo Piscina - Relay 2" status update is on
Z-Wave Watcher Debug Raw command received (Node 104 Endpoint 6): 01 09 00 04 00 68 03 25 03 FF FF
Z-Wave Watcher Debug Raw command received (Node 104): 01 0D 00 04 00 68 07 60 0D 06 01 25 03 FF 2A
Z-Wave received "Sensor Novo Piscina - Binary IN2" status update is off
Z-Wave Watcher Debug Raw command received (Node 104 Endpoint 2): 01 0F 00 04 00 68 09 71 05 00 00 00 FF 07 00 00 FF
Z-Wave Watcher Debug Raw command received (Node 104): 01 13 00 04 00 68 0D 60 0D 02 01 71 05 00 00 00 FF 07 00 00 6F
Z-Wave received "Sensor Novo Piscina - Relay 2" status update is off
Z-Wave Watcher Debug Raw command received (Node 104 Endpoint 6): 01 09 00 04 00 68 03 25 03 00 FF
Z-Wave Watcher Debug Raw command received (Node 104): 01 0D 00 04 00 68 07 60 0D 06 01 25 03 00 D5
Z-Wave received "Sensor Novo Piscina - Binary IN2" status update is on
Z-Wave Watcher Debug Raw command received (Node 104 Endpoint 2): 01 0F 00 04 00 68 09 71 05 00 00 00 FF 07 02 00 FF
Z-Wave Watcher Debug Raw command received (Node 104): 01 13 00 04 00 68 0D 60 0D 02 01 71 05 00 00 00 FF 07 02 00 6D

Indigo's GUI also now correctly show the changes when switching both IN1 (which triggers Relay 1) and IN2 (which triggers Relay 2).

Cesar
================================

UPDATE : Oh wait... I went ahead and tried the above mentioned 6 steps routine on the other Smart Implant (device 102) and it has cleared the issues. I don't know why it did not work the first time I tried those steps the first time on device 104. The output on Indigo's log can be seen below:

22 Feb 2020 12:44:14
Z-Wave received "Sensor Novo Piscina - Relay 2" status update is on
Z-Wave Watcher Debug Raw command received (Node 104 Endpoint 6): 01 09 00 04 00 68 03 25 03 FF FF
Z-Wave Watcher Debug Raw command received (Node 104): 01 0D 00 04 00 68 07 60 0D 06 01 25 03 FF 2A
Z-Wave received "Sensor Novo Piscina - Binary IN2" status update is off
Z-Wave Watcher Debug Raw command received (Node 104 Endpoint 2): 01 0F 00 04 00 68 09 71 05 00 00 00 FF 07 00 00 FF
Z-Wave Watcher Debug Raw command received (Node 104): 01 13 00 04 00 68 0D 60 0D 02 01 71 05 00 00 00 FF 07 00 00 6F
Z-Wave received "Sensor Novo Piscina - Relay 2" status update is off
Z-Wave Watcher Debug Raw command received (Node 104 Endpoint 6): 01 09 00 04 00 68 03 25 03 00 FF
Z-Wave Watcher Debug Raw command received (Node 104): 01 0D 00 04 00 68 07 60 0D 06 01 25 03 00 D5
Z-Wave received "Sensor Novo Piscina - Binary IN2" status update is on
Z-Wave Watcher Debug Raw command received (Node 104 Endpoint 2): 01 0F 00 04 00 68 09 71 05 00 00 00 FF 07 02 00 FF
Z-Wave Watcher Debug Raw command received (Node 104): 01 13 00 04 00 68 0D 60 0D 02 01 71 05 00 00 00 FF 07 02 00 6D

22 Feb 2020 12:44:31
Z-Wave received "Sensor Novo Piscina - Relay 1" status update is on
Z-Wave Watcher Debug Raw command received (Node 104 Endpoint 5): 01 09 00 04 00 68 03 25 03 FF FF
Z-Wave Watcher Debug Raw command received (Node 104): 01 0D 00 04 00 68 07 60 0D 05 01 25 03 FF 29
Z-Wave received "Sensor Novo Piscina - Binary IN1" status update is off
Z-Wave Watcher Debug Raw command received (Node 104 Endpoint 1): 01 0F 00 04 00 68 09 71 05 00 00 00 FF 07 00 00 FF
Z-Wave Watcher Debug Raw command received (Node 104): 01 13 00 04 00 68 0D 60 0D 01 01 71 05 00 00 00 FF 07 00 00 6C
Z-Wave Watcher Debug Raw command received (Node 104 Endpoint 5): 01 09 00 04 00 68 03 25 03 FF FF
Z-Wave Watcher Debug Raw command received (Node 104): 01 0D 00 04 00 68 07 60 0D 05 01 25 03 FF 29
Z-Wave received "Sensor Novo Piscina - Binary IN1" status update is off
Z-Wave Watcher Debug Raw command received (Node 104 Endpoint 1): 01 0F 00 04 00 68 09 71 05 00 00 00 FF 07 00 00 FF
Z-Wave Watcher Debug Raw command received (Node 104): 01 13 00 04 00 68 0D 60 0D 01 01 71 05 00 00 00 FF 07 00 00 6C
Z-Wave received "Sensor Novo Piscina - Relay 1" status update is off
Z-Wave Watcher Debug Raw command received (Node 104 Endpoint 5): 01 09 00 04 00 68 03 25 03 00 FF
Z-Wave Watcher Debug Raw command received (Node 104): 01 0D 00 04 00 68 07 60 0D 05 01 25 03 00 D6
Z-Wave received "Sensor Novo Piscina - Binary IN1" status update is on
Z-Wave Watcher Debug Raw command received (Node 104 Endpoint 1): 01 0F 00 04 00 68 09 71 05 00 00 00 FF 07 02 00 FF
Z-Wave Watcher Debug Raw command received (Node 104): 01 13 00 04 00 68 0D 60 0D 01 01 71 05 00 00 00 FF 07 02 00 6E

22 Feb 2020 12:45:22
Z-Wave received "Frente - Garage Door Controller (NGD00Z)" status update is open
Z-Wave received "Frente - Garage Door Controller (NGD00Z)" status update is open

22 Feb 2020 12:46:14
Z-Wave received "Sensor Novo Garagem - Binary IN1" status update is off
Z-Wave received "Sensor Novo Garagem - Binary IN1" status update is on

22 Feb 2020 12:48:44
Z-Wave received "086 - Sensor Piscina - Dry Contact" status update battery level 100%
Z-Wave received "086 - Sensor Piscina - Dry Contact" status update battery level 100%
Z-Wave removed association of "001 - Indigo Z-Wave Interface" from "Sensor Novo Garagem - Binary IN1" group 1
Z-Wave retrieved group 1 associations: []
Z-Wave Syncing - started for "Sensor Novo Garagem - Binary IN1"
Z-Wave Syncing - retrieved module neighbors list: 20, 43, 44, 66, 70, 91, 95, 103, 104
Z-Wave Syncing - assigning return route to "102 - Sensor Novo Garagem - Binary IN1"
Z-Wave Syncing - assigned return route

22 Feb 2020 12:52:44
Z-Wave Syncing - started for "Sensor Novo Garagem - Binary IN1"
Z-Wave Syncing - retrieved module neighbors list: 20, 43, 44, 66, 70, 91, 95, 103, 104
Z-Wave Syncing - assigning return route to "102 - Sensor Novo Garagem - Binary IN1"
Z-Wave Syncing - assigned return route
Z-Wave Syncing - retrieved manufacture and model names: Fibaro System - 010F, Smart Implant (FGBS222) - 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: 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: - 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 multi association to interface
Z-Wave Syncing - retrieved parameter 20 "Input 1 type" is 0 "Normally Closed"
Z-Wave Syncing - retrieved parameter 40 "Input 1 scene sending" is 0 "None"
Z-Wave Syncing - retrieved parameter 21 "Input 2 type" is 0 "Normally Closed"
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 0 * 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 "Sensor Novo Garagem - Binary IN1" status request
Z-Wave sent "Sensor Novo Garagem - Analog IN1" status request
Z-Wave received "Sensor Novo Garagem - Analog IN1" sensor update to 10.26 V
Z-Wave sent "Sensor Novo Garagem - Binary IN2" status request
Z-Wave sent "Sensor Novo Garagem - Analog IN2" status request
Z-Wave received "Sensor Novo Garagem - Analog IN2" sensor update to 10.24 V
Z-Wave sent "Sensor Novo Garagem - Relay 1" status request
Z-Wave sent "Sensor Novo Garagem - Relay 2" status request
Z-Wave sent "Sensor Novo Garagem - Temperature" status request
Z-Wave received "Sensor Novo Garagem - Temperature" sensor update to 36.2 °C
Z-Wave received "Sensor Novo Garagem - Relay 1" status update is on
Z-Wave received "Sensor Novo Garagem - Binary IN1" status update is off
Z-Wave received "Sensor Novo Garagem - Relay 1" status update is off
Z-Wave received "Sensor Novo Garagem - Binary IN1" status update is on
Z-Wave received "Sensor Novo Garagem - Relay 2" status update is on
Z-Wave received "Sensor Novo Garagem - Binary IN2" status update is off
Z-Wave received "Sensor Novo Garagem - Relay 2" status update is off
Z-Wave received "Sensor Novo Garagem - Binary IN2" status update is on

@Matt Please consider this case closed. I ran through the 6 steps on all of my Smart Implants, and am glad to inform It's working correctly with both IN1 and IN2 on all of my installed Fibaro Smart Implants.

@Howartp, many thanks for stepping in and helping me troubleshoot this issue.

Posted on
Sat Feb 22, 2020 1:12 pm
matt (support) offline
Site Admin
User avatar
Posts: 21417
Joined: Jan 27, 2003
Location: Texas

Re: Fibaro Smart Implant

Great, I'm glad you have IN2 reporting updates now. Thanks for the follow-ups.

Image

Posted on
Thu Feb 27, 2020 10:57 am
Nick offline
Posts: 18
Joined: Nov 06, 2018

Re: Fibaro Smart Implant

Thanks, this worked for me:

1. Go to Interfaces->Z-Wave->Manage associations
2. Remove: Association Group 1: 001 - Indigo Z-wave Interface
3. Resync the device

Binary 2 is reporting....on/off

Posted on
Sat Mar 28, 2020 7:02 am
McJohn offline
User avatar
Posts: 631
Joined: Dec 18, 2012
Location: The Netherlands

Re: Fibaro Smart Implant

Good and healthy day!

Does anyone have some experience with the Smart Implant and analog inputs?

We connected a distance sensor to analog input 1 and signals are ok (checked with a multimeter) but in Indigo the analog state only changed after each re-sync.

Input 1 type; Analog Input, Analog input interval 1, Analog input sensitivity 1
Attachments
Screen Shot 2020-03-28 at 13.48.00.png
Screen Shot 2020-03-28 at 13.48.00.png (28.33 KiB) Viewed 2251 times
Screen Shot 2020-03-28 at 13.45.37.png
Screen Shot 2020-03-28 at 13.45.37.png (38.21 KiB) Viewed 2251 times

Posted on
Sat Mar 28, 2020 10:22 am
Nick offline
Posts: 18
Joined: Nov 06, 2018

Re: Fibaro Smart Implant

Yes, I am using servodan 43-198 analogue lux sensor and wind speed sensor. At first the smart implant didn't report updates to indigo but after remove/resycn, see steps above, it worked.

But today I attached a binary rain sensor to another smart implant and again no updates in indigo. So it has some strange behavior.. indigo or the smart implant.

Posted on
Sat Mar 28, 2020 12:04 pm
McJohn offline
User avatar
Posts: 631
Joined: Dec 18, 2012
Location: The Netherlands

Re: Fibaro Smart Implant

Thanks for your feedback.
In the meantime I have sent Fibaro an email how the Implant response with analog devices, let you know the answer.

When you use the Z-Wave Watcher plugin, did you get any results with one of your Implants connected to analog inputs?
In our case the Z-Wave Watcher only sees results at Binary 1 of another Implant.

Posted on
Sat Mar 28, 2020 12:09 pm
matt (support) offline
Site Admin
User avatar
Posts: 21417
Joined: Jan 27, 2003
Location: Texas

Re: Fibaro Smart Implant

Hi John,

Does it update if you send the Analog 1 a device status request? If not, can you capture what is sent/received with debug logging and paste the results for me?

Image

Posted on
Sat Mar 28, 2020 12:29 pm
McJohn offline
User avatar
Posts: 631
Joined: Dec 18, 2012
Location: The Netherlands

Re: Fibaro Smart Implant

That was a good one Matt!

"Send Status Request" gave an update of the Volt status.
From 0.12V until 2.61 V (close to the distance sensor)

Z-Wave sent "108 - Analog IN1" status request
Z-Wave Debug RCVD multiEndPointPacket: 01 10 00 04 00 6C 0A 60 0D 03 01 31 05 0F 42 00 0C 97
Z-Wave Debug . . multiEndPointPacket: node 108, endPoint 3
Z-Wave Debug RCVD requestVarSensorStatus: 01 0C 00 04 00 6C 06 31 05 0F 42 00 0C FF
Z-Wave Debug . . requestVarSensorStatus: node 108, endpoint 3, type 15, raw value 4200...
Z-Wave Debug . . requestVarSensorStatus: 0.12 V (float: 0.120000)
Z-Wave received "108 - Analog IN1" sensor update to 0.12 V

Posted on
Sat Mar 28, 2020 12:39 pm
McJohn offline
User avatar
Posts: 631
Joined: Dec 18, 2012
Location: The Netherlands

Re: Fibaro Smart Implant

And with the "Send status request" command, Z-Wave Watcher gave also results:

Z-Wave Watcher Debug Raw command sent (Node 108 Endpoint 3): 01 0F 00 13 6C 08 60 0D 01 03 31 04 02 00 25 A5 5F (True)
Z-Wave sent "108 - Analog IN1" status request
Z-Wave received "108 - Analog IN1" sensor update to 1.37 V
Z-Wave Watcher Debug Raw command received (Node 108 Endpoint 3): 01 0C 00 04 00 6C 06 31 05 0F 42 00 89 FF
Z-Wave Watcher Debug Raw command received (Node 108): 01 10 00 04 00 6C 0A 60 0D 03 01 31 05 0F 42 00 89 12



So, the question is; why doesn't the Implant not automatically send this other status to Indigo?

Posted on
Sat Mar 28, 2020 12:46 pm
matt (support) offline
Site Admin
User avatar
Posts: 21417
Joined: Jan 27, 2003
Location: Texas

Re: Fibaro Smart Implant

I just checked how Indigo defines those configuration parameters and it looks correct to me (based on the PDF manual for the Implant). So I think either the PDF is wrong and the configuration parameters aren't documented correctly, or there is a firmware bug in the module. My guess is the latter, but that is just a guess.

Image

Posted on
Sat Mar 28, 2020 1:36 pm
McJohn offline
User avatar
Posts: 631
Joined: Dec 18, 2012
Location: The Netherlands

Re: Fibaro Smart Implant

Thanks for the info.

This Implant is a month old but has the same model ID as the version from October 2019.
See info below.

With a Schedule at every 1 second with a Full Status Request update it's working but that's not the way it has to be..

What's the different with Nick's configuration?
Yes, I am using servodan 43-198 analogue lux sensor and wind speed sensor. At first the smart implant didn't report updates to indigo but after remove/resycn, see steps above, it worked.


Model: Smart Implant (FGBS222)
Model ID: 05021000
Manufacturer: Fibaro System
Manufacturer ID: 010F
Protocol Version: 6.02
Application Version: 5.01
Model Definition Version: 2
Library Type: 3
Class Name: Notification Sensor
Class Hierarchy: 04 : 07 : 01
Command Class Base: 00
Command Versions: 85v1 86v1 8Ev1 98v1 9Fv1 20v1 22v1 25v1 31v11 55v1 56v1 59v1 5Av1 5Bv1 5Ev1 60v4 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)
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]
Multi-Instance Counts: - none -
Features: routing, beaming, security
Neighbors: 2, 3, 4, 5, 6, 7, 8, 9, 10, 12, 13, 14, 15, 20, 21, 22, 23, 24, 25, 26, 27, 29, 30, 31, 34, 35, 86, 87, 91, 95, 96, 100, 106
Associations: 1:[1] 2:[] 3:[]
Config Values: 64:1 65:5 66:0 67:1 68:1 40:0 41:2 20:4 21:2 150:1 151:10 24:0 25:0 154:0 155:0 156:0 157:0 63:1

Posted on
Sat Mar 28, 2020 1:38 pm
matt (support) offline
Site Admin
User avatar
Posts: 21417
Joined: Jan 27, 2003
Location: Texas

Re: Fibaro Smart Implant

Have you tried a complete reset of it? That is: exclude, re-include, re-sync, and re-configure settings in Indigo's UI?

Image

Who is online

Users browsing this forum: No registered users and 5 guests