If Ecobee no longer supports TLS 1.0 (can be checked again at SSL Server Test: api.ecobee.com (Powered by Qualys SSL Labs) but last I checked they only supported TLS 1.2), and UI5 does not support TLS 1.2 (needs some research to be sure but your 1.9 experience presents that as a possibility), then it might be that UI5 can no longer be used. If I were you I would try to again remove and install 1.9 just to get a sense that the plugin installation worked, and have a look at your log file.
watou[/quote]
ecobee did get back to me
tls 1.0 is no longer allowed
I am noticing this error coming up after a day or two. I cannot find anything searching. It seems to go away for a short time after a reboot or creating a new pin.
ecobee : Error: create function not permitted: no valid JSON value (reached the end)
Not sure if it is something just I am seeing or possibly others using the latest @rafale77 fork
[quote=“niharmehta, post:805, topic:174457”]I am noticing this error coming up after a day or two. I cannot find anything searching. It seems to go away for a short time after a reboot or creating a new pin.
ecobee : Error: create function not permitted: no valid JSON value (reached the end)
Not sure if it is something just I am seeing or possibly others using the latest @rafale77 fork[/quote]
This is the problem I described as the intermittent ?ghost? disconnection which goes away by a retry. I doubt that it is unique to my fork because I did not change anything to the communication code from watou and is likely a bug in the ecobee API. The retry loop in case of failure seems to decrease the frequency for me but does not completely eliminate it. When you get the error, just send another command (example change housemode) and it goes away. I am looking at increasing the delay between the retries to see if it helps. Testing is underway.
A quick update on the testing. It appears somehow that the plugin intermittently sends an empty table to the API or that the API believes it is receiving an empty json. I haven’t yet figured out why. I am testing another level of retry. It seems like the empty json occurs only when I am running a scene with a house mode change and many other things at the same time which makes me suspicious of some timing issue. I this still fails, I will test running all of the API calls with a slight delay in my scene to see if it gets rid of the problem. Because it is fairly rare, the problem is taking time to figure out.
I just got a ecobee4 - I first tried 1.9 from vera app store. Tried “get pin” button - no response… waited and again non.
Manually installed latest from github… not have API Key field. I registered as a developer, got an API Key… and now get “ecobee : Error: invalid protocol: no valid JSON value (reached the end)”
Waited, retry, overnight, retry… same message. Uninstalled app, same procedure same error. Tried delete App on ecobee and created new… same error.
Seems like other have gotten it to work IF they already had installed and working… anyone else experience this? Work around?
Would you be able to SSH into the vera and tell me what version of openWRT it is running? I am suspecting that the Vera 3 has not been updated and is running a Stone Age OS which does not support TLSv1.2. In this case I may need to have you do some deeper updates if you want to make it work. I don’t think the problem is related to new Ecobee user. I think it is related to how old your vera is. Even the latest vera units all run 6 year old operating systems.
On the splash screen when you ssh in the line just below the OpenWrt logo should be the version.
It should look something like this:
[code] _______ ________ __
| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -| || | | || || |
|_____|| |||||___||| |____|
|| W I R E L E S S F R E E D O M
@Paulcusick3: Sorry I tried. I the newest version of backfire and openssl are too old to be able to support the security protocol Ecobee now requires. The only thing I can suggest is to install openLuup and move all your automation to a much newer server.
After a week of testing, I am fairly confident to have fixed the json empty error with the beta as I have not observed a single event. For those experiencing it, please try the 2.12b version.