Java error

Hi everyone, I keep getting this java error and I'm unsure on how to fix it, any help would be much appreciated. The device is a shelly one relay. Many thanks
Mike

My guess is the relay is taking too long to respond or not responding at all, based on the socket timeout reference in the error. Does the relay physically operate how you expect when commands are issued by HE? Can you detect a lengthy delay between issuing a command in HE and the relay actually doing what you told it to?

I've just realised I've put the ip address in wrong and it seems to be working fine now, this definitely wasn't the issue to start with as I've deleted the device quite a few times and re-added it, oh well its working now. sorry for wasting your time and thanks for replying.

1 Like

the device is now working fine but im still getting this message in the logs, any ideas why ?

this is the device settings

Many thanks

Might be worth turning on some of the logging options on the device, particularly the debug logging, and see if anything else shows up in the logs.

I'm getting this error again, the device will operate as it should when I go the the device manager and operate/toggle it manually but I cant get it to work any other way. I've attached a copy of the logs and any help would be much appreciated.

Without knowing much about Shelly... (I'm sure she's nice :wink: )

Looking at the logs again... And your previous comment back in October '24 that the device was working fine even when you were still seeing socket timeout errors in the logs.... A couple of questions:

  • "can't get it to work any other way".... What does that include...? Do you have any examples? RM rules, etc?
  • I did not ask earlier, but what driver are you using? Is it a built-in one or a custom driver? My guess from your screenshots is a built-in driver, but just want to be sure...
  • What HE platform version are you running? Detail about the HE hub model and mode of connecting to the LAN / Internet could also be useful (ethernet vs Wi-Fi), but anything more technical than that can wait...
  • Does the HE hub have a reliable Internet connection? I am wondering if the mention of a firmware check in earlier screenshots could be a hint to an issue with communicating with the big bad world, rather than any local comm's with the device... Hence the speculation about the device performing as expected but maybe firmware checks failing. All speculation at this point...