xelemorf
xelemorf
I have the same problem
Issue still present with Firefox Nightly 113.0a1 (2023-03-23) (64-bit). Worked with Edge.
I've already attached a debug log, did you check that one? Do you need me a quick restart of HA or restart the host system instead (with debug logging enabled...
Attaching the debug log after HA restart, toggled each switch a couple of times. [home-assistant_tractive_2024-02-25T16-39-18.879Z.log](https://github.com/home-assistant/core/files/14397046/home-assistant_tractive_2024-02-25T16-39-18.879Z.log)
1. Copied content to "\\ha\config\custom_components\tractive\" 2. restarted HA 3. enabled debug logging 4. toggled switches, switches did not turn on at all (visually seemed to turn on but instantly turned...
Yes, I was using such automations which reloads the whole integration if it failed to report back in certain amount of time, I needed them previously for the issues we...
If I remove the custom component you provided even after a host restart I got the same issue again: Failed to call service switch/turn_off. 'pending'. My reload config entity automations...
I have tried the following scenarios: - removed the custom component, rebooted host: not working, same as before - removed custom component, removed integration, rebooted host, installed integration: not working...
It appears this has nothing to do with powersaving and as you mentioned most likely I have hit somekind of API limit, because it just stopped working, switches does not...