Open wilfredallyn opened 5 days ago
It's a problem with v1.1.14, it's seems like it's been having some issues. The config isn't being gathered properly from that miner, and so when you set it, everything is being reset to defaults.
Try with v1.1.15rc3 and see if it works any better.
I ran it with v1.1.15, and it did not fix the issue. Where in the code should I look to debug this?
The function used by pyasic to do this is set_power_limit
, but for a BOSMiner S9 that uses get_config
internally.
Best thing you could do likely is send the contents of /etc/bosminer.toml
from the miner before updating the config. Also, make sure the miner is on the most recent version for S9s (22.08.1).
It should also say in the miner logs what the issue is, but it seems like a formatting issue with the config. Not sure what exactly the problem would be though, so knowing what key it doesn't like would help.
Version of the custom_component
1.1.14
Configuration
Describe the bug
When I use the slider in Home Assistant to set the power limit to 500w, the power will jump to 1400w and wipe out any other settings (e.g., pool info)
Steps
Debug log
It thinks it sets the power limit correctly to 500w without any error. Also, after setting the power limit, it doesn't know the make and model.
Before changing power:
Found miner: S9 (BOS+)
DeviceInfo(make=<MinerMake.ANTMINER: 'AntMiner'>, model=<AntminerModels.S9: 'S9'>, firmware=<MinerFirmware.BRAIINS_OS: 'BOS+'>, ...)
After changing power:
Found miner: Unknown (BOS+)
DeviceInfo(make=None, model=None, firmware=<MinerFirmware.BRAIINS_OS: 'BOS+'>, ...)
Questions
I have some familiarity with the home assistant and pyasic codebases, so I can help debug if you point me to the code to look at. Thanks!