Join GitHub today
Variable types missing (V_VAR1...) and why readOnly="true" #8
I am dealing with a sensor that requests a numeric value from OH2. Unfortunatelly, the only item type I can use to link the channel from where the node makes its request, is a dimmer type because all the other variables are read only.
Is there any reason for this? Why wouldn't be possible for a node to ask for a temperature for example?
Another thing I noticed, is the lack of variables V_VAR1, V_VAR2...that are defined at MySensors variable types. Is there any reason to avoid this type of variables.
Once again, I appreciate very much the effort you have put in this binding. It really works greats.
Shouldn't we add this lines to MySensorsBindingConstans.java?
I am not sure how the ThingTypeUID definition would be for these cases.
Adding the variables V_VAR1, V_VAR2 ... is no problem!
Currently it is not possible to answer an request send to the OH2 binding due to a limitation of the API. I'm not able to get the value of an item.
Here is the answer of the core developer:
So we need to save the value by ourself, which is harder as it sounds, as all items are handled by the same handler and the handler handles all types of data (decimal, string, percentage ...).
This heartbeat or beacon, is send to the gateway every couple of minutes. This interval is defined by a Setpoint item in OpenHAB and requested by the nodes everytime they boot up. I called that interval "Heart Rate"
So, what I need, is the binding to detect this request and trigger a rule in OH2 such as the following:
Let me know if you need some extra details.
To speak in SerialAPI should it look like this?
Node sends a request for V_VAR_1 like:
OH should respond with:
I currently don't have a hardware node that sends requests so I will teach my MockGateway.
mmm not quiet right.
Suppose our node has id=1, heartbeat sensor id=252, with variable type V_VAR1.
And the answer from the controller would look like this:
Let me know if there is anyway in which I can help you.
Thanks for the heads up. So the debug output of the implementation looks like this:
This is what you need?