Accessing zwave.set_config_parameter from master instance

I have a master instance which is where I have almost everything (automations, scripts, scenes, etc.). My secondary instance is where a zwave radio is being used to connect zwave devices. One such device is an Inovelli Dimmer Switch, which has a LED on it that can be used for custom notifications.

To make use of this LED, I need to call the zwave.set_config_parameter service. I have done this successfully from my secondary instance (where zwave is configured), but (not surprisingly) my master instance doesn’t know what the zwave.set_config_parameter service is.

I tried adding zwave.set_config_parameter to the list of subscribe_events: in my master instance config, but that didn’t seem to work.

Is there any way to expose the zwave.set_config_parameter service to the master instance?

Thanks!

[postlund]

I believe this to be another case where the component takes control of the hardware rather than representing it via entities. This component cannot handle those cases. But I have added a workaround for it called “proxy services”. It allows you to set up new services that proxies calls to another instance, e.g. a service called zwave.summer_house_set_config_parameter could be set up which would be forwarded to the zwave.set_config_parameter service on the other instance. It’s more or less what you do, @jhein05, but more transparent. Errors are also propagated back to the master instance.

It’s currently a PR, see #90, but it would be great if you could try it out and let me know if it works. Have a look at the changes to README.md for more details.

[postlund]

If you experience any problems, please open the issue again as I consider it to be done now.