Hello @milandjurovic71 , I appreciate all your recommendations to improve the drivers!
Choosing only two values "Equal-Up" and “Down” has its explanation and cost me many hours of work lost in tests:
(I am going to be a bit extensive in the explanation)
- When in a routine it compares three options with an entered value, what really happens is that this comparison is answered with a True or false.
-
When the comparison is made with events, which depend on a comparison made by the driver and there is more than two response “=”, “>=”, or “<=”.
When the result of the comparison is “=”, then the driver would have to emit three different events followed by “=”, “>=”, “<=” so that the users who in the automation have chosen any of the 3 options are run the routine for them.
Therefore, a possible solution would be to have the options “=”, “>” or “<”, but this is very unstable to trigger a temperature, humidity or illuminance routine, let me explain:-
Making a routine with only the “=” condition for temperature, humidity or illuminance is like playing the lottery.
If you have set the temperature condition = 25ºc and the current temperature is 24.9ºc, it is very likely that the next event could be > 25ºC (25.1, 25.2…) and the routine will not be executed. Could you check your device history for temperature, humidity, or illuminance.
-
Making a routine with only the “=” condition for temperature, humidity or illuminance is like playing the lottery.
Therefore with “>=” and “<” all the possibilities are covered in a safer way and with fewer events circulated.
-
Regarding the names of the value labels, it also has its explanation:
-
What I would write would be: “Igual”, “Igual o Mayor” and “Igual o Menor”, but out of deference to those whose language is not Spanish, I try to find names that are the most familiar to all:
-
I started writing tag that everyone can understand “=”, “> or =”, “< or =”, but smartthings didn’t trigger the automations with these values, I don’t know why, but that’s how it is. @nayelyz I had to redo several times the presentations of the capabilities, the VIDs… etc…
-
So I decided to use “UP” and “Dwon” because most of them are tired of seeing it in many appliances, remotes… in their homes.
-
There is one thing that I haven’t been able to test, since my locale uses ºC and I can’t test if the conversion from the last stored temperature to ºF works well when a new temperature value is entered. I don’t know if the value that the system saves for the last value is ºC or ºF. I have assumed that it saves the same thing that it sends in the ºC event and the app or API converts it to ºF.
Could you please enter a couple of temperatures and look at this in the log?
2022-08-23T12:09:59.980121224+00:00 INFO Zigbee Temp Humidity Sensor Mc <ZigbeeDevice: eb7c780e-e667-46ab-ba47-ea81341df249 [0xEDE2] (Environment Sensor)> received command: {“args”:{“value”:27.5},“capability”:“legendabsolute60149.tempCondition2”,“command”:“setTempCondition”,“component”:“main”,“positional_args”:[27.5]}
2022-08-23T12:09:59.996020890+00:00 TRACE Zigbee Temp Humidity Sensor Mc Found CapabilityCommandDispatcher handler in st-zigbee-temp
2022-08-23T12:10:00.007536557+00:00 PRINT Zigbee Temp Humidity Sensor Mc set_TempCondition.value= 27.5
2022-08-23T12:10:00.056910890+00:00 PRINT Zigbee Temp Humidity Sensor Mc device:get_latest_state >>>> 28.64 table: 0x1805ba8
2022-08-23T12:10:00.132790890+00:00 PRINT Zigbee Temp Humidity Sensor Mc last_temp_value ºC= 27.2
2022-08-23T12:10:00.187942557+00:00 PRINT Zigbee Temp Humidity Sensor Mc last_temp_value = 27.2
2022-08-23T12:10:00.200237224+00:00 INFO Zigbee Temp Humidity Sensor Mc <ZigbeeDevice: eb7c780e-e667-46ab-ba47-ea81341df249 [0xEDE2] (Environment Sensor)> emitting event: {“attribute_id”:“tempTarget”,“capability_id”:“legendabsolute60149.tempTarget”,“component_id”:“main”,“state”:{“value”:“Down”}}
2022-08-23T12:11:19.772230262+00:00 TRACE Zigbee Temp Humidity Sensor Mc Found CapabilityCommandDispatcher handler in st-zigbee-temp
2022-08-23T12:11:19.979940929+00:00 PRINT Zigbee Temp Humidity Sensor Mc set_TempCondition.value= 81
2022-08-23T12:11:20.049644262+00:00 PRINT Zigbee Temp Humidity Sensor Mc device:get_latest_state >>>> 28.64 table: 0x1805ba8
2022-08-23T12:11:20.124811262+00:00 PRINT Zigbee Temp Humidity Sensor Mc last_temp_value ºC= 27.2
2022-08-23T12:11:20.132189262+00:00 PRINT Zigbee Temp Humidity Sensor Mc last_temp_value = 81
2022-08-23T12:11:20.162955595+00:00 INFO Zigbee Temp Humidity Sensor Mc <ZigbeeDevice: eb7c780e-e667-46ab-ba47-ea81341df249 [0xEDE2] (Environment Sensor)> emitting event: {“attribute_id”:“tempTarget”,“capability_id”:“legendabsolute60149.tempTarget”,“component_id”:“main”,“state”:{“value”:“Equal-Up”}}
Thanks