-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Ecobee: two cases where tokens should be ignored or discarded. #2849
Conversation
Ecobee: two cases where tokens should be ignored or discarded.
|
Thanks @watou. Yes, it would be great if you could update the ecobee-action PR. Best, Thomas E.-E. |
|
I'm curious, is there a way to pull the currently running time on the Ecobee...so say the AC has been running constantly for 4 hours; is there a way to pull that data...i see alot of runtime strings, but not one that stands out. Thanks Rich |
|
Hi @milty456, I would look at the persistence extensions or rules in the wiki. Also, howto questions are better asked over on the Google group. |
|
Just started seeing this in the openhab log; can anyone tell me what is going on here...what is that wacky token...has someone hacked in and replaced something; how can i fix this? Thanks 2015-07-16 05:35:30.873 [ERROR] [g.openhab.io.net.http.HttpUtil] - Fatal transport error: java.net.UnknownHostException: api.ecobee.com |
|
Hi @milty456 , I don't know for sure, but it would appear that the system on which openHAB is running, or a system upstream to it, has been compromised by some form of malware. Your DNS resolution is failing either due to a temporary situation, or as a result of malware. If I were you, I would quickly attempt to scan your systems for malware. Please feel free to continue discussion on the Google Group if you think there is a problem related to openHAB. |
|
...adding, that the last line of your log may in fact be unrelated to the previous lines, and that your openHAB server is possibly directly accessible to the Internet, and someone is attempting to compromise it. I would carefully consider the security ramifications of making openHAB directly accessible to the Internet. Your openHAB server may not be infected, but it's worth reviewing to make sure. |
|
So I'm trying to SEND a command to change the thermostat from Openhab. Any idea what I'm missing here? I have an item "EcoBeeSetTemp" and i use this: Thanks Log Below 2015-07-18 23:09:36.734 DEBUG o.o.b.e.i.EcobeeGenericBindingProvider[:207]- Processing binding configuration: '>[xxxxxxxxxxxxx#runtime.desiredCool]' |
|
If i change the binding to 2015-07-19 00:12:59.586 DEBUG o.o.b.e.internal.EcobeeBinding[:510]- About to set property 'settings.desiredCool' to '68' |
|
Hi @milty456, in order to change the cooling setpoint, you have to set a hold, which is basically the code version of what is described here. The binding examples in the Ecobee-Binding wiki show |
|
Which file do i need and where do i get it; i expect a jar file as usual, but i don't see one. Sorry I'm not too saavy with this stuff...what do i need to do to add the new action bundle for the binding? Thanks Rich |
|
Hi Rich, please follow the discussion thread here. |
* mult-ecobees-1-acct-bug (PR openhab#2765) * ecobee-celsius-arithmetic-exception (openhab#2793) * ecobee-discard-tokens (PR openhab#2849) * ecobee-echo-cancellation (PR openhab#2942)
* mult-ecobees-1-acct-bug (PR openhab#2765) * ecobee-celsius-arithmetic-exception (openhab#2793) * ecobee-discard-tokens (PR openhab#2849) * ecobee-echo-cancellation (PR openhab#2942)
* mult-ecobees-1-acct-bug (PR openhab#2765) * ecobee-celsius-arithmetic-exception (openhab#2793) * ecobee-discard-tokens (PR openhab#2849) * ecobee-echo-cancellation (PR openhab#2942)
* mult-ecobees-1-acct-bug (PR openhab#2765) * ecobee-celsius-arithmetic-exception (openhab#2793) * ecobee-discard-tokens (PR openhab#2849) * ecobee-echo-cancellation (PR openhab#2942) * changes similar to @teichsta's PR openhab#2967 so actions now appear in Designer; moved messages package out of internal; made ecobeeSetHold temp paramter truly optional.
* mult-ecobees-1-acct-bug (PR openhab#2765) * ecobee-celsius-arithmetic-exception (openhab#2793) * ecobee-discard-tokens (PR openhab#2849) * ecobee-echo-cancellation (PR openhab#2942) * changes similar to @teichsta's PR openhab#2967 so actions now appear in Designer; moved messages package out of internal; made ecobeeSetHold temp paramter truly optional. * Quiesce logging when network failure keeps a poll from completing.
* mult-ecobees-1-acct-bug (PR openhab#2765) * ecobee-celsius-arithmetic-exception (openhab#2793) * ecobee-discard-tokens (PR openhab#2849) * ecobee-echo-cancellation (PR openhab#2942) * changes similar to @teichsta's PR openhab#2967 so actions now appear in Designer; moved messages package out of internal; made ecobeeSetHold temp paramter truly optional. * Quiesce logging when network failure keeps a poll from completing.
* mult-ecobees-1-acct-bug (PR openhab#2765) * ecobee-celsius-arithmetic-exception (openhab#2793) * ecobee-discard-tokens (PR openhab#2849) * ecobee-echo-cancellation (PR openhab#2942) * changes similar to @teichsta's PR openhab#2967 so actions now appear in Designer; moved messages package out of internal; made ecobeeSetHold temp paramter truly optional. * Quiesce logging when network failure keeps a poll from completing.
Problems: (1) Discovered that some users were not entering their OAuth PIN at ecobee.com within the 9-minute window, which was causing an auth token to be persisted that was not usable. When this happens, there is no way to retrieve a new PIN unless the user knew how to find and move or delete the absurdly named and platform-specific Java Preferences file where the bad auth token was stored. (2) Users would then attempt to create a new app at ecobee.com and enter the new
ecobee:appkeyin openhab.cfg. The binding would not realize that theecobee:appkeyhad changed from when the old tokens had been stored, so this was not the solution the user was hoping it would be.Fixes: (1) The binding now discards expired tokens when an attempt to use them to get new tokens fails with "authorization_expired". (2) The binding also now ignores persisted tokens after the user changes
ecobee:appkeyin openhab.cfg, since any persisted tokens will not work against this different app key. The Nest binding does something similar to avoid using invalid persisted tokens.One user discussion and fix is here.
I recommend that this fix be included in OpenHAB 1.7.1. Please let me know if I should or should not merge it into the ecobee-action PR which is currently planned for 1.8.