Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added switches for each device which allow toggling mining #15

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

Newlance
Copy link

@Newlance Newlance commented Nov 11, 2021

Requires additional Manage Rigs permission

  • To do: Set switch to reflect the current state on init. (Currently defaults to off after HA reboot.)
  • Occasionally the custom component fails to load on HA start. Usually fixed by restarting HA.
  • When switches are toggled occasionally a false error is reported. This could be due to async call. The desired behavior still occurs though.

Evan Lawrence and others added 4 commits November 10, 2021 19:49
…ing.

very basic, needs testing.

* To do: Set switch to reflect the current state on init. (Currently defaults to off after HA reboot.)
* Occasionally the custom component fails to load on HA start.  Usually fixed by restarting HA.
* When switches are toggled occasionally a false error is reported.  This could be due to async call.  The desired behavior still occurs though.
…(there is a delay for the status to update into Home Assistant)

- Added property to switches which contains the last response from the API.  This will reflect "Success!" or otherwise the error message that was provided by the API.
- Added additional properties 'status' and 'device' to switches.
Copy link
Author

@Newlance Newlance left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Switches now properly reflect device state (albeit with a delay).
Switches also now have a property that reflect the API response.

@marciogranzotto
Copy link

@brianberg any reason not to merge this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants