I know this is an old thread, but I'm about to bump it (even though it's asked and answered - just not for an idiot).

I'm about to try to make a gas fireplace smart with a C4-Z2io and I feel like a complete idiot, even after reading all of the above.

I have a existing dump standard toggle paddle switch right now turning the fireplace on and off. This switch opens and closes the contacts and us low voltage.

I want to maintain the ability to use the toggle switch if possible, though I want to make sure C4 doesn't get confused.

Can someone give me the COMPLETE idiot guide to doing this. I mean so detailed that I can maybe pull this off? I have the Z2io complete. I'm thinking I might need to grab a few feet of LV wire? I don't know how to wire the Z2io and if someone says - wire the relay to the contact... blah blah... I'll pound my head against a wall. Just simply step by step and I'll be forever grateful.

Thanks!

Are you a C4 installer or end user?

The setup is exactly as explained by me above. Not really sure how to make it more simple. You’re providing dry contact closure from the Z2IO to ignite the fireplace. The lack of this dry contact closure (opening the Z2IO relay) cause the fireplace to extinguish. The Z2IO has on board contact sensor connections; this is where you’d wire the existing wires from your toggle switch. Configure the Z2IO driver according to the install doc for a relay and contact. Bind the relay to your fireplace timer driver and/or keypad button. Bind the contact to the contact portion of the driver. You can then have programming logic such as when contact closes (from your contact sensor via the wall switch), close relay to ignite fire. When contact opens, open relay to extinguish fireplace.
If you require support beyond that I’d recommend you contact C4 tech support.

You forgot to mention that it needs a 240 Volt AC line with one leg connected to the gas line and the other connected to one of the logs.

You'll run into trouble with this. Consider, for example, the case where the C4 app is used to turn the fireplace on. Now, you want to use the physical switch to turn it off. Guess what? The physical switch is already off. (The work around is to flip the switch on and then back off, but this is not exactly user friendly.)

Are you sure about that? The fireplace gas needs a constant closure, not a momentary one. The switch needs to go.

I am still pretty sure. The constant closure is provided by C4 to the fireplace when told to do so by the switch. That constant closure will be turned of by C4 whenever the switch turns off.

Incorrect.

You seem to be operating on theory rather than practical experience.

Wire it exactly as I have said, twice now.

Connections:
Z2IO Relay is bound to FP control relay.
Z2IO contact is bound to generic contact driver.

Programming for contact:
When contact opens, select FP
When contact closes, select FP

The toggling of the mechanical switch will toggle the state of the FP.

Programming for KP:
When button is pressed, set FP timer to off mins
When button is triple tapped, set FP timer to 30m

(led tracking programming omitted on purpose to not cloud the discussion)

If FP is turned on elsewhere than the mechanical switch, ie my KP programmed to start FP timer to 30m, toggling the mechanical switch (no matter if it is up or down) will cause the FP to go out.

you are correct but not quite right! toggling of the mechanical switch is not quite intuitive. while you are correct in all of your connections and operability, i would not leave like that for client. what i would do however is find an acceptable momentary push button switch to replace the toggle switch and program accordingly. press one to turn on/ start timer, etc. press while on turns off. much better solution

I stand by my post. Reread what you wrote and my response and tell me where the error is in my response.

I have read your post; you are still incorrect. Here is what you said (in bold):

Consider, for example, the case where the C4 app is used to turn the fireplace on.

OK, fully considered.

Now, you want to use the physical switch to turn it off. Guess what? The physical switch is already off. (The work around is to flip the switch on and then back off, but this is not exactly user friendly.)

This is where you are incorrect.

If I start the FP from elsewhere (not the mechanical switch).
I now have the FP on.
If the mechanical switch is in the down position, press the top position.
FP goes out.

If I start the FP from elsewhere (not the mechanical switch).
I now have the FP on.
If the mechanical switch is in the up position, press the down position.
FP goes out.

Try it out.

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

Let’s stop with anecdotal scenarios. Have you tried this in practice? I have it setup this way in 3 of my FPs. Would be happy to share connections and programming screen shots...or you could rig one up and try it.

Thanks everyone.

I have the fireplace control module wired to C1/C2 and the Z2io energized via its usb power port. I have not added it to C4, so I don’t know if it’s working. I was told I could maintain the switch control by wiring that to C3/CM. I did that and could not get it to fire. Maybe it needs to be added to C4 first? Regardless, I’m told that C4 will understand its state. But I’d rather get it working first before that debate. Thanks!

The Z2IO is a useless paperweight unless ID’d into the project and virtual connections are made to and from it; along with other drivers and programming. I’d suggest getting a qualified C4 installer on site ASAP (sorry if the assumption is you are not; just comes across that way).

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.