Good suggestion. Submitted a pull request at Add Amos Yuen repository by amosyuen · Pull Request #84 · dcmeglio/hubitat-packagerepositories · GitHub
1 Like
Glad it's working!
If any of you use Google Home, I found a bug with Google Home Community that you can't change the temperature if the device is off. I've proposed a fix at Cannot set temperature when thermostat is off · Issue #50 · mbudnek/google-home-hubitat-community · GitHub
Thank you for fixing it!
Submitted a fix for length error in v2.0.3 and refresh in 2.0.4.
To get the refresh to work you should click save preferences button after installing.
This app worked kind of OK for me, probably Eight Sleep's problem, but I was getting "Error 500" errors when trying to look at Hubitat Logs. Couldn't get to the logs page at all.
Going through my Hubitat backups, I had no problem before adding Eight Sleep Connect. Removing Eight Sleep devices and the app from my last backup fixed the problem, the only change I had to make.
I'm on Hubitat version 2.2.6.137. I first added this app with version 2.2.6.131.
I probably added the app via HPM, definitely on 3/12/2021. My current app version is 3.0.1.
If you're getting an error viewing logs page that sounds like a problem with hubitat and not specific to the driver. A buggy driver shouldn't take down logs for the whole hubitat. You should post in the support thread for hubitat for that.
It is suspicious that removing the app, fixed the problem. But I'm not really able to help without any logs or more info.
You could try different versions of the app (from github) and see if that makes a difference. Or try modifying the code in the app till logs work for you.
For me 3.0.1 gives the following error, when i roll back the app to 3.0.0 the error goes away. Like @dand, I’m fairly certain 3.0.1 was causing 500 errors in my log too. After support pushed out patch 2.2.6.150 to fix the 500 error is when i saw this app was not a happy camper and rolled back to 3.0.0 to fix.
[error](http://xxx.xxx.xxx.xx/installedapp/configure/418)org.codehaus.groovy.runtime.InvokerInvocationException: groovy.lang.MissingMethodException: No signature of method: java.lang.String.call() is applicable for argument types: (java.lang.String, org.codehaus.groovy.runtime.GStringImpl) values: [debug, getEightSleepAccessToken: eightSleepAccessToken=3279164b92e2482795868039d3febc42-14f98cc15814187e6e45bf129b039a32] Possible solutions: wait(), any(), trim(), grep(), split(), next() (credentialsPage)
Thanks for reporting, was able to narrow down the bug. Fix is out in v3.0.2
1 Like
Been working quite well -- thanks again.
I noticed this in logs and figured I'd drop it here in case you have any ideas or a fix?
(So that it's searchable:
org.codehaus.groovy.runtime.InvokerInvocationException: java.lang.Error: handleAsyncResponse: Error status=408, errorMessage=Read timed out, errorData=null (method handleBedResponse))
Is it expected I'd be getting so many read timeouts?
Thanks for calling that out. I also seem to have several throughout the day, so it seems like it's not just you. I don't remember seeing so many timeout errors before, so maybe something's changed or I haven't noticed it before. I'll play around with increasing the hubitat timeout setting and see if that helps.
1 Like
Pushed v4.0.1 which now has 30s timeout set on http calls. That seems to have fixed all my timeout issues.
Is anyone having a similar issue as mine where the "presence" state seems not to work? No matter if I am in the bed or off, the presence never changes and is always "present".
If I create a child presence for bed presence, that one seems to always be stuck in "not present".
So I have the parent device showing always present and the child presence always set as not present.
I see the same thing, but i dont use presence. Sleepstage seams to be fairly accurate and i use it in several automations instead.
Waiting on my Eight to ship, but really curious on what automations you have running/written for yours.
Also, I know slightly off topic, but curious if anyone has input/experience on their shipping times. My order said it would ship between 1 to 3 days ago and it hasn't yet.
I pretty much just use the status of sleepstage as one off the triggers in my wake / sleep automations.
Thanks, i’m trying it right now. Been laying in the bed for about five minutes and so far nothing has changed. I take it that setting will toggle once it is detected that you are asleep? That might be a little slow for me. I was hoping to have it detect when I lay in bed so that you can turn off the lights. If it doesn’t toggle until I go to sleep, then I would have to sleep with the lights on at the beginning. 
One of the bullet points in the first post is that the presence detection could be an hour delayed.
* Get whether there is a person in the bed (up to an hour delayed)
The presence on the eight sleep mattress is actuallly for the connectivity. It indicates that we got a response from the API for the mattress.
As others have said sleep stage should be used for being in-bed presence and is delayed.
