Closed cburger-scheidlin closed 9 years ago
We know the problem and we must definitely fix that. Currently, the server don't know the type of data return by the device. Objects descriptions are only available at client side and we probably need to add it at server side. If @jvermillard is not already on it, this will probably be my next task.
go for it @sbernard31
This should be fix now.
When reading an individual time resources (in this case /3/0/13) I get the time represented as an ASCII representation of the timestamp, e.g. 12. However, when reading it via the entire object, the webUI shows [HEX] 0B and then goes on to cycle through actual ASCII characters, only to return to the [HEX] representation when the printable characters run out.
I have observed this for integer resources as well.
I am running master @ fac6d08