[RELEASE] Fibaro Smart Implant FGBS-222

⚙️ Custom Apps and Drivers Custom Drivers
,
509

Per this link [RELEASE] Fibaro Smart Implant FGBS-222 - #487 by dnickel

There has been an incompatibility on beta testing under JS so I have been running the built-in driver until the official release when you were going to chase any platform issues.
Good luck!

2 Likes
510

I updated to 2.4.1.153. I don't get any errors when line 443 is executed (temperature conversion, tried default, deg C and deg F)

511

BTW, I can only test the internal temp. sensor, maybe the problem happens for external ones or for ZWJS?

512

Correct, I tried it and couldn’t get it working. I have a vague recollection that whoever wrote the HE driver skipped electronics circuit design 101 class and implemented “normally open” and “normally closed” inverted. But it was late, and I decided to revert to what I knew worked.

513

This is a long shot but if you or someone wants to try the following, it might help (enable the debug log).

Change the following lines (from line 441...)

		case [7,8,9,10,11,12,13]:
			(finalVal,units) = convertTemperature(cmd)
			finalVal = finalVal.toFloat() + settings["${"sensorOffset" + (endpoint-7).toString()}"]
			finalVal = (Math.round(finalVal* 10.0)/10.0).toFloat()
			target?.sendEvent(name: "temperature", value: finalVal, unit: units, descriptionText:"${target} temperature is ${finalVal}${units}" )
			break

to

		case [7,8,9,10,11,12,13]:
			(finalVal2,units) = convertTemperature(cmd)
			logDebug "finalVal2: ${finalVal2}"
			finalVal3 = finalVal2.toFloat() + settings["${"sensorOffset" + (endpoint-7).toString()}"]
			finalVal4 = (Math.round(finalVal3* 10.0)/10.0).toFloat()
			target?.sendEvent(name: "temperature", value: finalVal4, unit: units, descriptionText:"${target} temperature is ${finalVal4}${units}" )
			break
1 Like
514

I never bothered checking the temp sensor, my main issue was that the relays didn’t work in ZWJS. The digital sensors however worked fine for me.

515

Yea, the two problems are probably unrelated.

1 Like
516

I am using external DS18S20 probes and ZWJS.

517

I thought so...this post was meant to try to pinpoint the problem you describe with line 443.

518

Is there any update for getting this to work with? Z-Wave JS? I'm using it as a garage door controller and when I move it over to the JS it doesn't work. Just curious if there's any update on this or do we have to use the native drivers? Thank you for your time.

519

Same question here... I think I saw in this thread that digital outputs aren't working with thia driver and Zwave JS. Is that true/still the case?

520

It is the case for me, and the Official driver has the same issue. :frowning:

1 Like
521

Same

522

@christi999 I hadnt tested the OEM Hubitat driver on 2.4.3.x with ZWJS and it is now working with the Smart Implant, it's just your excellent community driver that isnt.

All I get are this odd message in the logs when I attempt to trigger a relay:
"Child on @ ep 5"

SCR-20250927-iohz
SCR-20250927-iohz2912×250 53.5 KB

523

I am still stuck with a C7 so I have no way to test ZWJS. I don't mind making a new release if someone has the fix.

1 Like
524

TBH, I don’t actually know what the root cause is, so I can’t advise what needs to be fixed.

525

I had nothing but issues with the smart implant. Absolute garbage in my opinion.

Swaped to konnected/wifi years ago.

No issues.

1 Like
526

TBH I find the smart implant to be very reliable under legacy ZW. I’m not s big fan of using wifi based automation products, I find them unreliable despite having a high end mesh system.

I’d switch to a Shelly zwave product if they had one with inputs and relay outputs that ran on DC power.

527

Just the opposite here. I used konnected for years and after changing to the new ESP home firmware my logs were full of warnings and I was told it was OK. Smart implant has been working perfect now for 7 months on legacy Zwave.

2 Likes
528

Same for me, I've found them reliable. I started with two implants - one controlling/monitoring my beds TV lift and one controlling/monitoring my alarms set status. I've now got them installed in about five of my alarms PIRs to use for motion lighting and they're working well.

I've had one continual issue with the one implant I have included with S2 Authenticated on my alarm system. Whenever the hub has had an update or reboot, that implant always fails to respond to its first command. I've a 'Goodnight' rule that performs multiple actions, part-setting the alarm being one of them. Following a reboot when I hit trigger that Goodnight rule, the implants output does not activate when it should (after that first failure it works perfectly until the next reboot)