${param} question with a slider control

Hi All

I have setup OR and have all all running and I have setup a switch and have that correctly back to my Fibaro HC2

I am working with the slider and have the status working but not the setvalue part

Status is setup as follows and this works. If I set the value in HC2 it is reflected in OR

I cant seem to get the slider “set value” part working and I think it is the way I am implementing the ${param} feature.

If I understand what I have read correctly, when you adjust the slider, OR passes this value (39 for 39%) from the slider control through the sensor and back to the command so it can be added to the url and be part of the POST request

If I use the following URL in chrome I can set the dimmer value on my system

If I then use this in OR with the ${param} in the url to pass the required value back from the slider control

My OR command looks like this .

and the URL I’m using is as follows${param}

…but its not working :-(

Does anybody know the correct want to implement the $param feature in my use case

If I can sort this I can start to build custom panels for myself…

any help appreciated…




Have you read any of the articles in old forum?


I did read quite a bit on the older forum but couldnt find an extact reference to the syntax.

I’ll read what your search query has listed

Do you know if my understanding on how it operates is correct ?

Is the syntax as I displayed correct and perhaps the problem is elsewhere

If I could get that answer I could resort to wireshark to see what is actually being requested and see where the issue may be



one other thing…

do I need to write a rule as well as use the ${param} in the url string or just use it in the url ?


Okay…I read through most of the threads and feel that it’s not a syntax issue

The http request is working in a browser with a numerical set value so the syntax is correct

all the threads seem to suggest that you put the string ${param} in either the url or the workload fields

I don’t think it makes any difference which one …

I think my issue is that the slider/command is not firing off the http request.

I can’t see anything on wireshark

so now I’m down to two things

DEBUG -----

Does anybody have a debug technique that would allow me to see if the slider/command is firing off the http request?

My OR controller is on a RPi


The slider references the setvalue command and the sensor

When the slider is adjusted it uses the sensor range (0 to 100) to determine what number/value the user has set the level to

This value is then sent to the slider command as the string ${param} and this gets added to the http request that the command fires off to the target

Is this correct ?

I added a table and can now see the level ( from the sensor)
If i adjust the dimmer through my Home Automation controller it gets reflected in the slider level and the numerical value in the label

This means the sensor is working

If I adjust the slider manually in OR this is not reflected in the label so I suspect that the slider is not picking up on the slider level and sending that off to teh command (with the http request)

Any idea what may be causing this ?

You're certainly putting some effort into this :wink:

I'm not expert in anything other than the Velbus protocol, so my help here is a guess at best.

That said, from what you've written I'd suggest that the slider isn't pushing the new value into the command.


You put a fixed value into the command and link it to a button, does that button work?

If so, I'd assume that it's something to do with the $param?

(We don't use the $param function in Velbus.
We can, but we don't need to)

Can you upload a higher resolution image of how you've setup the slider please?
I tried to zoom in, but got a very fussy image.

Thanks for the info and offer of help

I did the button idea and it didnt work and I now think the issue may be with the command firing off the http request

I dropped in a url (that works in a browser) and it doesnt do anything.

it might be the way OR encodes the http trequest (I dont specify the contnet, etc) - do you ?

I don’t have any supporting rules and dont think I need them ???

Is there any debug tools / logfiles that I can see what is going on under the cover with the request or am I back to wireshark??

images attached (including the one that I used to test with the button)

would it be worth sending me an example of how you implement with your devices ?

Thanks again


Hi Frank,

It just comes down to what type of HTTP request your device requires: -

From your first post you said you can call the URL from Chrome (I’m guessing by typing into the address bar) then that is a HTTP GET (not POST), so change your command to GET remove the Workload (that is only for PUT and POST requests) and then set the URL as follows: -


Should be good.

one last piece of info …

The sensor and associated command would appear to be working because if I change the dimmer level manually or through my HA controller it is reflected in the OR panel. This means that OR can communciate with my controller, at least with a GET

I'd always go with Richard's advice:-)

Hi Richard,

That worked !! - thanks a lot…

I thought I had tried that combination … but evidently not :frowning:

all sorted now - I can now go and build my panels.

BTW - are you a pro installer or an individual working on your home system ?

I an working on my home system but was wondering what was the difference between the pro OR version and the FREE one and how much the PRO cost. I searched the forum, say a reference to €200 but no feature comparison list… does it exist ?

any thanks again - it’s made my day searching/trying worthwhile


Thanks Stuart for guiding and looking to help

BTW - are you a pro installer or an individual working on your home system ?

I’m working on my home system but OR seems like a fantastic product.


You're very welcome.

I'm glad I could help, even though it's not my area of expertise.

As for my use....

I own MDAR Ltd, a UK importer of Velbus automation hardware.

OpenRemote is the platform I elected to invest in by funding the integration of the Velbus protocol.

For which I have Richard's magic fingers to thank.

The combination is proving to be extremely powerful.

the velbus devices are very nice - I took the zwave roiute using the Fibaro Controller. No crossover there which is a pity as the velbus design is very sleek

anyway much appreciate your time




You say 'no cross over', but there's no reason why a set of OpenRemote rules can't monitor activities on both networks and trigger events on opposing networks. :wink:

thats a good point - i must take a look
How do the products fair price wise ?

I’m in ireland .

rules - thats my next challenge, I think I may need a few and am dreading that part. I’m not a coder by profession but am technical so can generally figure stuff out given enough time and some guidence…

TBH…I’m very impressed with Openremote,but the documentation is very poor, I thought that Fibaro was bad but OR seems worse.

Could I ask when you supply OR and Velbus,what hardware do you supply for the controller

  • I’m using a Pi but am not entirely happy with it long term…


I'm sure we can help with some rules.

I've got a few that Richard created to get me started.
When you're ready to experiment, just start a new topic and you'll get plenty of help.

As for a hardware controller, I supply a nice din rail mounted 1Ghz dual core linux machine, pre loaded with OR Pro and a Velbus server for €150 + vat & postage.

I can easily comment out the Velbus server so that you can load your Z-Wave stuff.

Oh, I forgot to mention the cost of Velbus hardware.

All the resellers are held to the retail prices on the Velbus website, because they are well pitched there's very little point in any of us undercutting each other.


Drop me a line it you'd like a quote on any modules.


Thanks, Those DIN rail mounted units are starting to take off…

Could you send on the spec of the DIN rail linux unit you supply - I may be interested.

I wouldn’t need more space than that the OR takes as I have a separate HA z-wave Controller (fibaro HC2)