I see that the driver emits the status that the device sent.
When the On or Off command is sent from the app, the device receives it, but I think it is returning to the state that corresponds to the state open or close of input IN1 or IN2
I think the problem may be that you have to use the configuration of inputs IN1 and IN2 in:
0 – Normally closed alarm input (Notification) or
1 – Normally open alarm input (Notification)
instead of 3 – Bistable button (Central Scene).
When the setting is in value 2 or 3, it automatically changes the states of Out-1 and Out-2 internally and sends the command.
In the logs that @TapioX sent me when the inputs IN1 and In2 are at values 0 or 1, the device sends the status as a notification, but the status of Out-1 and Out-2 does not change and the driver tries to emit an open event /close or Motion/no Motion according to the default handlers.
This is what I have to implement with a contact sensor and motion sensor profile.
Por favor, puedes quitar el formato </> a los logs, los veo mejor sin tener que mover los cursores a derecha e izquierda para ver las líneas largas y cortas.
Si quieres estos logs puedes borrarlos ya los vi y los que me envies puedes hacerlo con un mensaje privado para mantener mas limpio el thread.
I have left the internal temperature information in the main component.
There are multi-Tile profiles showing the internal temperature in the main group and In-1, Out-1 and In-2 and Out-2 in the other four groups.
The open and closed status of IN-1 and In-2 will show open/close or motion/No motion state according to profile selected.
At the moment I have not implemented code to activate and deactivate Out-1 and Out-2 with the states In-1 and In-2.
This way you can do it with routines and choose the state you want. This also allows you to deactivate Out-1 and Out-2 (siren, light…) from the App and not activate it again if the contact does not change to closed and remains open.
If it is necessary to implement the code, you will tell me.
───────────────────────────────────────────────────
Driver Id ecfae8a0-9e46-44ae-b252-8407c4712fd9
Name Fibaro Smart Implant BETA-4
Package Key zwave-fibaro-smart-implant-4
Version 2023-03-07T12:02:14.955893973
───────────────────────────────────────────────────
I think that Smart Implant also internally changes Out1 when configuration is 0 – Normally closed alarm input (Notification) and In1 is turn on (contact closed).
I think that this is in the log is from Out1 (src_channel=5, Endpoint 5 ??? )
2023-03-07T15:20:18.837147400+00:00 TRACE Fibaro Smart Implant BETA-3 Received event with handler unnamed
2023-03-07T15:20:18.847844733+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-07T15:20:18.853045733+00:00 TRACE Fibaro Smart Implant BETA-3 Found ZwaveDispatcher handler in zwave_smart_implant
2023-03-07T15:20:18.861598733+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-07T15:20:18.864748400+00:00 DEBUG Fibaro Smart Implant BETA-3 Fibaro Smart Implant device thread event handled
In this case the problem is that the color sent to the device in the driver is R=0, G=0, B=0, W=0, off and a setlevel of 10% and this causes the device to set a power On
When calculating the rgbw values with the level increment from the last saved level to the new commanded level of 10%, the result is less than or equal to 0.
I have modified the way of calculating the new level to avoid this
install this driver version with CLI and try it
───────────────────────────────────────────────────
Name Z-Wave Bulb Mc
Version 2023-03-07T18:28:49.974785681
───────────────────────────────────────────────────
When you turn on with a level command now I see that it calculates the RGBW values well
The problem is that you are sending the setHue command instead of setColor, I guess it will be with sharp Tools since this command cannot be sent with the app.
The seHue command is handled by default instead of the custom handlers needed for this device.
I will have to modify the driver for the setHue and setSaturation commands.
With the stock Z-wave bulb driver, these commands won’t work either.
Try routines from the app or sharp Tools sending setColor should work fine
Thanks Mariano. When I started working with this and SharpTools I believe I was using setColor but we ran in to issues in the translation between the systems so I had to move to using setHue.
I can already confirm that using SmartThings Routines things do work correctly. Unfortunately, I can’t achieve the full set of rules I want with Routines.
As always, I really appreciate your work on these. Thanks.
Try this driver version with custom handler for setHue and setSaturation.
After install driver if not last hue and last saturation saved in memory apply a hue or saturation 50
───────────────────────────────────────────────────
Name Z-Wave Bulb Mc
Version 2023-03-07T21:13:28.764361403
───────────────────────────────────────────────────
Hate to say this but now the actual colors getting rendered are no longer correct. Here’s new logs (and sorry to everyone for the massive posts but these logs are verbose):
It is impossible for me to see in the logs if the color corresponds to what you think it should be correct.
Tell me what I have to see and I try to play it on my device., except send setHue o setSaturation commands, i only can send setColor command
when the color does not match, is it when you send only one command with setHue command?
The driver looks for the last known saturation value and sends it with the hue value to convert it to R,G,B values
As I told you, the lua libraries when converting the hue and saturation values received to R,G,B values to send to device, do not take brightness into account and use a brightness of 50% standard
These R,G,B values sent to the device generate 4 switch Multilevel report commands one for each color and another general level command that usually coincides with the maximum level of the three levels r,g,b
Try this version to see if it works better when sending hue or saturation commands
I’ll see it tomorrow, I’m going to sleep
───────────────────────────────────────────────────
Name Z-Wave Bulb Mc
Version 2023-03-07T22:56:41.161197091
───────────────────────────────────────────────────
Please, can you delete these logs?, I can’t analyze them