Yes I’ll add humidity device to the list for the next update.
Thanks for the report!
3 Likes
Would you mind sharing your Rule? Might be of interest to others how you send periodic updates for your zigbee sensors.
2 Likes
Rules API for Zigbee to MQTT sending (when Zigbee temperature measurement changes):
{
"name": "Temperature Changes - MQTT",
"actions": [
{
"if": {
"not": {
"equals": {
"left": {
"device": {
"devices": [
"id zigbee device"
],
"component": "main",
"capability": "temperatureMeasurement",
"attribute": "temperature"
}
},
"right": {
"device": {
"devices": [
"id mqtt device"
],
"component": "main",
"capability": "temperatureMeasurement",
"attribute": "temperature"
}
}
}
},
"then": [
{
"command": {
"devices": [
"id mqtt device"
],
"commands": [
{
"component": "main",
"capability": "partyvoice23922.vtempset",
"command": "setvTemp",
"arguments": [
{
"device": {
"devices": [
"id zigbee device"
],
"component": "main",
"capability": "temperatureMeasurement",
"attribute": "temperature"
}
}
]
}
]
}
}
]
}
}
]
}
Copy rule and just change device ids. Don’t change anything else.
3 Likes
Thanks for the hard work! I am running your drivers talking to an local instance of Home Assistant and it works great.
A request if it is possible, can you add a generic string/message device? I have serveral sensors that publish a timestamp and I track that to determine if a sensor has failed/not reporting. So I was looking for a device that could display a string of text.
Thanks again, fantastic driver and really breathed new life into my SmartThings hub.
1 Like
Welcome to the community. And I got a chuckle over your ID 
I’m wondering what kind of automation testing you needed to build around it. As you probably know, you’re a bit limited with what you can do with free form fields like that. Are you sure you’ll be able to actually do something the timestamp in an automation routine or Rule? If you’re confident you can do what you need to do, this shouldn’t be difficult to add. I’ll try to get to it sometime next week.
Rules API for Zigbee to MQTT sending (periodic updates):
{
"name": "Every 10 min copy temp - MQTT",
"actions": [
{
"every": {
"interval": {
"value": {
"integer": 10
},
"unit": "Minute"
},
"actions": [
{
"command": {
"devices": [
"id mqtt device"
],
"commands": [
{
"component": "main",
"capability": "partyvoice23922.vtempset",
"command": "setvTemp",
"arguments": [
{
"device": {
"devices": [
"id zigbee device"
],
"component": "main",
"capability": "temperatureMeasurement",
"attribute": "temperature"
}
}
]
}
]
}
}
]
}
}
]
}
Copy rule and just change device ids. Don’t change anything else.
Zigbee temperature measurement from SmartThings to MQTT broker is also operating using periodic updates.
3 Likes
hi how do i add this to smartthings ?
any help would be great
thanks
martin
Rules API Getting started
Create Automations via computer - Apps & Clients / Features & Feedback - SmartThings Community
More instructions
FAQ: Getting Started with the new Rules API - Developer Programs / Rules API - SmartThings Community
2 Likes
thanks the only bit im stuck on is this bit whats partyvoice23922
we need a mirror routine , would be eisier for less technically minded like me
ie - mirror temperature of zigbee sensor send as mqtt
Todd’s devices’ non standard capabilities’ names begins with partyvoice…
1 Like
or a tile that shows more than 7 days temperature readings
martin
I think that Rules API is only way to make mirror routine for temperature.
1 Like
Community-developed drivers often use “custom capabilities” (i.e. fields or controls) when there is no stock SmartThings capability that meets the need. SmartThngs assigns a random ID to developers that is used to create and identify their custom capabilities. My assigned ID happens to be ‘partyvoice23922’, so for devices created by my drivers, you’ll often find they contain some custom capabilities that include this name.
A quick tip for finding out what these capabilities are for any given device is to use my API Browser+ app. From the Devices menu, you can select the device of interest from the devices list, then tap the Status button and it will show all the components, capabilities, and attributes defined in the device. So you can quickly see what you need to include in your Rule definition.
2 Likes
thanks ,
i see i can create rules in the api browser+
i tried uploading the json and got a hhtp error 422 the request is malformed ,
Yes! I should have mentioned that. It might be a bit easier than using the CLI. But it doesn’t help you with the actual creation of the JSON file itself. Just with the submission to SmartThings.
all we need now is a rule to send send mqtt payloads so you dont need a virtual device
thanks
martin
ps it was realy easy to add the json to the hub with API BROWSER+
thanks
@TAustin