I’m setting up a second hub, should I wait for hubconnect 2.0?
If you need integration now I wouldn’t wait. I personally rely on it too much with my 3 hubs to wait. I am waiting though in 2.0 to upgrade as I am in an older version.
I wouldn’t, but I have no patience. The upgrade to V2 is painless (at least from the latest version).
1 Like
Is there a reason why hubs (both HE, socket connection) might loose connection overnight?
It shows connected in the list of apps, however when I look at the logs, no communication going on. When I reboot the slave hub, communication resumes.
I know it's quite vague, but just wonder if there's something like a very known thing that I am not aware of 
I’m pretty sure that losing the socket connection occasionally is why there’s an option to reconnect in the driver, which may be new in 1.6.4. I have mine set to reconnect at 0400 (after the nightly activity).
Yeah... I am on 1.4 and didn't notice this before the earlier-in-the-week botched upgrade to 1.6.4, which I successfully rolled back.
Now I am totally hesitant to touch what works lol.
1 Like
I feel ya. I’ll bet 2.0 will be much better with that; and I’ll bet it’s faster too. 
Eh I didn't see 2.0 in the repo? Is it in a diff repo?
v2.0 is in Beta and @Ken_Fraleigh is "teasing you" with futures. 
2 Likes
I thought that was your job.
4 Likes
It's Steve's but I decided he was having too much fun.. and I took some too. Now I'm thinking Ken has decided I'm having too much fun and has taken some.
1 Like
All you guys are having too much fun. My OCD says I want (need) 2.0 so get back to your beta testing so it can be released!
If you think I'm whining that's because I am.
1 Like
funny, but I am fine with my 1.4, as long as it does not break.
1 Like
Sorry 
. You’re right. I’ll go sit in the corner now.
I fixed my slip, so just pretend that wasn’t there.
1 Like
I am missing something easy with setting up hubconnect. I have the server instance installed, have the remote client installed, both the server and client say that they are connected. I have shared devices from the server to the client but those devices don't show up there. Do i need to install each device individually or something?
Have you installed the HubConnect drivers that are needed for the devices on the remote hub?
If you haven't then the devices won't copy across.
I did install the drivers.
Did you install the remote hub drivers on both, as well as HubConnect device drivers?
Every once in a while, I ask an insightful intelligent question. This is not one of those times.
I'm upgrading from 1.4 to 1.6. All is going fine until I try to install a (new) universal driver in SmartThings. Specifically, I am installing:
In the SmartThings IDE, "Create New Device Handler", I paste the above raw code (like I've done hundreds of times over the years), then hit Create and I get the dreaded:
Java.lang.RuntimeException: Metadata Error: Capability 'Initialize' not found. Usually, something like that indicates forcing a smartapp into a device handler, or vice-versa; but I don't think that's it. Would somebody please tell me what I'm overlooking? Thanks!
It's true, initialize is not a defined Capability within SmartThings.
It is within Hubitat, however.
Feel free to paste in the code to ST IDE and then comment out line 25.
//capability "Initialize"
to allow the Driver to save. It will demote the initialize feature from ST, but there's no button for it anyway via Universal Drivers. In other words, if you find ST can't get your speech device to speak, you'll have to use the 'real' driver to Initialize.
