New firmware available. I just pushed it with my C8, and it does actually show in the logs.
Would I need to create a new device driver to track this new attribute, or is there something existing that might work?
New firmware available. I just pushed it with my C8, and it does actually show in the logs.
Would I need to create a new device driver to track this new attribute, or is there something existing that might work?
The doorCondition: 2 vs doorCondition: 3 appears to be what we need.
Does it show last code name yet?
Not that I can find, no. At least, the stock driver is not parsing it properly if it is.
Here are the latest unlock entries for mine. I'd have to compare them and test a few different users to see if anything useful is there. The door position is a nice addition regardless.
I spoke with U-Tec this morning and they indicating that there is no official release of firmware to support this. I provided the link to the firmware and they indicated that I should not use this.
Well the link in the OP is a file hosted on U-tecs website... Seems odd they would be hosting an illegitimate firmware file on their own site?
Exposing this new capability (contact sensor) will need a new driver for the lock.
I did provided all the information to them, including the link.
If they send any additional information I will post it here.
Very odd indeed... I wonder if it's a pre-release thing that wasn't supposed to escape the lab yet...
Very possible.
I also provide the information to the community discussions, and they were going to send them to their engineers.
There's no point in talking to low-level support at a company like U-Tec. They legit announced the release of this new feature.
I can confirm that when I just open/close the door on an updated lock, I get Zwave responses:
on one of my other 3 locks, I get nothing. Only when actually locking/unlocking.
I have some issue with U-tec lock. If it jams while it tries to lock it shows locked. Anyone else have this issue?
Wow, the spam algorithm here is trash. It should be able to examine a user's post history to determine if they are a spammer.
Yeah that is odd -- I don't know what happened there... I wonder if someone accidentally flagged it somehow? There's obviously nothing offensive or spammy-sounding in your post!
When messages are flagged, it doesn't mean that they are "spam". There was nothing spammy in your post.
Flagging indicates that some community user found your message objectionable. Like @hydro311, I don't see any objectionable in what you wrote, so I'm guessing it was done by someone with fat fingers on a mobile device ......
Actually the system appears to be correct in this case. @stevenascott -- there isn't as much history for this user. If you have 2 different accounts and would like to merge them so that the system can better evaluate the historical data, please send me a PM and will merge them for you.
Yeah I'm not sure what's going on actually. It appears now I have three accounts. When I log in with my proper email, it actually goes to another account with the wrong email. This this odd behavior, and I'm sure it's user error on my behalf.
Anyhow on the jam situation, I'll try testing in a bit. I would imagine it doesn't get communicated via zwave. Does your utec app recognize the jam?
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
I saw this thread saying that the U-Bolt Pro Z-Wave could now report if it was open or not, not just if it was locked or unlocked.
Assuming this is so, how do I go about getting the sensor to be a device that I can use in a rule to send me a notification if it is open when the door says it is locked?