-
-
Notifications
You must be signed in to change notification settings - Fork 5
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
no HELIUM information after update to .25 #10
Comments
I should have add that i use Balena Cloud to update. |
Firmware Version | 2023.02.07.0-25 (c165b61) |
i'll do that tonight or tomorow morning.
bye
…On March 24, 2023 7:36:02 p.m. EDT, Aaron Shaw ***@***.***> wrote:
Please can you add gh_shawaj as a user on your BalenaCloud fleet @chapy23 ?
@Dani1914 how did you install? Using BalenaCloud?
--
Reply to this email directly or view it on GitHub:
#10 (comment)
You are receiving this because you were mentioned.
Message ID: ***@***.***>
--
Android with K-9 Mail, excuse my brevity.
|
Ok let me know when done so I can take a look at the device and see what's happening |
i add you in my Balena account, you can have a look now.
thank's
…On March 24, 2023 7:57:07 p.m. EDT, Aaron Shaw ***@***.***> wrote:
Ok let me know when done so I can take a look at the device and see what's happening
--
Reply to this email directly or view it on GitHub:
#10 (comment)
You are receiving this because you were mentioned.
Message ID: ***@***.***>
--
Android with K-9 Mail, excuse my brevity.
|
I will glad to know how you troubleshoot my device. Do you use the shell access to the device ?
I love to learn new stuff, thank's
bye
…On March 24, 2023 7:57:07 p.m. EDT, Aaron Shaw ***@***.***> wrote:
Ok let me know when done so I can take a look at the device and see what's happening
--
Reply to this email directly or view it on GitHub:
#10 (comment)
You are receiving this because you were mentioned.
Message ID: ***@***.***>
--
Android with K-9 Mail, excuse my brevity.
|
@chapy23 you added me as a member but you didn't give me access to any fleets. Also, I need to have "developer" level access so I can change device settings to try and see what's going wrong |
hi there,
I think i made the change that will give you access you need.
bye
…________________________________
De : Aaron Shaw ***@***.***>
Envoyé : 24 mars 2023 19:36
À : NebraLtd/helium-syncrobit ***@***.***>
Cc : chapy23 ***@***.***>; Mention ***@***.***>
Objet : Re: [NebraLtd/helium-syncrobit] no HELIUM information after update to .25 (Issue #10)
Please can you add gh_shawaj as a user on your BalenaCloud fleet @chapy23<https://github.com/chapy23> ?
@Dani1914<https://github.com/Dani1914> how did you install? Using BalenaCloud?
—
Reply to this email directly, view it on GitHub<#10 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AC2TKXRDHBHQWZMDUKWAYVDW5YVWFANCNFSM6AAAAAAWGWDKB4>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
ECC lock not required on this check because all we are doing is checking the i2c address of the attached device. Ref: NebraLtd/helium-syncrobit#10
I have the same problem as chapy23, no helium info after update to v25 with balenaCloud |
I wish to add to this, no helium information either but guessing you guys already know that? any update on the fix patch? another note glad to see OTA is working :) |
@MihaiDoro @MihaiDoro @chapy23 this will hopefully be fixed with the next update once this PR is merged (hopefully later today)... I'm pretty sure it's working fine with this update after checking it on a test unit. However, just FYI, this shouldn't cause an issue with mining just with the display of the correct info :-) |
- ECC lock not required on this check because all we are doing is checking the i2c address of the attached device. - persist a generated ECC location (from the i2c bus) to file to make get_ecc_location() function more efficient and to remove unnecessary calls to the i2c bus - additional tests for SWARM_KEY_URI_OVERRIDE and new "persist to file" feature Ref: NebraLtd/helium-syncrobit#10 Ref: NebraLtd/helium-syncrobit#2
The error message shows:
So it seems the ECC lock is interfering. Should be solved by NebraLtd/hm-pyhelper#234 |
Thank's for your effort to fix that and also for the quick explanation.
I will wait for my miners to be updated OTA 🙂
bye
…________________________________
De : Aaron Shaw ***@***.***>
Envoyé : 27 mars 2023 06:56
À : NebraLtd/helium-syncrobit ***@***.***>
Cc : chapy23 ***@***.***>; Mention ***@***.***>
Objet : Re: [NebraLtd/helium-syncrobit] no HELIUM information after update to .25 (Issue #10)
The error message shows:
diagnostics INFO:root:Frequency: US915
diagnostics
diagnostics INFO:root:Diagnostics shipping not requested, skipping.
diagnostics INFO:root:Diagnostics complete
diagnostics INFO:root:Running periodic hardware diagnostics
diagnostics INFO:root:Running periodic hardware diagnostics
diagnostics 2023-03-27 10:53:38,275 - [ERROR] - hm_pyhelper.lock_singleton - (lock_singleton.py).wrapper_lock_ecc -- /opt/python-dependencies/hm_pyhelper/lock_singleton.py:(67) - ECC is busy now.
diagnostics ERROR:hm_pyhelper.lock_singleton:ECC is busy now.
diagnostics 2023-03-27 10:53:38,276 - [ERROR] - hm_pyhelper.lock_singleton - (lock_singleton.py).wrapper_lock_ecc -- /opt/python-dependencies/hm_pyhelper/lock_singleton.py:(67) - ECC is busy now.
diagnostics ERROR:hm_pyhelper.lock_singleton:ECC is busy now.
diagnostics 2023-03-27 10:53:38,276 - [ERROR] - hw_diag.utilities.hardware - (hardware.py).get_public_keys_and_ignore_errors -- /opt/python-dependencies/hw_diag/utilities/hardware.py:(324) -
diagnostics INFO:root:Running periodic hardware diagnostics
diagnostics 2023-03-27 10:53:48,373 - [ERROR] - hm_pyhelper.lock_singleton - (lock_singleton.py).wrapper_lock_ecc -- /opt/python-dependencies/hm_pyhelper/lock_singleton.py:(67) - ECC is busy now.
diagnostics ERROR:hm_pyhelper.lock_singleton:ECC is busy now.
diagnostics 2023-03-27 10:53:48,374 - [ERROR] - hm_pyhelper.lock_singleton - (lock_singleton.py).wrapper_lock_ecc -- /opt/python-dependencies/hm_pyhelper/lock_singleton.py:(67) - ECC is busy now.
diagnostics ERROR:hm_pyhelper.lock_singleton:ECC is busy now.
diagnostics 2023-03-27 10:53:48,375 - [ERROR] - hw_diag.utilities.hardware - (hardware.py).get_public_keys_and_ignore_errors -- /opt/python-dependencies/hw_diag/utilities/hardware.py:(324) -
So it seems the ECC lock is interfering.
Should be solved by NebraLtd/hm-pyhelper#234<NebraLtd/hm-pyhelper#234>
—
Reply to this email directly, view it on GitHub<#10 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AC2TKXRZI2VBLQWDRHVIV73W6FW4ZANCNFSM6AAAAAAWGWDKB4>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Great. I'll keep you updated here 😊 |
I thought BalenaCloud deployed miners do not get OTA... :) |
@vstrong-info you are correct they don't unless you set it up yourself |
* fix: remove unnecessary ECC lock and improve bus check - ECC lock not required on this check because all we are doing is checking the i2c address of the attached device. - persist a generated ECC location (from the i2c bus) to file to make get_ecc_location() function more efficient and to remove unnecessary calls to the i2c bus - additional tests for SWARM_KEY_URI_OVERRIDE and new "persist to file" feature Ref: NebraLtd/helium-syncrobit#10 Ref: NebraLtd/helium-syncrobit#2 * Update miner_param.py * Update miner_param.py
@chapy23 can you push the latest release from this repo to the fleet and see if it's fixed? I don't seem to have access anymore |
yes, sorry i remove the access
i can do that, no problem
what is the best practice to push the new release
i want to learn what is the better way to do it, maybe there is just one 🙂
bye
…________________________________
De : Aaron Shaw ***@***.***>
Envoyé : 28 mars 2023 11:37
À : NebraLtd/helium-syncrobit ***@***.***>
Cc : chapy23 ***@***.***>; Mention ***@***.***>
Objet : Re: [NebraLtd/helium-syncrobit] no HELIUM information after update to .25 (Issue #10)
@chapy23<https://github.com/chapy23> can you push the latest release from this repo to the fleet and see if it's fixed?
I don't seem to have access anymore
—
Reply to this email directly, view it on GitHub<#10 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AC2TKXXCBIIG3YUNY7OSLODW6MAS3ANCNFSM6AAAAAAWGWDKB4>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
@chapy23 easiest way is to go to https://github.com/NebraLtd/helium-syncrobit and click "deploy with Balena" Then click to use an existing fleet and choose the correct one... Then toggle the advanced tab and make sure it's got all the info loaded... |
@vstrong-info but it's still showing "not available"? Is that an old screenshot? |
Forget about delete screenshot, i was able to remove it by myself, sorry Now, running: 2023.02.07.0-26 (7784b16) update with "Deploy with Balena", all good ! |
Yes, it is @chapy23's screenshot from the first post. |
Ah ok, perfect. Looks like everything fixed now then yes. 🎉🥳🙌 Perfect. Will close this issue but if you spot any other problems feel free to open a new issue 👍 |
The text was updated successfully, but these errors were encountered: