You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have written a workaround locally to use this when Virtual Inputs have this option, rather than trying to update the IoB state (which is currently correctly created read-only). It would be useful, however, to have the Loxone adapter (maybe optionally) detect Virtual Inputs with this option, make the IoB state read/write, and then send updates with an API request as noted above.
The text was updated successfully, but these errors were encountered:
In Loxone config it's possible to check a Show status only box on Virtual Inputs:
This is useful to show the input's value to users in the web interface when it is not desirable to allow them to update the value.
Side note: Ideally Loxone would have a more granular permissions system to allow only certain users to update virtual inputs, but anyway...
Even when a virtual input is checked like this, it can be updated via HTTP API with a request such as...
http://<miniserver>/dev/sps/io/<virtualInputUUID>/<value>
I have written a workaround locally to use this when Virtual Inputs have this option, rather than trying to update the IoB state (which is currently correctly created read-only). It would be useful, however, to have the Loxone adapter (maybe optionally) detect Virtual Inputs with this option, make the IoB state read/write, and then send updates with an API request as noted above.
The text was updated successfully, but these errors were encountered: