Managing myopenhab.org items with curl

[Djazz]

Hello,

i have an openhab setup which works very fine with KNX and myopenhab.org. I would like to integrate some scenario with my smartphone events with macrodroid, in order to do this i tested the management of my items with curl :

retrieve state from an item is working fine

pi@raspberrypi:~ $ curl --user mylogin:mypassword https://myopenhab.org/rest/items/mainroom_light/state
OFF

set state of an item is modifying the state of my item in the app, but does not turn on the light !

pi@raspberrypi:~ $ curl -X PUT --user mylogin:mypassword --header “Content-Type: text/plain” -d “OFF” https://myopenhab.org/rest/items/mainroom_light/state

Additionnal question, is that possible to pass login/password directly in the URL ?

Thanks for your help !

[Bruce_Osborne]

myopenhab.org used to permit Items but that was turned off due to abuse overloading the limited server resources,

The only current solution is to host your own copy of the cloud connector code.

[Wolfgang_S]

@Djazz

set state of an item is modifying the state of my item in the app, but does not turn on the light !

pi@raspberrypi:~ $ curl -X PUT --user mylogin:mypassword --header “Content-Type: text/plain” -d “OFF” https://myopenhab.org/rest/items/mainroom_light/state

Additionnal question, is that possible to pass login/password directly in the URL ?

your code is ok - apart of that the headline says turn on the light while the code contains “OFF”.
I am using this command in my private cloud setup.

Even in case login/password would work in the URL I would not do that. URLs can be sniffed on the network between your OH installation and the target. If login/password is part of the encrypted data stream although the packets can be sniffed they cannot be read in clear text.

[rossko57]

@Djazz

set state of an item is modifying the state of my item in the app, but does not turn on the light !

Why would it? It’s not supposed to. Item states are not commands. If you want a binding to take action, you need to command not state update.
For REST, that uses POST not PUT

[Bruce_Osborne]

@rossko57

If you want a binding to take action, you need to command not state update.
For REST, that uses POST not PUT

And, unless you have exposed your openHAB to the Internet, that would only work when connected to Wi-Fi on your local network.

[Djazz]

OK thanks for your replies. Once I will have chosen between setup my own cloud server or access to my local openhab only from my WiFi, I’m not sure if my url is correct (Wolfgang says it was OK but rossko57 not)?

Thanks again

[Wolfgang_S]

Follow rossko57 advice. I also use the POST command in my Personal Setup and testen your command. Both seem to work Herr nevertheless I would use the POST command.

[Djazz]

Thanks again, i tried to reach my openhab private IP address from my local wifi and it works fine with the POST command.

This is funny because it works fine too with myopenhab cloud server :
pi@raspberrypi:~ $ curl --user mylogin:mypassword -X POST --header “Content-Type: text/plain” --header “Accept: application/json” -d “ON” https://myopenhab.org/rest/items/mainroom_light

This command turns on the light.

Bye, and thanks again for your help,

[rlkoshak (Rich Koshak)]

@Bruce_Osborne

And, unless you have exposed your openHAB to the Internet, that would only work when connected to Wi-Fi on your local network.

myopenhab.org proxies the full OH REST API. It is and has always been possible to update and command Items through myopenhab.org. If that didn’t work, the UIs themselves wouldn’t work with myopenhab.org.

Anything you can do to OH through the REST API can be done through myopenhab.org. The only difference is having to deal with basic auth. No Items need to be exposed. The exposure of Items is only required for IFTTT integration as that’s how IFTTT gets the events that an Item has changed.

@Djazz

Wolfgang says it was OK but rossko57 not

Wolfgang is correct. To see an example using Tasker see Tasker with myopenHAB.org (Screenshots for tasker)