-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Heat set to 0 degrees #54
Comments
The left part until the 16° is produced by the App, the rest by the driver. The app checks the range of temperatures your driver supports, before setting it. Such, if the temperature you request if out of bounds, it chooses the lowest/highest possible value. I will look at the driver. |
I have 2 Nest thermostats 3 gen., worked with the beta issues (had to
restart the app. some times) until the upgrade, but since yesterday this
error.
Regards
Den tir. 19. feb. 2019 kl. 11.52 skrev Markus <notifications@github.com>:
… The left part until the 16° is produced by the App, the rest by the
driver. What kind of thermostats do you have?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#54 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AtkFZ_c3yum-TebsSIVeVpmNqjUx7rMsks5vO9dagaJpZM4bCnCQ>
.
|
Can you create a logfile via console.re? |
Have never tried it, will have a look at it later |
You can also contact me on slack if you like, than we can have a look together. |
I looked at the code again and checked relevant places. The temperature set is definitly validated against the device's min/max capability values. It's unclear to me how can this happen. I definitly need logfiles. |
Thanks for the logfile, I understood the problem now. The NEST thermostat does not report step size for the target_temperature capability. This leads to 2019-02-19 15:00:08 [log] [g] [INFO ] [AthomAPI ] Target adjusted Bedroom Thermostat (Bedroom Thermostat) was 16 -> NaN (min: 9, max: 32, step: undefined) 2019-02-19 15:00:09 [log] [g] [ERROR] [ST/Check ] Retry action 5 times, waiting for 1000 { (Bedroom Thermostat) Failed to set target temperature to 0, error: Error: TEMPERATURE C VALUE IS TOO LOW: %S: {"error":"Temperature C value is too low: 0.0","type":"https://developer.nest.com/documentation/cloud/error-messages#low-c-value","message":"Temperature C value is too low: 0.0","instance":"52bcf447-2a2d-47d0-9b54-f9b6bdcfb3d7","details":{"tempC":"0.0"}}: (Bedroom Thermostat) Failed to set target temperature to 0, error: Error: TEMPERATURE C VALUE IS TOO LOW: %S: {"error":"Temperature C value is too low: 0.0","type":"https://developer.nest.com/documentation/cloud/error-messages#low-c-value","message":"Temperature C value is too low: 0.0","instance":"52bcf447-2a2d-47d0-9b54-f9b6bdcfb3d7","details":{"tempC":"0.0"}} To be honest, I didn't expect that to be not set. I will fix this. |
Your bug is fixed in the RC for the next version. You can find the latest build here https://github.com/mskg/homey-heating/tree/release/v1.2.0-rc13 Would be great if you drop me a short not if it's fixed there? Release notes https://github.com/mskg/homey-heating/blob/feature/plan-overview/docs/releasenotes/v01-02-00.md |
Great job 👍, looks like the isuue has been solvet in rc13
tir. 19. feb. 2019 16.41 skrev Markus <notifications@github.com>:
… Your bug is fixed in the RC for the next version. You can find the latest
build here https://github.com/mskg/homey-heating/tree/release/v1.2.0-rc13
Would be great if you drop me a short not if it's fixed there?
Release notes
https://github.com/mskg/homey-heating/blob/feature/plan-overview/docs/releasenotes/v01-02-00.md
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#54 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AtkFZ1O86Z9BI0uJCjdaJvWOLvJ14yJ1ks5vPBsXgaJpZM4bCnCQ>
.
|
- **Add**: Translation to Dutch, resolves #30 - **Add**: Graphical plan overview, resolves #44 - **Change**: The initial bootstrapping of the web application has been made faster by lazy loading many components. - **Add**: Virtual heating thermostats for plans - **Fixed**: Issues with type references - **Change**: Startup now blocks using mutex - **Change:** @app modules are now in the node_modules folder - **Fix:** Reference to Settings enum - **Add**: Colors for console output during "athom app run" - **Add**: Notifcations can be turned off, resolves #52 - **Fix**: step size of capabilities can be unset #54 - **Add:** sentry.io, user can opt-out - **Change**: optimized logging implementation - **Change**: optimized settings handling and notification - **Change**: map file urls to allow external integration - **Add**: debug api to launch/stop "inspector" - **Add**: optimized color display #21
Subject of the issue
The app is picking up the right temperature from the schedule but try to set it to 0 degrees, startet after upgrade to 1.1.2
![img_0276](https://user-images.githubusercontent.com/47777127/53006996-aa352a00-3436-11e9-9689-2a104bfd6f23.PNG)
Steps to reproduce
Tell us how to reproduce this issue.
Expected behaviour
Tell us what should happen
Actual behaviour
Tell us what happens instead
The text was updated successfully, but these errors were encountered: