hass-miner
hass-miner copied to clipboard
Schnitzel
UI glitch: active toggle jumps back to inactive
"Active" toggle goes back to inactive after turning the miner on. After a minute or so it jumps to active. Presumably this is because the miner is returning an outdated state. But this might cause users to click the Active active button again in desperation.
Not sure what's possible here.
This has to do with the boot time of BraiinsOS+, and having no good way to check is_mining via pyasic. The way S9s on BOS+ report is_mining is by checking if the result of the devdetails RPC command returns a "not ready" response, which can indicate that the miner is still booting, OR that the miner is in shutdown mode. I'm not sure that there is a better way to get this, and even if there was, this state causes issues with gathering other data, such as temperature and hashboard data, as those commands are also shut down.
Not sure if you have seen anything that would fix this, I can reach out to the braiins team, but since pyasic uses the pause and resume RPC api commands, I'm not sure that there's any way to check status of that, since even checking if the /etc/bosminer process is running won't fix this.
It might make more sense to address this on the Home Assistant side. Isn't there a way to indicate "unknown" or to leave it "on" for a few seconds while waiting for it to come up?
The unknown idea is a good one, but I'm not actually sure of a way to tell the difference between "starting" and "paused" if that makes sense? I'll see what I can figure out.
I don't see a difference with your new tag, https://github.com/Schnitzel/hass-miner/issues/293#issuecomment-1904490795
Ok, this will have to be fixed on the pyasic side then. I'll see if I can find another thing I can cross reference to see if it is offline vs just starting.
I might have fixed this in 1.1.6, some weird stuff had to be done, but try it now.
I have this same problem. Toggle active / inactive seems inaccurate and therefore the miner reboots all the time
I have this same problem. Toggle active / inactive seems inaccurate and therefore the miner reboots all the time
You're using 1.1.6? You may want to re-add the miners after uodating. In theory now it should wait until the real state matches the set state, then start allowing the miner to update the state of the switch after that.
Yeah looks like I’m running v1.1.6rc4. I just added the miner like 2 hours ago. Will retry tomorrow by removing and reconnect the miner
Yeah looks like I’m running v1.1.6rc4.
I just added the miner like 2 hours ago.
Will retry tomorrow by removing and reconnect the miner
rc means "release candidate", it's actually pre-1.1.6. You still need another update.
Yeah looks like I’m running v1.1.6rc4. I just added the miner like 2 hours ago. Will retry tomorrow by removing and reconnect the miner
rc means "release candidate", it's actually pre-1.1.6. You still need another update.
aha okay! How can I update it (manually?) than? Because home Assistant says it is the latest version.
You may have to turn off beta cersions, HACS seems to be confused about how RC works.
I’ve been testing this evening and found out that the miner turns on and off continuously when I got fan control on auto instead of manual. Is this known?
ps: succeeded to reinstall and go to v 1.1.6
Are you talking about the fans ramping? Or the miner itself is shutting down?
The fans ramping up to 100% for like 1 minute, than it seems the miner restarts.
It's pretty likely that's just auto mode doing its thing. Is the hashrate affected?
Yes. Hash rate is affected, see attachment
Also attached my fan-settings.
It might not be applying immersion mode properly, is there anything in the miner logs about invalid configuration?
It might not be applying immersion mode properly, is there anything in the miner logs about invalid configuration?
This is part of the Bosminer-log. Is that what you are looking for?
2024-04-12T17:33:48.666187Z INFO bosminer_am1_s9::hashchain: Resetting hash board
2024-04-12T17:33:48.681678Z INFO bosminer_am1_s9::hashchain: Initializing hash chain 7, (difficulty 1)
2024-04-12T17:33:48.682117Z INFO bosminer_am1_s9::hashchain: Setting IP core baud rate @ requested: 115200, actual: 114679, divisor 0x6c
2024-04-12T17:33:48.682144Z INFO bosminer_am1_s9::hashchain: Resetting hash board
2024-04-12T17:33:49.153363Z WARN bosminer::client::stratum_v2: dev-fee:stratum2+tcp://[email protected]: Connection attempt error, attempt #1, next in: 100ms
Caused by:
failed to lookup address information: Name does not resolve
2024-04-12T17:33:49.191270Z WARN bosminer::client::stratum_v2: dev-fee:stratum2+tcp://[email protected]: Connection attempt error, attempt #1, next in: 100ms
Caused by:
Connection refused (os error 111)
2024-04-12T17:33:49.191261Z WARN bosminer::client::stratum_v2: Failed to connect to eth.eu1.sbicrypto.com:3333, user=RoelKyra.001 Connection attempt error, attempt #1, next in: 100ms
Caused by:
Connection refused (os error 111)
2024-04-12T17:33:49.191476Z WARN bosminer::client::stratum_v2: user:stratum+tcp://[email protected]: Connection attempt error, attempt #1, next in: 100ms
Caused by:
Connection refused (os error 111)
2024-04-12T17:33:52.661810Z INFO bosminer_am1_s9::hashchain: Starting chip enumeration
2024-04-12T17:33:52.772250Z INFO bosminer_am1_s9::hashchain: Starting chip enumeration
2024-04-12T17:33:52.788921Z INFO bosminer_am1_s9::hashchain: Starting chip enumeration
2024-04-12T17:33:53.117298Z INFO bosminer_am1_s9::hashchain: Discovered 63 chips
2024-04-12T17:33:53.117378Z INFO bosminer_am1_s9::hashchain: chain 8: setting frequency 546 MHz on All (error 1.986174 MHz)
2024-04-12T17:33:53.192429Z WARN bosminer::client::stratum_v2: dev-fee:stratum2+tcp://[email protected]: deadline has elapsed
Caused by:
0: deadline has elapsed
1: deadline has elapsed
2024-04-12T17:33:53.192443Z WARN bosminer::client::stratum_v2: dev-fee:stratum2+tcp://[email protected]: deadline has elapsed
Caused by:
0: deadline has elapsed
1: deadline has elapsed
2024-04-12T17:33:53.192729Z WARN bosminer::client::stratum_v2: dev-fee:stratum2+tcp://[email protected]: deadline has elapsed
Caused by:
0: deadline has elapsed
1: deadline has elapsed
2024-04-12T17:33:53.195999Z WARN bosminer::client::stratum_v2: dev-fee:stratum2+tcp://[email protected]: deadline has elapsed
Caused by:
0: deadline has elapsed
1: deadline has elapsed
2024-04-12T17:33:53.196007Z WARN bosminer::client::stratum_v2: dev-fee:stratum2+tcp://[email protected]: deadline has elapsed
Caused by:
0: deadline has elapsed
1: deadline has elapsed
2024-04-12T17:33:53.226202Z INFO bosminer_am1_s9::hashchain: Discovered 63 chips
2024-04-12T17:33:53.226266Z INFO bosminer_am1_s9::hashchain: chain 6: setting frequency 546 MHz on All (error 1.986174 MHz)
2024-04-12T17:33:53.240168Z INFO bosminer_am1_s9::hashchain: Discovered 63 chips
2024-04-12T17:33:53.240221Z INFO bosminer_am1_s9::hashchain: chain 7: setting frequency 546 MHz on All (error 1.986174 MHz)
2024-04-12T17:33:53.339067Z INFO bosminer_am1_s9::hashchain: Setting Hash chain baud rate @ requested: 1562500, actual: 1562500, divisor 0x01
2024-04-12T17:33:53.341192Z INFO bosminer_am1_s9::hashchain: Setting IP core baud rate @ requested: 1562500, actual: 1562500, divisor 0x07
2024-04-12T17:33:53.446575Z INFO bosminer_am1_s9::hashchain: Setting Hash chain baud rate @ requested: 1562500, actual: 1562500, divisor 0x01
2024-04-12T17:33:53.448715Z INFO bosminer_am1_s9::hashchain: Setting IP core baud rate @ requested: 1562500, actual: 1562500, divisor 0x07
2024-04-12T17:33:53.460632Z INFO bosminer_am1_s9::hashchain: Setting Hash chain baud rate @ requested: 1562500, actual: 1562500, divisor 0x01
2024-04-12T17:33:53.463266Z INFO bosminer_am1_s9::hashchain: Setting IP core baud rate @ requested: 1562500, actual: 1562500, divisor 0x07
2024-04-12T17:33:53.669117Z INFO bosminer_am1_s9::power: Setting voltage to 9.097457 (was: Some(9.402579))
2024-04-12T17:33:53.780098Z INFO bosminer_am1_s9::power: Setting voltage to 9.097457 (was: Some(9.402579))
2024-04-12T17:33:53.791348Z INFO bosminer_am1_s9::power: Setting voltage to 9.097457 (was: Some(9.402579))
2024-04-12T17:33:53.798527Z INFO bosminer_plus_am1_s9::tune: Tune/8: Status: start and preheat
2024-04-12T17:33:53.798607Z INFO bosminer_am1_s9: Preheat: waiting for target temperature: 89, current temperature: Unknown
2024-04-12T17:33:53.798778Z INFO bosminer_am1_s9::hashchain: Monitor watchdog temperature task started for hashchain 8
2024-04-12T17:33:53.919021Z INFO bosminer_plus_am1_s9::tune: Tune/6: Status: start and preheat
2024-04-12T17:33:53.921250Z INFO bosminer_am1_s9::hashchain: Monitor watchdog temperature task started for hashchain 6
2024-04-12T17:33:53.923107Z INFO bosminer_am1_s9: Preheat: waiting for target temperature: 89, current temperature: Unknown
2024-04-12T17:33:53.930744Z INFO bosminer_plus_am1_s9::tune: Tune/7: Status: start and preheat
2024-04-12T17:33:53.930827Z INFO bosminer_am1_s9: Preheat: waiting for target temperature: 89, current temperature: Unknown
2024-04-12T17:33:53.931166Z INFO bosminer_am1_s9::hashchain: Monitor watchdog temperature task started for hashchain 7
2024-04-12T17:33:54.158966Z INFO bosminer_am1_s9: Preheat: waiting for target temperature: 89, current temperature: Unknown
2024-04-12T17:33:54.158962Z INFO bosminer_am1_s9: Preheat: waiting for target temperature: 89, current temperature: Unknown
2024-04-12T17:33:54.159060Z INFO bosminer_am1_s9: Preheat: waiting for target temperature: 89, current temperature: Unknown
2024-04-12T17:33:54.162875Z WARN bosminer::client::stratum_v2: dev-fee:stratum2+tcp://[email protected]: Connection attempt error, attempt #1, next in: 100ms
Caused by:
failed to lookup address information: Name does not resolve
2024-04-12T17:33:54.199582Z WARN bosminer::client::stratum_v2: Failed to connect to eth.eu1.sbicrypto.com:3333, user=RoelKyra.001 Connection attempt error, attempt #1, next in: 100ms
Caused by:
Connection refused (os error 111)
2024-04-12T17:33:54.202390Z WARN bosminer::client::stratum_v2: dev-fee:stratum2+tcp://[email protected]: Connection attempt error, attempt #1, next in: 100ms
Caused by:
Connection refused (os error 111)
2024-04-12T17:33:54.203695Z WARN bosminer::client::stratum_v2: user:stratum+tcp://[email protected]: Connection attempt error, attempt #1, next in: 100ms
Caused by:
Connection refused (os error 111)
2024-04-12T17:33:55.160101Z INFO bosminer_am1_s9: Preheat: waiting for target temperature: 89, current temperature: Unknown
2024-04-12T17:33:55.160196Z INFO bosminer_am1_s9: Preheat: waiting for target temperature: 89, current temperature: Unknown
2024-04-12T17:33:55.160101Z INFO bosminer_am1_s9: Preheat: waiting for target temperature: 89, current temperature: Unknown
2024-04-12T17:33:56.160883Z INFO bosminer_am1_s9: Preheat: waiting for target temperature: 89, current temperature: Unknown
2024-04-12T17:33:56.160989Z INFO bosminer_am1_s9: Preheat: waiting for target temperature: 89, current temperature: Unknown
2024-04-12T17:33:56.160883Z INFO bosminer_am1_s9: Preheat: waiting for target temperature: 89, current temperature: Unknown
2024-04-12T17:33:57.162216Z INFO bosminer_am1_s9: Preheat: waiting for target temperature: 89, current temperature: Unknown
2024-04-12T17:33:57.162375Z INFO bosminer_am1_s9: Preheat: waiting for target temperature: 89, current temperature: Unknown
2024-04-12T17:33:57.166308Z INFO bosminer_am1_s9: Preheat: waiting for target temperature: 89, current temperature: Unknown
2024-04-12T17:33:58.162757Z INFO bosminer_am1_s9: Preheat: waiting for target temperature: 89, current temperature: Unknown
2024-04-12T17:33:58.162781Z INFO bosminer_am1_s9: Preheat: waiting for target temperature: 89, current temperature: Unknown
2024-04-12T17:33:58.166852Z INFO bosminer_am1_s9: Preheat: waiting for target temperature: 89, current temperature: Unknown
2024-04-12T17:33:58.192732Z WARN bosminer::client::stratum_v2: dev-fee:stratum2+tcp://[email protected]: deadline has elapsed
Caused by:
0: deadline has elapsed
1: deadline has elapsed
2024-04-12T17:33:58.192729Z WARN bosminer::client::stratum_v2: dev-fee:stratum2+tcp://[email protected]: deadline has elapsed
Caused by:
0: deadline has elapsed
1: deadline has elapsed
2024-04-12T17:33:58.193049Z WARN bosminer::client::stratum_v2: dev-fee:stratum2+tcp://[email protected]: deadline has elapsed
Caused by:
0: deadline has elapsed
1: deadline has elapsed
2024-04-12T17:33:58.197064Z WARN bosminer::client::stratum_v2: dev-fee:stratum2+tcp://[email protected]: deadline has elapsed
Caused by:
0: deadline has elapsed
1: deadline has elapsed
2024-04-12T17:33:58.197314Z WARN bosminer::client::stratum_v2: dev-fee:stratum2+tcp://[email protected]: deadline has elapsed
Caused by:
0: deadline has elapsed
1: deadline has elapsed
2024-04-12T17:33:58.908319Z INFO ii_hwmon: Address(152) manufacturer_id=0x55 device_id=0x0
2024-04-12T17:33:59.032972Z INFO ii_hwmon: Address(152) manufacturer_id=0x55 device_id=0x0
2024-04-12T17:33:59.044291Z INFO ii_hwmon: Address(152) manufacturer_id=0x55 device_id=0x0
2024-04-12T17:33:59.163900Z INFO bosminer_am1_s9: Preheat: waiting for target temperature: 89, current temperature: Unknown
2024-04-12T17:33:59.163900Z INFO bosminer_am1_s9: Preheat: waiting for target temperature: 89, current temperature: Unknown
2024-04-12T17:33:59.163992Z INFO bosminer_am1_s9: Preheat: waiting for target temperature: 89, current temperature: Unknown
Ah. I see whats going on, it looks like your miner isn't finding the temperature sensors sometimes, and it will have an unknown temperature, which causes the miner to stop mining since it tries to be safe about it. If you take a look at the graph picture you can see it, the miner runs, the yellow line starts tracking temp, the temp dissappears, then the miner shuts down.
You might want to submit support logs to the braiins team in their telegram, they will be more helpful in this case.
Ah thanks, will try that. At least i got something to dive into! Keep you posted.