A Pull Request on github.com. Its how you submit code changes to a repository.
Got it. Thank you, still learning…
HA! One of my locks is NOW reporting the battery level! (and I didn’t do anything to it, but changed the device type yesterday)
1 Like
Man sounds like its about time I update and re-donate. Sounds like we’re getting some great enhancements to an already really nice app.
Finally, after a week, removing the battery, waiting, praying, cussing, cursing… we have a battery status of 100%. Unfortunately, I’m not sure which of the above methods worked…
Sounds like…it may not be “magic” but a back-end issue, if we all are starting to see the battery levels showing up mysteriously TODAY!
1 Like
Wow! That’s good to hear that they recommend it. I guess the pressure is on to keep improving!
It is pretty suspicious that everyone is getting battery updates today. Pretty suspicious indeed.
I thought you may like to know that. Anyway, I’m pretty sure now that is a back end issue, as my other lock is showing the battery level and I didn’t do anything to it in the past 7 days…
Ooh, I will try this tomorrow. Crossing my fingers.
Side note: lock stopped responding tonight so hopefully that will be fixed as well. At first I could get it to lock or unlock about half the time, but I’ve got a 0% response rate now.
That’s exactly what happens if the lock is to far away when you pair it. During the paring process not all transmission are received so some functions will not work.
I wish ST would/could detect a bad zwave paring and tell you to try again. But this may be a limitation of zwave and out of STs control.
1 Like
Thanks. It was actually good for a week and then fell to pieces rapidly last night. Hopefully reconnecting will do the trick
Re-paired the lock - fixed the spotty lock/unlock behaviour but battery status is still missing. I’ll give it some time again.
Does anyone here have a v2 hub and Android app? I couldn’t get an older version to run on my new hub, so I came here to get the latest. It ran one time. I set up 3 users, and one that would burn. (First time I’ve seen this option ever work, as the older version always crashed when I set that, and I had to completely uninstall the smartapp.) Pretty cool stuff.
Anyhow, when I attempt to install the latest ULM on the v2 hub via Android app, it gives the “unauthorized” error, (vague, I know,) any time I try to enter the specific user settings, any of them.
Switch location to my v1 hub, install same exact code, same exact lock type, same exact device-type, (I’ve tried yours and the stock one,) and it works perfectly fine. There’s something specific about the new hub, and it’s trying to query null variables of some kind.
Right now, Live Logging isn’t working very well. I can’t isolate the view to only show this app, which is very frustrating. I hope that’s fixed soon.
Seems to have an issue with this section of the code:
> def allCodesDone() {
> def i = 0
> def codeComplete = true
> locks.each { lock->
> i++
> if (state."lock${i}".error_loop == true) { #### THIS LINE FLAGS AN ERROR ####
> codeComplete = false
> }
> }
> return codeComplete
> }
I was able to get something out of the live logging:
645e151e-274f-4f24-80e8-df257bb98c73 5:47:35 PM: trace getPhrases(), state.welcomeIssue = null
Earlier, I just so happened to stumble on one that mentioned line 1245 and a null value. Not sure if all these errors are connected, but the results are the same.
FWIW, I just combed through and commented out anything relating to hello home phrases or scheduling, and now the crash is gone.
My Modes and Phrases have semicolons in them. I bet somehow the code is not expecting that, and that text is not sanitized.
If that’s the case: http://xkcd.com/327/
1 Like
I am running on v2 hub. Should I uogradecto latest version … is the source changed in github
I just got my V2 hub on Saturday. I haven’t had time to set it up yet. I’m hoping later in the week or this weekend I can get cracking on that.
I can debug after that…
3 Likes
Reading some recent posts… New user and was about to install on my V2 hub, is the consensus to wait at the moment?
If you have a v1 hub and things are working fine, the recommendation is to just wait (that one came straight from ST). For v1 to v2, it can sometimes be a bit difficult. For new users starting with v2, it is easier. I have a v2 sitting in the cabinet - wanted the free stuff when they had the special! My plan is to roll it out in a few months when they have a migration tool of some sort. It’ll also give me time to re-evaluate how I’m doing things. I plan on doing the v2 as a complete redo. Plus, I really want to wait until the dashboard replacement is in place as well since I use that all the time as a quick glance.
But, like I said, if you are starting out with the v2, then proceed! Time to jump right in with both feet!!!
2 Likes
I looked to see if this was answered earlier, but couldn’t find anything from a search. Apologies if this has been asked.
Just received new hub v2. Was able to connect it to my Schlage lock, but wanted your functionality. Followed the how-tos to add a new app. Was able to install, and it works, but it’s asking for a custom device driver. You do have the code for this, but I’m not sure how to incorporate the code for a second file into the app. I looked around, and can’t find anything other than community posts, most of which are filled with people as confused as I am.
If you could give me pointers, or a quick how-to, I’ve be very grateful. I just need to know how to incorporate an app that has a dependency. Do I need to create as a second app?
Thanks
A device type is added in a different part of the IDE. Instead of smart apps, click “My Device Types” at the top of the IDE web page, create a device type there, and paste in the code.
1 Like