Purpose of this page

Many users regularly ask the same questions, without necessarily bothering to read Community, to have a reference page of Cookie or Demon worries, here is everything you need to respect and how to get out of potential worries.

Working principle of the Alexa-API plugin

This plugin interacts with the Amazon server by pretending to be a web browser.

To do this, it needs this browser to be identified with your email/login. It is obviously excluded for security reasons to store your login/password in Jeedom.

We will therefore ask you to identify yourself once, at that time, the generated cookie is recovered by the plugin, it is saved in a json file in the data folder of the plugin.

As this cookie has a lifetime, the plugin will regularly refresh it so that it remains valid.

Generation of the Cookie

On the configuration page, a green button allows you to manually generate the Amazon cookie.

At the press of the green button, an identification page opens:

If this page does not open correctly, look in the troubleshooting section

Enter your Amazon login and password and click the blue Login button.

The particularly elegant and discreet thumb of Sigalou congratulates you. The window can be closed.

Launch of the Demon

At this time, the cookie that is sent to the browser is retrieved by the plugin and saved in the plugin's data folder.

A few seconds later, the Demon launches, goes green and the status changes to OK

If this is not automatic, click on the small ‘Play’ arrow in (Re)Start, this will launch the Demon.

If a few seconds after the demon turns red, look in the troubleshooting section

Troubleshooting

First of all, try a reinstallation of dependencies

Dependencies must be up to date, for this, click on Relaunch

Amazon ID pop-up does not open

If you are in this situation:

• Click on Retry, activating the proxy on port 3457 can take a few seconds, the time to click on Retry allows you to retry a connection.
• Look at the IP address in the URL. On this example, we are talking about: 192.168.1.21. Check that this address is the address of your jeedom on your local network. If this address is false, check what is configured in Settings/System/Configuration/Networks

• The port must be 3457, if you do not have 3457 this is a new concern, report to Sigalou
• You must be on the same local network as your jeedom. Therefore, you do not need to be connected remotely and use the external network link. If your jeedom is as in the example in 192.168.1.21, you must be connected to a machine with an IP address starting with 192.168.1.xxx
• Put yourself in Debug mode on the logs, empty the log alexaapi _cookie and then restart the cookie generation. To the error message, close the window and look at the content of log alexaapi _cookie, Go to Community and add a message by giving the content of log alexaapi _cookie, the community will help you understand.

Password is incorrect

The plugin and this page will not be able to do anything for you, you must know its Amazon login/password.

The Demon Falls Back

The whole process of creating the cookie went well, the green OK is present under Configuration but the daemon does not hold.

It goes green when you press the green "play" button and a few seconds later, the status goes back to red NOK.

This is the most complex case, we have to try to understand why this happens.

The log alexaapi _node will give us clues.

You have to go into mode Debug.

Click on the blue button Alexaapi _node then click Empty to be new

Relaunch the Demon by pressing the green button Re(Start)

Let the Demon try to reset and then as soon as it has fallen back (Status at NOK), open the Alexaapi _Node log

Go to Community and add a message by giving the content of log alexaapi _Node, the community will help you understand.

Other "combinations" that can be tested

Reinstall the plugin

A concern with installation and updating that did not work well? A corrupted file, a reinstallation of the plugin may be attempted. This does not lose the devices and the scenarios are not to be remade. So it is risk-free.

So go to the update centre and click on Reinstall orange on the Alexaapi line

Overwrite Version

For some reason, many of us find that reinstalling the Beta version on the Stable version and then reinstalling the Stable version on the Beta version fixed some of the update issues that went wrong. Obviously, the opposite is true if you are in Beta.

Uninstall/Reinstall the plugin

This option is to be chosen only if you have few scenarios using the commands of the devices. Uninstalling the plugin will remove all the devices and therefore all the commands; All scenarios and design will have to be redone.

This solution worked for some, meaning that the previous installation had not worked properly.