This has been fixed
1 Like
Thank you both locks showing fine now.
Trying this out. I got the Google and Anthropic API keys set up. If there was a way to get the Anthropic API key without paying at least $5 to create a credit balance, I couldn’t figure it out. After adding the credits, my API key is working, but just a few test commands have used $.03 of the credit, so I’m not sure I have this set up correctly. If I understand correctly, that means I’ve already used thousands of tokens.
Edit: Found it in the Anthropic console:
That seems like a lot of tokens in for maybe a half dozen commands I tested.
I haven’t been able to get the wake word to work in my Chrome browser on my Chromebook, although it shows the icon to indicate the microphone is in use. I think I’d prefer to use the button rather than the wake word anyway. Is there an option to have the voice command only run when the button is pushed and not keep the microphone active all the time?
I assume this will not work over cloud URL for Maker API? I tried and wasn’t successful. If this is the case, have you considered accepting a CF service token during setup that would permit connection over a cloudflare zero trust connection and thus permit access to the local IP address on Hubitat without needing to use the maker API Cloud access?
Hi what is the best way to install it on a fire tablet 10 i tried different ways but wont connect worked fine on my samsung tablet. I have fully kiosk installed on the fire tablet.
I actually tested it on a fire tablet, if you’re trying to use the fully kiosk browser then go to Wall Panel, copy the link and paste it as the start link to the Fully Kiosk.
If that fails let me know as that would be a bug. You can follow-up test by going to Apps > Hestia Dashboard > and copy the local link from the App page.
Hey Alan,
You can choose to disable the permissions to the mic in the Athena options. Honestly, I’ve been testing for weeks now and I’m at 0.19 cents of usage. Is this your only API key? Did you set it to Haiku? Haiku is the least expensive because the reasoning is quicker, and less thorough. It should default to Haiku on the settings panel but double check.
If you want to turn off the mic, you can go to the settings in your browser and disable the access to mic and leave it toggled off permanently and just use the chat window. Though to be honest, this allows for rules, routines, reminders, timers, etc. to be done quicker but you’d miss out on having that nice personal assistant feel which is what we’re aiming for.
The wake word is a bit choppy which it is flagged as Beta/Experimental and why we’re still working on refining detection. It’s just me working on this so I don’t have tens of thousands of clips available to train the module from different humans, but it’s getting much better with synthetic training and we should have something rather good by the end.
Let me know what else you’re seeing.
Thanks for testing
Thank you, yes to get it going i had to use http:///local/hestia-token.json with my ip. I did do a copy and paste into Fully Kiosk once it was working but I only get the top portion of the app screen Groups and the gear on top right nothing else shows. But if i paste the same url into the Silk browser it seem to work fine and see the full screen.
That’s not expected behavior. Looking into it now.
Hey Brian, good question.
You're correct that Hestia won't work over Hubitat's cloud Maker API URL, and that's actually intentional.
We deliberately keep device control local-only. This isn't a missing feature so much as a security decision. A cloud path means device control tokens living on the public internet, which introduces an attack surface we're not comfortable with.
Local-only is a hard security boundary: someone would need to be physically on your LAN to issue commands. We want to keep it that way.
That said, remote access is totally doable! The approach is to make your network reachable to yourself rather than making your hub reachable to the internet:
- Tailscale (free for personal use, ~5 min setup) creates a private mesh network so your hub appears local from anywhere
- VPN (WireGuard, OpenVPN, etc.) accomplishes the same thing
- Cloudflare Zero Trust works too, but that's your tunnel to configure on your end
All three keep the security boundary at the network layer where it belongs. Once your hub is locally reachable through any of those methods, Hestia works exactly as expected with no changes needed on our
side.
Hope this helps!
1 Like
Thank you fyi if i paste the url into chrome it wont connect but when i paste it into silk no issues and the same condition happens in Fully partial page.
To confirm, you’re referring to the local URL That’s on the hestia app site and not the “wall panel” url that’s on the wall panel tab in the dashboard settings panel itself. Correct?
I copied the url in the app under wall panel where it says to copy and paste it into start in fully Kiosk (Paste this URL into your wall panel browser (Fully Kiosk, WallPanel, etc.) or open it on any new device to auto-configure.) its basically the same as HD+ and sharptools which i had both working in Fully.
Hey there,
Can you please go to Hestari.com > Dashboard > Settings > Wall Panel
Copy the Wall Panel link and paste it over to Fully Kiosk and try now?
We’ve implemented a fix and it should be up and running, including mic usage for athena.
Thanks again for looking into this, on my fire tablet 7 the only way I can get it to work is if I paste http:///local/hestia-token.json into start in Fully Kiosk when I copied the url from the wall panel in the app it comes up with the start screen to fill in the information from maker api and then when tested won’t let it connect. for my fire HD 8 it will only load a partial top portion of the app screen no matter what I paste in the start url no start screen to input information and the buttons that do show don’t function. again I did get it working fine on my samsung tablet and my pc all devices are on the same network. I can run other dashboard with the maker api id’s
That’s interesting because I have a Fire 10 for testing and installed Fully Kiosk with the watermarked mic access and it’s all working properly.
Settings > Wall Panel Link > Paste to Fire 10 > Works
I even tested the scrolling and it worked.
Is your Fully Kiosk perhaps cached or restricted somehow? I’m not too familiar with the settings so I wonder if there’s something restricting it from scrolling.
Ok I’ll play with it some more to see what it might be. I did reinstall HD+ with no issues but it would not do a self discover i had to input the maker api information to connect.
That tells me that something is breaking its connection to your local hub because we built the logic in a way that the dashboard tries to fetch your local config file for any device after the “first install.”
The intention is for you to install it once via the onboarding wizard and then all devices within your local network should discover the settings so that you don’t have to migrate a .json file each time.
If that fails, try exporting the .json from your current desktop and then loading it in your fully kiosk version and see if you encounter the same issues with connectivity and scrolling.
Would it be possible to get the ability to hide cards and the corresponding items on the left and top? I don’t have fans or blinds/shades.
Same for Smoke/CO and Freeze/Water under security.
PM shows 1.5.3 on Github. So, not pushed to HPM.
When will you push to HPM?