@Drewbert34, please check at the ecobee portal to determine if occupancy was changed and properly reported by the remote sensors during these hours.
It also depends on the polling interval that you have specified in the smartapp (by default 30 minutes).
My code just updates the Motion Sensor created in SmartThings according to the data provided by ecobee. If the data is not accurate, the Motion Sensor will report the same data.
As I said earlier in this thread, ecobee3’s motion Sensors are not as accurate as temp Sensors, see this thread for more details:
None of my sensors report movement in ST but they do at the thermostat. In this example I’m referring to the “office” which is lower most on the thermostat
You may already have this fixed with the above but I wanted to send you what I’m seeing thus far:
Motion Alerts:
3545764c-c957-460f-8953-1ab3f1352fad 6:49:31 PM: trace motion.active from Ecobee3 Motion Office was provided with motionActiveHandler…creating subscription
3545764c-c957-460f-8953-1ab3f1352fad 6:49:31 PM: trace subscribing to [Ecobee3 Motion Office]
3545764c-c957-460f-8953-1ab3f1352fad 6:49:31 PM: trace Motion Alerts is attempting to unsubscribe from all events
3545764c-c957-460f-8953-1ab3f1352fad 6:49:31 PM: trace Motion Alerts updated with settings: [modes:[Home Day, Home Night], pushNotification:true]
OK, got an answer from ecobee (that was pretty quick this time!)…
Here it is:
Hesham Fahmy (Official Rep) 15 minutes ago
Our apologies, but our documentation should have been made clearer to clarify that remote sensor data is only reported by thermostats with a firmware version of 3.6 and higher. Earlier versions of the firmware are not reporting the sensor data upstream.
In your code check the value of Thermostat->Version-> thermostatFirmwareVersion.
The 3.6 firmware version will be rolling out to all thermostats shortly. An official announcement regarding this will be made soon.
So, at the moment, occupancy data is not accurate at all.
My apologies to all, I was not aware of it…And, I spent a lot of time debugging with people (especially @Drewbert34) for nothing…
Thanks @yvesracine and @Drewbert34 for your work. After a long day of work and an evening of meetings I was all ready to crack open a drink and dig into this.
A quick note to anyone else watching this thread, the iphone app for Ecobee does have the firmware version listed under ABOUT from the main menu. I am still at version 3.5.x. Will be watching and will report back when I see the update.
Just to confirm - I have all the same results as @Drewbert34. Temp is working, motion is not, anxious to see if we can read humidity soon.
doing this on an iphone
updated the devices and forced close the ST app after to make sure everything was gone (even deleted the app and brought it back)
but i get the same problem as someone listed above, get into init, select my thermostat, leave interval at default and then click next and its just a blank window and errors if i hit next…
live log shows this
1b9e2b82-172a-4cd9-983f-1a0cc2214834 11:01:24 PM: error groovy.json.JsonException: A JSON payload should start with an openning curly brace ‘{’ or an openning square bracket ‘[’.
Instead, ‘null’ was found on line: 1, column: 1 @ line 75
d5fc63de-739a-4013-b9bf-6d5d59972f70 11:01:24 PM: error java.lang.NumberFormatException: For input string: “unknown” @ line 2747
@a2thejay23, for this issue, the cause is one of the following:
for some reason, the My ecobee Device type was not updated correctly.
Grab the code at
Make sure to Save and publish.
Your old device is still in the cache. And you need to delete your OS
cache again…I know how to do it in Android, but not on an Iphone. Usually
you need to go under your OS menu, select the app, and clear the associated
cache for it.
To know what’s going on, just activate the live logging and get more tracing
in the IDE by following these steps:
From what I know on an iPhone the only way to clear app cache is to delete it and re-install it. This isn’t too much of an issue except I am not sure if you will lose all of the tiles or “things”. YMMV.
Hey jay, may be a day late and a dollar short to this party but what I did to get it going was to go to the code for the device type in the IDE, drop line 2747 down one, and type the word “continue” in line 2747, like this:
@antolope, if you have a blank page error within ecobee3RemoteSensorInit, there are 2 potential causes:
The device type has not been updated correctly within the IDE.
You must grab the latest device type code at github:
And, don’t forget to save & publish.
The old device type is still in the cache.
If you have an android device, you must go to the settings/app, scroll down to the smartThings app, and
clear the cache. If you have an iOS device, I’ve been told that you need to reinstall the smartThings app.
P.S. You do not need to modify any code in the IDE, as you may encounter other errors later.
Hey Yves, first, I reverted the changes I made back to your original code. I then deleted the app on my iPhone and reinstalled it.
You were correct, deleting and reinstalling the app allowed me to get past the blank page error with no code modifications on my part. All sensors have been picked up and installed.
Moral of the story, if the directions have been followed properly on an iPhone and the blank page error is coming up, uninstall and reinstall the SM app and that should take care of it.
Hi @yvesracine when launching the ecobee3RemoteSensorInit app I get a “Failed to save page: Notifications” message in the mobile app.
I also get the following message in the IDE logs: 10:12:24 AM EDT: error physicalgraph.app.exception.UnknownDeviceTypeException: Device type ‘Motion Detector’ in namespace ‘smartthings’ not found. @ line 187
@huydnguyen, please make sure to follow all the steps in the readme.ecobee3RemoteSensorInit
Refer to
You seem to have skipped the step no 3, and more specifically substeps g,h and i) to create the Motion Sensor object.
As far as the ‘Failed to save page: notifications’ is concerned, I think that this could be a momentary ST issue. Please retry, and if you encounter this issue again, please PM me any errors in the logs.
I did do step 3, only thing was the template for motion sensor was called “motion detector”. But i found my error. I renamed the devices to “EcoBee3 Remote Temp” and “EcoBee3 Remote Motion” so i knew later on why i had those devices Guess it didn’t like that.
@huydnguyen, please do not rename the device types (Temperature & Motion Sensors) as they will be instantiated by my ecobee3RemoteSensorInit smartapp for your specific remote sensors.
If you rename them, my smartapp won’t be able to create these objects for you.
Guess it didn’t like that.