-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issues after being down for a couple months. #27
Comments
Just some additional info. I downloaded the SAM for that function The alexa client ID and Secret are the same as in the "Permissions" tab of the Alexa skill. I just don't know where the breakdown is. |
So I took the plunge and updated everything.
|
Hi @turbo2ltr, Have you checked your DynamoDB table? My hunch is that your user record got auto-deleted after inactivity. You should be able to fix this by just creating a new VSH-connection. Make sure you configure your Node-RED instance to (again) use your own backend. Hope that helps. Best, |
Ahh dang, I should have waited before I blew everything away. I did look at the Dynamo DB, but I also didn't know what should be in there. All I saw was my devices which seemed like it was working. |
You'd have to know your Amazon User ID, so I guess manually recreating the record wouldn't work. But creating a new VSH-connection as I pointed out should do the trick. |
Are you sure your Node-RED is talking to your backend and not mine? After going through the account linking process, there should be a TOKEN record in the VSH DynamoDB table. |
Yeah I give up. I have like 10+ hours into this now.. I deleted everything out of my AWS and tried to start completely over, but serverless refuses to complete complaining about running out of memory. (Fresh alpine VM with 2gb of memory) Also there is nothing in the instructions about having to modify
|
Indeed, the VSH backend was never optimized for self-hosting and setting it up is not straight forward. Perhaps you want to consider using the official VSH backend?! ;-) |
I'm running version 2.0.3 in a node red docker container with my own AWS back end and everything was working fine when I moved.
I'm set up in the new house and I'm trying to figure out why alexa commands to virtual devices are not working.
In NodeRed, I get "user not found! Is VSH skill enabled?" next to virtual devices. I went checked everything and not seeing any issues.
The virtual devices show up in my alexa app, but says "server is unresponsive".
In the VSH AWS IoT thing I'm seeing Connected, Subscribed, Shadow Updated, Disconnect messages when I restart the flow. But no further messages appear.
If I refresh the token in the connection setup in NodeRed, it seems to update just fine. All my registered devices are there.
I went through my VSH Skill settings in the Developer console and all seems fine.
So I'm really confused why it stopped working or exactly what "user" it is talking about. Essentially I unplugged it from one house and plugged it into another, but clearly something broke.
Also I'm unclear what this "momento" thing is that is required. I don't recall ever doing that.
Really don't have the time to do a full node red upgrade required to run the latest version of VSH. The rabbit hole is already way deeper than I was prepared for for today.
The text was updated successfully, but these errors were encountered: