-
Notifications
You must be signed in to change notification settings - Fork 30
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
Event node #10
Comments
Hi. RitaSghe |
Hi, There must be something simpler, please explain to me how to do...... |
Well, EDIT: after some test also in the ubuntu pc I have this error "Invalid property or argument value, Cannot read property 'type' of null" and the palette don't works .... it's correct that for each flow I must set the node "My device"? |
Your error with "Invalid property or argument value, Cannot read property 'type' of null" is likely related to the version of Node.js you are running. This was determined in issue 9 as part of the problem I was experiencing. I created a test environment with Node.js 14.16 and that did seem to correct the issue. |
My raspberry has Node.js 10.24 |
This is a problem introduced with the version 1.1.0 of the pallet. The previous version would run on node.js 10.x In my case it was. I was running the Docker image of node red and it was running that version of Node.JS. I manually installed everything on a Ubuntu VM and it worked fine with Node.14. One thing to take note of is that Node-Red recommends Node.js 12 today. Node.js 14 is supported but not the recommend version. In Issue 9 were I reported this problem it was stated that while developing the pallet they use the latest version of Node.JS. Version 14 is the most recent LTS version of Node.js Hopefully they will be more careful of this in the future or atleast announce what the dependency is when they release it so we know to check before upgrading. |
Yes, it is. I'm running Rpi 4 too and upgraded from node 10 to 14 and problem is gone. I did this after finding out this Promise.allSettled function did not exist in node 10. |
Thanks for reporting! |
@RitaSghe When a device's status changes in SmartThings Cloud, you need to register a webhook as a subscriber with SmartThings Cloud to receive the status. It is called SmartApp or Automation. It is the basic subscription mechanism for SmartThings Cloud. However, It is complicated and only a development mode is provided. |
@Mavrrick - Ok, thank you @lslomczynski - Ok, thank you @dplaya-min - Ok thank you ........, I'm asking you again, it's correct that I must set the node "My device" for each flow? |
@RitaSghe Yes, each flow need a My Device. because it is not a configuration node. We are considering changing it to a configuration node according to /issues/3. But there are no plans yet. |
Yesssss! Now everything works fine! |
No description provided.
The text was updated successfully, but these errors were encountered: