I fixed @Jake_Knocki account for now, but as @aaiyar mentioned above, anyone joining the Owners group gets access to messaging and picture uploads.
3 Likes
Thanks!
3 Likes
So what's going on with Knocki. I am eager to ditch Alexa but need something such as Knocki to break away.
Hi @jnosa899, we're currently talking to TomW and Dgnuff, both of whom have samples of our device and have been kind enough to reach out with feedback and ideas for integration of Knocki with Hubitat. I'll keep you posted!
2 Likes
Hope your going to offer a launch sale when it's ready. I eagerly await. I can't help with programming but if you need some testers I'm more than happy if it speeds things up.
We'll definitely offer an exclusive deal for you guys once we get a Hubitat integration built that the volunteer testers from the Hubitat community feel is up to snuff.
3 Likes
I'll try and post progress reports as I slowly work through this.
First attempt: TL;DR it works, in that I have the Knocki, and I can turn a specific set of lights on and off using the combination of some "duct tape and bailing wire" glue logic, and a rule in RM.
That said there are two closely related problems: (1) it still uses the cloud, and (2) it's not in any sort of generally usable condition.
Specifically, the "duct tape and bailing wire" consists of a custom PHP endpoint on my local webserver here that accepts https:// requests from Knocki's servers, massages them and then forwards them to the HE. You can almost certainly get to the same place with IFTTT, but as has been noted, we want to go local.
That's definitely in the pipeline, but not in the next few days.
2 Likes
dgnuff - thanks for the update!
1 Like
Happy New Year everybody ... any updates to share as the new year gets underway?
Hi Mark, thanks for checking in! Our latest update is that dgnuff has been helping us evaluate HTTP requests. While HTTP requests sent through cloud are working seamlessly, Dgnuff pointed out some kinks with our LAN http requests, which we have already partially resolved. What's currently on the plate is enabling our LAN http requests to support multiple headers (and based on the bandwidth constraints of our very small team) is in the queue to roll-out within 6-8 weeks. I'll keep you guys posted!
4 Likes
How is this coming along?
1 Like
Sorry for the very late reply! We're still working on the http requests - adding the ability to add multiple headers, and also fixing various bugs. For full transparency, this will take longer than expected due to some unrelated "fires" we're putting out on the engineering side of things.
3 Likes
Slow & steady wins the race?
Has any more development happened with this product. How is the i tegration with HE coming alomg?
Random thought, though it might not be the direction you're going.... It's easy for a Hubitat driver to subscribe to MQTT and consume events. Lots of automation systems build around MQTT. Have you considered just publishing the knock events to a configured MQTT topic and getting easy integration with lots of local ecosystems?
1 Like
Hi there, thanks for checking in! We're currently working on improving sending json with LAN http requests, and general LAN stabilization. We feel that getting this stable is a pre-requisite to our integration with Hubitat!
1 Like
Hi Mark, thanks for checking in. Yes, slow and steady wins the race.
We're currently working on improving sending json with LAN http requests, and general LAN stabilization. We feel that getting this stable is a pre-requisite to our integration with Hubitat!
Thank you for the idea! Is the Hubitat "MQTT Bridge" the integration you are referencing?
While I'm not @mbishop, I think they were referring to the fact that it is easy to write a Hubitat driver that connects to an MQTT broker. So if your device sent data via MQTT to a broker on the LAN, Hubitat can easily subscribe to that topic and updates.
There are details in the Hubitat documentation;
https://docs2.hubitat.com/developer/interfaces/mqtt-interface
There are multiple, community-provided, MQTT "client" integrations available for Hubitat.
Exactly. Someone could use a generic MQTT driver, or you could publish a custom driver that consumes and parses the events. Since Hubitat has an MQTT client built into the API, either becomes easy to manage.
1 Like
