IoT device fails DHCP

I just purchased a Marble and after setting it up, one of the two devices I have connected to its LAN ports doesn’t get a DHCP address.

The first device is a Lutron Caseta bridge and it works fine. I can see it show up in the list of clients with a DHCP lease.

The other device is a Gecko In.Touch2 hot tub bridge, which works fine if when I have it connected to my old router (T-Mobile 5G). But when it’s connected to the Marble, all I see in the logs is a loop of DHCPDISCOVER/DHCPOFFER and no request or ack, and it stays red and doesn’t show up in the list of devices.

It’s obviously something to do with how its DHCP client or Ethernet is set up. Is there anything I can do from the router side to fix this? The device itself is pretty much a black box with an LED and no way to configure settings or anything.

Hi

Please try upgrading the firmware to beta 4.7.15 and configure a static IP for this device to see if it can be made to work.
Firmware download link: GL.iNet download center
Firmware upgrade guide: Upgrade - GL.iNet Router Docs 4
Address reservation guide: LAN - GL.iNet Router Docs 4

If that doesn't work, please share the Marble with us via GoodCloud so we can perform further remote diagnostics.