GEM's stop responding when using DNS or sending to HASS
Posted: Sun Oct 06, 2019 5:39 pm
Hi, my GEM's stop responding, I think it has to do with the combination of data format or DNS in network config or sending data to Home Assistant.
I have 4 GEM's, early models, installed when I built the house in 2012, but did not touch them for many years (too much trouble to get (too short) CT leads routed to GEM cabinets.
About a year or two ago I tried to get one working, had a hell of a time to get it to connect and update firmware, including password reset flash and button dance, gave it up.
I am now installing Home Assistant (HASS), and I want to send data from GEM to HASS which seems to be reasonable well supported.
I followed the instructions to prep for GEM:
https://www.home-assistant.io/integrati ... ye_monitor
I have two GEM's configured, with lots of trial and error I updated the firmware on both to COM:4.36 and ENG:1.49, and I replaced batteries.
I set Ethernet Only (Ethernet Module 4.1) to:
Local Port : 80
Remote Port : 8000 (HASS GEM listening port)
Server IP: 192.168.1.26 (HASS listening IP)
Ethernet Mode: Mixed
Packet send format is 4, BIN48-NET-Time, and interval is 10s.
Data Post is all empty.
In this configuration I can Get GEM Info and I can view Live Data.
When I enable DNS, and I set Server to hass.home.insanegenius.net (which resolves to 192.168.1.26), things go wrong, and I can no longer call Get GEM info, and the web pages no longer load.
Even when the configuration is set to IP and not DNS, when I enable HASS, and the GEM can start posting data to HASS, the GEM again becomes unresponsive.
A few minutes after HASS starts listening to GEM traffic, GEM becomes unresponsive.
To get the GEM to become responsive again, I need to disable HASS, such that it is no longer listening for GEM traffic, and the network configuration needs to be IP not DNS, then I can again get GEM info.
Can I upgrade the GEM ethernet/COM module to something faster / more reliable / more feature rich, maybe an ESP32 device or a Pi?
This is just so frustrating, any ideas how to solve this?
I have 4 GEM's, early models, installed when I built the house in 2012, but did not touch them for many years (too much trouble to get (too short) CT leads routed to GEM cabinets.
About a year or two ago I tried to get one working, had a hell of a time to get it to connect and update firmware, including password reset flash and button dance, gave it up.
I am now installing Home Assistant (HASS), and I want to send data from GEM to HASS which seems to be reasonable well supported.
I followed the instructions to prep for GEM:
https://www.home-assistant.io/integrati ... ye_monitor
I have two GEM's configured, with lots of trial and error I updated the firmware on both to COM:4.36 and ENG:1.49, and I replaced batteries.
I set Ethernet Only (Ethernet Module 4.1) to:
Local Port : 80
Remote Port : 8000 (HASS GEM listening port)
Server IP: 192.168.1.26 (HASS listening IP)
Ethernet Mode: Mixed
Packet send format is 4, BIN48-NET-Time, and interval is 10s.
Data Post is all empty.
In this configuration I can Get GEM Info and I can view Live Data.
When I enable DNS, and I set Server to hass.home.insanegenius.net (which resolves to 192.168.1.26), things go wrong, and I can no longer call Get GEM info, and the web pages no longer load.
Even when the configuration is set to IP and not DNS, when I enable HASS, and the GEM can start posting data to HASS, the GEM again becomes unresponsive.
A few minutes after HASS starts listening to GEM traffic, GEM becomes unresponsive.
To get the GEM to become responsive again, I need to disable HASS, such that it is no longer listening for GEM traffic, and the network configuration needs to be IP not DNS, then I can again get GEM info.
Can I upgrade the GEM ethernet/COM module to something faster / more reliable / more feature rich, maybe an ESP32 device or a Pi?
This is just so frustrating, any ideas how to solve this?