Fibaro Smart Implant

Yes, a "Z-wave Command Received" trigger is for the time being the best option.
(We made one with a Trigger to Variable)

Beside this problem, we discovered something else strange:
the incoming "On"/"Button 1 Held Down" command is more than 3 seconds on the way before it receives Indigo (and the log).
The "Off"/"Button 1 released" command is immediate.

What settings have you got for input 1?

I suspect you’ve got a monostable/retractive button (ie doorbell) configured as a bistable/non-retractive button (ie normal light switch) or (more likely) vice-versa.

Therefore turning on the light switch appears to Indigo as though you’re holding down the button, which is why it takes 3 seconds to appear.

In parameter 20, value 2 is monostable scenes, value 3 is bistable scenes.

You want bistable for a regular switch.


Sent from my iPad using Tapatalk Pro

Thanks fore the feedback and your suggested parameters.
When we set parameter 20 to 3 (instead of 2), there is no reaction anymore of the Implant, also no life in the log.
The only thing we saw was:

Z-Wave retrieved parameter 20 "Input 1 type" is 3 "Toggle (Enables Scenes)"

And that's right because when we set this setting into the GUI, nothing happens also.

So, the only life feedback we got from the Implant was with the setting;
Input 1 type: "Push Button (Enables Scenes)"
and
Input 1 scene sending: "Held Down and Released Only".

For years we used the Fibaro Binary Sensor with an ABUS Infrared Light Beam detector (in front of the garage door) and that works perfect.
https://www.abus.com/eng/Home-Security/ ... -Beam-120m
The settings of the Binary sensor were:
Input 1 Type: Normaly Open.
Not so special...
Because the Implant is Z-Wave Plus we want this faster solution but it isn't unfortunately not plug & play with Indigo... Input 1 Type: Normaly Open at the Implant does nothing,

PS:

When we set at the Implant, Binary IN1 to:
Input 1 Type: "Normaly Open"
Input 1 scene sensding: "None"

As said before: no activity in the normal Indigo log and no Indigo Device "Binary IN1" goes on or off when we make a connection.
But:
When we set Z-Wave debug on:

Connect:

Code: Select all

  Z-Wave Debug                    RCVD requestAlarmSensorStatus: 01 0F 00 04 00 5B 09 71 05 00 00 00 FF 07 02 00 28
   Z-Wave Debug                    . .  requestAlarmSensorStatus: node 091, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
   Z-Wave Debug                    . .  requestAlarmSensorStatus: typeExt 7, valueExt 2, classSubKeyExt 7100000702
   
Break:
Z-Wave Debug                    RCVD requestAlarmSensorStatus: 01 0F 00 04 00 5B 09 71 05 00 00 00 FF 07 00 00 2A
   Z-Wave Debug                    . .  requestAlarmSensorStatus: node 091, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
   Z-Wave Debug                    . .  requestAlarmSensorStatus: typeExt 7, valueExt 0, classSubKeyExt 7100000700


So, I think Matt still has something to finish?

PS: Raw packets trigger doesn't work, no hits at this:

On:
3.1 seconds ago from 091 - Smart Implant - Binary IN1:
0x01 0x0F 0x00 0x04 0x00 0x5B 0x09 0x71 0x05 0x00 0x00 0x00 0xFF 0x07 0x02 0x00 0x28

Off:
0.9 seconds ago from 091 - Smart Implant - Binary IN1:
0x01 0x0F 0x00 0x04 0x00 0x5B 0x09 0x71 0x05 0x00 0x00 0x00 0xFF 0x07 0x00 0x00 0x2A

Matt can’t fix the Implant not sending any data.

Suggest you use Zwave Watcher plugin, which is same as Zwave Debug but only for one device - much easier to monitor in the log instead of the entire Zwave network activity.

For a detection beam, I would expect Normally Closed.

You won’t get Scenes sent by implant if using NO or NC, they only get sent for Push Button or Toggle.

Put a Zwave Watcher on your implant, set implant to Normally Closed, scenes: none.

Make sure implant has received the settings (it’s woken up).

Then play with detector and see what logs you get.


Sent from my iPhone using Tapatalk Pro

Thanks for all the tips & tricks.

What does this mean?:

Indigo 7.4 is now available and includes support for the Fibaro Smart Implant.

And this is the data the Implant sends:

Open:

Code: Select all

Z-Wave Debug                    RCVD requestAlarmSensorStatus: 01 0F 00 04 00 5B 09 71 05 00 00 00 FF 07 02 00 28
   Z-Wave Debug                    . .  requestAlarmSensorStatus: node 091, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
   Z-Wave Debug                    . .  requestAlarmSensorStatus: typeExt 7, valueExt 2, classSubKeyExt 7100000702


Break:

Code: Select all

Z-Wave Debug                    RCVD requestAlarmSensorStatus: 01 0F 00 04 00 5B 09 71 05 00 00 00 FF 07 00 00 2A
   Z-Wave Debug                    . .  requestAlarmSensorStatus: node 091, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
   Z-Wave Debug                    . .  requestAlarmSensorStatus: typeExt 7, valueExt 0, classSubKeyExt 7100000700

And this is from the Z-Wave Watcher:

Connect:
Z-Wave Watcher Debug Raw command received (Node 91): 01 0F 00 04 00 5B 09 71 05 00 00 00 FF 07 02 00 28
Disconnect:
Z-Wave Watcher Debug Raw command received (Node 91): 01 0F 00 04 00 5B 09 71 05 00 00 00 FF 07 00 00 2A

The log of Indigo says:


3.1 seconds ago from 091 - Smart Implant - Binary IN1:
0x01 0x0F 0x00 0x04 0x00 0x5B 0x09 0x71 0x05 0x00 0x00 0x00 0xFF 0x07 0x02 0x00 0x28


0.9 seconds ago from 091 - Smart Implant - Binary IN1:
0x01 0x0F 0x00 0x04 0x00 0x5B 0x09 0x71 0x05 0x00 0x00 0x00 0xFF 0x07 0x00 0x00 0x2A

Match Raw package trigger doesn't work for this Binary IN1 Indigo Device..

But it works with the selection of "Any Device"! -> Trigger fires to a Variable On and Off!

I recognise the commands from the Watcher, but I need to check at my PC what they say.

Watch this space.


Sent from my iPhone using Tapatalk Pro

Ok.

So the 71 05 notifications you're getting (...0x71 0x05 ....) are the Implant sending Home Security intruder alarm notifications. (Rather useful given you've got it hooked up to an intruder beam!)

I'm not sure how you're referring to "open/break" and "connect/disconnect" in your posts as they seem to contradict each other, but regardless - the Implant is sending a "Intruder" notification then a "All Clear" notification.

You could use a pattern match on these of "* 0x71 0x05 * 0x07 0x02 *" to detect the intrusion.

When Matt says he's added support for it, he means all the UI you see (Input 1 type.... input 1 send scenes ... toggle input 1/2 ....) which wouldn't be present if he hadn't worked all that out from the manual and included it into an Indigo release, and also handling the incoming scenes:

For scenes, when you set Input 1 type to Push Button or Toggle (not NO/NC) and enable scene sending, you will see what you posted earlier in the thread:

Z-Wave Debug RCVD sceneActivateCmd2: 01 0B 00 04 00 59 05 5B 03 17 02 01 E0
Z-Wave Debug . . sceneActivateCmd2: node 089, type: 2, scene: 1
Z-Wave received "089 - Binary IN1" button 1 held down

Z-Wave Debug RCVD sceneActivateCmd2: 01 0B 00 04 00 59 05 5B 03 18 01 01 EC
Z-Wave Debug . . sceneActivateCmd2: node 089, type: 1, scene: 1
Z-Wave received "089 - Binary IN1" button 1 released

That will mean you can use a trigger on Button 1 Held or Button 1 Released as in the image attachment you provided earlier.

What I suspect Matt hasn't allowed for, which is purely a theory of mine, is handling any combination of Clicked, Double-Clicked, Held, etc...

