Closed Martin-OHV closed 8 months ago
Put a path to an empty file, not a directory. Then it'll work.
Something like this:
facepalm so sorry mate... Thank you. This fix the issue with the "EISDIR: illegal operation on a directory, read" error...
Unfortunatly i get this now: "failed to load smarthome devices: "Timeout"" "failed to load smarthome devices: "Timeout"" "Initialisation was aborted!"
Source of all 3 is the config node. The Init Node says: "Init with Proxy" and the On Device Activity says "listening", but nothing happens.
i watching the whole Message Object of the Dev Activity Node with an Debug node and no commands from any Alexa device are sending
Thank you for you support
This issue is stale because it has been open for 30 days with no activity.
This issue was closed because it has been inactive for 14 days since being marked as stale.
Hi,
i Fading an issue since a while...
if i use /home/pi/ as FilePath in the Config Node, i get an error:
"EISDIR: illegal operation on a directory, read"
If i let the Filepath blank, it works and i get asked to open the Authentication site. after logon i receive:
Amazon Alexa Cookie successfully retrieved. You can close the browser.
but the Initialize Node still shows up with "open ... in your browser"
I already checked permissions on /home/pi/ and it is 0777 for user/group pi...
Using NodeRed v2.2.2 on Raspberry PI with node-red-contrib-alexa-remote2-applestrudel v5.0.49
Any ideas?