Antminer T21 Integration problems since >1.1.13

[mark0st83]

Since version 1.1.13 I have problems with installation of a new miner T21.

In version 1.1.13 I can install it and everything works fine. Due the problem with pyasic I have to reinstall it via shell if there is a HA Update. (pyasic 0.59.6)

If I upgrade to versions above 1.1.13 the "installation-window" is missing the SSH login so the installation fails. (pyasic to 0.60.10)

If I upgrade to >1.1.13 with an already installed T21 the entities doubles, but the new one works. (also pyasic 0.60.10)
A new installation because of the double entities is also not possible.

I have no idea what can be the problem. I thought the problem will be fixed without my report, but T21 might be not the "standard-miner" and there was no report since 1.1.13 so far.

[b-rowan]

This might be related to #393, I have a fix in the works for that, I will look into this more closely once that is solved.

[mark0st83]

This might be related to #393, I have a fix in the works for that, I will look into this more closely once that is solved.

I don’t think that this is the Same Problem. I‘ve installed the pyasic Version that is mentioned in the error log.

Other Miners like S9 or Bitaxe still work.
Only the T21 with Braiins is not installable after 0.1.13.

Username and Password for the WebUI ist shown, SSH Login is missing.
This is shown on the S9-Installation.

I‘ve tried also the 0.17.rc5

[b-rowan]

Username and Password for the WebUI ist shown, SSH Login is missing.
This is shown on the S9-Installation.

Newer models don't use SSH, since it's quite inefficient compared to the APIs.

If you have some logs on what's happening I can look into it.

[mark0st83]

But the same miner is running on 0.1.13, as i mentioned.

I've installed 0.1.17rc5 again and updated pyasic to 0.62.1 (Error said this)
I deleted the Bitaxe and installed it again -> working

I deleted the T21 and installed it again -> not working

This problem occurs since 0.1.13, before that I had no problems with this miner.
(And SSH login was showed like on the screenshots above)

Log:

Dieser Fehler wurde von einer benutzerdefinierten Integration verursacht

Logger: py.warnings
Quelle: custom_components/miner/coordinator.py:55
Integration: Miner (Dokumentation, Probleme)
Erstmals aufgetreten: 16:22:12 (25 Vorkommnisse)
Zuletzt protokolliert: 16:26:43

