Throttling from useEntity

[maumi]

Hey, I think there is a delay caused by the throttle of the useEntity.
I just combined 2 demo codes from your documentation to measure the timings of the rendering.
Without a throttle set the change of the entity seems to happen around 200ms later and with a throttle set to 0 (as in example code) the change happens roughly 50ms later.
I personally think that the throttle happens because the value is changed at the second re-render of react (After button click the entity is first at the same state and only changes at the second re-render (which seems to be throttled)

Example code below

import { HassConnect, useEntity } from '@hakit/core';

function Office() {
  const lightStrip = useEntity('input_boolean.mdhaustuerreset', {
    returnNullIfNotFound: true,
    throttle: 0,
    history: {
      disable: true,
    },
  });
  console.info(Date.now(), 'light state', lightStrip?.state);
  // can now access all properties relating to the light
  return lightStrip?.state ?? 'unknown';
}

function UseServiceExample() {
  const entity = useEntity('input_boolean.mdhaustuerreset');
  return (
    <button
      onClick={() => {
        console.log(Date.now());
        entity.service.toggle();
      }}
    >
      TOGGLE LIGHT
    </button>
  );
}

function App() {
  return (
    <>
<HassConnect hassUrl={import.meta.env.VITE_HA_URL} hassToken={impo=t.meta.env.VITE_HA_TOKEN}>
        <Office />
        <UseServiceExample />
      </HassConnect>
    </>
  );
}

export default App;

[shannonhochkins]

This all sounds intentional - 50ms for home assistant to respond with a 150ms delay, i would double check this, however are you saying that 50ms isn't fast enough or even 200ms for your UI to update?

[maumi]

It‘s not about fast or fast enough.
It is about avoidable 150ms.
and the 50ms Are for a helper boolean without any real functionality. At a real light Switch with the relais Delay it is more base time.

[shannonhochkins]

1. I don't control how fast home assistant can respond, that's up to your hardware
2. In the attached screenshot you can see the time I emit the "toggle" event, and the time it took for the websocket connection to respond
3. We can measure the time it takes for the react component to respond by using performance.now (see example below.

import { useEffect, useRef } from 'react';
import { useEntity } from '@hakit/core';

function Office() {
  const lightStrip = useEntity('light.all_office_downlights', {
    throttle: 0,
    history: {
      disable: true,
    },
  });

  // Store the timestamp of the last render
  const lastRenderTimeRef = useRef<number | null>(null);

  useEffect(() => {
    if (!lastRenderTimeRef.current) return;
    // Calculate how long since the last update/render
    const now = performance.now();
    const elapsed = now - lastRenderTimeRef.current;
    console.log('Time between updates:', elapsed, 'ms');
    // Update the reference to the current time
    lastRenderTimeRef.current = now;
  }, [lightStrip.state]); // Dependency array: runs whenever lightStrip.state changes

  return <button onClick={() => {
    lastRenderTimeRef.current = performance.now();
    lightStrip.service.toggle();
  }}>toggle</button>;
}

Toggle event ws sent at: 10:43:59.485
HA responds with update at: 10:43:59.770
Total HA request -> response: 295ms

Time taken from the click dispatch to the react component updating 297.5ms - which is within ~50ms of home assistant also updating

[shannonhochkins]

I'm still confused but what you're actually after, it's not clear exactly what your issue is? One thing we could change the method so it fires at the leading edge of the throttled function as well as the trailing (if another event was sent to update) - which might omit the initial throttle time of 150ms if only one event was sent, it should fire as if the delay was 0ms

[maumi]

When you Take my example Code and just set for Demo purposes throttle to an abnormal high value of 5000 than you should see that the entity State Change is only visible After 5,x s. And I would say that is Not what you intended with the throttle.
I just want to discuss that the throttle seems not to work as you designed it.

[shannonhochkins]

Okay, think we got there in the end - You're saying the throttle is acting like a delay, and i can replicate this behavior and will have it out and fixed as soon as possible

[shannonhochkins]

Released with v5.0.8 - Let me know if you have any other issues :)

[maumi]

thanks for the fast and working fix