BrewPi Remix – What’s Old is New Again

[blau]

Hi,
As for the video, it is a very good idea. My procedure is the same as yours, although it does not work.

Have you tried it as a serial device? It's a separate firmware, and you will need to change the port back (auto works), but it will let you know if your hardware is capable of saving the devices.

You mean to flash the devices with firmware rev 0.11 - Serial? I have not tried it. That being the case, I suppose I should connect the device via cable to the raspberrypi, right? What connections should I use then? As I said on some occasion, I trust a cable more than a Wi-Fi connection. It is possible that the final cable connection was a possibility for me, although I would like to see the system work via wifi to decide.
While you can see this, I am going to start by updating to the new version.
Thanks

 

[LBussy]

You mean to flash the devices with firmware rev 0.11 - Serial? I have not tried it. That being the case, I suppose I should connect the device via cable to the raspberrypi, right? What connections should I use then?

Yes, you would want to remove external power from the controller, at least for now.

If you connect as a serial, and it is the only one (for now let us keep it simple) then you use "port = auto" in the config.cfg.

 

[blau]

ok this is what i have done:
- update 0.7.4
- configuration line in config.cfg: port = auto (the old one removed by #)
-flashing firmware 0.11 - Serial (sorry, I didn't think to try the old version)
- connection between mini d1- Raspberrypi: micro usb-USB
- connections on mini D1 pin D-5 ---> -5VSSR; D6 yellow probe cable (2)
- Food + 5v from SSR and + -5v probes (2) with an external power supply.
The result in this case is that the maintenance panel does not automatically find the probe. Via wifi if it did.
Either I am missing something to connect or raspberrypi and miniD1 do not speak.

 

[LBussy]

That's ok for now - see if you can assign the actuators (heat and cool) and if they will then show up in assigned devices.

Remember to "Refresh Device List" after you assign them.

 

[blau]

I only have one SSR connected, but it doesn't install.

I have remembered that in the old brewpi I used the command "dmesg" to recognize the serial port (towards this by recommendation, my knowledge does not understand this). I do not know if it helps you, but I have captured the end of that command after restarting the mini D1.

 

[LBussy]

I have remembered that in the old brewpi I used the command "dmesg" to recognize the serial port (towards this by recommendation, my knowledge does not understand this). I do not know if it helps you, but I have captured the end of that command after restarting the mini D1.

This tells us that the script has connected to the controller, so there's no need to worry about dmesg logging:

I am honestly scratching my head on this one. I cannot make it happen here, I have what should be the same setup. I did manage to break my mule again (I blame @day_trippr so it will be a couple of hours before I can test that specific workflow and see if the messages are the same.

 

[blau]

Ok, I hope, no problem. The only thing I can think of to try to make the job easier is a mini d1 change. I received some I have several purchased at the same time. As I received some damaged I bought some more to replace the damaged one and for future projects. They are still in the unopened package. I'm going to try to install one of the new ones in case my whole first game had problems.

 

[LBussy]

It's all very strange, but we'll figure it out.

 

[LBussy]

(wrong thread)

 

[Brewski_59]

just updated due to your last post. Now the script wont start.

doPerms.sh returns command not found.

Refreshing device list returns. Error while receiving device configuration: SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data

 

[LBussy]

just updated due to your last post. Now the script wont start.

What do the logs say?

doPerms.sh returns command not found.

Try with sudo.

Refreshing device list returns. Error while receiving device configuration:

That's to be expected if the script is not running. The controller is still doing it's job

 

[blau]

Hello, just for adding new data.
I have prepared one of the new mini d1 purchase batch. The result is the same.
On the other hand, I see that now the firmware does not matter and what I install, when I click the button "refresh device list" it never recognizes any of the installed probes.
Would it be useful to start a clean installation by setting up a single chambre?

 

[LBussy]

see that now the firmware does not matter and what I install, when I click the button "refresh device list" it never recognizes any of the installed probes.

That suggests a wiring issue.

Would it be useful to start a clean installation by setting up a single chambre?

Perhaps. We can also test without probes since all we are trying to do is get the controller to save a configuration.

 

[Brewski_59]

What do the logs say?

I didn't see anything new from the update when I looked at the logs. I don't have time to mess with it now. Were going away for a few days. I'll have to get back with you when we get back.

Try with sudo.

I did, of course.

That's to be expected if the script is not running. The controller is still doing it's job

I switched over to a card with Fermentrack on it to complete this ferment. I'll get back with you after the 10th when I can spend some time on it.

 

[LBussy]

I didn't see anything new from the update when I looked at the logs. I don't have time to mess with it now. Were going away for a few days. I'll have to get back with you when we get back.

If it's not connecting to the controller (which is why the script will not start,) there's something there.

I switched over to a card with Fermentrack on it to complete this ferment. I'll get back with you after the 10th when I can spend some time on it.

Oh sure, kick me while I'm down.

I'll be here, would like to see the contents of both of the stderr.txt and stdout.txt. You can PM them to me here.

 

[blau]

Hello,
today I was able to dedicate some time to this.
I have reconfigured my wiring, using "protoboard"
I have reinstalled brewpiremix as single chambre.
I see that the installation asks 2 new questions. I don't know what they mean but I answer "yes"
I'm going to configure the config.cfg file. the file does not contain anything. I add the line "port = socket: //192.168.168.143: 23" (with the ip of my Mini D1). Save the file.
In the new installation of my hardware I have installed 3 probes and 1 ssr. It does not recognize any of the 3 Probes, nor does it install the ssr.
Now I don't know what else to try. I am very lost.
ideas?
Thank you.

 

[LBussy]

Would you please take a picture of your wiring? It is not a question of whether you did it right, it may be that documentation is wrong and we are losing something in the Google Translate.

Would you also please attach your /home/brewpi/logs/stdout.txt and /home/brewpi/logs/stderr.txt?

 

[blau]

Hello,
Sure. This shouldn't be so much of a problem. I am sure there is something basic that is wrong and I am checking as ok.

 

[LBussy]

Please remove all wires but power, and see if you can save one actuator (such as D0 for heat or cool).

 

[blau]

d1 mini only with the power connected. I get the same answer.

 

[LBussy]

Well, we've ruled out almost everything. When I got done today I'll line up the commands mine sends and see if they are the same.

 

[Thorrak]

Hello,
today I was able to dedicate some time to this.
I have reconfigured my wiring, using "protoboard"
I have reinstalled brewpiremix as single chambre.
I see that the installation asks 2 new questions. I don't know what they mean but I answer "yes"
I'm going to configure the config.cfg file. the file does not contain anything. I add the line "port = socket: //192.168.168.143: 23" (with the ip of my Mini D1). Save the file.
In the new installation of my hardware I have installed 3 probes and 1 ssr. It does not recognize any of the 3 Probes, nor does it install the ssr.
Now I don't know what else to try. I am very lost.
ideas?
Thank you.

When you are installing the SSR pin, what exactly happens? What do the logs show?

 

[LBussy]

@Thorrak and I are talking. He’s making me jump through unspeakable hoops but I did replicate the issue and we’re looking into it.

 

[Thorrak]

@Thorrak and I are talking. He’s making me jump through unspeakable hoops but I did replicate the issue and we’re looking into it.

I made you install fermentrack. The horrors.

 

[day_trippr]

hahahahaha!

 

[blau]

Oh my goodness. I'm going to hell for putting you on this path ... Sorry Lee, don't hate me for that ...

 

[LBussy]

I made you install fermentrack. The horrors.

It's like a little game of "just the tip." Now I've got freaking Docker installed.

The good news, however, is I think I've found the issue. Somewhere along the way BrewPi and Fermentracl diverged on the JSON format. It's interesting because I am running an ESP8266 right now and I had trouble reproducing the issue. That said, I know where it is and @Thorrak and I will put our heads together to figure it out to ensure backward-compatibility.

 

[smokejohn]

Hey there. The last two times I did an update with the provided update file the system stopped working. The symptom is that I cannot start the script. I just reinstalled everything for a second time in order to get it working again. Any idea what could be wrong? I am afraid to update this pi again

 

[LBussy]

If you know where the logs are kept, I would need to see those. If not, I can give you the location when I get home.

 

[LBussy]

Okay, I need to know the contents of /home/brewpi/logs/stdout.txt and /home/brewpi/logs/stderr.txt.

For grins, if you just want to try something, try these two commands:

sudo /home/brewpi/utils/doPerms.sh
sudo reboot now

After it reboots check again and see what happens.