Did you use the binary from the dropbox link (scroll a bit up)? If not: that is exactly what this snapshot is trying to fix and I’m planning to release this soon.
If you do use this snapshot, please let me know how to reproduce this issue, so I can fix this before the next release.
If you have time to test it, please share your feedback. It should also give you the encoder / decoder errors on the .../error MQTT topic + live device events in the web-interface
My assumption was that the JS VM would only return certain types and I was wrong (assumptions…). I’ve updated the code to handle every possible int / float in the returned array:
@ruben_gr@sslupsky I think this should solve all the reported issues. Thanks again for reporting these. As different Encode functions are returning different types, these errors did not show up in my testing.
Could you test (hopefully) one more time? I’ve created new snapshots including the above change:
You can post the steps you followed to receive data to your device. Also the structure of your file to send the data.
I have not been successful yet, my device says it has not received packages.
Thank you.