There is now, check the GEM Setup Adv section.io_guy wrote:There should really be a way to just disable wireless.
If you get locked out however due to an issue with Ethernet, you'll have to do a full reset to the module.
There is now, check the GEM Setup Adv section.io_guy wrote:There should really be a way to just disable wireless.
Full reset of the WiFi/Ethernet module, not the GEM itself.io_guy wrote:Do you mean a full reset of the comm module or GEM itself?
thanks Ben!ben wrote:The recovery mode baud rate instructions are only for old firmwares. The GEM will now program at 115200 in Recovery Mode.
Put the baud back up to 115200, and load it with that baud.
Hmm, does sound like something might've been coming through the Ethernet. The Xbee wouldn't cause issues as I confirmed with Paul that it ignores the opposing COM port once it starts updating firmware.scyto wrote:Ok fixed.
I unplugged the ethernet cable.
I put a wifi adapter in my desktop so i could connect directly
Nothing else is connecting via wifi to the GEM
I happened to be at 19,200 but i don't think the baud has any bearing on this issues.
Upgrade went fine.
I have a hypothesis - that it is communication from another device that is consuming GEM data that causes the issue (Vera home controller or nodelink for ISY or somesuch) - in my system these connect by ethernet only.
For completeness the unit is a GEM-WE-X (Wifi/Ethernet V2 + XBee Module)
Alex
Well the only things are a Vera and the brultech plugin for that and Nodelink for the ISY. Nothing else i have interrogates the GEM.ben wrote:
Hmm, does sound like something might've been coming through the Ethernet. The Xbee wouldn't cause issues as I confirmed with Paul that it ignores the opposing COM port once it starts updating firmware.