Could you please run brewblox-ctl coredump ?
As with log, this generates an URL you can share. You do not need to copy and upload the file manually.
Ah I misunderstood. I thought you made a custom cable.
Coredump is empty, so I guess there was never a crash that caused a coredump.
If you go to the spark page, and in the top right corner click ‘discover onewire blocks’, you don’t get new blocks?
And if you run ‘remove all blocks’ and then try to discover again? Export your blocks first if you don’t want to loose anything.
With the coredump empty, you may also want to try some different USB cables / power sources. Your problem is caused by the Spark constantly rebooting.
Hi there,
it have worked before with this cable.
I delete all blocks, and try discovering new blocks, but nothing appears.
Is there a way to start to factory settings ?
To reset the Spark to factory settings:
. .venv/bin/activate
pip3 install esptool
esptool.py erase_flash
brewblox-ctl flash
You will need to re-provision Wifi credentials.
Afterwards:
- What is the status of the Spark screen and time shown?
- In the UI, in the spark service page, SystemInfo block, does the “controller uptime” value periodically reset?
- If the uptime resets, do you hear the startup beep?
On spark, the status show IP adress and the time is incrementing (minus 2 hours)
On brewblox ui, the uptime increment every 5 sec, so the “last block update” too.
There is no beep, it doesn’t restart
And it doesn’t find new GPIO nor temperature sensor
Could you please run the below commands to attach to the USB log
. .venv/bin/activate
pyserial-miniterm /dev/serial/by-id/usb-{press tab to autocomplete long name} 115200 | tee monitor.txt
Press the reset button on the Spark, and let the logs roll until they’re quiet.
Then press ctrl + ] to exit, and upload the log with
brewblox-ctl termbin monitor.txt
When testing, you can also run the monitor command yourself. Newly detected sensors are shown in the log. Example output from my Spark:
␛[0;32mI (00:00:05.944) Brewblox: Temp sensor connected: 2808712A0D000064␛[0m
␛[0;32mI (00:00:06.012) Brewblox: Temp sensor connected: 28FBF6FF08000060␛[0m
␛[0;32mI (00:00:06.080) Brewblox: Temp sensor connected: 28F75C2A0D000026␛[0m
␛[0;32mI (00:00:06.133) Brewblox: DS2413 connected: 3A04212100000089␛[0m
␛[0;32mI (00:00:06.201) Brewblox: Temp sensor connected: 2819285306000094␛[0m
This is with a GPIO module + sensor attached?
Yes, i tried both (connected and disconnected), and none give a trace of brewblox
With that, I’m reasonably certain it’s not a software issue. I pinged Elco to have a look at possible hardware causes. If he doesn’t spot anything there, the next step would be to return it for repair or replacement.
Ok, thank you for your time.
I will work low-tech for some time 