Closed myervin closed 4 months ago
myervin
commented
5 months ago So I modified all the nodes (changed one letter in the name, did a deploy, then changed it back to the original and did a deploy) and they now show up as active in the Connection and are recognized by Alexa. However, unfortunately all those nodes have been deleted from all my Alexa Groups and Routines.
csuermann
commented
5 months ago Hi @myervin,
Thanks for your report. What you describe sounds bizarre. Un-discovering devices (bulkundiscover) only happens explicitly when deploying flows in Node-RED. Not sure what might have triggered this from your environment.
Below is a log of relevant actions originating from your connection in the last 24 hours. I hope you'll find it useful for retracing the series of events.
requestConfig happens when your Node-RED flows start upbulkdiscover happens after your flows start up and contain devices that the server has no records of yet. This action registers the new devices with Alexa.bulkundiscover happens after your flows start up and do no longer contain devices that the server still has records of. This action unregisters these devices from Alexa.| timestamp (UTC) | action |
|---|---|
| 2024-02-05 23:54:11 | requestConfig |
| 2024-02-06 00:02:03 | requestConfig |
| 2024-02-06 00:02:04 | bulkundiscover |
| 2024-02-06 00:02:11 | requestConfig |
| 2024-02-06 00:02:12 | bulkdiscover |
| 2024-02-06 00:03:12 | bulkundiscover |
| 2024-02-06 00:04:31 | requestConfig |
| 2024-02-06 00:05:29 | requestConfig |
| 2024-02-06 00:05:32 | bulkundiscover |
| 2024-02-06 00:06:07 | requestConfig |
| 2024-02-06 00:08:38 | requestConfig |
| 2024-02-06 00:09:47 | requestConfig |
| 2024-02-06 00:12:16 | requestConfig |
| 2024-02-06 00:15:24 | requestConfig |
| 2024-02-06 00:16:04 | requestConfig |
| 2024-02-06 00:16:46 | requestConfig |
| 2024-02-06 00:17:14 | requestConfig |
| 2024-02-06 00:21:07 | requestConfig |
| 2024-02-06 00:21:26 | requestConfig |
| 2024-02-06 00:21:45 | requestConfig |
| 2024-02-06 00:23:26 | requestConfig |
| 2024-02-06 00:24:17 | requestConfig |
| 2024-02-06 00:25:37 | requestConfig |
| 2024-02-06 00:26:02 | requestConfig |
| 2024-02-06 00:26:40 | requestConfig |
| 2024-02-06 00:27:23 | requestConfig |
| 2024-02-06 00:27:51 | requestConfig |
| 2024-02-06 00:29:01 | requestConfig |
| 2024-02-06 00:29:23 | requestConfig |
| 2024-02-06 00:29:52 | requestConfig |
| 2024-02-06 00:30:38 | requestConfig |
| 2024-02-06 00:31:02 | requestConfig |
| 2024-02-06 00:31:25 | requestConfig |
| 2024-02-06 00:31:50 | requestConfig |
| 2024-02-06 00:35:56 | requestConfig |
| 2024-02-06 00:36:39 | requestConfig |
| 2024-02-06 00:37:30 | requestConfig |
| 2024-02-06 00:37:58 | requestConfig |
| 2024-02-06 00:38:30 | requestConfig |
| 2024-02-06 00:40:20 | requestConfig |
| 2024-02-06 00:40:41 | requestConfig |
| 2024-02-06 00:41:12 | requestConfig |
| 2024-02-06 01:05:15 | requestConfig |
| 2024-02-06 01:18:18 | requestConfig |
| 2024-02-06 01:21:23 | requestConfig |
| 2024-02-06 02:41:28 | requestConfig |
| 2024-02-06 02:41:29 | bulkdiscover |
| 2024-02-06 02:42:27 | requestConfig |
| 2024-02-06 02:42:27 | bulkdiscover |
| 2024-02-06 02:58:28 | requestConfig |
| 2024-02-06 03:16:30 | requestConfig |
| 2024-02-06 03:16:31 | bulkundiscover |
| 2024-02-06 03:34:14 | requestConfig |
| 2024-02-06 03:34:15 | bulkdiscover |
| 2024-02-06 03:35:19 | requestConfig |
| 2024-02-06 03:35:47 | requestConfig |
| 2024-02-06 03:35:47 | bulkdiscover |
| 2024-02-06 03:38:44 | requestConfig |
| 2024-02-06 03:38:45 | bulkundiscover |
| 2024-02-06 03:38:45 | bulkdiscover |
| 2024-02-06 03:39:37 | requestConfig |
| 2024-02-06 03:39:38 | bulkdiscover |
| 2024-02-06 03:40:56 | requestConfig |
| 2024-02-06 03:40:57 | bulkdiscover |
| 2024-02-06 03:41:15 | requestConfig |
| 2024-02-06 03:41:16 | bulkdiscover |
| 2024-02-06 03:44:00 | requestConfig |
| 2024-02-06 03:44:01 | bulkdiscover |
| 2024-02-06 03:47:13 | requestConfig |
| 2024-02-06 03:47:14 | bulkdiscover |
| 2024-02-06 03:47:31 | requestConfig |
| 2024-02-06 03:47:32 | bulkdiscover |
| 2024-02-06 04:09:30 | requestConfig |
| 2024-02-06 04:09:31 | bulkdiscover |
| 2024-02-06 04:10:17 | requestConfig |
| 2024-02-06 04:10:18 | bulkdiscover |
| 2024-02-06 07:07:51 | requestConfig |
| 2024-02-06 07:07:52 | bulkdiscover |
| 2024-02-06 07:10:03 | requestConfig |
| 2024-02-06 07:10:36 | requestConfig |
| 2024-02-06 07:10:59 | requestConfig |
| 2024-02-06 07:19:08 | requestConfig |
| 2024-02-06 07:34:44 | requestConfig |
| 2024-02-06 07:35:32 | requestConfig |
| 2024-02-06 07:36:40 | requestConfig |
| 2024-02-06 07:39:17 | requestConfig |
| 2024-02-06 07:40:00 | requestConfig |
| 2024-02-06 07:40:28 | requestConfig |
| 2024-02-06 07:41:38 | requestConfig |
| 2024-02-06 07:52:00 | requestConfig |
| 2024-02-06 08:01:35 | requestConfig |
| 2024-02-06 08:07:24 | requestConfig |
| 2024-02-06 08:08:16 | requestConfig |
| 2024-02-06 08:08:40 | requestConfig |
| 2024-02-06 08:09:11 | requestConfig |
| 2024-02-06 08:10:15 | requestConfig |
| 2024-02-06 08:11:09 | requestConfig |
| 2024-02-06 08:11:59 | requestConfig |
| 2024-02-06 08:12:27 | requestConfig |
csuermann
commented
4 months ago @myervin, Please note that a newer version of VSH has been published containing several reliability improvements. It recommend you update to it.
myervin
commented
4 months ago Cornelius, thank you for your support, I found some corruption in my node-red files that I believe may have been part of the problem as well. It has been ok since I fixed that issue.Regards,Rob -------- Original message --------From: Cornelius Suermann @.> Date: 2/27/24 1:26 AM (GMT-06:00) To: csuermann/node-red-contrib-virtual-smart-home @.> Cc: myervin @.>, Mention @.> Subject: Re: [csuermann/node-red-contrib-virtual-smart-home] Alexa stopped recognizing my VSH nodes (Issue #238) @myervin, Please note that a newer version of VSH has been published containing several reliability improvements. It recommend you update to it.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>
Describe the bug Suddenly Amazon stopped recognizing my VSH nodes today, somewhere between 16:00 and 19:00 CST. No changes were made to my node-red flow that I am aware of. I have about 36 VSH nodes. All say they are "online" with a green status lamp, but Amazon has lost knowledge of them. When I look at my "Connection" in a node, it shows I have a PRO plan but no registered devices. If I drag a new VSH node onto the palette it is quickly recognized by Amazon and appears as a registered device in the node. If I make a minor change to a node and deploy, it is then recognized. I have disabled the VHS Skill and relinked with no joy. My subscription is paid up and expires on March 28. I can go thru and reactivate all my nodes by making changes and redeploying, but was wondering why this might have happened.
To Reproduce Steps to reproduce the behavior:
Expected behavior A clear and concise description of what you expected to happen.
Screenshots If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
Additional context Add any other context about the problem here.