Brewery down, (5) Onewire sensor:s cant be read

Hello guys!

Need help from the experts!
My system has been runnin great for years but now i got an problem.

The brewery is down and the fermenters are sitting full of beer in roomtemp that are suppossed to be lagering at 2C.

The issue is the onewire sensors that cant be read. I have 5 in total and no one can be read.
So obviously the PID:s cant operate…

However when i install an new unused sensor in the port it can be discovered and read.
Is it really possible that all 5 sensors have broke at the same time and need to be replaced?
I have tried to put them in, one at the time in each and every output, but it doesent make an difference.

I am a bit of an noob, and have updated brewblox and flashed the controller.
I am running on an Spark3 and raspberry pi 3.

Here is the log: https://termbin.com/m3l3

Many many thanks in advance!

You will most likely get a reply from @Elco in the Discord forum if you post it there.

I see that you have 3 spark services.

  • 1 with no device ID specified
  • 2 with the same device ID

All 3 of them want to connect to the same spark. I don’t know how you ended up with that, but you should keep only 1.

If you go to the service page, and click discover sensors, do they come back?

I see that some sensors don’t have the right setting for oneWireBusId. When you discover sensors, this is corrected. But I think it is a bug that we don’t store this value when it is fixed during discovery, so after a reboot it might be needed again. I’ll have to fix this after my holiday.

When you make a change to a sensor, like setting the offset to 1 and back to zero, it will also save this auto detected fixed setting.

Thank you so much for the reply!

Ok do i simply remove the service by “brewblox-ctl service remove -n <SERVICE_NAME>” ?.

It could not find any sensors under discover in service page.

However i must thank you for the great service at brewpi store.
I express orderd 5 new sensors and they arrived the next day.
The new sensors was discovered unlike the old ones and i could replace them onto the PID:s, so now it is running.

I wish you an pleasant holiday Elco!

Hey guys, it´s me again…

Brewery down but with a new problem :sweat_smile:
The raspberry pi3 dosent connect to the wifi anymore.

Installed and configured it with the raspberry pi imager this summer with an fresh SD card and raspberry pi3.

Worked great until know.
The wifi itself is running and the Spark3 is still connected to it.

i have copied the ssh file and wpa_supplicant.conf document onto the sdcard but no luck.
I can see the IP adress of the pi on briefly on fling app for like 4 seconds and then it disappears.

For every time it boots up the ssh file is somehow deleted and i have to put the sd card back into the PC and add it again for another try?

Any other ideas? How can i even access or manage the pi?

Thanks!

Edit:
Could not solve it so i did an complete reinstall with an fresh sd card. Now the production is running again :slight_smile: Thanks!

Glad you solved it. Easiest way to set up ssh and wifi is to configure it in the raspberry pi imager.
If you enable ssh by putting a file in the boot directory, I think it is normal that it is removed after ssh is enabled.