Maybe I should start a new thread but I'm having issues with the mysensors driver for version 1.4/1.5. It just stops listening on the port after a while and I have to reload the driver in order to make it processing messages again.
In the management/drivers page there's nothing coming in under "last known messages" but if I do "cat /dev/ttyUSB0" I can see lots of messages. That makes me think the problem is with the driver. Does it sound familiar?
I'm on the latest build released a few days ago and using a serial gateway.
Hi John, appLog.txt
I also tried using datatype string but it doesen't work. Meanwhile I have studies the log files more detailed and found the following behavior:
when defining the device skeletal and when updating the derived device (first approx. 25 lines in the log file V_STATUS is declared as string with values 51 resp. 52 as specified in the web interface. The entity is "Modul 433 MHz".
Later on, when using the toggle switch in the web interface the value has changed in the decription in the log file (see line 164 or 185) value has been changed to on/off. With this definition it seem that the mysensors-Plugin is feeded has been changed from the specified values.
My conclusion is that the change is taking place somewhere outside the mysensors-plugin.
By the way, if I change the type to string do I have to use quotation marks in the web interface?
The reason that the log is being filled is because despite not having the gateway ready message data can become available. I have been thinking of adding an extra switch in the software that if gateway ready is not received, but other data arrives to toggle the internal state and have the gateway marked ready. And when first data arrives ask for the version number.
I do not have enough knowledge about the differences between the FTDI FT232RL (nano) and ATmega32U4 (pro micro) when they are ready to accept data to be send to/from the gateway. If the usb chip is not ready to accept and gateway ready is send, data is lost. But this is an assumption (Arduino's only have receive and not send buffers as far as i know), maybe some hardware guru can shine a light on it.
The server is able to do debug logging. Could you please turn this logging on by going to: "system" > "server" > "debug logging" and switch the toggle button.
After this re-connect the serial device, turn no discovery and let the log list be filled as your screenshot shows. After a couple of minutes turn on debug logging and send me the following file "logs/system/appLog.txt" to firstname.lastname@example.org (as it may contain sensitive information so you do not want to post it online) and include a link to this thread so i know it is yours.