New version of Z-Wave Switch and Child Mc:
───────────────────────────────────────────────────
Name Z-Wave Switch and Child Mc
Version 2023-04-06T11:23:43.217297079
───────────────────────────────────────────────────
First of all, thank you Mariano for the Fibaro Smart Implant (FSI) driver. I can finally see the value of the onboard temperature sensor.
I still have one issue. I have two DS18B20 temperature sensors connected to the FSI but I can only get a temperature reading from one of them. When I connect each one individually they each work correctly so I believe the sensors and wiring are correct. When I connect them at the same time to the FSI the driver reports “- ‘C” for the second one.
I’ve also tried to get it to work with and without the 4.7K ohm pull-up resistor on the serial line. There is no change in the behavior.
In order to try and get the driver to recalculate what temperature sensors were attached I went into Settings and checked “6 External Temp Probe”. The log file output at this point is here.
Has anyone been able to get more than DS18B20 temperature sensor to work? If so, could you please give me any ideas on what else I can try. Thanks.
I have two sensors working for several weeks using Smart Implant Beta-4 driver. Try remove Smart Implant and then rejoin Smart Implant when both sensors are connected.
@TapioX, thank you for the suggestion. I removed and reinstalled the device again this morning and, unfortunately, only one external temperature probe is providing a reading.
Do you use a pull-up resistor in your configuration?
I’m not using pull-up resistor.
Both sensors are connected using 1 meter cable.
@Mariano_Colmenarejo
Can you please add the following parameters to
Fibaro Roller Shutter 3
This parameter allows reversing the operation of switches connected to S1 and S2 without changing the wiring.
Available settings:
0 – default (S1 – 1st channel, S2 – 2nd channel)
1 – reversed (S1 – 2nd channel, S2 – 1st channel)
Default setting: 0
Parameter size: 1 [byte]
And also
This parameter allows reversing the operation of Q1 and Q2 without changing the wiring (in case of invalid motor connection) to ensure proper operation.
Available settings:
0 – default (Q1 – 1st channel, Q2 – 2nd channel)
1 – reversed (Q1 – 2nd channel, Q2 – 1st channel)
Default setting: 0
Parameter size: 1 [byte]
Thanks
Hi Mariano
Would it be possible to use this to make the child device(Edge_child) display the power and energy?
Is it possible to make the child device display the energy and power?
I integrate Smartthings with Home Assistant and use the energy and power there.
Thanks
HI @Ped
Sorry, this requires modifying and adding quite a few things to the driver.
I don’t know if in the future I will have time to do it, right now I don’t have it.
The stock Zwave Switch driver has it done
Thanks, appreciate the reply.
Can’t seem to get my Fibaro devices to work properly with the stock drivers.
Your drivers have been a life saver.
Thanks again
@Mariano_Colmenarejo
This pictures sent from a friend of mine:
Looks like the reverse polarity is missing… Can you please check
This profile in your screenshot is for a qubino-flush-shutter, is not for fibaro roller shutter 3
- id: QubinoFlushShutter/AC
deviceLabel: Qubino Window Treatment
manufacturerId: 0x0159
productType: 0x0003
productId: 0x0052
deviceProfileName: qubino-flush-shutter
- id: QubinoFlushShutter/DC
deviceLabel: Qubino Window Treatment
manufacturerId: 0x0159
productType: 0x0003
productId: 0x0053
deviceProfileName: qubino-flush-shutter
name: qubino-flush-shutter
components:
- id: main
capabilities:
- id: windowShade
version: 1
- id: windowShadeLevel
version: 1
- id: windowShadePreset
version: 1
- id: powerMeter
version: 1
- id: energyMeter
version: 1
categories:
- name: Blind
preferences:
- name: "operatingModes"
title: "Operating Modes"
description: "Set the device's operating mode."
preferenceType: enumeration
required: true
definition:
options:
0: "Shutter mode"
1: "Venetian mode"
default: 0
- name: "slatsTurnTime"
title: "Slats turn time"
description: "Specify the time required to rotate the slats 180 degrees. (100 = 1 second)"
required: true
preferenceType: integer
definition:
minimum: 0
maximum: 32767
default: 150
- name: "slatsPosition"
title: "Slats position"
description: "Configuration defines slats return to previously set position after up/down
movement through Z-wave or push-buttons."
preferenceType: enumeration
required: true
definition:
options:
0: "In case of Z-wave control"
1: "Manual operation or limit is reached"
default: 0
- name: "motorUpDownTime"
title: "Motor up down time"
description: "Set the amount of time it takes to completely open or close shutter.
Check manual for more detailed guidance."
required: true
preferenceType: integer
definition:
minimum: 0
maximum: 32767
default: 0
- name: "motorOperationDetection"
title: "Motor operation detection"
description: "Power usage threshold which will be interpreted as motor reaching the limit switch."
required: true
preferenceType: integer
definition:
minimum: 0
maximum: 127
default: 30
- name: "forcedCalibration"
title: "Forced calibration"
description: "After selection '1' option, shutter enters the calibration mode.
When it is finished, completing full cycle - up, down and up, set this parameter value back to first option."
preferenceType: enumeration
required: true
definition:
options:
0: "Calibration finished or not started"
1: "Start calibration process"
default: 0
@Mariano_Colmenarejo
My friend confirm that you were right. He forgot that he is using Qubino module. NOT Fibaro…
As usual thanks for helping
Sorry, I forgot to reply to you.
You have to activate in preferences send scenes, parameter 28 for S1 and parameter 29 for S2 to value 15, which sends all possible actions
When you perform the actions on the ficisco switch, you have to see in the details view that Button-1 shows the scenes for S1 and Button-2 shows the scenes for S2.
The routines are made by putting in the IF part the actions of button-1 or button-2
Thank you. After Smarthings broke their Z-Wave Switch Driver, I was able to use this to get this dual outdoor switch working again.
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!