Connect GEM to Home Assistant

[rogerfar]

Managed to make it work, turns out that if you leave COM2 as "Disabled" it does NOT do what the manual states, it basically prevents all communication.

I set COM2 to BIN32 and COM1 to JSON and was able to receive the JSON. I now switched both to BIN32 and Home Assistant is now parsing the data.

Is your COM1 or COM2 Flow Control on? They should both be set to "Off". That will cause it to hang as Flow Control is left floating.

No, the status page shows both COM1 and COM2 FLOW OFF.

[ben]

Managed to make it work, turns out that if you leave COM2 as "Disabled" it does NOT do what the manual states, it basically prevents all communication.

I set COM2 to BIN32 and COM1 to JSON and was able to receive the JSON. I now switched both to BIN32 and Home Assistant is now parsing the data.

Is your COM1 or COM2 Flow Control on? They should both be set to "Off". That will cause it to hang as Flow Control is left floating.

No, the status page shows both COM1 and COM2 FLOW OFF.

When COM2 packet format is set to Disabled it sends the same packet format as COM1. You can leave it as-is or try disabling it again then checking the GEM Sys LED if you aren't getting packets thru. The Sys LED will flash red with every packet sent.

[rogerfar]

Is your COM1 or COM2 Flow Control on? They should both be set to "Off". That will cause it to hang as Flow Control is left floating.

No, the status page shows both COM1 and COM2 FLOW OFF.

When COM2 packet format is set to Disabled it sends the same packet format as COM1. You can leave it as-is or try disabling it again then checking the GEM Sys LED if you aren't getting packets thru. The Sys LED will flash red with every packet sent.

I played with it again over the weekend but it's still showing the same behaviour.

When disabling COM2, no matter what COM1 is set to (with flow control off) it will only send 0x80 bytes, not the actual packets. The LED blinks every 5 seconds as expected.

But when I enable COM2 (any packet format) it will start sending the proper packet on COM1.

[ben]

I played with it again over the weekend but it's still showing the same behaviour.

When disabling COM2, no matter what COM1 is set to (with flow control off) it will only send 0x80 bytes, not the actual packets. The LED blinks every 5 seconds as expected.

But when I enable COM2 (any packet format) it will start sending the proper packet on COM1.

The setup page has a "Status" page, can you attach that information? I'll see if there's anything weird in there.

[rogerfar]

For sure.

This is the setup currently, working for me:



This is when it's not working:

[ben]

For sure.

This is the setup currently, working for me:



This is when it's not working:

Does the ENG always show 0.0?

[rogerfar]

In the webinterface yes, when I use the GEM utility:

[ben]

We ended up finding a recently introduced bug with the packet formats that we're working on a fix for.

We've recently (in the last 6 months) have implemented an RF module for the DashBox/GEM connection and it's likely related to that.

[ben]

You can keep it running as-is or load this F/W here:

https://brultech.com/software/files/dow ... _5.39_.fmw

To load the firmware,

- Download the GEM Network Utility: https://brultech.com/software/files/dow ... _8.01_.exe
- Connect via TCP Client at the top.
- Click the Get GEM Info button.
- Click Select Firmware File and select the F/W file downloaded above.
- Click Start and let it run to 100%, you should see the SYS LED flash on the GEM while programming.

Once finished, you're good to go.

[rogerfar]

Just updated and changed it to only transmit on COM1, works perfectly!

Also the FW version is now showing up again in the web interface.

Thanks!