@Matt, that parameter appears to be summable, as the values are 1,2,4,8 so you could handle 1+2=3 for Click and Double-Click or 1+2+8 for Click, DoubleClick and Held etc. (Number/values from memory) It seems as stated in the manual and presumably how you've implemented it, that the Implant only reports 1 OR 2 OR 4 OR 8 which doesn't make usability sense; why would I ONLY want to know if someone double-clicked my switch, for example?)

@McJohn, If my theory is correct, you could manually set parameter 40 to value 9 (1 byte value) and see if you get a more useful response, ie less than 3 seconds.

Peter

ps - i've just ordered a Smart Implant so i'll be able to work with Matt on any tweaks.

...and see if I can track Durosity with it.

Peter

[matt (support)]

We'll get Indigo 7.4.1 to route the alarm notification messages to the Binary IN1 and IN2 devices. The current definition wasn't expecting those commands to be used for IN1 and IN2. That'll address the main problem here I think, although I am still curious about the scene commands being sent...

Peter: regarding the parameter 40 (and 41), this is how Indigo maps the UI popup choices currently shown:

Code: Select all

( 0x00, "None" ),
( 0x01, "Single Tap" ),
( 0x03, "Single and Double Tap" ),
( 0x07, "Single, Double, and Triple Tap" ),
( 0x08, "Held Down and Released Only" ),
( 0x0F, "All Scenes" )

which isn't all of the permutations but what I thought would be the useful ones. It sounds like I might have misread the manual though and the only possible choices are 1, 2, 4 and 8 which like you said doesn't make sense but maybe that is the way it works. They should have just used values 1, 2, 3, and 4 if that weren't trying to use combinable bit flags, but who knows.

McJohn: Are you saying the it only sends scenes commands (as shown in the Event Log) if you choose "Held Down and Released Only"? If we take the manual literally, then I'd expect "Single Tap" to also report single taps (but not held or releases), and I'd expect the other 3 options, including "All Scenes" to do nothing. Can you verify the behavior you are seeing?

Thank you so much for all the (interesting) feedback.

Implant settings are now: Input type 1: “Normally Open”
When the beam is interrupted (that makes a connection to Input 1);
(Node 91): 01 0F 00 04 00 5B 09 71 05 00 00 00 FF 07 02 00 28

When the beam is back to normal (disconnect Input 1):
(Node 91): 01 0F 00 04 00 5B 09 71 05 00 00 00 FF 07 00 00 2A

Thanks for this code (* 0x71 0x05 * 0x07 0x02 *) but with the Raw packets trigger on Indigo Device
“Smart Implant Binary 1” it does nothing.
With “Any Device” it works (but that works also with the loooong code).
I think this is double raw and deep Z-Wave stuff because normally a raw code gives a hit to an Indigo device.

When I set set parameter 40 to value 9 the same thing happened as with the scene sending "Held Down and Released Only”: 3 seconds before something happens into the log and release give an immediate reaction.
(and suddenly value 9 came into the GUI..)

And indeed Matt: we have tested all the scenes this morning again (when you were sleeping ) Only "Held Down and Released Only” give a message into the normal Indigo log.

[matt (support)]

So choosing the "Single Tap" item doesn't even report when you do a quick tap/release? I'd definitely expect that to work, although I understand it may not be useful for you scenario.

I think 7.4.1 will get it working correctly and the IN1 state will update.

So choosing the "Single Tap" item doesn't even report when you do a quick tap/release?

That's right. We have tested again this setting (with a fast interrupting of the beam) and nothing happened into the log.
(Maybe it's because the 3 seconds delay of the Scene setting?, it has no chance to respond with 1 second single "tap")

We are looking forward for a quick solution, many thanks for support of all the (complicated) settings of this module.

PS: we have only 2 wires connected to ground and input1 (NO).
At this moment there is no connection between the 2 wires but Indigo (Device setting is also NO) says: "Smart Implant - Binary IN1" = On. (It has to be off).
And further on we have no temp sensor installed and no analog inputs. So, it's magic where the temperature is coming from and the both 10.31V inputs...