Exactly. That’s why I’m baffled by the character array as an evt.value result.
So I’ve just changed the switch to
(evt.value) instead of ($evt.value”)
Here is the instant results from the logs.
Another thing I don’t get here is there are multiple active events without an inactive in between. That’s not how this sensor reports. In the live logs with text logging enabled for this particular sensor are you seeing multiple actives without an inactive in between?
And you are sure that the driver for this sensor is the system driver and not a user driver…
They are from different child apps Mike.
I didn’t put any filters on the live log window.
You're seeing the logs from all the apps.
Here’s a screen grab from just one child app.
Put this in the beginning of the method:
log.debug "is string? ${evt.value instanceof String}, evt.value=$evt.value"
if evt.value is not a string, revealed by this, then there would indeed be a platform issue here.
2 Likes
Did you notice that it appears to always be
Active
Array active
Array active
then
Inactive
First three close together.
Thanks. We will dig into this. There was an update to the C-7 JVM, so perhaps there is some issue arising from that. Thanks for your patience.
3 Likes
Exactly that. Yes.
No worries. Glad I could be helpful.
Can you check if 2.3.8.118 (just released) fixes it?
I was unable to reproduce the issue, but I've added some code that should, in theory, deal with it.
If not, back to the drawing board.
1 Like
