Been testing this again .. I have done this before... even wrote detailed posts how to do it in the past.

Years later I am wanting to use Polisy and ZMatter for something....

But I cannot get scenes to work with zwave as a controller to turn on/off insteon. I can add zwave zen71 switch to a scene like I have done in the past using its basic assoc 2 node... but it never controls the Insteon device. I have check all parameters on the zwave swtich - nothing works. I even factory reset ZMatter.

IoX is supposed to do some magic behind the scenes to make ZWave devices act as controllers - picking up the on/off presses from the zwave switch and mapping as a controller to a scene but it appears that it no longer works.

Some evidence here possibly in this thread below....

Did this get broken in an update? I am on a Polisy 6.1.2

Not a huge deal since I can use programs but this is kinda driving me crazy LOL.

Interesting that I have to put a 1 sec delay or else the switch turn on/off.. maybe because I am turning on the scene instead of the device and direct device turning on/off does not have this issue...

Note I renamed the scene after the top screenshot from test scene to zwave test.

ZWave Switch Scene Controller - [ID 0009][Parent 0003][Enabled]

If

'ZY 005 On-Off Power Switch' Status is On

Then

// Needs a delay to prevent race condition

Wait 1 second

Set 'zwave test' On

Else

// Needs a delay to prevent race condition

Wait 1 second

Set 'zwave test' Off

Edited 16 hours ago16 hr by brians

I had always assumed that Scene control was meant to be peer-to-peer (for example, ZWave devices both using basic association 2 to talk to each other) - this would imply that you can't do scene control between different technologies, such as Insteon <-> ZWave, since they don't speak the same language.

It’s likely handled as if it were an eISY program behind the scenes.

I think the issue is status vs control (scene uses control). An issue was recently identified with Z-Wave recently not publishing controls. This is assigned scheduled for review.

ID: /udi-tasks/issues/12

4 minutes ago, Javi said:

I think the issue is status vs control (scene uses control). An issue was recently identified with Z-Wave recently not publishing controls. This is assigned scheduled for review.

ID: /udi-tasks/issues/12

Maybe a workaround could be used (I haven't tried this): Create a program looking for the status change of your triggering Zwave device, which then issues a scene command.

@Javi Is the issue mentioned above (ID: /udi-tasks/issues/12) something that we can view, or is it internal to UDI?

Internal ID, in case a reference is needed

43 minutes ago, peterathans said:

@Javi Is the issue mentioned above (ID: /udi-tasks/issues/12) something that we can view, or is it internal to UDI?