Mios binding EOL

[hafniumzinc (T)]

@jswim788

On the Vera side you can post updates to OH on the REST api. I think I may have some examples of that too, but it may take a little longer to dig up.

I’d definitely be interested, thanks! No rush though.

---

For others following along, I’ve (eventually) found out that you can find the details and methods for all your attached devices by going to (swap the IP address for your Vera IP address):

http://192.168.1.91:3480/data_request?id=invoke

For me, this shows the following:

Clicking on device 4, the radiator, shows the following:

Now, I’m mostly interested in setting the temperature, so I click SetCurrentSetpoint (NewCurrentSetpoint), which shows the following:

Not too encouraging. However, when clicking on SetCurrentSetpoint (NewCurrentSetpoint) on the previous page, the URL which is used is:

http://192.168.1.91:3480/data_request?id=action&DeviceNum=4&serviceId=urn:upnp-org:serviceId:TemperatureSetpoint1_Heat&action=SetCurrentSetpoint&NewCurrentSetpoint=

You can see there is no value after NewCurrentSetpoint=. Adding a value in, such as 19, and trying again, now shows a valid XML response, and eventually the thermostat itself updates.

EDIT:
Just dumping some info so I don’t lose it:

• http://wiki.micasaverde.com/index.php/Luup_UPNP_Files
• http://wiki.micasaverde.com/index.php/Luup_UPnP_Variables_and_Actions
• http://wiki.micasaverde.com/index.php/Luup_Requests

To perform a valid action, you need id=action and action= in the URL.
To get a variable, you need id=variableget and Variable= (case sensitive!) in the URL.