On August 9, 2019 at 10:38, crosen said...
Nope, you're making the same mistake again. Here are your words:
I will show how this programming is wrong and doesn't lead to the behavior you say.
Step 1: the beginning
- Switch is down
- Contact is open
- Relay is open
- Fireplace is off
Step 2: turn on fireplace from Control4
- Switch still down
- Contact still open
- Relay now closed
- Fireplace turns on
Step 3: try to turn off fireplace from switch push pushing it up
- Switch now up
- Contact now closed
- Relay still closed
- Fireplace still on
So, the switch went up, but the fireplace did not turn off. Why not?
Again, in your words: "when contact closes (from your contact sensor via the wall switch), close relay to ignite fire."
If you want each successive press of the switch to actually toggle the fire, then your logic needs to be different from what you say above. Specifically, it needs to be "when contact state changes, toggle relay."
You can look for a change of state and envoke programming based on it.
In this case, it won't matter if the switch is on or off, when it changes state, you take action.
Furthermore, you can simplify experance for the client to say:
If the fireplace is on and switch changes state, turn the fireplace off.
If the fireplace is off and switch changes state, turn the fireplace on for 30 minutes.
Also, one of the posts mentioned using a keypad, in which case the fireplace button (1, 2 or 3 space one) doesn't have a top or bottom so the button can be programmed for Press, Release, Single, Double or Tripple tap.
