-
Notifications
You must be signed in to change notification settings - Fork 19
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
Integration seems broken under HA 2024.9.2 #374
Comments
This is on |
Sorry, yes, I tried under 1.1.14 and 1.1.14rc1. Here's what I've got from the logs: Logger: homeassistant.helpers.entity_platform miner raises exception ConfigEntryNotReady in forwarded platform sensor; Instead raise ConfigEntryNotReady before calling async_forward_entry_setups |
Alright, config entry timing again. Ill see what I can do about this, but this specific issue is pretty annoying since it doesnt seem to be well documented where im supposed to raise that error when the miner doesn't respond... |
Is there anything I can do to workaround? I'm having this issue on one HA install, but it doesn't seem to be happening on my other install. Just trying to make your life a little easier if possible. |
Not really, its likely this will happen on multiple versions, and im not sure the exact circumstances that cause it. I'm looking into it, as others have raised this issue as well, just a bit difficult for me to emulate HASS without just spinning up an instance. |
Understood. I feel your pain. I tried my hand at developing an integration and I ultimately quit because I got no help from the HA devs (and they were actually quite rude). |
Yeah, I've asked about a couple things in the discord and not gotten any response. Quite disappointing, as HASS is a cool system. For reference, here is the docs on how to do this "properly" - https://developers.home-assistant.io/docs/integration_setup_failures/#handling-offline-or-unavailable-devices-and-services And the implementation in this repo - hass-miner/custom_components/miner/__init__.py Lines 18 to 34 in ba6a220
From the docs -
Here, we have the Log reports -
This is irrelevant, as you can see above this is raised way before TL;DR: repo does EXACTLY as the documentation says, and it doesn't work? |
From what I can see, it might be some weird conflict between |
Fixed with a PR I think, I'm going to release a rc version for testing. |
Try |
It looks to be retrying automatically now but I'm now getting: Failed Setup, will retry: Unknown error This time I'm not really seeing anything in the logs. |
Ok, that's a good sign, it's raising a valid error now, that's from the coordinator. Something is happening that it can't identify... |
Debugging fix coming for that |
Let me know, happy to help however I can. |
Try with |
Here's what I got when I removed and added back one of my miners: 2024-09-17 14:13:36.999 ERROR (MainThread) [homeassistant.components.mqtt.client] Failed to connect to MQTT server due to exception: [Errno -5] Name has no usable address |
Bumped to RC3 with explicit |
I think this will help you:
|
Betterproto. I hate GRPC lol. This will have to be fixed in pyasic, Ill see what I can do. |
That is something I'm not familiar with personally. But thanks for looking into this! |
GRPC is the communication protocol used by recent version of BOS+ for their API. Not sure where that error is coming from, but its being raised here in betterproto - I may just need to re-compile the proto files for BOS. |
Can you try updating your miners actually? Possible the compiled files in pyasic are TOO new for your miner... |
I actually did that in the process of trying to fix this, I'm now on 24.08.1-plus |
Ok, ill have to re-compile them then I suppose. |
BTW, I should mention that your integration is really awesome. I use it to turn on my bitcoin miners only when my solar panels are making enough energy to not take from the grid so mining is still profitable. |
Thanks, although not entirely my integration, as I just maintain it. Was a great idea on the part of @Schnitzel. |
Either way, it's really useful. I also use it to control my bitcoin miner that heats my hot tub... |
Thats pretty awesome. I'm never sure how many people are doing projects like this, but we need to see more of this stuff in the industry. The more people find use for bitcoin mining the more innovation we get in the home mining space. |
I agree. Honestly, this project was great to find because I also use my miners to heat my business during the winter. Previously I was just doing it with a shell script and some TCP commands, but this is way better because I can use the status to turn on and off my external fans (the built in ones are too loud). |
Hey there, same issue on my end setting up for the first time with a S19. Thanks |
Not sure of a working version, I can look and see if I can figure out what version it was compiled for, but I don't think there are any indicators in the sources... I would try 24.04 or 24.06 maybe? |
Just FYI, I was on BOS 24.0.3.1 when I was initially experiencing this issue. |
Ok, issue was with betterproto 2.0.0b7, I have pinned it in pyasic now. Technically the BOS+ proto files aren't following proper GRPC protocol now, the This should be fixed with v1.1.15rc4, let me know if that works and ill move it from pre to latest. |
Ok, it's working on rc4! One small note which isn't particularly consequential but I did have to restart my miners and toggle the active switch once or twice to seemingly get things in sync and functioning. When I added the device, it showed as on in HA, but the device was not running and seemed to be in some sort of stuck state until I restarted. No idea if this is related to the integration or not, but I thought I would mention it. |
Possibly a pyasic bug, but at least it's less concerning haha |
I agree 100%! Thanks again for your great work! |
Ok, fixed in v1.1.15 on stable. Thanks for all your help! |
Under HA 2024.9.2 I am able to add the integration and add miners (two S19s running BOS 24.0.3.1) but there are no entities available. I had this problem in a previous version and I was going to report it but removing and re-adding the integration and the devices resolved the issue. However, as of 2024.9.2 (running on VirtualBox) this no longer works and the integration seems to be non-functional.
The text was updated successfully, but these errors were encountered: