core: Rachio switches in front end not working.

The problem

Rachio switches in the front end do not reflect real world state. For example, if I turn on a switch to manually enable a watering zone, the switch will automatically toggle back to off after a few seconds even though the manual watering begins on the Rachio controller.

Environment

arch armv7l
dev false
docker true
hassio true
os_name Linux
os_version 4.19.106-v7
python_version 3.7.7
timezone America/Los_Angeles
version 0.108.3
virtualenv false
  • Home Assistant Core release with the issue: Unknown. I added it around .107 and hasn’t worked once.
  • Last working Home Assistant Core release (if known): N/A
  • Operating environment (Home Assistant/Supervised/Docker/venv): Docker
  • Integration causing this issue:
  • Link to integration documentation on our website:

Problem-relevant configuration.yaml

rachio:
  api_key: !secret rachio_api
  manual_run_mins: 1

logger:
  default: warn
  logs:
    homeassistant.components.rachio: debug

Traceback/Error logs

I am not seeing any info in the logs despite changing the Rachio Component to "debug".  I included my logger config above, so please let me know if I need to modify something there to get valid traceback data.

Additional information

It seems that after a restart of HA it will refresh the Rachio switches with current state. For example if I change the switch.rachio_main_in_standby_mode in the front end, it will go back to “off” after a few seconds, even though the Rachio controller has in fact been put into standby mode. After a restart of HA, the switch.rachio_main_in_standby_mode will show the correct position of on. Seems like it is getting that info from the Rachio API upon reboot only?

Thanks in advance to whomever can take the time to look into this.

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 22 (17 by maintainers)

Most upvoted comments

Thats great and sorry for the false alarm, I am just used to testing things in my dev instance and forgot about the externally accessible part lol

@bdraco my bad when I tested your custom component at first I realized that my dev instance was not externally accessible 🙈 so I ended up testing in my prod instance which is externally accessible and I see that the switch stays on with your custom component and the webhook returns a 405 error. Odd that the webhook URL hits smartthings lol but the code in your custom component is indeed working as expected.

That’s good news as that’s what’s in 0.109

ok ill take a look at it in a few and report back

Initially no it wasn’t creating a webhook.

However I removed the rachio integration, restarted HA, then re-added the integration and it created the webhook.

So far it seems like it is working now, going to do a few more tests over the next couple of days and will close it out if its working.

Thanks for all the help here.