Jens B.

@Profil404 The output you posted looks quite unexpected. The "trying to connect to MQTT server ..." is from the default firmware but the rest must be from your own code...

Happy New Year, soundanalogous! As you already assumed, I am talking about serial data from a peripheral device. I the meantime I tried something similar by checking Firmata::available before adding...

Changing the LAN-Module from ENC28J60 to W5100 shows that the reconnect issue seems to be caused by the UIPEthernet driver. The Firmata reconnect works as expected even with serial receive...

Thanks for your support. I will contact Norbert about this.

After less than 10 hours continuous operation the setup with the W5100 also failed - this time not caused by a reconnect but in mid operation by ceasing to transmit...

Thanks for the suggestion, but I wanted to avoid any issues with DHCP, so I used a fixed IP from the start. An interesting aspect is the unchanged traffic indication...

To make sure there are no side effects caused by my setup, I reinstalled/updated all software components: - Arduino IDE 1.6.7 - Teensyduino 1.27 - up-to-date Ethernet for Teensy (https://github.com/PaulStoffregen/Ethernet)...

For me this is not a breadboard experiment (some things would be easier to test but it is not easy to replicate the setup). Because of the current instability with...

I use a modified version of the current official release of FHEM as host application (see recent merges in https://github.com/ntruchsess/fhem-mirror and https://github.com/ntruchsess/perl-firmata). If SERIAL_MESSAGE support is missing, I will make...

The SERIAL_DATA telegram handling in FHEM is the commit I have provided but I think you wanted to say STRING_DATA. STRING_DATA will be logged anyway but SERIAL_DATA will be passed...