Skip to content
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

Closed
ghost opened this issue Apr 4, 2021 · 12 comments
Closed

Event node #10

ghost opened this issue Apr 4, 2021 · 12 comments
Labels
duplicate This issue or pull request already exists

Comments

@ghost
Copy link

ghost commented Apr 4, 2021

No description provided.

@dplaya-min
Copy link
Contributor

Hi. RitaSghe
If you have any inquiry, please do not hesitate to leave it.
Your comments are always appreciated.

@ghost
Copy link
Author

ghost commented Apr 5, 2021

Hi,
my necessity is in my flow to know when the status of my contact sensor or switch change ,,,,
I hope that the way are not that you explained here ...
https://sasm.developer.samsung.com/tutorials/templates/b092f96b.944da8

There must be something simpler, please explain to me how to do......

@ghost
Copy link
Author

ghost commented Apr 5, 2021

Well,
I try this palette on my pc test with ubuntu and works ok.
I try this palette on my raspberry 4pi and when I create the node Device I have this error "TypeError: Promise.allSettled is not a function" and don't works .....

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"?

@Mavrrick
Copy link

Mavrrick commented Apr 5, 2021

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.

@ghost
Copy link
Author

ghost commented Apr 5, 2021

My raspberry has Node.js 10.24
Do you think this is the problem for this error:
"TypeError: Promise.allSettled is not a function" ?

@Mavrrick
Copy link

Mavrrick commented Apr 5, 2021

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.

@lslomczynski
Copy link

My raspberry has Node.js 10.24
Do you think this is the problem for this error:
"TypeError: Promise.allSettled is not a function" ?

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.

@iamjaehun
Copy link

Thanks for reporting!
We think this is the same issue as #7. So, we'll mark this as a duplicate.

@iamjaehun iamjaehun added the duplicate This issue or pull request already exists label Apr 6, 2021
@dplaya-min
Copy link
Contributor

dplaya-min commented Apr 6, 2021

@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.
So we made the My Device node. it can also be useful to check your status by pulling.

@ghost
Copy link
Author

ghost commented Apr 6, 2021

@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?

@dplaya-min
Copy link
Contributor

@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.

@ghost
Copy link
Author

ghost commented Apr 6, 2021

Yesssss! Now everything works fine!
Thank you all for help!
Have a nice day .....

Orchemi pushed a commit to D5MI/SamsungAutomationStudio that referenced this issue Oct 1, 2022
jg8008 pushed a commit that referenced this issue Oct 18, 2022
jongsu2 pushed a commit that referenced this issue Oct 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

4 participants