# Setting raw configuration parameters on unsupported device

**URL:** <https://community.homey.app/t/setting-raw-configuration-parameters-on-unsupported-device/17916>\
**Category:** Questions & Help\
**Tags:** z-wave\
**Created:** [September 9, 2019, 10:11am UTC](https://community.homey.app/t/setting-raw-configuration-parameters-on-unsupported-device/17916 "2019-09-09T10:11:52Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![ToreL](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/torel/32/13626_2.png) [@ToreL](https://community.homey.app/u/ToreL)\
**Post date:** [September 9, 2019, 10:11am UTC](https://community.homey.app/t/setting-raw-configuration-parameters-on-unsupported-device/17916/1 "2019-09-09T10:11:53Z")

</div>

I have a Fakro SWZ230 window opener which appears as an unsupported Z-wave device. Operating the opener is fine (open/close), however the device doesn’t seem to accept/operate according to the configuration parameters I am sending. Are there any tricks to this or is this not supported on unsupported Z-wave devices?

In the Homey app on the phone, the response is that the data has been saved. The log file shows the following:

[2019-09-09T09:01:50.120Z] Node[8]: [COMMAND\_CLASS\_CONFIGURATION] [CONFIGURATION\_SET] {“type”:“Buffer”,“data”:[7,1,2]}  
[2019-09-09T09:01:50.120Z] Node[8]: sendData to COMMAND\_CLASS\_CONFIGURATION, params 0x04070102  
[2019-09-09T09:01:50.126Z] Command[9] start: sendData  
[2019-09-09T09:01:50.127Z] ProcessSendData[10]: To node: 8 with data: 0x7004070102 and txOptions: AUTO\_ROUTE  
[2019-09-09T09:01:50.195Z] Command[9] end: sendData

This to me looks correct. The command should change the speed of the window opener, but this doesn’t happen.

Any advice is greatly appreciated.

Tore