iot-dsa-v2 / sdk-dslink-java-v2 Goto Github PK

Reading a value from a BACNet point, an integer per device specs. For whatever reason, when calling value.toInt() I'm getting java.lang.ClassCastException: org.iot.dsa.node.DSString not int.

Looking into the sources/comments - it says out that Strings will attempt to parseRequest the numeric which may result in a parseRequest exception., but no trace of implementation in DSString class.

My problem definitely is somewhere else, but it'd be great if DSString actually attempted parsing, and included the value that failed to parse into the exception message.

@a-hansen Somewhere between 0.70.5 and 0.70.7, I've lost flip-switch as boolean action parameter editor.
I am expecting the editor to default to flip-switch (or whatever is the correct name for it) to reflect the type of the second parameter in addParameter. E.g.
addParameter("override-to-value", DSBool.TRUE, ""); since 0.70.7, and including 0.71.0 is rendering as text input field.

java.lang.ClassCastException: com.acuity.iot.dsa.dslink.sys.logging.SysLogService cannot be cast to org.iot.dsa.node.action.DSAction
at org.iot.dsa.node.DSInfo.getAction(DSInfo.java:141)
at com.acuity.iot.dsa.dslink.sys.logging.StreamableLogNode$3.getAction(StreamableLogNode.java:69)
at com.acuity.iot.dsa.dslink.protocol.responder.DSInboundInvoke.writeColumns(DSInboundInvoke.java:362)
at com.acuity.iot.dsa.dslink.protocol.responder.DSInboundInvoke.write(DSInboundInvoke.java:218)
at com.acuity.iot.dsa.dslink.protocol.v1.DS1Session.writeResponse(DS1Session.java:410)
at com.acuity.iot.dsa.dslink.protocol.v1.DS1Session.send(DS1Session.java:363)
at com.acuity.iot.dsa.dslink.protocol.v1.DS1Session.doSendMessage(DS1Session.java:120)
at com.acuity.iot.dsa.dslink.protocol.DSSession$WriteThread.run(DSSession.java:457)

[2019-02-11 08:37:18:810] INFO [DSLink.sys.Connection] iothub2-local-localhost:8080 connected

Hi @a-hansen,

Pls clarify if I'm doing something wrong, or this might be a sdk bug?

I'm implementing DSValueNode. I have two child values called:
"normal-value" and "effective-value". I've implemented getValueChild like this;

   @Override
    public DSInfo<DSIValue> getValueChild() {
        return effectiveValue;
    }

I would expect my DSValueNode to always display effectiveValue child's value.
However, I'm experiencing the behaviour of always showing the value of last changed child.

After some debugging, I've realized this line is being executed (hence updating parent's value) upon either of child nodes being set: