# Sending raw Z-Wave parameters **URL:** \ **Category:** Questions & Help\ **Tags:** z-wave, advancedflow\ **Created:** [October 28, 2024, 1:42pm UTC](https://community.homey.app/t/sending-raw-z-wave-parameters/119172 "2024-10-28T13:42:52Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![Domenico\_Etere](https://avatars.discourse-cdn.com/v4/letter/d/f19dbf/32.png) [@Domenico\_Etere](https://community.homey.app/u/Domenico_Etere)\ **Post date:** [October 28, 2024, 1:42pm UTC](https://community.homey.app/t/sending-raw-z-wave-parameters/119172/1 "2024-10-28T13:42:52Z")
Hello, I am struggling to send configuration parameters to a Fibaro Head Controller Z-Wave device by an advanced flow using the “Send raw commands” Z-wave flowcard. I need to send a configuration string to set specific parameters to it. I have already tried successfully to send them by using the “advanced settings\row configuration parameters” directly on the device. In this case there is no need to use the device Node Id since it is already known inside the device advanced settings. I sent them in decimal using the following format: parameter\_id, size\_in\_byte, value; successfully to the device and the updated configuration is in place. But it seems impossible to do that by using instead the “Send raw commands” Z-wave flowcard in a flow to the NodeId of my Fibaro Head Controller… I tried to send them in different ways: 1. parameter\_id, size\_in\_byte, value; (both in Hex (0x…) or decimal without success) 2. 112, 4, parameter\_id, size\_in\_byte, value; (both in Hex (0x…) or decimal without success) 112 and 4 (in dec but I tried also in Hex) are respectively the CONFIGURATION COMMAND Class and the CONFIGURATION SET Function which I have seen are needed to send a configuration parameter change to a Z-Wave device. In all of these cases the outcome was unsuccessful… I have an HPE 2023. Could anyone help me? ---
**Author:** ![DirkG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dirkg/32/118897_2.png) [@DirkG](https://community.homey.app/u/DirkG)\ **Post date:** [October 28, 2024, 2:53pm UTC](https://community.homey.app/t/sending-raw-z-wave-parameters/119172/2 "2024-10-28T14:53:02Z")
Please have a look at this post, the info will probably help you: > [@Sending Zwave raw commands from Flow](https://community.homey.app/t/sending-zwave-raw-commands-from-flow/99509/3): > > the raw z-wave command is fully raw though, not just configuration command class like the advanced settings input is, so we also need to define that it has to be configuration command class (0x70), and also want to set (0x04) a value to that command class: hexadecimal command you need for value “1”: 0x70 0x04 0x03, 0x01, 0x01 but as there was a time that hex didn’t work (Homey Pro 2023 made it all 0’s for a reason, not sure if it was fixed yet), so here is also the decimal values: 112, 4, 3,… ---
**Author:** ![Domenico\_Etere](https://avatars.discourse-cdn.com/v4/letter/d/f19dbf/32.png) [@Domenico\_Etere](https://community.homey.app/u/Domenico_Etere)\ **Post date:** [October 28, 2024, 2:58pm UTC](https://community.homey.app/t/sending-raw-z-wave-parameters/119172/3 "2024-10-28T14:58:46Z")
Hello , Yes thank you, I have already read this but I have already tried to put the CONFIGURATION COMMAND CLASS (112) and CONFIGURATION SET (4) both in decimal and in Hex before my parameters change but it didn’t work… ---
**Author:** ![JPe4619](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jpe4619/32/9017_2.png) [@JPe4619](https://community.homey.app/u/JPe4619)\ **Post date:** [October 28, 2024, 3:38pm UTC](https://community.homey.app/t/sending-raw-z-wave-parameters/119172/4 "2024-10-28T15:38:33Z")
This flow works for me: [https://homey.app/f/uHiNjb](https://homey.app/f/uHiNjb) Stuur = send Naar Node = to Node ---
**Author:** ![Caseda](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/caseda/32/138695_2.png) [@Caseda](https://community.homey.app/u/Caseda)\ **Post date:** [October 28, 2024, 4:22pm UTC](https://community.homey.app/t/sending-raw-z-wave-parameters/119172/5 "2024-10-28T16:22:16Z")
> [@Domenico\_Etere](#): > > In all of these cases the outcome was unsuccessful… define “unsuccessful”, doesn’t the card finish? doesn’t the device receive it? doesn’t the flow activate? Just to be sure, the device is included unsecure (`Secure (x)`)? raw flow card doesn’t work when the device is included secure. ---
**Author:** ![Domenico\_Etere](https://avatars.discourse-cdn.com/v4/letter/d/f19dbf/32.png) [@Domenico\_Etere](https://community.homey.app/u/Domenico_Etere)\ **Post date:** [October 28, 2024, 4:31pm UTC](https://community.homey.app/t/sending-raw-z-wave-parameters/119172/6 "2024-10-28T16:31:50Z")
Hello, correct questions that I have missed: - Unsuccessful because the card doesn’t show any error and I checked also in Homey developer Z-Wave logs that Homey sends commands to destination NodeId, but the status on the device doesn’t change. It change, instead, if I send the parameters values from device configuration in “advanced settings\row configuration parameters” as I said before. - I confirm that the device has been paired in unsecure mode. The Z-Wave status in the Homey developer page is (Secure (x)) for this Node ---
**Author:** ![Domenico\_Etere](https://avatars.discourse-cdn.com/v4/letter/d/f19dbf/32.png) [@Domenico\_Etere](https://community.homey.app/u/Domenico_Etere)\ **Post date:** [October 28, 2024, 4:54pm UTC](https://community.homey.app/t/sending-raw-z-wave-parameters/119172/7 "2024-10-28T16:54:31Z")
To be more precise. This is the parameter values possibility I have to set to my Fibaro Heat controller.I I have to change the parameter: 2 it is a bitmask which leads different configurations shown below: ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/d/0/d056208fc787a5d56ed614033725908228004dbc.png) I have to put 177 in parameter 2 which the size is 4 byte. If I put directly in advanced settings\row configuration parameters the string: 2,4,177 it works fine and the status change. But If I try to do that by using the first or the second flowcard: ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/2/b/2b57c7805ac2658af7c1fc649d65219443103365.png) Both flowcards execute successfully but the status on the device doesn’t change ---
**Author:** ![Caseda](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/caseda/32/138695_2.png) [@Caseda](https://community.homey.app/u/Caseda)\ **Post date:** [October 28, 2024, 4:59pm UTC](https://community.homey.app/t/sending-raw-z-wave-parameters/119172/8 "2024-10-28T16:59:29Z")
Homey probably makes the 177 into 1 byte value, not a mandatory 4 byte value: `0x70, 0x04, 0x02, 0x04, 0x00, 0x00 0x00, 0xb1` ---
**Author:** ![Domenico\_Etere](https://avatars.discourse-cdn.com/v4/letter/d/f19dbf/32.png) [@Domenico\_Etere](https://community.homey.app/u/Domenico_Etere)\ **Post date:** [October 28, 2024, 5:00pm UTC](https://community.homey.app/t/sending-raw-z-wave-parameters/119172/9 "2024-10-28T17:00:30Z")
I’ll try… But the flowcard accept Hex values only? ---
**Author:** ![Caseda](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/caseda/32/138695_2.png) [@Caseda](https://community.homey.app/u/Caseda)\ **Post date:** [October 28, 2024, 5:01pm UTC](https://community.homey.app/t/sending-raw-z-wave-parameters/119172/10 "2024-10-28T17:01:23Z")
Should also be able to do decimal, but as the value has to be of 4 bytes long, not sure it is smart enough to make it a 4 byte value if it isn’t necessary for the value itself. Might be able to make it a full on decimal, but can’t guarantee that will work: `112, 4, 2, 4, 0, 0, 0, 117` ---
**Author:** ![Domenico\_Etere](https://avatars.discourse-cdn.com/v4/letter/d/f19dbf/32.png) [@Domenico\_Etere](https://community.homey.app/u/Domenico_Etere)\ **Post date:** [October 28, 2024, 5:10pm UTC](https://community.homey.app/t/sending-raw-z-wave-parameters/119172/11 "2024-10-28T17:10:51Z")
Tested and in both cases (Hex or Dec) it doesn’t work unfortunately… ---
**Author:** ![Domenico\_Etere](https://avatars.discourse-cdn.com/v4/letter/d/f19dbf/32.png) [@Domenico\_Etere](https://community.homey.app/u/Domenico_Etere)\ **Post date:** [October 28, 2024, 5:12pm UTC](https://community.homey.app/t/sending-raw-z-wave-parameters/119172/12 "2024-10-28T17:12:22Z")
So it is sure that I have to put before 112, 4 before any parameter configuration changes, correct? ---
**Author:** ![Caseda](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/caseda/32/138695_2.png) [@Caseda](https://community.homey.app/u/Caseda)\ **Post date:** [October 28, 2024, 5:17pm UTC](https://community.homey.app/t/sending-raw-z-wave-parameters/119172/13 "2024-10-28T17:17:14Z")
With the flow card yes, as that is a _real_ raw card, not just for configuration but able to do any command, the one in the advanced settings is purely for configuration parameters. ---
**Author:** ![Domenico\_Etere](https://avatars.discourse-cdn.com/v4/letter/d/f19dbf/32.png) [@Domenico\_Etere](https://community.homey.app/u/Domenico_Etere)\ **Post date:** [October 28, 2024, 7:33pm UTC](https://community.homey.app/t/sending-raw-z-wave-parameters/119172/14 "2024-10-28T19:33:04Z")
Ok that is clear. Do you have any other idea why it still doesn’t work with the last command you suggested? Thank you for your help ---
**Author:** ![Caseda](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/caseda/32/138695_2.png) [@Caseda](https://community.homey.app/u/Caseda)\ **Post date:** [October 28, 2024, 7:47pm UTC](https://community.homey.app/t/sending-raw-z-wave-parameters/119172/15 "2024-10-28T19:47:57Z")
Nope, it should work if the device is included unsecure, is within range, (full) batteries inserted, the value is valid and does change anything visible on the device itself (settings in Homey itself _won’t_ change if there is a corresponding setting). ---
**Author:** ![Cuprum](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/cuprum/32/41409_2.png) [@Cuprum](https://community.homey.app/u/Cuprum)\ **Post date:** [October 29, 2024, 1:07am UTC](https://community.homey.app/t/sending-raw-z-wave-parameters/119172/16 "2024-10-29T01:07:22Z")
> [@Domenico\_Etere](#): > > Do you have any other idea If no other(better) ideas, then… You already mentioned the Z-Wave developers page logs. You also have a successful and not working actions. But what’s the difference between them in logs? Hope, both are present in logs, but what’s the difference? Actually this point hopefuly elliminates speculations on theme decimal/hex and how long the byte is. ---
**Author:** ![Domenico\_Etere](https://avatars.discourse-cdn.com/v4/letter/d/f19dbf/32.png) [@Domenico\_Etere](https://community.homey.app/u/Domenico_Etere)\ **Post date:** [October 29, 2024, 9:12am UTC](https://community.homey.app/t/sending-raw-z-wave-parameters/119172/17 "2024-10-29T09:12:31Z")
In the logs I have only seen (in case I use the “row parameters change flowcard”) that the command was sent from Homey to Z-Wave NodeId I have choosen. That’s all. My doubt was (as Caseda asked) about the fact that the “row parameters change flowcard” could have failed. Then I don’t understand where is the speculation… Caseda explained well the possibility that since the parameter has a value that can be represented with less than 4 bytes (177 can be represented with 8 bits (1 byte)) then the remaining three bytes should be put to zero, in Hex: 0x00, 0x00, 0x00, 0xb1, in Dec: 0,0,0,177 But also in that case the configuration in the device does not change. So I have to find another way to change the parameters since there is no other idea on that ---
**Author:** ![tlink](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tlink/32/120666_2.png) [@tlink](https://community.homey.app/u/tlink)\ **Post date:** [December 22, 2024, 9:42pm UTC](https://community.homey.app/t/sending-raw-z-wave-parameters/119172/18 "2024-12-22T21:42:29Z")
@Domenico_Etere @Caseda I tried to follow the thread but completely miss where you find the Fibaro raw command list 🤔 In my case I have several [Fibaro Roller Shutter 3](https://manuals.fibaro.com/roller-shutter-3/) that already have some raw parameters set (see [my tutorial post](https://community.homey.app/t/z-wave-raw-configuration-parameter/124410)) #1 Not sure if this is an issue: They use an “Authenticated” secure connection. #2 Where can I find the list of commands? I do have a four-button Wallmote that I need to adopt from Fibaro HomeCenter. I am extremely surprised that Homey Flows does not offer a “Stop” action?!? This was not a problem in HomeCenter. The Wallmote button should move the blinds when pressed and held and stop when released. How do find the raw command for STOP? ---
**Author:** ![Caseda](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/caseda/32/138695_2.png) [@Caseda](https://community.homey.app/u/Caseda)\ **Post date:** [December 23, 2024, 9:57am UTC](https://community.homey.app/t/sending-raw-z-wave-parameters/119172/19 "2024-12-23T09:57:41Z")
There is no such thing as a raw command list, such a list would consist of 1000s of pages of raw commands (probably closer to 10 million pages). Raw commands are just “raw” hexadecimal values where the entire z-wave communication works in. So to get to a command you have to read the z-wave documentation (available on the silab’s website after creating an (free) account), and “create”/lookup your command that way. But yes, the device being secure does create a problem, the raw command flow card doesn’t account for the encryption necessary by secure devices. ---
**Author:** ![tlink](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tlink/32/120666_2.png) [@tlink](https://community.homey.app/u/tlink)\ **Post date:** [December 23, 2024, 10:07am UTC](https://community.homey.app/t/sending-raw-z-wave-parameters/119172/20 "2024-12-23T10:07:32Z")
Looks like I try once more some workarounds using variables and/or virtual buttons. [Next page](https://community.homey.app/t/sending-raw-z-wave-parameters/119172.md?page=2)