cakebake / node-red-contrib-alexa-remote-cakebaked

Forked for me and the community to keep dependencies up to date :)
MIT License
42 stars 6 forks source link

smarthome entity not found #4

Closed tdejneka closed 3 years ago

tdejneka commented 3 years ago

Just switched from the now non-functional node-red-contrib-alexa-remote2 to node-red-contrib-alexa-remote-cakebaked. My existing flow (which used to work with remote2 prior to the recent failure) reports:

smarthome entity not found

Node-red debug screenshot: Screenshot from 2021-02-23 15-11-06

The SmartHome Action node receives the correct commands (first message in the screenshot) but the response to the request is a failure to find the entity.

Living Room Light is one of several devices that has been discovered and registered by Alexa: Screenshot from 2021-02-23 15-19-47

Let me know what additional information may be required to debug this issue.

tdejneka commented 3 years ago

Here's more information.

I tried this simple flow:

Screenshot from 2021-02-23 15-41-53

Where Smarthome Turn On is configured like this:

Screenshot from 2021-02-23 15-40-44

The result is "unexpected response layout":

Screenshot from 2021-02-23 15-42-31

tdejneka commented 3 years ago

I just examined the node-red/node_modules directory and can confirm it does not contain node-red-contrib-alexa-remote2 which I had removed via the UI (after deleting all instances of its nodes from my flow).

The directory contains a node-red-contrib-alexa-remote-cakebaked sub-directory but I noticed it also contains an alexa-remote2 sub-directory. Is that correct or is it a leftover that is possibly interfering with the cakebaked version?

MattL0 commented 3 years ago

Here i use the other fork( cliked on this one first). The directory alexa-remote-2 is outside the alexa-remotecontrib[..]fork directory (directly in nodered nodes_module directory)

tdejneka commented 3 years ago

The directory alexa-remote-2 is outside the alexa-remotecontrib[..]fork directory

Yes, that's what I mentioned in my previous post. What I see is this:

/usr/share/hassio/homeassistant/node-red/node_modules/alexa-remote2
/usr/share/hassio/homeassistant/node-red/node_modules/node-red-contrib-alexa-cakebaked

The contents of alexa-remote2

drwxr-xr-x   4 root root  4096 Feb 22 12:36 .
drwxr-xr-x 153 root root  4096 Feb 22 12:36 ..
-rwxr-xr-x   1 root root 96676 Oct 26  1985 alexa-remote.js
-rwxr-xr-x   1 root root 22564 Oct 26  1985 alexa-wsmqtt.js
drwxr-xr-x   2 root root  4096 Feb 22 12:36 example
-rw-r--r--   1 root root  1150 Oct 26  1985 LICENSE
drwxr-xr-x   3 root root  4096 Feb 22 12:36 node_modules
-rw-r--r--   1 root root  2003 Feb 22 12:36 package.json
-rw-r--r--   1 root root 11007 Oct 26  1985 README.md

My question is the alexa-remote2 directory a leftover from node-red-contrib-alexa-remote2 or is it employed by node-red-contrib-alexa-remote-cakebaked?

If it's a leftover then does it potentially interfere with node-red-contrib-alexa-remote-cakebaked?

tdejneka commented 3 years ago

So to answer my own question: No, it's not a leftover but a part of node-red-contrib-alexa-remote-cakebaked.


I reconfigured the freshly re-installed node-red-contrib-alexa-remote-cakebaked but it still fails to work:

Screenshot from 2021-02-24 17-22-28

Any guidance to resolve this would be appreciated.

bwims commented 3 years ago

This is not a true fork, as I understand it. Cakebaked has generously taken the code and made necessary changes so that after installation everything was as before, with updates.

My guess is this is a regional problem. I suspect Amazon are rolling out changes on a staggered basis and don't care about non-monetised developers making something useful.

Which country are you logging in to? If not UK or US, could you try one of those? I might be completely wrong, but it seems to be a factor in Issue - https://github.com/cakebake/node-red-contrib-alexa-remote-cakebaked/issues/3

tdejneka commented 3 years ago

Which country are you logging in to?

US

tdejneka commented 3 years ago

From the lack of replies, I now understand what you meant by "not a true fork". This repo only serves as a means of distributing updated libraries for node-red-contrib-alexa-remote2 and nothing more.

Neither repo's product works for me so I'll have to look for an alternative.