Great stuff here, Kevin - thank you! Your professional attention-to-detail with your DH builds and SmartApps is much appreciated. Donation happily sent
When I open or close the valve using the SmartThings app, it will say “Opening” or “Closing” indefinitely. If I immediately do a refresh the status is not corrected. However, if I wait an hour or two and do a refresh the status will be updated correctly. This problem just started recently but the device handler obviously hasn’t changed in a while. Is anybody else having this issue?
It’s most likely related to the platform bug below that started last week. I was hoping they’d fix it fast enough to avoid having to add a workaround to all my DTHs, but I’ll take a look at this one tomorrow.
Just a minor point that you may want to revisit at some point to update for the color changes ST introduced some time back. I think it’s just the blue that is inconsistent.
Also, I can’t figure out why the icon on the main tile shows the ‘closed’ icon (no drip) when it’s open. the code looks correct.
I’ve created the device handler in smarthings and it seemed to connect just fine. I tried to operate the valve via SmartThing, but it doesn’t actually move, the icon changes like it should be tho? How do I get this thing to start responding?
Did you create the device handler before adding the device?
Does the device open and close when you push the physical button on the top of the device?
If you log into the IDE and open live logging and then try activating it through the mobile app it might provide additional information about why it’s not working.
I attempted to connect it before I knew you had create the device handler for it, but it did not connect to the network. Then I created the device handler and added it.
The device opens\closes fine when pushing the physical button on the device.
When I check the logs it shows it as follows, but it never actually moves the valve unless I press the physical button(status updates properly when button is physically pressed)
8:07:02 PM: debug Requesting valve position.
8:06:48 PM: debug Valve is Open
8:06:38 PM: debug Closing Valve
8:06:36 PM: debug Valve is Open
8:06:26 PM: debug Opening Valve
8:06:24 PM: debug Valve is Open
8:06:23 PM: debug Requesting valve position.
8:06:21 PM: debug Valve is Open
8:06:12 PM: debug Closing Valve
8:06:06 PM: debug Valve is Open
8:05:57 PM: debug Device Checked In
8:05:56 PM: debug Closing Valve
@krlaframboise Thanks for this DTH. I have a problem with the device that is not an issue with the DTH, but I wonder if it’s possible for you to compensate in the DTH?
The arm has no adjustable limit capability and mine tries to swing too far, in both the open and closing cycle. I’ve tried everything that’s been suggested here to solve the physical incompatibility between the motor and the valve arm. The motor tries indefinitely to complete the close (or open) operation. I’ve just accepted that in an emergency I’d prefer to close the valve 99% and probably have the motor burn out.
So, finally, my question: Is there a way for the DTH to recognize that the cycle is running too long and stop the operation after some period? I wouldn’t want it to revert to open, but to just leave it in a mostly-closed state. Thanks!
When you execute the “close” command all the DTH does is send an off command to the device. If I remember correctly the device immediately reports that it’s off so the DTH has no way of knowing if it finished closing the valve.
To prevent burning out the motor you could attach it to a smart switch. When water is detected have one rule that closes the valve and another that waits 1 minute and turns off the switch.