This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
CC3220SF: TIDM-1020: Smart Config Fail?
Part Number: CC3220SF
After fixing the lambda handler to "lambda.lambda_handler", Alexa App was able to discover the Thermostat. But when I say "Alexa set Thermostat to 28". It replied back "Sorry, Thermostat is not responding".
But, I see this at Tera Term log below
"Delta - target setpoint changed from the cloud!"
So, seems its working
Do, click "This Resolved my issue", if any of my replies helps solve your problem. For Tiva ARM Forum, see links below.
TM4C123 NMI unlock - To those who want to use PF0 and PD7, be reminded that these pins default as NMI ! ! !
JTAG Communication Failures
Featured Blog Projects: Create Bluetooth Projects using TI CC2640R2F Launchpad Online Course, Adding Bluetooth Connectivity to DPS3005 Programmable Power Supply using TI CC2640R2F BLE MCU, Bluetooth Low energy Point Of Sale using TI CC2652RB Simplelink™ Crystal-less BAW Wireless MCU, TI CC2640R2F Eddystone Beacon, Bluetooth Low Energy Game Controller, Bluetooth Low Energy Power Bank, Secure Internet Of Things Humidifier
Company Projects: FOBO Tag - World’s 1st Patented Bluetooth 5 Tracker
I suggest you take a look at the lambda logs on cloudwatch to see what may have gone wrong in your test. The logs should display the received Alexa directive as well as the response passed back for every Alexa request you make.
If you look at the response given back and compare that to the expected Alexa schema, do you see anything obviously wrong there?
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
In reply to Michael Reymond:
I see the cloudwatch logs but I am not familiar with it. But at CCS debug I was able to confirm the targetSetpoint variable changed, so it works.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.