« Reply #62 on: September 01, 2015, 09:04:25 am »
This is the down side of using the luup io module to communicate with a device. If the power fails on the remote device, then the link cannot be re-established once power is restored, unless Vera is restarted. This is a major Vera problem.
This still seems to be a problem with the Ethernet Gateway in its current form?
Due to this limitation, users may be better off having the Arduino Gateway act as a web server? You would command with GETs or POSTs and receive data in say json.
I'm presuming that the actual constraint is that you can't change the implementation of the gateway on the Arduino... this should be controller independent.
That being the case, I would suppose that a re-implementation using the LuaSocket library can go around the
luup.io.open (or, rather, lack of
luup.io.close problem.)
Also, does the MQTT gateway approach offer another way around this?
(New to MySensors, so much catching up to be done. Hence the interest in an old post.)

Logged
3x Vera Lite-UI5/Edge-UI7, 25x Fibaro, 23x TKB, 9x MiniMote, 2x NorthQ Power, 2x Netatmo, 1x Foscam FI9831P, 9x Philips Hue,
Razberry, MySensors Arduino, HomeWave, AltUI, AltHue, DataYours, Grafana, openLuup, ZWay, ZeroBrane Studio.