Great to have a driver available for the Fibaro Smart Implant thank you. I installed mine yesterday with the “Smart Implant Beta-4 driver” and a single external temperature sensor, but will mainly be using the outputs. The outputs both seem to be able to be switched on remotely, but when trying to switch them off, I just get a spinning button in the SmartThings app and it eventually says there is a network error. If I manually switch them off on the device whilst the app is requesting them to switch off, the app recognises that they have switched off and stops spinning the button. Therefore I don’t think it really is a network error, just that the code to activate the turn off isn’t successfully creating the action. Any thoughts @Mariano_Colmenarejo ???
Hi @tstrafford
The operation of the out switches depends on the configuration parameters of the device.
The parameters shown in preference settings after installation are the default values, but the device may have other values saved from its previous use.
You can do a factory reset to restore the default values or modify the parameters manually.
Other users could help you with this, I don’t have this device, but if you want to send me the CLI logs of what doesn’t work I’ll look at it.
This is the manual, in case you don’t have it
This part is important to allow out1 and out2 local or zwave control
@Mariano_Colmenarejo I have same problem
Here is error messages from driver log:
2023-05-15T16:38:10.672429581+00:00 TRACE Fibaro Smart Implant BETA-4 Received event with handler capability
2023-05-15T16:38:10.678396914+00:00 INFO Fibaro Smart Implant BETA-4 <ZwaveDevice: 4cc2b52b-dd4b-40cf-b817-f117f0357d36 [0B] (Fibaro Smart Implant)> received command: {“args”:{},“capability”:“switch”,“command”:“off”,“component”:“out1”,“positional_args”:{}}
2023-05-15T16:38:10.681994581+00:00 TRACE Fibaro Smart Implant BETA-4 Found CapabilityCommandDispatcher handler in zwave_smart_implant
2023-05-15T16:38:10.689806581+00:00 PRINT Fibaro Smart Implant BETA-4 <<<<<<< switch_off_handler >>>>>>
2023-05-15T16:38:10.690639247+00:00 TRACE Fibaro Smart Implant BETA-4 SWITCH_BINARY supported.
2023-05-15T16:38:10.691854914+00:00 ERROR Fibaro Smart Implant BETA-4 Fibaro Smart Implant thread encountered error: [string “st/dispatcher.lua”]:233: Error encountered while processing event for <ZwaveDevice: 4cc2b52b-dd4b-40cf-b817-f117f0357d36 [0B] (Fibaro Smart Implant)>:
arg1: table: 0x1eb9500
[string “st/utils.lua”]:188: bad argument #2 to ‘pack’ (number expected, got nil)
2023-05-15T16:39:07.708082941+00:00 TRACE Fibaro Smart Implant BETA-4 Received event with handler capability
2023-05-15T16:39:07.718977275+00:00 INFO Fibaro Smart Implant BETA-4 <ZwaveDevice: 4cc2b52b-dd4b-40cf-b817-f117f0357d36 [0B] (Fibaro Smart Implant)> received command: {“args”:{},“capability”:“switch”,“command”:“off”,“component”:“out2”,“positional_args”:{}}
2023-05-15T16:39:07.720354941+00:00 TRACE Fibaro Smart Implant BETA-4 Found CapabilityCommandDispatcher handler in zwave_smart_implant
2023-05-15T16:39:07.721589275+00:00 PRINT Fibaro Smart Implant BETA-4 <<<<<<< switch_off_handler >>>>>>
2023-05-15T16:39:07.722776275+00:00 TRACE Fibaro Smart Implant BETA-4 SWITCH_BINARY supported.
2023-05-15T16:39:07.723969275+00:00 ERROR Fibaro Smart Implant BETA-4 Fibaro Smart Implant thread encountered error: [string “st/dispatcher.lua”]:233: Error encountered while processing event for <ZwaveDevice: 4cc2b52b-dd4b-40cf-b817-f117f0357d36 [0B] (Fibaro Smart Implant)>:
arg1: table: 0x1e447f0
[string “st/utils.lua”]:188: bad argument #2 to ‘pack’ (number expected, got nil)
Earlier driver has operated normally. I have only used temperature measurements.
Sorry, This driver version fix the problem. it was a copy and paste error and due to I have not the device to debug driver
───────────────────────────────────────────────────
Name Fibaro Smart Implant BETA-4
Package Key zwave-fibaro-smart-implant-4
Version 2023-05-15T16:49:27.780169641
───────────────────────────────────────────────────
Now using this driver version outputs control from App is operating normally.
Many thanks again for the excellent work!
Mariano,
Great support for temperature sensors, and digital inputs, outputs.
Can BETA-4 driver also support Analog inputs (0-10V) ? This would enable to support wind sensor and weight sensor as well.
Thanks for the great work on this driver!
This part has not been implemented since it would be necessary to add profiles and specific code for the capabilities that you want to show in the App. Doing that without having the device and sensors to debug is complicated.
The code developed so far is in this github repository, if someone wants to implement it they can use it without problem
Hello Mariano,
Coding the driver is beyond my capabilities, but I can send you a test device. Just let me know.
Would be more than sufficient to show the voltage figure for an analog input only. That would be similar how the old device handler solved this.
Try this driver version BETA-5
───────────────────────────────────────────────────
Driver Id 009ff93e-18e8-49fc-bf05-c379c6530d1b
Name Fibaro Smart Implant BETA-5
Package Key zwave-fibaro-smart-implant-5
Version 2023-05-19T20:28:04.662658254
───────────────────────────────────────────────────
- Added in preferences a new profile option : “9” : “2 Analog Inputs + 2 Switch”
options:
"0" : "Double Switch"
"1" : "1 External Temp Probe"
"2" : "2 External Temp Probe"
"3" : "3 External Temp Probe"
"4" : "4 External Temp Probe"
"5" : "5 External Temp Probe"
"6" : "6 External Temp Probe"
"7" : "2 Contact Sensors + 2 Switch"
"8" : "2 Motion Sensors + 2 Switch"
"9" : "2 Analog Inputs + 2 Switch"
default: "9"
-
The profile show VoltageMeasurement capability for Analog input-1, Analog Input-2, limited range 0v-10v and Out-1, Out-2 switches
-
You can use preference option for multi-Tile or single Tile.
In Single Tile the information now is internal temperature, in the future it could be changed to show Analog-1 or Analog-2 if you need it with a custom VID.
Remember to change parameters 20 and 21 to values 4 or 5, depending on the analog device you use on inputs 1 and 2
Try it and tell me if works
Good afternoon Mariano;
I’ve read through this list of post concerning the FGBS-222 and still have an issue and a question. First off, like everyone else, thank you for your efforts! I’m sure it’s time consuming so these are no rush. I use the smart implant to monitor a millivolt pool heater. The inputs are connected to relay contacts that monitor burner status (Pilot on, main burner on) and one output is a burner shutoff output, the other a light. I also monitor water temperature with the external temperature sensor and have a routine to shut off the heater if a high limit is exceeded. The issue, using profile 7 the outputs work fine, the inputs will not read data (null reading) at all. In settings I have the inputs set up as Normally open alarms and disconnected from the outputs. I was wondering if you might have any suggestions.
The obvious question, is there a way to combine profiles to use an external temperature sensor along with the inputs and outputs?
As already stated, no rush but wanted to at least inquire.
Thanks in advance!
Ed
Hi @edschaefer
The user who tested the contact sensor profiles sent me CLI logs and the open and close status was emitted perfectly.
2023-03-09T01:39:03.621385031+00:00 INFO Fibaro Smart Implant BETA-4 <ZwaveDevice: 280cbc3b-5556-4f7b-8083-b70f34e335bb [5D] (Fibaro Smart Implant)> received Z-Wave command: {args={alarm_level=0, alarm_type=0, event=“STATE_IDLE”, event_parameter=“”, notification_status=“ON”, notification_type=“HOME_SECURITY”, v1_alarm_level=0, v1_alarm_type=0, z_wave_alarm_event=0, z_wave_alarm_status=“ON”, z_wave_alarm_type=“BURGLAR”, zensor_net_source_node_id=0}, cmd_class=“NOTIFICATION”, cmd_id=“REPORT”, dst_channels={0}, encap=“NONE”, payload=“\x00\x00\x00\xFF\x07\x00\x00”, src_channel=2, version=3}
2023-03-09T01:39:03.635101531+00:00 TRACE Fibaro Smart Implant BETA-4 Found ZwaveDispatcher handler in zwave_smart_implant
2023-03-09T01:39:03.635635448+00:00 TRACE Fibaro Smart Implant BETA-4 Found ZwaveDispatcher handler in zwave_smart_implant
2023-03-09T01:39:03.636316073+00:00 INFO Fibaro Smart Implant BETA-4 <ZwaveDevice: 280cbc3b-5556-4f7b-8083-b70f34e335bb [5D] (Fibaro Smart Implant)> emitting event: {“attribute_id”:“contact”,“capability_id”:“contactSensor”,“component_id”:“in2”,“state”:{“value”:“closed”}}
2023-03-09T01:39:03.776142406+00:00 INFO Fibaro Smart Implant BETA-4 <ZwaveDevice: 280cbc3b-5556-4f7b-8083-b70f34e335bb [5D] (Fibaro Smart Implant)> received Z-Wave command: {args={alarm_level=0, alarm_type=0, event=“INTRUSION”, event_parameter=“”, notification_status=“ON”, notification_type=“HOME_SECURITY”, v1_alarm_level=0, v1_alarm_type=0, z_wave_alarm_event=“INTRUSION”, z_wave_alarm_status=“ON”, z_wave_alarm_type=“BURGLAR”, zensor_net_source_node_id=0}, cmd_class=“NOTIFICATION”, cmd_id=“REPORT”, dst_channels={0}, encap=“NONE”, payload=“\x00\x00\x00\xFF\x07\x02\x00”, src_channel=2, version=3}
2023-03-09T01:39:03.786513948+00:00 TRACE Fibaro Smart Implant BETA-4 Found ZwaveDispatcher handler in zwave_smart_implant
2023-03-09T01:39:03.786961948+00:00 TRACE Fibaro Smart Implant BETA-4 Found ZwaveDispatcher handler in zwave_smart_implant
2023-03-09T01:39:03.787642198+00:00 INFO Fibaro Smart Implant BETA-4 <ZwaveDevice: 280cbc3b-5556-4f7b-8083-b70f34e335bb [5D] (Fibaro Smart Implant)> emitting event: {“attribute_id”:“contact”,“capability_id”:“contactSensor”,“component_id”:“in2”,“state”:{“value”:“open”}}
Are inputs In1 and In2 connected correctly with ground or open?
If you send me the CLI logs with the inputs to open and close (GND) I can see what happens
I can add a new profile with contact sensors inputs, external temperature and outputs if you help me debug it.
There are users who ask to add new things and then do not comment again if it works or not
They worked perfectly with the old DTH, I actually have a second one wired to other heater status contacts still using a DTH that is still working just fine. I’ll send logs later this evening or in the morning.
I’ll be happy to help and provide feedback, that would be the very least I could do!! I don’t have any programming experience but do have a technical background.
Thanks for the quick reply
Ed
@Mariano_Colmenarejo Hello Mariano, I have a problem with the device or the edge. I have 3 fibaros fgs-222 dual switch where it is added, but it does not separate the two channels of use, it also happens that when using the switch the state in the app does not change. I also have several philio pan 06 and pan 04 that have the same thing, they use your edge driver, but it doesn’t separate the channels. And it’s a double switch. I am sending you the information on pan-06 as an annex. If you can give me an answer, I’d appreciate it.
I don’t know what driver your devices are using.
The philio that tells me is not included in my driver, there is only the 013C/0001/0011, which is a single plug metering.
It may be pairing with driver as a generic binary switch device.
As for the fibaro double swicth, I don’t know what fingerprints they have.
I have two that work perfectly with my Zwave Switch and child Mc controller
@Mariano_Colmenarejo, For the fibaro I use the z-wave switch and chil mc, but it doesn’t create the children. And it also doesn’t update the state with when using the switch. That’s why I’m asking. Then with the Pan06 and Pan04, the problem is the same, it creates only 1 switch, when the devices are 2 gang.
As I was saying, I don’t know what fingerprints your fibaro devices have.
The driver does not understand the fgs-222 commercial model, it only understands fingerprints and I need them to know what to look for in the driver.
If you send me the CLI logs of when you press on and off in the app, then I could see what happens.
The child device is optionally created from preferences and appears in the room where the hub is.
For the other devices, the PAN 06, as I told you, is not included in the driver and could paired by the generic command class as a single switch and therefore the driver does not know that it is a double switch.
I don’t know Pan04 fingerprints. If you send me all the information I can try to add them to the driver to see if they work.
I couldn’t get the analog inputs to show voltages. I have them setup as analog input with no pull ups.
I don’t have a device to test, if you send me the logs with the CLI I can try to look at it.
Have you configured parameters 63 and 64 to configure the reports of analog 1 and 2?
As the driver uses the handler defaults to handle the voltageMeasurement capability then it might be necessary that after selecting the correct profile “2 Analog Inputs + 2 Switch” make a driver change to Zwave Thing Mc and then change back to this driver or make a hub reboot. This will run the lifecycle init and register the voltageMeasurement capability to run the handler defualts.
To avoid this you may have to embed the code for the default handlers in the driver.
Hi @edschaefer
This version has new profile smart-implant-temp-two-contact-switch with one external temp probe and two contact sensors and two switches
───────────────────────────────────────────────────
Name Fibaro Smart Implant BETA-5
Version 2023-05-25T19:36:17.125365365
───────────────────────────────────────────────────
options:
"0" : "Double Switch"
"1" : "1 External Temp Probe"
"2" : "2 External Temp Probe"
"3" : "3 External Temp Probe"
"4" : "4 External Temp Probe"
"5" : "5 External Temp Probe"
"6" : "6 External Temp Probe"
"7" : "2 Contact Sensors + 2 Switch"
"8" : "2 Motion Sensors + 2 Switch"
"9" : "2 Analog Inputs + 2 Switch"
"10" : "Ext Temp + 2 Contact + 2 Switch"
default: "10"
@TapioX tested open close input 1 and ext temperature probe, thanks
Here’s the log. It seems that the device is sending reports, but the GUI on the iOS smartthings app doesn’t show it. It only shows -V
2023-05-25T19:18:50.739724980+00:00 DEBUG Fibaro Smart Implant BETA-5 Fibaro Smart Implant device thread event handled
2023-05-25T19:19:30.465088666+00:00 TRACE Fibaro Smart Implant BETA-5 Received event with handler unnamed
2023-05-25T19:19:30.466272332+00:00 INFO Fibaro Smart Implant BETA-5 <ZwaveDevice: 57b32232-7f63-4d9a-9f39-550a51c2cd31 [3B] (Fibaro Smart Implant)> received Z-Wave command: {args={precision=2, scale=“VOLTS”, sensor_type=“VOLTAGE”, sensor_value=2.98, size=2}, cmd_class=“SENSOR_MULTILEVEL”, cmd_id=“REPORT”, dst_channels={0}, encap=“S2_AUTH”, payload=“\x0F\x42\x01\x2A”, src_channel=3, version=1}
2023-05-25T19:19:30.509321332+00:00 TRACE Fibaro Smart Implant BETA-5 Found ZwaveDispatcher handler in zwave_smart_implant
2023-05-25T19:19:30.569981999+00:00 PRINT Fibaro Smart Implant BETA-5 << Temperature_report_handler >>
2023-05-25T19:19:30.570943666+00:00 DEBUG Fibaro Smart Implant BETA-5 Fibaro Smart Implant device thread event handled
2023-05-25T19:20:00.451332680+00:00 TRACE Fibaro Smart Implant BETA-5 Received event with handler unnamed
2023-05-25T19:20:00.452535347+00:00 INFO Fibaro Smart Implant BETA-5 <ZwaveDevice: 57b32232-7f63-4d9a-9f39-550a51c2cd31 [3B] (Fibaro Smart Implant)> received Z-Wave command: {args={precision=2, scale=“VOLTS”, sensor_type=“VOLTAGE”, sensor_value=0.07, size=2}, cmd_class=“SENSOR_MULTILEVEL”, cmd_id=“REPORT”, dst_channels={0}, encap=“S2_AUTH”, payload=“\x0F\x42\x00\x07”, src_channel=3, version=1}
2023-05-25T19:20:00.479248347+00:00 TRACE Fibaro Smart Implant BETA-5 Found ZwaveDispatcher handler in zwave_smart_implant
2023-05-25T19:20:00.503491347+00:00 PRINT Fibaro Smart Implant BETA-5 << Temperature_report_handler >>
2023-05-25T19:20:00.504775347+00:00 DEBUG Fibaro Smart Implant BETA-5 Fibaro Smart Implant device thread event handled