Issues with Fibaro FGBS-222-US Smart Implant adding child devices

[RenderCAD]

I don't have a Smart Implant but I do have a number of Universal Binary Sensors, one of which I repurposed recently. Based on my experience I would suggest you first upgrade to Z-Wave Beta 3.0.11.0 then exclude and re-include non-secure. I found 3.0.10.0 had problems when including a number of devices.

Steve

Hello Steve,
I followed your instructions and now it works fine. Thank you, really thank you

Massimo-RenderCAD srl

[rmasonjr]

I'm new to the Smart Implant device and I just spent a while reading through this thread.
I have one on my test bench - boy this thing is tiny!

Can someone confirm if these versions work?

HS v4.2.18.3
Z-Wave Plugin: 4.1.1.0 Beta (Add device unsecured)

So, what I need is a Z-Wave sensor with a remote probe to monitor refrigerators and freezers. We've never had a failure, but I really like stats and thought this would be a good sensor to use. One sensor to monitor everything, and maybe even throw in a water sensor around the ice maker water supply.

Thanks in advance!

[allenc3]

This Implant device has so much promise but in HS4 it is worthless. Multiple includes and removes produce different numbers of child items each time. Only the two outputs ever work and I need the two binary inputs only. And what the heck are all those Application Status items?

What really bugs me are the videos on YT showing ppl getting it installed, up and fully configured easily in a minute or two by using a Fibaro or HomeAssistant app. For this device to integrate into HS4 would take custom code from HS or a plug-in driver of some sort. Sad.

[allenc3]

That's good, and yes the low-voltage world is shocking unregulated for a lot, so you should be good on that side.

You say “the low voltage world is shocking…”. Really. You some kind of comedian? 😆

[allenc3]

I just spoke with Tyler in Support at HomeSeer about this Smart Implant device. He looked in the call log and said they had only a few requests for help on it. I mentioned that there a many comments and requests for help on this forum and he said if they don’t get Support calls for an item they don’t log the requests and don’t add the feature to the Z-Wave driver.

May I suggest that all of you call HS Support at 603-471-2816 and ask for this device to be supported in the code base. Only then will it ever work right.

[rmasonjr]

I added the device in unsecured mode on the Z-Wave plugin v4.1.1.0. I did not get the temperature sensors created (except for the internal) even though I had 2 DS18B20 sensors connected at the time of inclusion. I would expect there to be 2 since the device supports up to 6.

The Z-Wave error seems to indicate sensors, so I'm not sure if that's the cause or not.
I updated my ticket with the info.

[allenc3]

Interesting… where is IN1 and IN2, the two binary inputs? Are they Notification 2 and 7 that show ‘OK’?
What are the 7 Application Status items, what do they do?

[avpman]

I added the device in unsecured mode on the Z-Wave plugin v4.1.1.0. I did not get the temperature sensors created (except for the internal) even though I had 2 DS18B20 sensors connected at the time of inclusion. I would expect there to be 2 since the device supports up to 6.

The Z-Wave error seems to indicate sensors, so I'm not sure if that's the cause or not.
I updated my ticket with the info.

Did you try to re-auditing the node in the Zwave plugin? I've had luck with that. Also, I bought a small Fibaro hub to update the firmware. I know that fixed a discovery problem I was having. Check your Implant against the Fibaro website to see if you have the most current firmware. Mine is V5.2

[rmasonjr]

allenc3 I have no idea. I included it unsecured with the Z-Wave beta. I opened a ticket and Matt wants me to try it with the Z-Wave public release 4.1.0.3
I did that and get the same results. I did enable Z-Wave debugging and am including all that debug info in the ticket.

avpman Thanks - will check and try that next

[avpman]

allenc3 I have no idea. I included it unsecured with the Z-Wave beta. I opened a ticket and Matt wants me to try it with the Z-Wave public release 4.1.0.3
I did that and get the same results. I did enable Z-Wave debugging and am including all that debug info in the ticket.

avpman Thanks - will check and try that next

rmasonjr , PM me if you would like me to send you my hub so you can update your firmware if need be.

[rmasonjr]

Thanks for the offer avpman you're the best!

I did check and it looks like I was lucky enough to get one already on 5.2


I asked Matt to check with Rich. Earlier in this thread, he indicated he had his hands on one.

[avpman]

Thanks for the offer avpman you're the best!

I did check and it looks like I was lucky enough to get one already on 5.2


I asked Matt to check with Rich. Earlier in this thread, he indicated he had his hands on one.

Rich fixed a problem with the Zwave plugin sometime back. It wasn't enumerating all of the features because the Fibaro went beyond the limit hardcoded in the plugin. I believe the original limit was ten features and Rich increased it. PM me if I can be of any more help. I have more than one on hand. You might want to check the Fibaro site to see if there is a more recent firmware than 5.2 - just in case!