Support for GE Appliances (SmartHQ)

On the reconnect question. Yes the new driver copes much better with reconnect issues and the connection moved into the app, so the old per-device initialize trick doesn't work anymore. Since there are still cases it wont recover from automatically I've added a reconnect command to all the appliance drivers.

Because the whole integration now runs over a single connection, you don't need to hit every device: just point your "no activity in 12 hours" rule at any one appliance and run its reconnect command. That re-logs in and rebuilds the connection for all your appliances at once.

One thing to note — after you update, you may need to open the device and hit Save Device once for the new reconnect button to show up.

Longer term I'm planning to build this straight into the app as an automatic check, so it'll kick a stale connection on its own and you won't need the rule at all. But this gets you back to where you were in the meantime.

And thanks for the rinse aid code — send it my way whenever and I'll fold it into the dishwasher driver.

I did on May 8th in a PM did you not get it?

I don't see a reconnect button on any of my devices. Where should it be?

Where the button lives
It's on the device detail page, not a dashboard. Go to Devices → click one of your SmartHQ appliances, and look in the Commands section (the block of buttons near the top, alongside Refresh/On/Off). Hubitat title-cases it, so it'll read "Reconnect". It won't appear as a dashboard tile unless you add it as one.

Confirm the hub is actually on 1.0.7
The command only exists in 1.0.7. In HPM → check the installed version of SmartHQ. If it still says 1.0.6, run Package Manager → Update.

If you're on 1.0.7 but still no button
An already-loaded device page won't show a newly-added command until the driver is re-read. Open the device and hit Save Device once (or just reload the page). That forces Hubitat to re-render the command list, and Reconnect should appear.

1 Like

Found it and added in. thanks!

That was the problem. I was still on 1.0.6