I just tried this in the SS:
“set great room heating setpoint to 66”
Log shows:
6:36:12 PM: debug I could not process your request for the ‘great room’. Ensure you are using the correct commands with the device.
6:36:11 PM: debug Param: heating
6:36:11 PM: debug Num: undefined
6:36:11 PM: debug Op: 66
6:36:11 PM: debug Dev: great room
6:36:11 PM: debug -Device command received-
6:36:11 PM: debug --Begin commands received–
Looks like 66 is going into OP instead of NUM.
@MichaelS, it seems that this problem is not unique to the ecobee thermostats.
I can now reach my endpoints (AWS was down for a while)…
I’ve tried with my basement stelpro and it does not work as well.
Here is what I get in the Ask Alexa logs:
Set basement stelpro to 18
bug I could not process your request for the ‘basement stelpro’. Ensure you are using the correct commands with the device.
4ce5f887-ea3d-4a1a-a010-c27a10ccd4a5 9:38:47 PM: debug Type: thermostat
4ce5f887-ea3d-4a1a-a010-c27a10ccd4a5 9:38:47 PM: debug Param: undefined
4ce5f887-ea3d-4a1a-a010-c27a10ccd4a5 9:38:47 PM: debug Num: undefined
4ce5f887-ea3d-4a1a-a010-c27a10ccd4a5 9:38:47 PM: debug Op: 18
4ce5f887-ea3d-4a1a-a010-c27a10ccd4a5 9:38:47 PM: debug Dev: basement stelpro
4ce5f887-ea3d-4a1a-a010-c27a10ccd4a5 9:38:47 PM: debug -Device command received-
Set basement stelpro to heat
4ce5f887-ea3d-4a1a-a010-c27a10ccd4a5 9:38:47 PM: debug --Begin commands received–
4ce5f887-ea3d-4a1a-a010-c27a10ccd4a5 9:38:38 PM: debug I could not process your request for the ‘basement stelpro’. Ensure you are using the correct commands with the device.
4ce5f887-ea3d-4a1a-a010-c27a10ccd4a5 9:38:38 PM: debug Type: thermostat
4ce5f887-ea3d-4a1a-a010-c27a10ccd4a5 9:38:38 PM: debug Param: heat
4ce5f887-ea3d-4a1a-a010-c27a10ccd4a5 9:38:38 PM: debug Num: undefined
4ce5f887-ea3d-4a1a-a010-c27a10ccd4a5 9:38:38 PM: debug Op: undefined
4ce5f887-ea3d-4a1a-a010-c27a10ccd4a5 9:38:38 PM: debug Dev: basement stelpro
4ce5f887-ea3d-4a1a-a010-c27a10ccd4a5 9:38:38 PM: debug -Device command received-
4ce5f887-ea3d-4a1a-a010-c27a10ccd4a5 9:38:38 PM: debug --Begin commands received–
However, the report status works well.
basement stelpro status
4ce5f887-ea3d-4a1a-a010-c27a10ccd4a5 9:38:24 PM: debug The basement stelpro temperature reading is currently 18.5 degrees, and the thermostat’s mode is: ‘comfort’. The relative humidity reading is 88%. The thermostat is currently idle. The heating setpoint is set to 16 degrees.
Regards.
OK. Looking into this when I get to my computer.
Ok…I tried the following:
set nest thermostat to sixty three degrees
The result I got was as follows:
I am setting the heating setpoint of the nest thermostat to 63 degrees.
This is odd just in itself as I DIDN’T set the heating or cooling parameter in my statement…then I remembered I set the code to look for what mode you are in and set the appropriate setpoint. The ONLY time you need to set the heating and cooling now should be when you are in auto mode, which actually has two setpoints that can be set.
This does NOT explain what is happening with the parameters going into the wrong slots. That almost feels like an Amazon issue…
For your issue, I did set my thermostat to auto mode and did the following:
set nest thermostat to sixty three degrees
At first, I got the same result verbal response as before that it was setting the heating temp, but the heat did NOT get turned up…This was because the thermostat DTH did NOT refresh from when it was just in heating mode, which is a common problem with WiFi thermostats. I refreshed the device and ran it again, with the result being:
You must designate a ‘heating’ or ‘cooling’ parameter when setting the temperature. The thermostat will not accept a generic setpoint in its current mode. For example, you could simply say, ‘ask SmartThings to set the nest thermostat heating to 65 degrees’.
Exactly what I would expect…
So the next test:
set nest thermostat to sixty three degrees heating
and the result:
I am setting the heating setpoint of the nest thermostat to 63 degrees
Again, what I would expect (I am typing these end to eliminate the chance Alexa is misunderstanding). Notice I put the heating at the end.
Here is my log entries:
8:38:57 PM: debug I am setting the heating setpoint of the nest thermostat to 63 degrees.
8:38:57 PM: debug Param: heating
8:38:57 PM: debug Num: 63
8:38:57 PM: debug Op: undefined
8:38:57 PM: debug Dev: nest thermostat
Trying more like your verbiage:
set nest thermostat heating setpoint to sixty four degrees
I get the following:
8:42:10 PM: debug I am setting the heating setpoint of the nest thermostat to 64 degrees.
8:42:09 PM: debug Param: heating
8:42:09 PM: debug Num: 64
8:42:09 PM: debug Op: undefined
8:42:09 PM: debug Dev: nest thermostat
So again, I can’t confirm why this happening…The ONLY thing I can think of is that there were some lingering AWS issues, or you have a device or something else that could be conflicting with the logic in the app.
Let’s take this offline and work on it. The fact that Yvees is seeing the same issue is strange, but on the same day half the internet was down takes everything off of the table.
Thanks for your patience, but the good thing is I think that this is easily fixed. As you continue your testing I would ensure your DTH is refreshed to match the actual device as the polling rate is different. In addition, I recommend turning OFF the Ecobee switch in the settings area just to see if that helps…While I have a Nest what you and I are using should utilize the standard code I haven’t changed in months for the thermostats.
I have the latest code for the SmartApps, but when i go into configure a new Voice Macro, i can’t get out of the Voice Macro, i hit done and it gets completed out of the Smart App. Is this an issue or do i need to do something different?
If you go back into the app does it show the macro was created. Because of the combined parent/child app structure this is one of the side effects but doesn’t affect the operation if the macro was created. I typically use the < button instead of pressing Done.
Let me know when you are seeing.
Hi Michael,
If I send the exact command to my CT30 and my basement stelpro thermostats (not ecobee), I get
the same errors in the Ask Alexa app:
Here is the result for my bedroom thermostat:
set bedroom thermostat to twenty three degrees heating
4ce5f887-ea3d-4a1a-a010-c27a10ccd4a5 5:51:54 PM: debug --Begin commands received–
4ce5f887-ea3d-4a1a-a010-c27a10ccd4a5 5:48:00 PM: debug I could not process your request for the ‘bedroom thermostat’. Ensure you are using the correct commands with the device.
4ce5f887-ea3d-4a1a-a010-c27a10ccd4a5 5:48:00 PM: debug Type: thermostat
4ce5f887-ea3d-4a1a-a010-c27a10ccd4a5 5:48:00 PM: debug Param: heating
4ce5f887-ea3d-4a1a-a010-c27a10ccd4a5 5:48:00 PM: debug Num: 23
4ce5f887-ea3d-4a1a-a010-c27a10ccd4a5 5:48:00 PM: debug Op: undefined
4ce5f887-ea3d-4a1a-a010-c27a10ccd4a5 5:48:00 PM: debug Dev: bedroom thermostat
4ce5f887-ea3d-4a1a-a010-c27a10ccd4a5 5:48:00 PM: debug -Device command received-
Here is the result for my basement Stelpro thermostat:
set basement stelpro to twenty three degrees heating
4ce5f887-ea3d-4a1a-a010-c27a10ccd4a5 5:51:56 PM: debug I could not process your request for the ‘basement stelpro’. Ensure you are using the correct commands with the device.
4ce5f887-ea3d-4a1a-a010-c27a10ccd4a5 5:51:56 PM: debug Type: thermostat
4ce5f887-ea3d-4a1a-a010-c27a10ccd4a5 5:51:56 PM: debug Param: heating
4ce5f887-ea3d-4a1a-a010-c27a10ccd4a5 5:51:56 PM: debug Num: 23
4ce5f887-ea3d-4a1a-a010-c27a10ccd4a5 5:51:56 PM: debug Op: undefined
4ce5f887-ea3d-4a1a-a010-c27a10ccd4a5 5:51:56 PM: debug Dev: basement stelpro
4ce5f887-ea3d-4a1a-a010-c27a10ccd4a5 5:51:56 PM: debug -Device command received-
4ce5f887-ea3d-4a1a-a010-c27a10ccd4a5 5:51:54 PM: debug --Begin commands received–
So, I guess the problem is at the thermostat level, not at the ecobee level.
By the way, I don’t have any problems getting the status of both thermostats.
{
“response”: {
“outputSpeech”: {
“type”: “PlainText”,
“text”: "The bedroom thermostat temperature reading is currently 19.2 degrees, and the thermostat’s mode is: ‘off’. The thermostat is currently idle. The heating setpoint is set to 10 degrees. Anything else? "
},
“card”: {
“content”: "The bedroom thermostat temperature reading is currently 19.2 degrees, and the thermostat’s mode is: ‘off’. The thermostat is currently idle. The heating setpoint is set to 10 degrees. Anything else? ",
“title”: “SmartThings Devices”,
“type”: “Simple”
},
“shouldEndSession”: false
},
“sessionAttributes”: {}
}
Regards.
OK, further testing…
When I check off the Device Specific commands for the Stelpro And the Ecobee thermostats, I can
then send the above commands without any issues.
As soon as I check on the Stelpro or the ecobee thermotat’s specific commands, it no longer works:
Without any specific thermostat commands:
4ce5f887-ea3d-4a1a-a010-c27a10ccd4a5 6:41:58 PM: debug --Begin commands received–
4ce5f887-ea3d-4a1a-a010-c27a10ccd4a5 6:41:35 PM: debug I am setting the heating setpoint of the bedroom thermostat to 23 degrees.
4ce5f887-ea3d-4a1a-a010-c27a10ccd4a5 6:41:35 PM: debug Type: thermostat
4ce5f887-ea3d-4a1a-a010-c27a10ccd4a5 6:41:35 PM: debug Param: heating
4ce5f887-ea3d-4a1a-a010-c27a10ccd4a5 6:41:35 PM: debug Num: 23
4ce5f887-ea3d-4a1a-a010-c27a10ccd4a5 6:41:35 PM: debug Op: undefined
4ce5f887-ea3d-4a1a-a010-c27a10ccd4a5 6:41:35 PM: debug Dev: bedroom thermostat
4ce5f887-ea3d-4a1a-a010-c27a10ccd4a5 6:41:35 PM: debug -Device command received-
With the stelpro specific thermostat commands on:
4ce5f887-ea3d-4a1a-a010-c27a10ccd4a5 6:41:35 PM: debug --Begin commands received–
4ce5f887-ea3d-4a1a-a010-c27a10ccd4a5 6:40:54 PM: debug I could not process your request for the ‘bedroom thermostat’. Ensure you are using the correct commands with the device.
4ce5f887-ea3d-4a1a-a010-c27a10ccd4a5 6:40:54 PM: debug Type: thermostat
4ce5f887-ea3d-4a1a-a010-c27a10ccd4a5 6:40:54 PM: debug Param: heating
4ce5f887-ea3d-4a1a-a010-c27a10ccd4a5 6:40:54 PM: debug Num: 23
4ce5f887-ea3d-4a1a-a010-c27a10ccd4a5 6:40:54 PM: debug Op: undefined
4ce5f887-ea3d-4a1a-a010-c27a10ccd4a5 6:40:54 PM: debug Dev: bedroom thermostat
4ce5f887-ea3d-4a1a-a010-c27a10ccd4a5 6:40:54 PM: debug -Device command received-
I hope that it helps…
Regards.
I was able to finally get it to work, i kept hitting the < but i add to delete all of my macros and then re-add it, and i re-add it w/ just the name first and then came back in and then editted it again. And it was finally able to work.
Very odd, but I am glad you got it all working.
Enjoy!
Ah…so you believe it is the StelPro commands…interesting…I will test that tonight!. I REALLY appreciate the additional troubleshooting on my behalf.
@M3Rocket Can you verify that you have any of these other specific devices on in Settings>>Device Specific Commands? If not, what if you simply turn off Ecobee commands temporarily…does that work? If so I know exactly where to look.
No, what I wrote above is that if you have any specific device commands checked on (either Stelpro or ecobee), it won’t work.
Regards.
Ah…Ok…I think we are saying the same thing, and DOES tell me where the issue might be. Either way, I am looking into it tonight!
Ok…I was able to reproduce this…however, if you look closely at your thermostat it IS reacting to the commands…it is just the feedback that is incorrect…
This will be fixed by the next release (scheduled for Friday). Will post if there is an interesting explanation outside of there just being a logic issues.
Yes–I have both ecobee commands setting on. Will try turning off and running the SS later tonight when I have access to my laptop.
Ok…I did find the issue…it is inadvertently sending commands to the device that it can’t accept…and there is a global trap if ANY errors coming through in the response…I am reworking this now. I really appreciate you bringing this to my attention.
Ok…this was fixed…the specific command that was triggering this (the stelPro.applyNow) is now trapped specifically. No verbal error is given but a note is put into the log. People with multiple types of specialized thermostats in their household will encounter this only.
This is the same with Ecobee devices…if you DON’T have them and you have those settings set (or you have different types in your environment) it fails. Now it just warns you in the IDE logging.
Again, thanks @M3Rocket and @yvesracine for helping to troubleshoot.
OK–I was just going to say I just tested with the device specific commands off, and it indeed did fix the problem. Nice catch @yvesracine!
Thanx for the quick fix @MichaelS!
No problem…fixes coming probably on Friday.
And the new version has been released: