Home Assistant with 3 GEMs and a 1240

[crazydane]

I have 2 GEMs connected to a Dashbox and 1 with an Ethernet module. I also have a 1240 with an EtherPort.

Here is the view from the Dashbox:



I tried switching the GEM in the shop (last one in above screenshot), to Bin-32-NET and HA did not see it. I'm assuming it is setup to use port 8000 since that is the link I use to get into setup mode?

I did fire up the GEM Network Utility, but what I see there looks a little odd:



10.0.1.151 is my GEM in the shop, but it can't connect. It is also not able to connect to my 1240, but I guess that is to be expected from my utility?

Anyway, with the shop GEM set to Bin-32-Net, HA does not see the GEM at all.

I added the following to my configuration.yaml:



But after restarting HA, nothing shows up on my Integrations tab.

Also, would best practices be to have my GEMs talk directly to HA, or would I be better of having the GEMs report directly to HA? That of course would mean adding Ethernet modules to my 2 GEMs that are currently connected to the Dashbox via serial.

I looked around in the Network and System menus on the Dashbox, but didn't find anywhere where I could change the packet type to Bin-32-Net.

Also, is a 1240 able to report directly to HA, or only GEMs?

Thanks!

[ben]

The 2 GEMs on the DashBox you should be able to get those connected up via Packet Forwarding under Add-ons in the DashBox Settings.

The DashBox can take in binary packets via 8001/8002 in the new F/W (Ethernet usually requires HTTP Post). Right now however it binds COM Port to External Port so both GEMs would get pushed onto the same port. This needs to be extended to COM Port -> Device -> Port for it to work correctly.

[ben]

Also, is a 1240 able to report directly to HA, or only GEMs?

I'm unaware of an ECM-1240 integration for HA.

[crazydane]

Ok, so I enabled packet forwarding on the Dashbox (10.0.20.99:8009) and I updated the configuration.yaml to reflect that port and also changed the GEM serial number to one of the GEMs hanging off the Dashbox.

On the GEM in question, under advanced settings/system settings, real-time is ON and primary packet format appears to be locked to Bin-48-NET-Time.

Secondary Packet Format is disabled (Use COM1) and secondary packet format is Bin-32 NET (RF default).

Is that what I want?

Where is the COM Port -> Device -> Port you make reference to?

Thanks!

[ben]

Ok, so I enabled packet forwarding on the Dashbox (10.0.20.99:8009) and I updated the configuration.yaml to reflect that port and also changed the GEM serial number to one of the GEMs hanging off the Dashbox.

On the GEM in question, under advanced settings/system settings, real-time is ON and primary packet format appears to be locked to Bin-48-NET-Time.

Secondary Packet Format is disabled (Use COM1) and secondary packet format is Bin-32 NET (RF default).

Is that what I want?

Where is the COM Port -> Device -> Port you make reference to?

Thanks!

It's just COM Port -> Port for now. Does HA require a separate port for each GEM device?

[crazydane]

You use a single port for all GEM devices in HA. You group by GEM serial number.

Anyway, so you're saying to use port 8001 since that is what the GEM on COM1 on the Dashbox is connected to, like this?



That by itself is still not working as I don't see anything GEM related under Integrations in HA still.

[ben]

You use a single port for all GEM devices in HA. You group by GEM serial number.

Anyway, so you're saying to use port 8001 since that is what the GEM on COM1 on the Dashbox is connected to, like this?



That by itself is still not working as I don't see anything GEM related under Integrations in HA still.

Assuming 10.0.20.99 is the server hosting HA and given your settings above, it looks like you'd be using Port 8000. It's whatever port is listening for the GEMs on the server. See if you can get the 2 STS cabled GEMs sending to HA before trying the Ethernet GEM.

-------------------

Port 8001 is a Port you can try sending Binary Packets to the DashBox via the GEM. The same client/server connection you use to configure the GEM Setup Webpage thru the DashBox also checks for valid packets from both client/server ends.

If you try this later, make sure you also put a very low Idle Time on the Ethernet module (I would consider 1-2 seconds) to close the Client connection.

[crazydane]

This is my setup:

10.0.1.150 Dashbox with 2 GEMs connected directly to it via RS232 COM ports
10.0.1.151 GEM with Ethernet module
10.0.20.99 My HA server

10.0.1.150:8001 takes me to GEM1 from a browser
10.0.1.150:8002 takes me to GEM2 from a browser
10.0.1.151:8000 takes me to GEM3 from a browser

The below does not work:

configuration.yaml:

greeneye_monitor:
port: 8000
monitors:
- serial_number: "01001221"
channels:
- number: 1
name: GEM1_Channel1
- serial_number: "01001222"
channels:
- number: 1
name: GEM2_Channel1
- serial_number: "01021400"
channels:
- number: 1
name: GEM3_Channel1

The above with with Packet Forwarding on the Dashbox set to:

IP: 10.0.20.99
Port: 8000
RS232 Port: Both
Persistent Connection: checked
Device: All Devices (the dropdown only lets be pick between my 2 1240 devices)

Not sure what I'm doing wrong...

[ben]

That all looks good for the 2 STS connected GEMs.

Is there any debugging on Home-Assistant? Does it show when a connection is made for example?

Are your STS connected GEMs set to run packet format Bin-32-Net? It looks like that's the only one HA supports. The DashBox supports both Bin-48-NET-Time and Bin-32-NET since the b-series.

[crazydane]

I installed netstat on my HA server and verified that HA is listening for traffic on port 8000:



The 2 STS connected GEMs were set to Bin-48-NET. I changed them both to Bin-32-Net and after a few seconds, the Dashbox saw them again. I'm on the latest firmware (4.2.4b17c).

But alas, HA is still not seeing anything. I'll enable debug logging on the HA server to see what that might tell me.