Anyone here have a Lockitron and able to comment on its use compared to a Z-Wave lock like the Kwikset 910 or other locks? I put 2 Kwikset locks in, and have 1 more door to update. I still have my kickstarter Lockitron order in, but I’m debating on canceling…
If you have any feedback and able to share that would be awesome!
I know @dkirker has one. Hopefully he’ll chime in and give you some info.
I don’t have any experience with the other locks. Unfortunately, I am changing ISPs, so… my Lockitron isn’t really doing anything. Once my Internet is back up, I’ll be plugging with it. I’m gonna try to make some headway this evening on a device type for the Lockitron, and hopefully have something mid week. (And I still want to get the BT on my Lockitron working…)
@dkirker This is great news. I have a Lockitron Access model (which is a door buzzer as opposed to a dead bolt “cover”) but works identically and responds to the same API commands. Please let me know if there’s any way I can assist. Here is some information that might help get you going. Thanks for starting this undertaking!
Thanks! No problem. I have started writing the connect SmartApp. Going to make more headway tomorrow/today.
There’s no day like today. ;p
Just popping in to say that I am slowly making progress. Well, not super slowly. However, I need to look into an issue with my particular Lockitron. I may see if I can swing by their offices tomorrow if I am able to arrange it.
@dkirker Thanks for the update on your progress. I’m really looking forward to integration with this device along with the new Ring video doorbell. This could make for a fantastic entry solution for those of us with gates.
Alright, making headway! I actually had the code working last night (for simple lock and unlock), but a nice typo masked that…
I’m going to chug ahead some more to get some more basic features in, then go ahead and get it in a state that is more usable (and more tested!).
@dkirker - Anything you can share for testing? Very excited about this integration. Thanks again for your investment of time and energy.
I apologise for the delay. Been working on getting my car fixed and regaining employment.
I don’t have anything useable/testable at the moment (well, it is usable, but it is more a demo state, so I’d rather spend another day on it before handing it out). Let me do some more work with it tomorrow and I’ll get something that can be played with up.
Any progress to share? Thanks for your effort!
A tiny bit, however, I have been occupied the last week or so being hired by SmartThings.
I have uploaded the source that I have so far to https://github.com/dkirker/smartthings-lockitron Basically, at this point, it can lock and unlock the door; however the state refreshing is very rough, so the icon may not update properly. Mostly what I am interested in is that you can log into your Lockitron account during setup, add a lock, and lock and unlock it. I’m planning to clean it up and improve it, plus add lock codes. You’ll see a bit more from me over the coming couple of weeks.
Feel free to fork and create pull requests!! B-)
So, it looks like Lockitron is reving their hardware. http://blog.lockitron.com/post/109301218722/introducing-bolt-our-next-generation-connected
I’m still looking to finish my code up. The Bolt sounds like it will be a MUCH better device (looks sexier, too). My lock sort of just eats my batteries in the worst possible way…
Would be great to continue working on this device type - I honestly haven’t had an opportunity to play with it as I had hoped, but will try to provide you some feedback. That way, when Lockitron releases the Bolt, the integration will already be ready. Thanks for the continued attention to this.
The original Lockitron is what happens when a team without sufficient engineering expertise tries to design hardware. No one else was doing a WiFi based lock for a reason–power consumption. It was inevitable that a battery powered WiFi lock was going to consume batteries way too quickly.
The new generation, the Bolt, is dropping WiFi altogether, as it should. The next generation will be BLE only.
WiFi is still a great protocol for many residential applications. Just not for battery powered devices that don’t get recharged every day.
The new bolt will still have a Wifi-to-Bluetooth bridge for handling communication from devices like our v1 SmartThings hubs.
The new lock, called The Bolt, is BLE only. They’re going to ship a separate device they call the Bridge which will provide wifi to BLE. You’ll be able to get the lock without the bridge if you don’t need it.
They don’t say, but it would make sense if the bridge unit is a plug in.
[quote]Bridge: Instantly Responsive WiFi
To conserve battery life and allow for instantaneous connectivity, we’ve removed the integrated WiFi chip from Lockitron Bolt and put it into Bridge. Bridge connects Bolt to the internet and allows for full, instantaneous control anywhere you have internet access. Whether you just want to let a guess in or forgot to lock your door on the way to work, Bridge is the perfect solution. It’s important to note that Lockitron Bolt is a standalone product and doesn’t require Bridge for local, Bluetooth Low Energy access or to share access with family and friend. This means you can choose the best Lockitron Bolt or Bolt+Bridge solution to suit your needs and budget.
Hi dkirker. Thanks for getting this far on lockitron for smart things. I have a v2 lockitron with two Bolts on order.
Doesn’t look like any further work has happened on this smart app. I’m curious as to what state you got it to or is the state polling still not good as you say above ?
auth is failing when going into auth the app to access lockitron
lockitron response from auth website "an error has occured client auth failed due to unknown client, no client authentication included or unsupported authentication method.