search

NebraLtd / helium-syncrobit

Nebra OpenFleet for Syncrobit CM4 Miners
https://nebra.io/syncrobit
MIT License
11 stars 5 forks source link

no witness since ota v25 from v23 yesterday at noon Eastern standard time #13

Closed sourdoughG closed 1 year ago

sourdoughG commented 1 year ago

Hi I have a syncrobit miner that had the v25 firmware flashed and all was well until yesterday noon when the miner must have received an over the air upgrade to the v25 version.

Miner dead since then. Rebooted the miner this am around 10 am. No activity.

Please advise

sourdoughG commented 1 year ago

correction I meant to say I had v23 flashed. Just saw a code change in issue #10. do we wait for another OTA update?

shawaj commented 1 year ago

We are still seeing activity on our test devices so don't think there's anything wrong

sourdoughG commented 1 year ago

New 2023.02.07.0-25 (d2dd598) OTA. No PoC after working on the prior firmware

On Sun, Mar 26, 2023 at 5:40 PM Aaron Shaw @.***> wrote:

We are still seeing activity on our test devices so don't think there's anything wrong

— Reply to this email directly, view it on GitHub https://github.com/NebraLtd/helium-syncrobit/issues/13#issuecomment-1484232159, or unsubscribe https://github.com/notifications/unsubscribe-auth/A6XRYDR2J73KD3Z6PILPM4TW6DAWPANCNFSM6AAAAAAWHSQK44 . You are receiving this because you authored the thread.Message ID: @.***>

shawaj commented 1 year ago

@sourdoughG we can see several units working fine so this doesn't seem to be a code issue. Can you share the diagnostics JSON output from the diagnostics page on your device?

For example this device is running our firmware and is working fine... https://explorer.helium.com/hotspots/11263y4WiKtyHKjUJfu2ZUuzYmPuVyt6TT5DcijwNJNmJPk2wXaq/activity

timetraveler90 commented 1 year ago

What I discovered is that hard reset helps in this situation, but it's really annoying to do it.

here is my diag: {"AN":null,"BA":"HELIUM-SYNCROBIT","BALENA_DEVICE_TYPE":["raspberrypicm4-ioboard"],"BN":"humble-whirlwind","BT":true,"BUTTON":27,"CELLULAR":false,"CONTAINS_FCC_IDS":[],"CONTAINS_IC_IDS":[],"CPU_ARCH":"arm64","E0":"E4:5F:01:3F:5B:AD","ECC":true,"ECCOB":true,"FCC_IDS":[],"FR":"N/A (Non Nebra Miner)","FRIENDLY":"Syncrobit Hotspot","FW":"2023.02.07.0-25","IC_IDS":[],"ID":"0b8c850ad68f704a1cccf83a1b5fdf3d","LOR":true,"LTE":false,"MAC":"wlan0","OK":null,"ONBOARDING_KEY_URI":["ecc://i2c-1:96?slot=0","ecc://i2c-1:88?slot=15"],"PF":true,"PK":null,"RE":"EU868","RESET":17,"SPIBUS":"spidev0.0","STATUS":22,"SUPPORTED_MODELS":["Syncrobit Hotspot"],"SWARM_KEY_URI":["ecc://i2c-1:96?slot=0","ecc://i2c-1:88?slot=2"],"TYPE":"Full","VA":"COMP-SYNCROBITCM4","W0":"A2:21:88:E9:C4:C9","firmware_short_hash":"d2dd598","last_updated":"20:09 UTC 27 Mar 2023","serial_number":"100000004711c4c8"}

sourdoughG commented 1 year ago

Thank you! It is now back up after a hard reset. Will I have to do this going forward everytime I notice a PoC hasnt occurred in 3 hrs?

On Mon, Mar 27, 2023 at 1:35 PM Aaron Shaw @.***> wrote:

@sourdoughG https://github.com/sourdoughG we can see several units working fine so this doesn't seem to be a code issue. Can you share the diagnostics JSON output from the diagnostics page on your device?

— Reply to this email directly, view it on GitHub https://github.com/NebraLtd/helium-syncrobit/issues/13#issuecomment-1485556647, or unsubscribe https://github.com/notifications/unsubscribe-auth/A6XRYDWGB6FJY7NWNMSFPTTW6HFVDANCNFSM6AAAAAAWHSQK44 . You are receiving this because you were mentioned.Message ID: @.***>

shawaj commented 1 year ago

@timetraveler90 when you say "hard reset" - do you mean just rebooting the device? Or something else?

@sourdoughG it might just be that your setup got stuck in some weird state to be honest. This can happen sometimes after an update but usually a reboot can help. Or a purge of the software

sourdoughG commented 1 year ago

Yes just rebooting the device🤞👍

On Tue, Mar 28, 2023 at 11:45 AM Aaron Shaw @.***> wrote:

@timetraveler90 https://github.com/timetraveler90 when you say "hard reset" - do you mean just rebooting the device? Or something else?

@sourdoughG https://github.com/sourdoughG it might just be that your setup got stuck in some weird state to be honest. This can happen sometimes after an update but usually a reboot can help. Or a purge of the software

— Reply to this email directly, view it on GitHub https://github.com/NebraLtd/helium-syncrobit/issues/13#issuecomment-1487160536, or unsubscribe https://github.com/notifications/unsubscribe-auth/A6XRYDXAORB27BCWP3KJU5DW6MBQNANCNFSM6AAAAAAWHSQK44 . You are receiving this because you were mentioned.Message ID: @.***>

shawaj commented 1 year ago

Like with all electronics, a reboot can often fix things yes!

It shouldn't normally need that after an OTA but it would always be my first suggestion if you are having unexpected issues.

Will close this issue for now. But if you have any other problems in the future feel free to open a new issue here.