Hey @jtmpush18, quick question: did you install the Hestia Dashboard app through HPM (Hubitat Package Manager) or by pasting the code manually into Apps Code?
If you did a manual code paste, can you check this:
- Go to Apps Code in your Hubitat admin
- Click on Hestia Dashboard in the list
- Look for the Enable OAuth checkbox (usually near the top, after the app name)
- Make sure it's checked
- Click Save
- Then go to Apps > Hestia Dashboard > Done
The discovery file requires an OAuth token to write. If OAuth isn't enabled on the app, the token never gets created and the discovery file silently fails.
A couple other things that might help us figure out what's going on:
Check the logs: Go to Logs in the left sidebar of your Hubitat admin. Look for any entries from "Hestia" that mention "could not create access token" or "could not write discovery file." That would tell us
exactly where it's getting stuck.
Verify the file directly: Try opening this in your browser: http:///local/hestia-token.json (replace with your actual hub IP). If you get a 404 or blank page, the file was never created.
If nothing else works: As a last resort, you can remove the Hestia Dashboard app entirely (Apps > Hestia Dashboard > Remove) and reinstall it fresh. That forces a clean setup cycle and usually resolves token
issues. Your Maker API setup won't be affected since that's a separate app.
In the meantime, the dashboard should still work for controlling devices through the local URL (http:///local/index.html) since device control goes through your Maker API, not the discovery file. The
discovery file is mainly used for auto-setup and config sync between devices.
—————————————————————————————————————————–
Hey @JdThomas24, thanks for the feedback! Both issues have been fixed:
Fan classification: The dashboard now uses a name-based fallback for fans. If a device doesn't report the FanControl capability (common with Bond Bridge, community drivers, and other integrations that only
expose Switch/SwitchLevel), but has "fan" in its name, it will be classified as a fan instead of a dimmer or switch.
Thermostat auto-discovery: New thermostats are now automatically added to the thermostat section when discovered, instead of going to the staging area as generic devices.
Both fixes will take effect the next time the dashboard loads from hestari.com or when you update your local file.
Since your fans are probably already saved as switches in your current config, the automatic reclassification won't override what's already there. You'll want to go into Settings > Rooms & Devices, find the
fans that are showing as switches, and remove them. Then hit Scan for new devices and they should come back correctly as fans.
For the thermostat, same thing. If it ended up in a room as a generic device, remove it and re-scan. It should drop into the Thermostats section automatically this time.
Let me know if you run into any issues!
BUG Device Room Assignment change in settings: When you assign devices to a room and then come back to reassign to a different room, the device duplicates each time you assign a different room. (Example: If I change from Den to Office, it changes it but duplicates the OLD assignment. Each time you do this and continues to duplicate)
