Remotec ZFM-80 oddities

So like many before me, I'm trying to use the ZFM-80 to automate my gas fireplace. This was previously working and installed on an old Zwave network. I've moved it to my Hubitat zwave network and am using the generic Zwave relay driver.

The problem is that this test app, which just flashes the bedroom light when it sees the ZFM-80 turn on, DOES WORK if I do a software 'turn on' via the Bedroom Fireplace software button. HOWEVER, if I use either the button on the front of the ZFM-80 OR the physical wall switch, while the fireplace IS turned on in both of those cases, I do not get the same log entry, and the app does not fire.

Use software switch: infoMasterBedroomLight was turned on [digital]

Use physical switches: debugparse description: zw device: 17, command: 2003, payload: FF , isMulticast: false

I tried this with the default Remotec ZFM-80 driver as well but no better.

SO - why doesn't the ZFM-80 report the same ON indication if it's turned on with software or turned on with one of its physical buttons? And if I must, how do I get notified when the logged command is

"debugparse description: zw device: 17, command: 2003, payload: FF , isMulticast: false"

, which seems to be the "physical button ON" command?

Here is the device info and the zwave network info



I've read from discussions with other z-wave devices, that some don't always send an event, I think it was the older Jasco switches. That said there maybe a parameter to adjust that behavior, so check the manual for parameters that can be set. Although I'd expect any settable parameters to show in state variables, like this:


There are lots of folks who own remotec devices, hopefully one of them will chime in

@user5841 if it is z-wave and not z-wave plus, you will need to install the built in poller app.

1 Like

So helpful; thanks, you've opened up a few directions for me to explore. So:

  1. Where do I find the "poller device"? That might work as I do see one of those variables on the device page change when the relay is closed by any means. Is there documentation on how I find those variables to poll?

2 )How do I configure settings on a device if they're not explicitly called out on the device page?

Thanks!

yourhubip>>apps>>add built in app..

Well the driver typically exposes whats settable on the device. You would set polling time on polling app. You may have to switch to generic z-wave switch for the poller to see it.

Looking at the specs on the switch, it is indeed non-plus... If you change drivers, after you click save, click configure.

https://products.z-wavealliance.org/products/660?selectedFrequencyId=-1

What @rlithgow1 said. Except you don't need to switch drivers for the poller app to see it.

One more thing. You've changed drivers a few times. Make sure you click the "Configure" button the device page every time you change drivers.

I have indeed tried bot the generic zwave relay driver and the ZFM-80 driver, but neither provides the notification when the physical switch is activated or deactivated. I have hit the Configure button after each driver change but the button does not seem to actually do anything (such as refresh the page.)

Does anyone have a tutorial on how to poll this device so I can react to changes in the relay state based on physical switch activity?

(I had this working just fine on a Homeseer system I've migrated away from, but seem to be stuck.)

Try what @rlithgow1 suggested:

  1. Change the driver to "Generic Z-Wave Switch".
  2. Hit the Configure button on the device page.
  3. Load the built-in "Z-Wave Poller" app.
  4. Click on "Add Switches to Poll".
  5. Select your ZFM-80.
2 Likes

Thank all of you so much; these instructions worked great in my case (but being new to this platform it took awhile to get the details right.) Now my fireplaces work fine with a single rule that automatically turns them off after they've been on for 20 minutes - -a good safety protocol for me.

So again, Thanks to all who helped me take this next step.

2 Likes

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.