Yes. I understood that no driver would work… But I was expecting to get the source of the smart implant to be able to change it myself in order to make it work (at least the sensor part) with my version. I’ve not made any edge drivers myself, so not having to start from scratch would be really helpful. I’ll wait for you to release the code. Thanks! Keep it up!
I’ve a working version for mine already only for the contacts. Key points are:
productType: 0x0501
local function process_contact_change_with_component(component, device, cmd)
if cmd.args.value == 255 then
device:emit_component_event(component, capabilities.contactSensor.contact.open())
else
device:emit_component_event(component, capabilities.contactSensor.contact.closed())
end
end
local function get_components(device)
return {
device.profile.components.main,
device.profile.components.second
}
end
local function handle_zwave_contact_change(driver, device, cmd)
local components = get_components(device)
process_contact_change_with_component(components[cmd.src_channel], device, cmd)
end
zwave_handlers = {
[cc.BASIC] = {
[Basic.SET] = handle_zwave_contact_change
}
}
I guess it would be “easy” for me, when you release you FGBS-222 code to make a working copy for the FGBS-001 
. I can live with my ugly (I really like what you did with the presentations) version till then. Thanks!
Hola Alfonso
In this link is the smart Implant Beta-4 code.
There are the handlers of the On-off capabilities, they are not tested or I don’t know if they work when you invert the logic of out-1 and out-2 in preferences, before I used the ones from the default libraries
Your device parameter are different
I don’t have any temperature sensors myself… but I’ll try 
1 Like
(New Version) Edge Driver Z-Wave Switch and Child Mc:
- To facilitate the configuration of parameters and Association groups of the different Zwave devices and because when changing to the Z-Wave Device Config Mc driver to configure them, the routines and scenes that we have made are lost:
- I have integrated the Z-Wave Device Config Mc driver inside the Z-Wave Switch and Child Mc driver as a subdriver
- The subdriver configurator is executed by creating a Child device that will work exactly the same as the Z-Wave Device Config Mc driver, with the Options in preferences for:
- “Device Fingerprint Info”
- “Device Parameters Scan”
- “Device Parameter Configure”
- “Device Association Groups Scan”
- “Device Association Groups Configure”
default: “Device Fingerprints Info”
- The created device will appear in the room where the hub is located with the name “Device Info-Name of the Father device”
-
It is possible that the first time you have to clear the cache of the app to see the profiles of the child device configurator.
-
This allows you to configure device parameters and association groups, test if the device works with the new values without changing the driver and without losing routines or scenes
-
Once the parameters or association groups have been configured, it is convenient to delete the child device to ensure that the real devices work correctly, if they use configuration, association or version report handlers.
-
It is a BETA version, which I have tested with two different types of devices that I have, I would like more tests before replacing the current Mc version.
Please, if you find any error, tell me and I will try to correct it.
───────────────────────────────────────────────────
Name Z-Wave Switch and Child CONFIG
Version 2023-03-20T19:59:26.49339752
───────────────────────────────────────────────────
- To use this driver you only have to make a driver change to the Z-Wave Switch and Child CONFIG version. No setting, routine or scene will be lost.
- If everything works as expected, I will also integrate it into other drivers such as Z-Wave Sensor Mc…
27 mar 2023 Update:
As it seems that there are no bugs reported merge with the Z-Wave Switch and Child Mc and the Z-Wave Switch and Child CONFIG will disappear.
The update will be done automatically in 12 hours maximum
───────────────────────────────────────────────────
Name Z-Wave Switch and Child Mc
Version 2023-03-27T15:26:34.151021779
───────────────────────────────────────────────────
3 Likes
(New Version) Edge Driver Z-Wave Sensor and Child Thermostat Mc:
As in Z-Wave Switch and Child Mc and since no one has reported errors, I have added the optional Child Device for Parameter Configuration and Association Groups subdriver to this driver.
If anyone wants to try it, I don’t have Zwave sensors.
Remember that in battery-powered sensors you have to wake up the devices for them to respond to to configure parameters and association groups configuration
This is the driver version Z-Wave Sensor and Child Thermostat CONFIG:
────────────────────────────────────────────────────────
Name Z-Wave Sensor and Child Thermostat CONFIG
Version 2023-03-23T15:50:09.35770828
────────────────────────────────────────────────────────
1 Like
Hi, Im currently running the beta 4 driver for my smart implant device with 1 external probe.
The driver works fine in ST and shows the value of the external probe in the tile for the device. But in systems integrated with ST it is the internal sensor that are shown / sendt. Could you make the external sensor “primary” ?
Hi @kjelljk
Sorry, that change in component and endpoint mapping would modify all other driver profile settings.
You can create a child device for ext temperature probe 1 with a single tile and use it for routines with third party applications that don’t see the child components.
okay, thanks for replying. What driver works with smart imlant and have option to create child device?
Go to settings and enable preference “Create Virtual Thermostat 1”
The virtual device will appear in the room in which the Hub is located.
It is a virtual thermostat, but if you leave it Off it only synchronizes the temperature of the external temperature probe 1
1 Like
Hi,
I have a problem with Fibaro Switch Single module.
The status updated OK when using Smartthings App, BUT , does not chaged when toggling from the mechanical switch. I can see messages in CLI when logging this driver. The following is turn on and turn off log via mechanical switch.
Please advise… @dotan_shai helped me
I replied this via PM to @dotan_shai
I need you to confirm that the switch cable is connected to the S1 input of the physical switch.
The stock driver and mine expect a source endpoint of 0 or nil and the device is sending source endpoint=1
local function switch_binary_report_handler(self, device, cmd)
if cmd.src_channel == nil or cmd.src_channel == 0 then
SwitchDefaults.zwave_handlers[cc.SWITCH_BINARY][SwitchBinary.REPORT](self, device, cmd)
end
end
The S2 input is used to send scenes and therefore is not allowed by code to emit a switch state change.
If you confirm it, I will modify the code of my driver since these changes would affect more users.
On the other hand, if it is well connected, you should also report it to smsrtthings so that they can fix the stock driver.
@Mariano_Colmenarejo @omergranot88
I’ve got the same behaviour w this device and driver. As it sits in a remote location I’m not able to use the CLI to make a log at the moment. It works well using the app and routines, but not using the physical switch. (The S1 is connected)
I am going to correct the code and if it works well you should notify smartthing so they can fix the stock driver
@S.F.B @omergranot88 update
Modified in this driver version:
- Switch binary report
- Meter report for Energy and power events
- Central scene notification for S1 scenes to button, but not will work for button1, S1 and Button2, S2 scenes it not will work due to profile need add a button1 and button2 components, missing
In preferences you can configure S1 and S2 send scenes but it not will works until button1 and button2 added to profile.
I can’t debug this profile change and therefore I leave it without fixing
Need this profile modification
You can install immediately this driver version with CLI with command:
smartthings edge:drivers:install
───────────────────────────────────────────────────
Name Z-Wave Switch and Child Mc
Version 2023-04-03T19:58:02.016897363
───────────────────────────────────────────────────
1 Like
2 posts were split to a new topic: [Edge drivers] Issue with stock Z-Wave Switch driver (Fibaro single switch)
Hi @Mariano_Colmenarejo
Sorry for the delay but i had no time before.
For me i need an edge driver button because is more like the keyfob but with only 2 buttons.
however when I look at the devices compatible with the button edge drivers I see the fibaro button and the keyfob but not the fibaro walli controler.
can you add it in your edge drivers or i have not yet understood how smartthings works
Thank you
Just wanted to say thank you for the Smart Implant driver, Mariano. My gate is now working again!
New version of Z-Wave Switch and Child Mc:
- Added to profile of Fibaro single switch FGS- 213, button1 and button2 components.
- Modified code to execute scenes, sending events to button1 for S1 scenes and to button2 for S2 scenes if are activated wit parameters 28 or/and 29
───────────────────────────────────────────────────
Name Z-Wave Switch and Child Mc
Version 2023-04-06T11:23:43.217297079
───────────────────────────────────────────────────