Error Saving Page on SmartApp Setup (No devices installed)

[yuckypants]

I searched and found 2 nearly identical posts, related to my exact issue.

I followed the directions verbatim: configured the device handlers and smartapps on the IDE using the github repo. I successfully installed the Ecobee (Connect) SmartApp, added my thermostats, and configured preferences. However, when I click "Done", I get an "Error Saving Page" message. No devices are actually installed in "Things."

I'm on Android 7.1 and have confirmed OAuth is enabled under the "My SmartApps" tab in the IDE. I also removed ALL of the code and re-added using the manual settings, just to be certain. I merged the code with the repo and it's current again. So then I viewed the "Live Logging" page and found the following errors:

pollEcobeeAPI(): General Exception: java.lang.NullPointerException: Cannot get property 'value' on null object.

refreshAuthToken(), General Exception: java.lang.NullPointerException: Cannot get property '4ce3fe7e-6f7a-4f83-9e96-aa3a118dca37.411932355850' on null object.

Lastly, and I hope this is not important, but I want you to be aware prior to troubleshooting - I'm using two of the new EcoBee3 Lite models. So I don't have Ecobee external sensors, and I've yet to fully configure the ST sensors as external sensors (I have some other code that's supposed to handle it, it's just overriding my routines).

Looking forward to a reply!

Ecobee (Connect) Log.txt

[ascottmccauley]

Same problem here. Also have the Ecobee Lites.
Same error descriptions.

[yuckypants]

There is literally zero support for this app. I use the paid version from mracine that accomplishes so much more. Give up - not a single reply from this guy since dec.

[ncsufire]

He is providing a free app that he spent time on with no compensation. He may have other stuff going on with a paid job or got tired of supporting a program on an unstable platform like ST. This happens a lot with programmers here.

…

On Mar 8, 2017 7:13 PM, "yuckypants" ***@***.***> wrote: There is literally zero support for this app. I use the paid version from mracine that accomplishes so much more. Give up - not a single reply from this guy since dec. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#76 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/APws2177C80b2b8jIKCVoKM_HhZtTI_eks5rj0Q7gaJpZM4Lo47_> .

[yuckypants]

Oh I'm not badmouthing the guy, in another thread he said he's busy. I'm just saying don't hold your breath. By the time he gets it working, ST changes something and it breaks again. He's unable to support it, so go with someone else who does.

[StrykerSKS]

I don't have a Lite version, so it is nearly impossible for me to quickly fix this. SmartThings hadn't broken anything in a long time with any changes.

I'm sorry that I haven't been able to update to include the Lite version yet. But this does work well for over 500 users at the moment.

But the code is all there, so if someone tracks down the fault that would make it easier to address.

That was one of my main reasons for releasing open source so that others can also contribute.

[MuggleMarc]

I'm running into this issue as well. I don't suppose there's been any progress on a solution? Not smart enough to debug this on my own, I'm afraid.

[MuggleMarc]

I think I found the issue. In updateThermostatData(), round about line 1427, I changed 2 lines:

	LOG("updateThermostatData() - occupancyCap = ${occupancyCap} value = ${occupancyCap?.value}")
    
	// Check to see if there is even a value, not all types have a sensor
	occupancy =  occupancyCap?.value ?: "not supported"

Looks like the "?" was missing after occupancyCap in both of those lines. My guess (and it's just a guess, I'm a complete noob with this), is that the Ecobee3 Lite doesn't support occupancy information, so was returning a null for occupancyCap.

Adding those 2 "?" seems to have fixed the problem.... the thermostat device gets created and appears to function correctly.