Hello, I have a Zigbee Temp & Humidity Sensor that looks to be compatible with your Edge Driver (TS0201) but the Device Manufacturer is not listed yet (_TZ3000_yd2e749y). What additional information do you need to have this added to the list of compatible devices? Right now it is found as a Zigbee Thing and when I try to manually change the driver I get a weird message to make sure my phone is on the Network (it is fine, just seems to be a standard response to just this device).It won’t let me change it in IDE as it already is defaulted a Zigbee Thing Edge driver. Thanks.
Aded to this driver version of temperature sensor
┌─────────────┬──────────────────────────────────────┐
│ Name │ Zigbee Temp Humidity Sensor Mc │
│ Version │ 2022-05-27T21:17:54.248927656 │
└─────────────┴──────────────────────────────────────┘
- id: "_TZ3000_yd2e749y/TS0201"
deviceLabel: Tuya TS0201
manufacturer: _TZ3000_yd2e749y
model: TS0201
deviceProfileName: temp-humid-battery
Added to this version of Thermostat sensor
┌─────────────┬───────────────────────────────────────┐
│ Name │ Zigbee Temp Sensor with Thermostat Mc │
│ Version │ 2022-05-27T21:20:56.692246502 │
└─────────────┴───────────────────────────────────────┘
- id: "_TZ3000_yd2e749y/TS0201"
deviceLabel: Tuya TS0201
manufacturer: _TZ3000_yd2e749y
model: TS0201
deviceProfileName: temp-humid-therm-battery
1 Like
Hello,
I apologize if an answer to this question has already been provided. I did scan the thread and did not see an answer. I am also unable to tinker as my drivers have not yet been migrated to edge.
I am looking for methods to account for the ecobee helper apps in Ecobee Suite Manager now that the end of Groovy has been made official.
I use it for two methods, one to turn off the hvac system when windows are opened and secondly to also disable the fan completely. If I am understanding the documentation correctly turning off the thermostat is no issue but I am not seeing anything about disabling the fan.
When the windows are open I want the fan disabled through my ecobee thermostat. Secondly, I want a virtual switch to disable the fan so the “off” state can be triggered manually.
Is this something that is possible or is it something that can be added?
Yes, it is possible.
This how i do that. I have one virtual contact sensor that changes to Open, when any window or patio door is open, and changes to Closed when All windows and patio door are closed. 10 minutes delay give me time to get in and out without turning off A/C every time someone goes through the door, or opens window for less than 10 minutes. If anything is open 10 minutes or longer it puts A/C Off.
For turning back on you need to change Thermostat mode to Heating or Cooling.
You can always turn off A/C manually, and it will stay that way until someone closes all windows and doors. If you manually turn A/C On, when something is open, it will last only for 10 minutes (if someone wants to circulate fresh air).
I do have additional virtual switch (HVAC Mode) that is used to store A/C state Heating or Cooling, that I use when I turn A/C back on to previous Cooling or Heating
When you turn thermostat off, fan is off too, it might take some time to run after, but that is settings in ecobee app.
Hopefully this helps
Thank you. It is far from the simplicity of the helper apps with some reduced functionality but at the least the core aspects are there. Good to know the fan turns off with the “off” using this driver. I will miss the fan being separate since I would disable that alone and have it activate when the cooling triggered again. Maybe in time someone will figure out how to recreate a helper app in Edge.
1 Like
New version 4 of the Zigbee Temp Humidity Sensor Mc driver.
To make it easier to create slightly more complex automations and need to create fewer routines:
- Routines that require dynamically changing the temperature value in the comparison condition, for example at a certain time or according to the location mode… change the reference to 20º.
- Routines that may need a minimum and maximum range for comparison. (Using in the same rule the Temperature capability and the custom Temperature Comparison capability)
- I have added these new functions for temperature, humidity and illuminance, according to the profile of the device used.
I will only count the temperature one, the Humidity an Illuminance work the same.
- I have added capabilities to introduce the comparison value to be used in the driver and automations:
- For temperature, enter the value in ºC or ºF, depending on your location and you have to choose the ºC and ºF units in preferences since the driver does not have access to know which units the app is using.
- The driver compares the current temperature with the entered reference value and emits an event with the result of the comparison “Equal or Up” or “Down” to a capability, which is only seen and used in automations/conditions to trigger the routine. (I don’t know how to compare =, >=, or <=, since they overlap and would give wrong results.)
@nayelyz This capability allows the entry of decials for temperature (-50º to 250º), but the app only shows the value rounded to an integer. Let’s hope they fix it
The update will be manual, since it has several new custom capbilities and it is better for each one to update whenever they want and clear the app cache to see the new VIDs.
To facilitate the update, I am going to change version 3 to the name Zigbee Temp Humidity Sensor Mc-(OLD) .
I will publish the new version 4.0 with the original name Zigbee Temp Humidity Sensor Mc.
In this way, your driver installed will have the rename with (OLD), indicating that there is a new version available and you can install the new version with a driver change whenever you want
New driver version
┌─────────────┬──────────────────────────────────────┐
│ Driver Id │ fce41c83-ef6f-4d6c-8e13-8c1b63588641 │
│ Name │ Zigbee Temp Humidity Sensor Mc │
│ Package Key │ Zigbee_Temp_Humidity_Sensor_v4 │
│ Version │ 2022-08-22T20:34:07.582474383 │
└─────────────┴──────────────────────────────────────┘
2 Likes
@Mariano_Colmenarejo I was going to ask if you can match THEN part of Routine to match default (stock)
From
To
I have case where i need both temperature to be equal. Also it is more correct to use above and below then up and down term.
Thank you my friend
- Now if i can find a way to mirror another sensor in to this two conditions, that would allow to create some complex automations. For example to compare external and internal temperature or humidity
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
3 Likes
I’ll check CLI later when I get back home.
This screenshot is from the app, and temperature in F looks good
1 Like
And if you change the temperature of the condition above and below and do an automation, does it fire correctly?
Thank you
Hi, @Mariano_Colmenarejo!
So, just to confirm, you use those symbols as the possible options in the list and it caused issues, right? Maybe, there’s an issue due to the way the Rules API translates the selection by the user to execute the automation, remember that’s the backend for the Routines.
Yes it does work.
I just checked with temperature increase notification
I did change conditional temperature to 80F to speed up testing, and it worked
1 Like
@Mariano_Colmenarejo
I am looking to have these devices added to your driver.
Centralite Door/contact sensor: (Centralite 3323-C). One of these was onboarded recently and is running the ST zigbee edge driver.
Centralite Temp/Humidity Sensor (Centralite 3310-C)
Thank you,
Hi @nayelyz
To be more precise, this didn’t work others presentation, the automation was only triggered when the emitted value was “Equal”
This led me to the conclusion that the values of “key” and “value” have to be identical and not contain spaces.
"automation": {
"conditions": [
{
"label": "Temperature Comparation",
"displayType": "list",
"list": {
"alternatives": [
{
"key": "Equal",
"value": "Equal",
"type": "active"
},
{
"key": "Up",
"value": "Equal or Up",
"type": "active"
},
{
"key": "Down",
"value": "Equal or Down",
"type": "active"
}
],
"value": "tempTarget.value",
"valueType": "string"
}
}
],
"actions": []
},
This is the final works fine:
"automation": {
"conditions": [
{
"label": "Temperature Comparation",
"displayType": "list",
"list": {
"alternatives": [
{
"key": "Equal-Up",
"value": "Equal-Up",
"type": "active"
},
{
"key": "Down",
"value": "Down",
"type": "active"
}
],
"value": "tempTarget.value",
"valueType": "string"
}
}
],
"actions": []
},
According to documentation examplekey and value can be different and contain spaces in “value”
In fact, when you create or update the presentation of the capability, it does not give any error.
"automation": {
"conditions": [
{
"label": "Garage Door Status",
"displayType": "list",
"list": {
"alternatives": [
{
"key": "closed",
"value": "Closed",
"type": "inactive"
},
{
"key": "open",
"value": "Open",
"type": "active"
},
{
"key": "partial",
"value": "Jammed or unresponsive",
"type": "active"
}
],
"value": "door.value",
"valueType": "string"
}
}
],
the 3323-C is not included in the stock driver.
The 3323-G is included as in mine.
It is right?
I hace included 3310-G. is correct 3320-C?
Only one of my door/contact sensors is running an edge driver and if I try to change it to another it does not give me any other options even though I other edge drivers installed. Unfortunately, I accidentally discarded the box with the part number. The number listed is what was on the site I ordered the sensor for and what was supposed to be sent to me. I did check to see if it is valid and available elsewhere and it is, it seems to indicate it is the US version.
For the Temp/humidity sensor, I do have the packaging and it is 3310-C.
I hope this helps. With the announcement of the official end of Groovy I have been trying to get a basic understanding of Edge and how to address the loss of smart apps I have. Thank you for all you have done to help with transitions and provide functionality.
To confirm the exact measurement, you could to install my zigbee thing Mc driver and perform a driver change.
This will give you the exact fingerprints.
I don’t see that model 3323-C in the stock driver and I don’t know how it can be paired to it if it isn’t
I installed your zigbee driver and it did come up as an option and as the 3323-g when used.
1 Like
Then install my drivers zigbee contact Mc and It will be a driver option
Dame for zigbee temp humidity sensor Mc
1 Like