Well. It works in classic app not new app. Didn't know that. Has anyone got this to work with Google home? Home doesn't recognize hubitat fans as fans but it will recognize smartthings fans as fans. Problem is control doesn't work thru home
Yes, HubConnect for ST is Classic App only at this time.
There's just one Tile for Fan Control and it cycles through, Auto, Low, Med-Low, Medium, Med-High, High, On, and Off. The logs above show I rotated through them all.
Anyone get performance issues on their hub using HubConnect? i was using old version 1.4x (trying to hang on for v2) but i had to remove it as i was having issues with my hub and since removing the hub is so much faster on webui and dashboards etc...
I've used every version of HubConnect on the same three hubs since.. well since before there were version numbers.
v1.4 was superseded by v1.5 and then v1.6 when @srwhite came back from camping in Nov '19.
The current version is v1.6.4 and v2.0 will replace it. One big difference with v1.6 is the use of the Hub Driver on all hubs. Upgrading to v.1.6.4 will put all of the pieces in place for upgrading to v2.0
I doubt there is a package available on Hubitat that hasn't (by now) been presumed to be the reason for this hub's slowdown. Under v1.4, and using HubConnect's EventSocket option, means the App is practically doing nothing. The EventSocket is a feature of the Platform, intended to be used by Dashboard. It's roughly equivalent to an unfiltered MakerAPI. The "other hub" simply listens to the first hub's EventSocket and injects Events as they arrive. Only when you're actively clicking through HubConnect's menus is the App really doing anything. (There is a 'ping' heartbeat that runs, but it's a LAN packet every couple of minutes. HSM and Modes also cause a packet, but again, just a few times per day.)
To be fair i've not seen anyone say they have had issues, that's why i asked @csteele
Maybe mine just got corrupted or something but the speed difference is like night and day after removing.
think i'll hang on for v2 rather installing 1.6 then 2.
When you remove HubConnect, how dashboard works ? ( devices on Hub 1, dashboard on hub 2 ... ? ). I got some error because HubConnect, right now my phone dashboard spinning but I'm not home, can not reboot the hub server.
Server Instance or Remote Client... because it's the one displaying the error and thus the one being sent an update from DEV:718 on the 'other hub'.
718 got deleted from 'this hub'. You could try going into 'other hub' and pretending to select a device, then Done out. You should see the message go away, because it got recreated, or you'll see a log saying the Driver for that device isn't found on 'this hub'.
I have not...yet. I actually switched to using hubconnect with my smartthings hub for "echo speaks" on the smartthings hub. Echo speaks is one app that IS confirmed to slow down your hubitat hub. My hub was locking up every couple of days when that was installed on it.
Hi - just setup HubConnect today ... one on each of the three floors of my house. I have a forth hub as the "coordinator hub:" where I will control everything.
I'm noticing the devices on the coordinator are never in sync unless I hit "sync". Example, I turn on a device from the coordinator (hub 1) - it instantly turns on the light at hub 2 - but the "Hublink Device" on hub one still shows "off" unless I hit the sync button.
Is this how it is supposed to work? If not, any ideas as to what I'm doing wrong? Thanks