Home Remote dashboard for Hubitat


The datastores (if you haven't already figured this out) aren't necessary. They are only related to the feature I added of changing the dashboard color theme from within the running app.

I started by hard coding colors into my HRP for each element. But I was never happy with what I chose and kept tinkering. And it was annoying to change a color, then start the simulator and see if I liked it. To speed up the process, I changed the dashboard element colors to a variable. Then I could change the variable from within the app and find the color I liked in real time. Turned out I was still never completely happy, and had created multiple themes I liked (TNG, Borg, Voyager, Battle Bridge).

Here comes the datastore - Home Remote variables are reset to the defaults upon restarting the app. I needed a way to store the color variable so it would persist after a restart. As suggested by Bill/the Home Remote forums, I created multiple virtual devices on Hubitat to store a string for each color code I needed to save. I have so many because I created five themes and multiple colors in each. But now from within the Home Remote app I can save the color to Hubitat, and later restore it back to Home Remote.

All of that is completely unnecessary if you can decide on one color theme and stick to it.


I can't say exactly how it works on the back end, but it appears to connect by name.

From my experience - if you don't change any of the device data in Hubitat, and don't manually change the device settings in Home Remote (Picture Below), then you can resync and everything will continue working. It just deletes all the Hubitat devices and then puts them back exactly as they were. I am often adding / removing devices in the Hubitat app and then resyncing and there is no issue. Everything comes back the same, except of course for the new or deleted device.

But for example, if you were to rename the device in Home Remote and then resynced, it would go back to the name that comes from Hubitat and I believe everything related to that device would be broken. If you want to rename a device, I suggest doing so within Hubitat, resyncing, and then fixing anything that linked to the now gone name. More work upfront, but next resync you won't have to make any manual changes.


Bill from Home Remote has made a significant improvement to his app. The plugin script on my GitHub page has been updated to match. GitHub - mihaca/homeremote: Home Remote Integration for Hubitat

Please be sure to update your install of the Home Remote designer, paste the new plugin script into your project, and make sure all your device apps running the program are up to date as well.

Home Remote version 2.12.0's main upgrade is that "plugin.Devices" is now a JavaScript object instead of a JavaScript array. This was changed because it was discovered that looping through large arrays can take a while & have a very significant impact on performance.

More information on the change can be found here:

Personally, I have found a significant decrease in the time the app takes to parse the data received from Hubitat.

The plugin script code also adds a new hard coded device - "Connection". The state of the connection device can be displayed in the app to show whether you are connected locally or via the cloud. I also use it to decide which web address to use to access my webcams. It has a lot of possibility, so I wanted to include it for others.

Also note I have changed the polling interval: plugin.PollingInterval = 500;
Home Remote will now request changes from Hubitat every 500ms. This may be too often for some users. I'm also not sure if it will cause Hubitat to get bogged down. Let me know!


I keep getting an error of Device is Undefined when saving the 3 plugin settings in home remote. Has anyone else run into this before?


Sorry about that - my fault with the new features. Can you try the new pluginscript posted to github?


That worked! thanks a bunch!