I dunno, where?
I hope I didn't ruffle any feathers with this post. Some of the replies are defending all of the amazing features that Hubitat offers and I agree with all of those opinions. I'm a Homekit user but it is VERY lacking in it's automation abilities and I am very hopeful to add lot's of big additions with Rule Machine, mirror, virtual everything etc.
But my first goal is to use HE to bring a few of my favorite devices into HK. I've received lot's of kind responses to this thread so thank you to the community for trying to help. Let me try to clear a few things up:
- Sorry for the long paragraphs as I wanted to make sure you had all of my details so as not to send you down the wrong rabbit hole. Bullet points are a great suggestion for me to be more concise. Thanks.
- I have read all of the tutorials and still none help me figure out how to import (my terminology) a private app or device. The Weatherflow Tempest is what I'm hoping to start with: - Do I click on the link for "Tempest" or the "API" link? Do I click on the 3rd link in that description? Or do I scroll down and read all 117 posts on the subject of bringing the Tempest into HE? Lot's of chat about changes to the code so where would I start??????
- csteele - You are the kindest soul I've ever come across in a forum. You literally made a video specific for my needs. THANK YOU!!!!! However, it starts by saying empty hub. I already downloaded much of Sonos, Ecobee, virtual button and my ipad which are in my devices and apps. Do I need to delete them all and start from scratch? I followed along with your video but got stuck on import on "Download from URL". When I clicked on that nothing populated. Is it because my hub is not empty? Needless to say, I only got a few seconds into your video before hitting a roadblock.
- Unless someone wants to contact me so I can pay for a consult to guide me through this I think I'll return to Homekit with my tail between my legs and wait for Matter to complete my smarthome - I think it's going to take Matter a long time before it is useful for consumers like me however.
I'm not convinced I'm following along.... Which qualifies as the blind leading the blind, I suspect. 
I hope you took the step of pasting the URL. I know the video highlights the Clicks with those blue rings BUT there's no highlight on a Paste.
Notice the differences between these screencaps:
This is the screen when you click Bundles.. notice the Choose File button.. notice that when you click "Download from a URL, it vanishes and becomes:
Fundamentally it's a completely new set of options. Note that the blue rings appear on that "Insert URL to..." line.. note that a second later the video shows the URL has been pasted in:
THEN the Import button is clicked. If there's nothing in the URL field, clicking import does exactly that, imports nothing.
2 Likes
I hate to say it but matter will do nothing for you. You will still be limited to exactly what Apple offers for automation capabilities which sadly along with Google and Amazon is terrible.
5 Likes
Yeah, I think folks who believe Matter is going to really move the needle WRT knocking down all the walled gardens enroute to a smart-home utopia are in for disappointment.
I would be happy to be proven wrong though -- time will tell.
3 Likes
I’m assuming you’re referring to this community developed integration.
The original post of that thread mentions that you must install two drivers. So the answer to your question is “both.”
The hub documentation has a page on how to install custom drivers.
Once you have installed both drivers, try to continue following the instructions in the OP of the thread devoted to the Tempest integration.
3 Likes
I notice that Snell's ( @snell ) community offerings are not in HPM, therefore installing HPM does nothing for that particular driver. @user3829 will be forced to use the many-click method for installing code manually... as documented. It's a good skill to learn, obviously.
2 Likes
Ok csteele where did I miss on what to copy? As in what I’m supposed to paste in the URL field. These instructions are to help me install HPM?
Oh wow now I’m really lost????? Are you saying that for the program I’m trying to install HPM does no good? Where would you suggest I go from here then? Thanks again for all of your help.
Yes. HPM is likely to be a significant part of your Hubitat journey, so I encourage you to pursue it's installation.
The documentation for adding code to Hubitat has been suggested a few times. It's actually the answer for that specific community created code.
2 Likes
Try to focus on my post.
3 Likes
Only a few of my drivers are in HPM. Since my WeatherFlow API driver only has two pieces (parent driver and child driver) HPM does not help much for it directly.
The base post of the thread has the basic setup. But you still need to get both drivers loaded. Here are the basic steps for that:
- Open up the thread page that has links for whatever driver code files you need.
- Open a new tab or separate window for your Hub.
- In the second tab, expand the "Developer Tools" list by selecting the arrow at that row.
- Now select the "Drivers code" item from the list.
- Select the "New Driver" button at the top right of the window.
- Select the Import button.
- Now, going back to the links in the first tab/window, copy the code file's link (usually right click and copy link).
- Go back to the tab/window with the Import field and paste the link into the field there, then select the Import button.
- Select the OK button saying you want to override the code (since there is none yet).
- Select the Save button.
The driver is now saved on the Hubitat. You can repeat most of the steps (4-10) for additional drivers. An alternative is to copy-paste code into the code window rather than importing it.
4 Likes
Not to critique but you can see that our dear friend @user3829 is having trouble following a series of screencaps as well as a video.
What I'm saying is that as new hub owners join this community their experience with other interfaces/GUIs may lead them to "guess ahead" -- not follow each actual step, but say to themselves "Oh, I get it now... " and jumping ahead... leading to failure.
Adding code to Hubitat is very easy, but yet there are certainly a number of pitfalls, I repeat two of them often: Putting driver code in Apps code or vv. And not copying the code completely or not copying the URL for an Import completely. One char off and it won't work, and most miss pages of code. Github contributes because you have to know about clicking RAW. Therefore, HPM has a niche with that group of new hub owners, I think. Keyword search then a single click to start the process sure seems simpler to me.
The same logic is what lead me to Bundle HPM (1 app) and then Bit.ly the URL. All intended to reduce the two issues I have with first time installs. 
7 Likes
Update:
- I was able to download a virtual switch into my Hubitat hub and then was successful in migrating that switch into Homekit. It’s good to know I’m not a complete, moron.
- I thought I had successfully brought HPM into my hub. It showed up in my apps screen, but when I tried to use it or install it or save it, it would bring me to the code page and then it looked like I may have copied and pasted a couple of different things there that screwed it up.
- I am still confused as to whether or not I need Snells “API”? Or the other link for “Tempest”? I have also now gotten conflicting messages as to whether or not I should use HPM. Does anybody know of a consultant that I can pay over the phone to do this for me?
1 Like
Both.
Not for the weatherflow tempest.
2 Likes
So if HPM is under the APPS code page, click the APPS button on the left side of the screen. Click ADD USER APP, then look for Hubitat Package manager. It will then appear under the regular apps button.
As to weather flow, when you get into HPM, click INSTALL, then search by keyword for weatherflow. The weatherflow lite driver will show up. click to install. Once it's done, go to the devices page. Click add new device, then virtual device. Pick weatherflow lite as the driver. click save. Now the device is in your device page. Go to devices and click on your new weather flow device. Fill out all the fields (you will need some info from the weather flow site..Click save preferences. Now do what you will...
Here is a shot of my weather dash...Needs work though
1 Like
For my WeatherFlow driver, only the WeatherFlow API is REQUIRED. All the useful data your weather station returns via the API will be presented by the device, once you create it (following the instructions on the thread).
The WeatherSensorChild driver is optional. It is only needed if you want to use the Enable Child Devices preference. This will create a child device for each part of the station the API reports. For example, mine reports the outdoor station and the forecast. This can make it easier to look for specific values but is NOT required overall.
EDIT: I have also added my WeatherFlow (and most other drivers) into HPM.
2 Likes
Thank you rlithgow1 as I stumbled along far enough that you have dragged me close to the finish line. I now have HPM in my apps and I have Tempest Weatherflow Lite in my devices tab. I'm in the Homekit Intgegration app which I have already successfully used to pull some devices (both virtual and actual) into Homekit. However, now in my Homekit app it is telling me that the Tempest is an "incompatible" device and therefore cannot be moved into HK as is. I have a feeling this has to do with the Tempest credentials. I acquired a token from my Tempest app and have saved it in the "API key" field as well as the "Station ID" field. I'm pretty sure this is incorrect. What did I screw up?
BTW, I forgot to mention that after I "Saved Preferences" I clicked on the "Initialize" button at the top of the page. It did nothing as far as I can see. I've been using the Tempest app on my phone for about a month so I know my login credentials are correct.
It is an incompatible device because it uses a "User (custom) virtual driver".
From the Hubitat HomeKit Integration (Beta) documentation:
But there is a way around it because the only meteorological information currently supported by HomeKit is temperature and humidity.
So create virtual temperature and humidity sensors in Hubitat (using built-in drivers), and a rule that updates the temperature and humidity values for these virtual sensors each time they change in the weatherflow tempest lite device you've created.
Then expose your virtual temp/hum sensors to HomeKit .....
FWIW - I use a totally different Weatherflow integration (one that I created in Node-RED), and I use this approach to get temp/hum information into HomeKit.
1 Like
