I have a Plus i4 DC. Cloud is disabled, Wifi is very strong (-40 dbm), and there is no ‘native code’ running on it… it simply connects to the Shelly Integration and send shelly.click events… which there is an HA automation listening and setting a single input_select helper entity. Doesnt get more simple than that.
The issue is, when I look at the logs…
HA logs the event 2 to 3 seconds after the Shelly device logs the button press.
HA shows the event triggering under 1 second from the time the log shows the Shelly Event to the Automation Trace showing it executing.
Tried firmware 1.7.1 (stable) and 1.7.4 beta. 1.7.1 seems consistent at 2 seconds, the beta between 2 and 3 sec. This is the only Shelly device I have so nothing else to compare to, but also no other Shelly device to cause integration lag.
Why is using Websockets not recommended (and HA gives warning message about) on powered devices?
… I’m wondering if web sockets will solve the problem
This is a communications delay/problem or an issue with the Integration – settings, or bug, or something similar.
I’m new to Shelly devices but have done serious home automation for 25 years. I run HAOS and the PC (which is very fast) is not the issue - I have a very large HA setup, in all ways and all automation process in under 1 sec - even complex ones which this is super-basic.
I meant the automation is super basic. Even as an expert in many things HA, I follow a rule of … if I have not seen the exact issue posted about, or know I am not very experienced in the actual subject, I will often follow the thread and not post.
Shelly integration uses WebSocket by default, if you enable WebSocket outbound there will be two WebSocket connections in parallel, that’s why HA opens a repair issue on this.
