Been having issues with my Echo->CQC integration for some time, finally had time to dig into it. Can't figure out what's wrong, keep getting 'difficulty communicating with the skill' from the Echo.
Is this still working for people?
No one has been complaining about it, so I assume it's basically still happy. Anyone else had any issues?
Has this skill been around for a long time? If so, did you update it to use the more recent node.js? They deprecated the version everyone was originally using a while back, and may have turned it off altogether now.
(01-13-2018, 09:38 AM)Dean Roddey Wrote: [ -> ]Has this skill been around for a long time? If so, did you update it to use the more recent node.js? They deprecated the version everyone was originally using a while back, and may have turned it off altogether now.
Um, say the what to the whom?
Remind me, is that node.js the CQC portion that I copy/pasted in?
One of the settings on the skill is to select which underlying engine should be used on the Amazon side. The skills use node.js, but they made a more recent version of it available a little while back. Everyone was supposed to update to that. It's just a selection you make, no code changes or anything. There isn't any change required in the skill javascript.
I use it multiple times a day, and IÔÇÖve not had any issues.
yeah somehow it got blanked out for my skill. I may have not updated it and it may have finally been deprecated.