/usr/local/lib/python3.12/site-packages/pyasic/miners/factory.py:854: UserWarning: Partially supported miner found: BM1370, please open an issue with miner data and this model on GitHub (https://github.com/UpstreamData/pyasic/issues). warnings.warn(

[b-rowan]

Strange. That's actually an issue with the bitaxe model not being fully added, so it makes no difference for functionality.

What version of BraiinsOS is your miner running?

[mark0st83]

It is a T21 with Braiins Version: 2024-05-21-0-d5fa91c4-24.04.1-plus.

It only works with version 0.1.13 or up to 0.1.13. The only difference I can identify is the additional SSH password.

Additionally, it’s strange that if I install a version > 0.1.13 over an already installed T21 device, all entities are duplicated, but the second set of entities is “live.”

However, I would then have to redo all automations to respond to the *_2 entities. This is not productive and will probably cause more issues in the future when there’s another update.

[b-rowan]

Can you try updating the miner? The latest version of pyasic had to regenerate the gRPC files, so there's a good chance that's the problem.

[mark0st83]

I updated the miner to 24.09 and the integration to 0.1.17rc6 — it’s working again, SSH login is back.

But I wanted to know if it’s due to the miner or the integration. So I downgraded back to 0.1.17rc5. Error message says pyasic needs at least 0.62.1, so I installed it via shell.

Still doesn’t work.
So it must be due to a change in 0.1.17rc6. Or a change between 0.1.13 and now

I hope this can help.

[mark0st83]

And the behavior is back in 0.1.17 🤣

Here’s the translation:

I then noticed that in 0.1.17rc6, there was no pyasic version error. I still had pyasic 0.59.6 installed. 0.1.17rc6 didn’t seem to be bothered by that.

So the issue is with pyasic > 0.59.6.
I tried also 0.60.0, 0.60.1, 0.60.4, 0.61.0.

It seems like it is since 0.61.0

Any ideas what can I do?

[b-rowan]

I updated the miner to 24.09 and the integration to 0.1.17rc6 — it’s working again, SSH login is back.

But I wanted to know if it’s due to the miner or the integration. So I downgraded back to 0.1.17rc5. Error message says pyasic needs at least 0.62.1, so I installed it via shell.

Still doesn’t work. So it must be due to a change in 0.1.17rc6. Or a change between 0.1.13 and now

I hope this can help.

Yeah, during the updates to hass-miner I updated pyasic quite a bit (it is much more active), so it will just be the changes in pyasic. Older miner versions will be imcompatible with newer hass-miner/pyasic, same goes for newer miner versions with older hass-miner/pyasic.

Also, should no longer have to manually install with v1.1.17, I found a very hacky workaround.

[b-rowan]

And the behavior is back in 0.1.17 🤣

Here’s the translation:

I then noticed that in 0.1.17rc6, there was no pyasic version error. I still had pyasic 0.59.6 installed. 0.1.17rc6 didn’t seem to be bothered by that.

So the issue is with pyasic > 0.59.6. I tried also 0.60.0, 0.60.1, 0.60.4, 0.61.0.

It seems like it is since 0.61.0

Any ideas what can I do?

Sorry, a bit confused here, can you start over? What is the issue? pyasic is failing to install properly? or just that the miner isnt working?

[mark0st83]

It seems like since pyasic Version ~0.60.4-0.60.10 there was a change that crashed my T21 miner.

If I try to install the T21 in Homeassistant the SSH Login beside the Web Login is missing. An error occurs that says nothing to me.
„unknown error“

The initial Problem was the pyasic Version that was required since >0.1.13.
Now since I can install pyasic < 0.60.10 by my own without an Error in Homeassistant that wants an other Version it is working.

Means if there comes an Update with an higher pyasic Version the Same Problem occurs again.

[b-rowan]

It seems like since pyasic Version ~0.60.4-0.60.10 there was a change that crashed my T21 miner.

If I try to install the T21 in Homeassistant the SSH Login beside the Web Login is missing. An error occurs that says nothing to me. „unknown error“

The initial Problem was the pyasic Version that was required since >0.1.13. Now since I can install pyasic < 0.60.10 by my own without an Error in Homeassistant that wants an other Version it is working.

Means if there comes an Update with an higher pyasic Version the Same Problem occurs again.

One of the names of the entries was wrong, that causes some issues. I would give it another try with v1.1.19rc2 (remove your miner first, it should pick it up as the same one with the MAC address being the UID).

[mark0st83]

It seems like since pyasic Version ~0.60.4-0.60.10 there was a change that crashed my T21 miner.
If I try to install the T21 in Homeassistant the SSH Login beside the Web Login is missing. An error occurs that says nothing to me. „unknown error“
The initial Problem was the pyasic Version that was required since >0.1.13. Now since I can install pyasic < 0.60.10 by my own without an Error in Homeassistant that wants an other Version it is working.
Means if there comes an Update with an higher pyasic Version the Same Problem occurs again.

One of the names of the entries was wrong, that causes some issues. I would give it another try with v1.1.19rc2 (remove your miner first, it should pick it up as the same one with the MAC address being the UID).

Unfortunately, it still doesn't work. I first updated to 1.19.rc2. However, I already get an error message when opening the configuration of the device.

So I updated to 1.19.rc3 as well. At first glance, it seems to work. When creating the devices, I have Web and SSH login again.

But unfortunately, it's because I manually downgraded to pyasic 0.60.4 (as I wrote before, since pyasic > 0.60.4 I have the problems and Homeassistant always upgrade to versions above that).

When I updated Home Assistant Core to 2024.11.3 to see if it still worked, pyasic 0.64.1 was reinstalled. Unfortunately, I still have the issue that I can't add the T21 as a device anymore.

[mark0st83]

Any news about this?
I have updated minutes ago to 2024.12.3.

Now I have all miners again twotimes. One is working, the other one with not working entities (sensor.xxx_2 is working)

On the Bitaxe I can delete the whole Miner and add it again it is working.
The T21 has the same problem like in the beginning of the thread.

Now i will downgrade pyasic again to 0.60.4 until Homeassistant upgrade to versions above of that...

[mark0st83]

Is this issue no longer being addressed? So far, I’ve always managed by downgrading the pyasic version to 0.60.4 after every update.

However, since the latest HA version, the higher pyasic version is installed after every restart.

The issue remains the same: the Antminer creates new entities, and the device cannot be reinstalled because the SSH login is missing.

[b-rowan]

I'm still confused about what exactly the issue is...

Have you tried wiping the old entities? Everything I have been able to test shows newer miners like that working. We have a S21 showing up here soon, so I will test more, but I just don't understand what's causing the issue in the first place since I can't replicate it.

[mark0st83]

The problem is that I can no longer add the device if I delete it.
Sure, I can manually delete the entities and rename everything that ends with _2.

But it’s tedious when the first entity is used in the dashboard.

I’m not a programmer and can only see that the SSH login is missing (compared to the old version).
Bitaxe and S9 can be re-added (but they also create duplicate entities after the update).

[b-rowan]

It really shouldn't be possible to create duplicate entities in the first place since they are using MAC address for entity ID.

SSH login is missing because there is no reason to use SSH on newer miners with the implementation of gRPC, and most of the data on the filesystem is just wrong with them.

[mark0st83]

Ok, I did some more testing.

Deleted the password in Braiins: works.

Set the password again: unknown error.

So, are passwords not allowed? Or are there restrictions on password selection?
Currently, I’m only using letters and numbers. Previously, I had hyphens.

[b-rowan]

That's a good question. I'm not exactly sure of the full impact of setting a password on the device, I can take a look further into that at least.

[b-rowan]

Ok, I think I found it. Much easier to test now that I have it. Try with v1.1.25

[mark0st83]

Indeed, it works again 🤙🏽

Thank you so much. Has no one else set a password on their miner, or am I the only one who noticed this? 😅

[b-rowan]

Pretty much no one uses passwords, there's not much point.