This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
GPIO triggered actions
#1
Hi,
I updated to OP 0.11.3 and do not succeed in configuring GPIO triggered actions.

I cant't see the inputs in SK diagnostics, nor can I trigger an action with GPIO inputs.
The configured GPIO inputs do not show up in the Signal K key lists. I had to wrote the names in sensors.* by hand.

Actions with I2C sensors are working.

What am I doing wrong?

[Image: 8889b247d7135b17961fcf251327a5d2.jpg]

[Image: 6eb5c37ebe42a9528ae549bd7811eeb5.jpg]

[Image: 5ac536ecb73740899b5fcaff67ea88f4.jpg]

[Image: 3f8a00c00d2dc4420394af992e6b815e.jpg]
Reply
#2
Update:
My mistake - actions are working with the above described settings.

In OP 0.8 the GPIO triggered action was performed when actualizing the action settings.
I was using this for the check.

I guess now the action ist performed when the GPIO state realy changes.

Anyway it works.

Is there a way to see the state of the defined GPIO input sensors?
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)