Hola Mariano, lamento la insistencia pero el driver no refresca el perfil cuando seleccionas “double switch”
Todos los profiles funcionan correctamente e impactan casi instantáneamente en mi caso.
En cambio cuando selecciono DOUBLE SWITCH, siempre conserva el ultimo profile antes del cambio.
SIN CAMBIOS 
Saludos!
Hola Matias
I think it is because that profile has a preference to use a simple or multiple mosaic and as in the rest of the profiles there is not that preference sends a null value and the change of profile is not performed.
Try this version that must solve it, change to the profile with simple mosaic and then you can change to a multiple mosaic profile if you need it.
I’m losing freshness, I need a break 
Saludos
───────────────────────────────────────────────────
Name Fibaro Smart Implant BETA-3
Version 2023-02-28T22:18:37.924708702
───────────────────────────────────────────────────
This driver version is not updated automatically to my hub.
I also used CLI command smartthings edge:drivers:install but I didn’t get this driver version to my hub.
My hub is still using Fibaro Smart Implant BETA-3 driver
version 2023-02-27T20:11:35.24229972
I used again CLI command smartthings edge:drivers:install and now this latest driver version is installed to my hub.
I have taken time to dedicate to the Fibaro RGBW Controller that an user gave me, thank you!
I’ve made a complete new diver.
Changes and features:
As this device has parameters settings to adjust the transition times between colors or level or on and off, if a transition time with more than 8 seconds is set, it could cause updating problems of the correct states since the device only informs when it is interrogated, that it is either normal or when the transition to new color, level or on or off ends.
The minimum time to GET the device states is 2 sec according with constants.DEFAULT_POST_DIMMING_DELAY
When the device transition time is greater than 8 sec, then the driver interrogates the device and updates states every 8 sec until it reaches the end transition.
In the App, the status can take up to 8 seconds to update, to avoid possible inconsistent status changes.
If the details view is open, the message “A network or server error has occurred. Please try again later”. may also appear
At the end of transition time execution, the value of the final states is updated, but if intermediate commands are carried out, there may be errors and they may not coincide with reality until final transition.
I didn’t want to limit these settings in preferences, in case someone needs slow power-up and shutdown times, but I have put a warning that there may be errors.
The maximum time to interrogate the status of the commands sent is 8 seconds (constants.DEFAULT_POST_DIMMING_DELAY + 6 sec delay calculated with preferences settings), therefore I recommend not to exceed those 6 seconds of transition times in the device configuration.
The update to the new version will be done manually since capabilities disappear and others are added, which may affect routines that users have active.
The current version of Z-Wave Bulb Mc is renamed Z-Wave Bulb Mc-(OLD) and the new one will be Z-Wave Bulb Mc.
Each user will be able to make the change when they want to or not and will continue using their current version and will remain in their hub until they delete it.
I have done many tests, but if someone detects any error, please tell me so I can try to correct it.
New driver version:
───────────────────────────────────────────────────
Driver Id 0ec75098-cf62-47c5-a23c-5bf7fb1f2dd6
Name Z-Wave Bulb Mc
Package Key zwave-bulb-v2
Version 2023-03-05T19:27:53.67672184
───────────────────────────────────────────────────
Hi @John_K
This driver version merged with TEST driver for monoprice dual relay with firmware 13.7
Perform a driver change to see if works fine too
@Cleon @kwichma @greenzkool monoprice dual relay firmware version 17.02 must work fine too
───────────────────────────────────────────────────
Name Z-Wave Switch and Child Mc
Version 2023-03-05T14:46:12.374397448
───────────────────────────────────────────────────
Hi @matiasjg
If you or someone sends me some logs to see the commands that the device sends when the IN1 and IN2 inputs close and open, I can try to make a profile for contact sensors for the inputs.
Hi
Some log
Input 1 - operating mode 0 – Normally closed alarm input (Notification)
2023-03-06T16:53:30.480073987+00:00 TRACE Fibaro Smart Implant BETA-3 Received event with handler device_lifecycle
2023-03-06T16:53:30.492067321+00:00 INFO Fibaro Smart Implant BETA-3 <ZwaveDevice: 4cc2b52b-dd4b-40cf-b817-f117f0357d36 [0B] (Fibaro Smart Implant)> received lifecycle event: infoChanged
2023-03-06T16:53:30.582264987+00:00 TRACE Fibaro Smart Implant BETA-3 Z-Wave command(9e031095) queued for radio transmission: CC:Configuration, CID:0x04
2023-03-06T16:53:30.583324987+00:00 TRACE Fibaro Smart Implant BETA-3 Found DeviceLifecycleDispatcher handler in zwave_smart_implant
2023-03-06T16:53:30.584603321+00:00 PRINT Fibaro Smart Implant BETA-3 <<<< parameter_number = 20
2023-03-06T16:53:30.585783654+00:00 PRINT Fibaro Smart Implant BETA-3 <<<< size = 1
2023-03-06T16:53:30.586936987+00:00 PRINT Fibaro Smart Implant BETA-3 <<<< configuration_value = 0
2023-03-06T16:53:30.588087321+00:00 INFO Fibaro Smart Implant BETA-3 <ZwaveDevice: 4cc2b52b-dd4b-40cf-b817-f117f0357d36 [0B] (Fibaro Smart Implant)> sending Z-Wave command: {args={configuration_value=0, default=false, parameter_number=20, size=1}, cmd_class=“CONFIGURATION”, cmd_id=“SET”, dst_channels={}, encap=“AUTO”, payload=“\x14\x01\x00”, src_channel=0, version=1}
2023-03-06T16:53:30.618001321+00:00 TRACE Fibaro Smart Implant BETA-3 Found CapabilityCommandDispatcher handler in zwave_smart_implant
2023-03-06T16:53:30.716852321+00:00 TRACE Fibaro Smart Implant BETA-3 Z-Wave command(f9e97510) queued for radio transmission: CC:Switch Binary, CID:0x02
2023-03-06T16:53:30.721294654+00:00 INFO Fibaro Smart Implant BETA-3 <ZwaveDevice: 4cc2b52b-dd4b-40cf-b817-f117f0357d36 [0B] (Fibaro Smart Implant)> sending Z-Wave command: {args={}, cmd_class=“SWITCH_BINARY”, cmd_id=“GET”, dst_channels={6}, encap=“AUTO”, payload=“”, src_channel=0, version=1}
2023-03-06T16:53:30.733588987+00:00 TRACE Fibaro Smart Implant BETA-3 Z-Wave command(316e0732) queued for radio transmission: CC:Switch Binary, CID:0x02
2023-03-06T16:53:30.742182321+00:00 INFO Fibaro Smart Implant BETA-3 <ZwaveDevice: 4cc2b52b-dd4b-40cf-b817-f117f0357d36 [0B] (Fibaro Smart Implant)> sending Z-Wave command: {args={}, cmd_class=“SWITCH_BINARY”, cmd_id=“GET”, dst_channels={5}, encap=“AUTO”, payload=“”, src_channel=0, version=1}
2023-03-06T16:53:30.745372987+00:00 TRACE Fibaro Smart Implant BETA-3 Z-Wave command(574b68b7) queued for radio transmission: CC:Sensor Multi-level, CID:0x04
2023-03-06T16:53:30.746802321+00:00 INFO Fibaro Smart Implant BETA-3 <ZwaveDevice: 4cc2b52b-dd4b-40cf-b817-f117f0357d36 [0B] (Fibaro Smart Implant)> sending Z-Wave command: {args={scale=0, sensor_type=“TEMPERATURE”}, cmd_class=“SENSOR_MULTILEVEL”, cmd_id=“GET”, dst_channels={7}, encap=“AUTO”, payload=“\x01\x00”, src_channel=0, version=5}
2023-03-06T16:53:30.759748321+00:00 TRACE Fibaro Smart Implant BETA-3 Z-Wave command(c9d4af14) queued for radio transmission: CC:Sensor Multi-level, CID:0x04
2023-03-06T16:53:30.760653987+00:00 INFO Fibaro Smart Implant BETA-3 <ZwaveDevice: 4cc2b52b-dd4b-40cf-b817-f117f0357d36 [0B] (Fibaro Smart Implant)> sending Z-Wave command: {args={scale=0, sensor_type=“TEMPERATURE”}, cmd_class=“SENSOR_MULTILEVEL”, cmd_id=“GET”, dst_channels={8}, encap=“AUTO”, payload=“\x01\x00”, src_channel=0, version=5}
2023-03-06T16:53:30.774770987+00:00 TRACE Fibaro Smart Implant BETA-3 Z-Wave command(e97e3400) queued for radio transmission: CC:Sensor Multi-level, CID:0x04
2023-03-06T16:53:30.778982987+00:00 INFO Fibaro Smart Implant BETA-3 <ZwaveDevice: 4cc2b52b-dd4b-40cf-b817-f117f0357d36 [0B] (Fibaro Smart Implant)> sending Z-Wave command: {args={scale=0, sensor_type=“TEMPERATURE”}, cmd_class=“SENSOR_MULTILEVEL”, cmd_id=“GET”, dst_channels={9}, encap=“AUTO”, payload=“\x01\x00”, src_channel=0, version=5}
2023-03-06T16:53:30.791973654+00:00 DEBUG Fibaro Smart Implant BETA-3 Fibaro Smart Implant device thread event handled
2023-03-06T16:53:30.809142987+00:00 TRACE Fibaro Smart Implant BETA-3 Z-Wave command(9e031095) transmit status: TRANSMIT_COMPLETE_OK
2023-03-06T16:53:30.872082987+00:00 TRACE Fibaro Smart Implant BETA-3 Received event with handler unnamed
2023-03-06T16:53:30.879124321+00:00 INFO Fibaro Smart Implant BETA-3 <ZwaveDevice: 4cc2b52b-dd4b-40cf-b817-f117f0357d36 [0B] (Fibaro Smart Implant)> received Z-Wave command: {args={value=“ON_ENABLE”}, cmd_class=“SWITCH_BINARY”, cmd_id=“REPORT”, dst_channels={0}, encap=“S2_AUTH”, payload=“\xFF”, src_channel=5, version=1}
2023-03-06T16:53:30.902765987+00:00 TRACE Fibaro Smart Implant BETA-3 Found ZwaveDispatcher handler in zwave_smart_implant
2023-03-06T16:53:30.903587321+00:00 INFO Fibaro Smart Implant BETA-3 <ZwaveDevice: 4cc2b52b-dd4b-40cf-b817-f117f0357d36 [0B] (Fibaro Smart Implant)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“out1”,“state”:{“value”:“on”}}
2023-03-06T16:53:30.907076654+00:00 DEBUG Fibaro Smart Implant BETA-3 Fibaro Smart Implant device thread event handled
2023-03-06T16:53:30.965237654+00:00 TRACE Fibaro Smart Implant BETA-3 Z-Wave command(f9e97510) transmit status: TRANSMIT_COMPLETE_OK
2023-03-06T16:53:31.006220987+00:00 TRACE Fibaro Smart Implant BETA-3 Received event with handler unnamed
2023-03-06T16:53:31.007059987+00:00 INFO Fibaro Smart Implant BETA-3 <ZwaveDevice: 4cc2b52b-dd4b-40cf-b817-f117f0357d36 [0B] (Fibaro Smart Implant)> received Z-Wave command: {args={value=“OFF_DISABLE”}, cmd_class=“SWITCH_BINARY”, cmd_id=“REPORT”, dst_channels={0}, encap=“S2_AUTH”, payload=“\x00”, src_channel=6, version=1}
2023-03-06T16:53:31.059594987+00:00 TRACE Fibaro Smart Implant BETA-3 Found ZwaveDispatcher handler in zwave_smart_implant
2023-03-06T16:53:31.060616321+00:00 INFO Fibaro Smart Implant BETA-3 <ZwaveDevice: 4cc2b52b-dd4b-40cf-b817-f117f0357d36 [0B] (Fibaro Smart Implant)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“out2”,“state”:{“value”:“off”}}
2023-03-06T16:53:31.064424321+00:00 DEBUG Fibaro Smart Implant BETA-3 Fibaro Smart Implant device thread event handled
2023-03-06T16:53:31.127250654+00:00 TRACE Fibaro Smart Implant BETA-3 Z-Wave command(316e0732) transmit status: TRANSMIT_COMPLETE_OK
2023-03-06T16:53:31.154531987+00:00 TRACE Fibaro Smart Implant BETA-3 Received event with handler unnamed
2023-03-06T16:53:31.159232321+00:00 INFO Fibaro Smart Implant BETA-3 <ZwaveDevice: 4cc2b52b-dd4b-40cf-b817-f117f0357d36 [0B] (Fibaro Smart Implant)> received Z-Wave command: {args={value=“ON_ENABLE”}, cmd_class=“SWITCH_BINARY”, cmd_id=“REPORT”, dst_channels={0}, encap=“S2_AUTH”, payload=“\xFF”, src_channel=5, version=1}
2023-03-06T16:53:31.173188987+00:00 TRACE Fibaro Smart Implant BETA-3 Found ZwaveDispatcher handler in zwave_smart_implant
2023-03-06T16:53:31.178474321+00:00 INFO Fibaro Smart Implant BETA-3 <ZwaveDevice: 4cc2b52b-dd4b-40cf-b817-f117f0357d36 [0B] (Fibaro Smart Implant)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“out1”,“state”:{“value”:“on”}}
2023-03-06T16:53:31.244788654+00:00 DEBUG Fibaro Smart Implant BETA-3 Fibaro Smart Implant device thread event handled
2023-03-06T16:53:31.257290654+00:00 TRACE Fibaro Smart Implant BETA-3 Z-Wave command(574b68b7) transmit status: TRANSMIT_COMPLETE_OK
2023-03-06T16:53:31.282339321+00:00 TRACE Fibaro Smart Implant BETA-3 Received event with handler unnamed
2023-03-06T16:53:31.283166654+00:00 INFO Fibaro Smart Implant BETA-3 <ZwaveDevice: 4cc2b52b-dd4b-40cf-b817-f117f0357d36 [0B] (Fibaro Smart Implant)> received Z-Wave command: {args={precision=1, scale=“CELSIUS”, sensor_type=“TEMPERATURE”, sensor_value=30.6, size=2}, cmd_class=“SENSOR_MULTILEVEL”, cmd_id=“REPORT”, dst_channels={0}, encap=“S2_AUTH”, payload=“\x01\x22\x01\x32”, src_channel=7, version=1}
2023-03-06T16:53:31.305733987+00:00 TRACE Fibaro Smart Implant BETA-3 Found ZwaveDispatcher handler in zwave_smart_implant
2023-03-06T16:53:31.306963654+00:00 PRINT Fibaro Smart Implant BETA-3 << Temperature_report_handler >>
2023-03-06T16:53:31.308294654+00:00 INFO Fibaro Smart Implant BETA-3 <ZwaveDevice: 4cc2b52b-dd4b-40cf-b817-f117f0357d36 [0B] (Fibaro Smart Implant)> emitting event: {“attribute_id”:“temperature”,“capability_id”:“temperatureMeasurement”,“component_id”:“main”,“state”:{“unit”:“C”,“value”:30.6}}
2023-03-06T16:53:31.318983654+00:00 DEBUG Fibaro Smart Implant BETA-3 Fibaro Smart Implant device thread event handled
2023-03-06T16:53:31.456968654+00:00 TRACE Fibaro Smart Implant BETA-3 Z-Wave command(c9d4af14) transmit status: TRANSMIT_COMPLETE_OK
2023-03-06T16:53:31.481254654+00:00 TRACE Fibaro Smart Implant BETA-3 Received event with handler unnamed
2023-03-06T16:53:31.482307654+00:00 INFO Fibaro Smart Implant BETA-3 <ZwaveDevice: 4cc2b52b-dd4b-40cf-b817-f117f0357d36 [0B] (Fibaro Smart Implant)> received Z-Wave command: {args={precision=1, scale=“CELSIUS”, sensor_type=“TEMPERATURE”, sensor_value=22.2, size=2}, cmd_class=“SENSOR_MULTILEVEL”, cmd_id=“REPORT”, dst_channels={0}, encap=“S2_AUTH”, payload=“\x01\x22\x00\xDE”, src_channel=8, version=1}
2023-03-06T16:53:31.543600321+00:00 TRACE Fibaro Smart Implant BETA-3 Found ZwaveDispatcher handler in zwave_smart_implant
2023-03-06T16:53:31.547315987+00:00 PRINT Fibaro Smart Implant BETA-3 << Temperature_report_handler >>
2023-03-06T16:53:31.548578987+00:00 INFO Fibaro Smart Implant BETA-3 <ZwaveDevice: 4cc2b52b-dd4b-40cf-b817-f117f0357d36 [0B] (Fibaro Smart Implant)> emitting event: {“attribute_id”:“temperature”,“capability_id”:“temperatureMeasurement”,“component_id”:“externalTemp1”,“state”:{“unit”:“C”,“value”:21.800000000000004}}
2023-03-06T16:53:31.595983321+00:00 DEBUG Fibaro Smart Implant BETA-3 Fibaro Smart Implant device thread event handled
2023-03-06T16:53:31.656896987+00:00 TRACE Fibaro Smart Implant BETA-3 Z-Wave command(e97e3400) transmit status: TRANSMIT_COMPLETE_OK
2023-03-06T16:53:31.795879654+00:00 TRACE Fibaro Smart Implant BETA-3 Received event with handler unnamed
2023-03-06T16:53:31.796834987+00:00 INFO Fibaro Smart Implant BETA-3 <ZwaveDevice: 4cc2b52b-dd4b-40cf-b817-f117f0357d36 [0B] (Fibaro Smart Implant)> received Z-Wave command: {args={precision=1, scale=“CELSIUS”, sensor_type=“TEMPERATURE”, sensor_value=22.0, size=2}, cmd_class=“SENSOR_MULTILEVEL”, cmd_id=“REPORT”, dst_channels={0}, encap=“S2_AUTH”, payload=“\x01\x22\x00\xDC”, src_channel=9, version=1}
2023-03-06T16:53:31.881644987+00:00 TRACE Fibaro Smart Implant BETA-3 Found ZwaveDispatcher handler in zwave_smart_implant
2023-03-06T16:53:32.039271987+00:00 PRINT Fibaro Smart Implant BETA-3 << Temperature_report_handler >>
2023-03-06T16:53:32.121546987+00:00 INFO Fibaro Smart Implant BETA-3 <ZwaveDevice: 4cc2b52b-dd4b-40cf-b817-f117f0357d36 [0B] (Fibaro Smart Implant)> emitting event: {“attribute_id”:“temperature”,“capability_id”:“temperatureMeasurement”,“component_id”:“externalTemp2”,“state”:{“unit”:“C”,“value”:21.8}}
2023-03-06T16:53:32.247186321+00:00 DEBUG Fibaro Smart Implant BETA-3 Fibaro Smart Implant device thread event handled
Input 1 on or off
2023-03-06T16:55:34.017747359+00:00 TRACE Fibaro Smart Implant BETA-3 Received event with handler unnamed
2023-03-06T16:55:34.023634692+00:00 INFO Fibaro Smart Implant BETA-3 <ZwaveDevice: 4cc2b52b-dd4b-40cf-b817-f117f0357d36 [0B] (Fibaro Smart Implant)> received Z-Wave command: {args={value=“ON_ENABLE”}, cmd_class=“SWITCH_BINARY”, cmd_id=“REPORT”, dst_channels={0}, encap=“S2_AUTH”, payload=“\xFF”, src_channel=5, version=1}
2023-03-06T16:55:34.043011026+00:00 TRACE Fibaro Smart Implant BETA-3 Found ZwaveDispatcher handler in zwave_smart_implant
2023-03-06T16:55:34.043843692+00:00 INFO Fibaro Smart Implant BETA-3 <ZwaveDevice: 4cc2b52b-dd4b-40cf-b817-f117f0357d36 [0B] (Fibaro Smart Implant)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“out1”,“state”:{“value”:“on”}}
2023-03-06T16:55:34.045569692+00:00 DEBUG Fibaro Smart Implant BETA-3 Fibaro Smart Implant device thread event handled
2023-03-06T16:55:34.572453692+00:00 TRACE Fibaro Smart Implant BETA-3 Received event with handler unnamed
2023-03-06T16:55:34.573417692+00:00 INFO Fibaro Smart Implant BETA-3 <ZwaveDevice: 4cc2b52b-dd4b-40cf-b817-f117f0357d36 [0B] (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=“S2_AUTH”, payload=“\x00\x00\x00\xFF\x07\x00\x00”, src_channel=1, version=3}
2023-03-06T16:55:34.581389026+00:00 TRACE Fibaro Smart Implant BETA-3 Found ZwaveDispatcher handler in zwave_smart_implant
2023-03-06T16:55:34.584450692+00:00 TRACE Fibaro Smart Implant BETA-3 Found ZwaveDispatcher handler in zwave_smart_implant
2023-03-06T16:55:34.595583359+00:00 WARN Fibaro Smart Implant BETA-3 Attempted to generate event for 4cc2b52b-dd4b-40cf-b817-f117f0357d36.main but it does not support capability Contact Sensor
2023-03-06T16:55:34.597193692+00:00 TRACE Fibaro Smart Implant BETA-3 Found ZwaveDispatcher handler in zwave_smart_implant
2023-03-06T16:55:34.599381026+00:00 WARN Fibaro Smart Implant BETA-3 Attempted to generate event for 4cc2b52b-dd4b-40cf-b817-f117f0357d36.main but it does not support capability Motion Sensor
2023-03-06T16:55:34.602095026+00:00 TRACE Fibaro Smart Implant BETA-3 Found ZwaveDispatcher handler in zwave_smart_implant
2023-03-06T16:55:34.604224692+00:00 DEBUG Fibaro Smart Implant BETA-3 Fibaro Smart Implant device thread event handled
Input 1 on or off
2023-03-06T16:57:03.376822703+00:00 TRACE Fibaro Smart Implant BETA-3 Received event with handler unnamed
2023-03-06T16:57:03.393041703+00:00 INFO Fibaro Smart Implant BETA-3 <ZwaveDevice: 4cc2b52b-dd4b-40cf-b817-f117f0357d36 [0B] (Fibaro Smart Implant)> received Z-Wave command: {args={value=“OFF_DISABLE”}, cmd_class=“SWITCH_BINARY”, cmd_id=“REPORT”, dst_channels={0}, encap=“S2_AUTH”, payload=“\x00”, src_channel=5, version=1}
2023-03-06T16:57:03.397957703+00:00 TRACE Fibaro Smart Implant BETA-3 Found ZwaveDispatcher handler in zwave_smart_implant
2023-03-06T16:57:03.401567703+00:00 INFO Fibaro Smart Implant BETA-3 <ZwaveDevice: 4cc2b52b-dd4b-40cf-b817-f117f0357d36 [0B] (Fibaro Smart Implant)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“out1”,“state”:{“value”:“off”}}
2023-03-06T16:57:03.412481370+00:00 DEBUG Fibaro Smart Implant BETA-3 Fibaro Smart Implant device thread event handled
2023-03-06T16:57:03.930168036+00:00 TRACE Fibaro Smart Implant BETA-3 Received event with handler unnamed
2023-03-06T16:57:03.931225370+00:00 INFO Fibaro Smart Implant BETA-3 <ZwaveDevice: 4cc2b52b-dd4b-40cf-b817-f117f0357d36 [0B] (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=“S2_AUTH”, payload=“\x00\x00\x00\xFF\x07\x02\x00”, src_channel=1, version=3}
2023-03-06T16:57:03.945176036+00:00 TRACE Fibaro Smart Implant BETA-3 Found ZwaveDispatcher handler in zwave_smart_implant
2023-03-06T16:57:03.946021036+00:00 TRACE Fibaro Smart Implant BETA-3 Found ZwaveDispatcher handler in zwave_smart_implant
2023-03-06T16:57:03.947225036+00:00 WARN Fibaro Smart Implant BETA-3 Attempted to generate event for 4cc2b52b-dd4b-40cf-b817-f117f0357d36.main but it does not support capability Contact Sensor
2023-03-06T16:57:03.949066370+00:00 TRACE Fibaro Smart Implant BETA-3 Found ZwaveDispatcher handler in zwave_smart_implant
2023-03-06T16:57:03.950324036+00:00 WARN Fibaro Smart Implant BETA-3 Attempted to generate event for 4cc2b52b-dd4b-40cf-b817-f117f0357d36.main but it does not support capability Motion Sensor
2023-03-06T16:57:03.957123370+00:00 TRACE Fibaro Smart Implant BETA-3 Found ZwaveDispatcher handler in zwave_smart_implant
2023-03-06T16:57:03.957954036+00:00 DEBUG Fibaro Smart Implant BETA-3 Fibaro Smart Implant device thread event handled
Is this correct log?
It’s like this in my CLI log
I don’t know how to remove </> format
Remove the tree ’ ’ ’ at the beginning and end of the logs
On is closed and Off is open?
I need log of IN1 Closed contact and Open contact
I have switch connected to IN1. I didn’t know exact operation.
I made some voltage measurements and I think that operation is like this.
First Input 1 on or off is closed contact
Second Input 1 on or off is open contact
Edit:
It’s also difficult to know what
Normally closed alarm input (Notification)
really means.
Is the contact normally ( no alarm ) closed and
when contact opens alarm is activated.
Thank you for the work on the 441 Mariano, very much appreciated
@Mariano_Colmenarejo
I have noted one anomoly that is different from your previous version
I have multiple virtual switches for controling programed sequences and colours on the 441
if i use a virtual switch to turn on and off a colour the transition to full off from on is smooth and consistant
If i use a virtual switch to switch on and off a programed sequence, on is smooth most of the time but occasional flashes of colour can be seen, off is instant with no fade to off
Is fade to off for programed sequence a possability with the new driver ?
Hi @fido
The driver does not intervene in the programmed sequences, it only sends the value of the parameter and the device carries out the sequence. In fact, the device does not send anything to the driver when it is doing the sequence.
This is identical to the previous driver, only it has changed, that with the previous driver when the sequence was turned off the device could be stay On or Off randomly and the states could be wrong.
To avoid this, I added that driver get the status of each color to update the correct status.
I could add that an Off command be sent in case it stays On and it would turn Off with the transition time that is established in preferences
I think this is correct
Thank for this Mariano. A nice update.
I am still struggling with something that was also an issue for me in the previous driver version. When I do a setHue in SharpTools (so via the API) the dimmer level always changes to 100% no matter what I send as setLevel. Looking at the logs I think I see my seLevel coming through (10%). I’m not experienced enough to understand exactly what is going on.
If I set colors through a ST Routine then any dimmer level set IS honored.
Could this be an API issue?
Here’s a log snippit. The full log is too large to post so I hope I have captured relevant entry:
2023-03-06T20:01:41.342648569+00:00 TRACE Z-Wave Bulb Mc Received event with handler capability
2023-03-06T20:01:41.362015069+00:00 TRACE Z-Wave Bulb Mc Z-Wave command(d7683dd7) queued for radio transmission: CC:Switch Color, CID:0x05
2023-03-06T20:01:41.367249861+00:00 INFO Z-Wave Bulb Mc <ZwaveDevice: xxxxxxxxxxxxxxxxx [BE] (Study Bookshelf LEDs)> received command: {“args”:{“level”:10},“capability”:“switchLevel”,“command”:“setLevel”,“component”:“main”,“positional_args”:[10]}
This is no subsequent log entry for setLevel with 100% but the dimmer level in the ST app (and actual device) is getting set to 100%. I THINK the 10% is processed then it reverts to 100%.
Any clue?
Note, and perhaps completely irrelevant, I do a setHue and setLevel on Zigbee devices (through your related driver) and those work just fine, ie, the dimmer sets correctly to the setLevel values I send.
It must be programmed like this in the firmware since it ignores transition time changes in preferences when any sequence is turned inactive
Hi @Nezmo
When a setLevel command is received you should see something like this, example set level sent 37%
If you either see this log it is that the correct command is not received or an On command is being received before, check it
2023-03-06T20:45:31.485626967+00:00 INFO Z-Wave Bulb Mc <ZwaveDevice: e78f6785-37e1-48bd-a197-ecf8dbc13260 [27] (Fibaro RGBW)> received command: {“args”:{“level”:37},“capability”:“switchLevel”,“command":"setLevel”,“component”:“main”,“positional_args”:[37]}
2023-03-06T20:45:31.487499967+00:00 TRACE Z-Wave Bulb Mc Found CapabilityCommandDispatcher handler in zwave_bulb → Fibaro RGBW Controller
2023-03-06T20:45:31.488705633+00:00 PRINT Z-Wave Bulb Mc <<<< set_switch_level_handler >>>>
2023-03-06T20:45:31.489898967+00:00 PRINT Z-Wave Bulb Mc <<<<< rgbwl_handler >>>>>>>
2023-03-06T20:45:31.491079967+00:00 INFO Z-Wave Bulb Mc <ZwaveDevice: e78f6785-37e1-48bd-a197-ecf8dbc13260 [27] (Fibaro RGBW)> sending Z-Wave command: {args={color_components={{color_component_id=“RED”, value=0}, {color_component_id=“GREEN”, value=78}, {color_component_id=“BLUE”, value=0}, {color_component_id=“WARM_WHITE”, value=0}}}, cmd_class=“SWITCH_COLOR”, cmd_id=“SET”, dst_channels={}, encap=“AUTO”, payload=“\x04\x02\x00\x03\x4E\x04\x00\x00\x00”, src_channel=0, version=1}
2023-03-06T20:45:31.540454967+00:00 TRACE Z-Wave Bulb Mc Z-Wave command(98f16af6) queued for radio transmission: CC:Switch Multi-level, CID:0x01
2023-03-06T20:45:31.541369300+00:00 INFO Z-Wave Bulb Mc <ZwaveDevice: e78f6785-37e1-48bd-a197-ecf8dbc13260 [27] (Fibaro RGBW)> sending Z-Wave command: {args={value=37}, cmd_class=“SWITCH_MULTILEVEL”, cmd_id="SET", dst_channels={}, encap=“AUTO”, payload=“%”, src_channel=0, version=1}
This device is different to a zigbee device, it doesn’t have a level attribute like the zigbee.
The level is set with the values between 0 and 255 of the three RGB values.
When you send a set Hue command, the Hue and Saturation value are converted to R,G,B values, but the problem is that the lua libraries don’t take into account the brightness that Hue and Saturation were encoded with and convert them to R, G,B with a standard value of 50% brightness.
therefore device will not maintain the brightness prior to the hue and/or saturation command
When you send a set level command, what is sent to the device is a command that modifies the % level values of R,G,B (between 0 and 255) to keep the same color with less or more brightness.
I’ve made a custom handlers that should respect the last level on initial power up.
When a setColor command is received, the brightness will correspond to the RGB conversion of the default libraries.