BrewPi Remix – What’s Old is New Again

[smokejohn]

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.

I had to do the uninstallation first before installing again so I guess those logs got deleted?

You want me to execute those commands and then check the log files?
I guess the doPerms.sh is executed after the update script so maybe something's wrong there?

 

[LBussy]

If you have already reinstalled then there's no reason. In the future, try doPerms.sh when you have issues starting. That's pretty much Penicillin.

 

[LBussy]

I get the same answer.

Please install the devel branch (you will need to uninstall or use a clean card) with the following command:

curl -L devinstall.brewpiremix.com | sudo bash

 

[blau]

Thanck. When I am at home, I will try to do a new installation and test what you tell me in your last post.

 

[blau]

Hello, after doing the installation with the sequence that you have indicated, I still have problems. I have been capturing all the screens that I have believed appropriate or suggested a question:
-Wifi acces point: I answer yes. This point is quite recent. what is it for?

- unable to ... I have no idea what this is. I answer yes.

- End of installation

- I am looking for the ip of my ESP8266.

- file settings.cfg. It is empty. This is the configuration that I write.

- I check ping access.

- Test result with ESP8266 only powered.

 

[LBussy]

Wifi acces point: I answer yes. This point is quite recent. what is it for?

@day_trippr pointed out a workflow (likely he's the only one ) where having this daemon running was not optimal. I moved it to be optional. It's a small daemon that checks the WiFi connectivity and reconnects if needed. Something like this was part of the original BrewPi and I ported it over.

Test result with ESP8266 only powered.

That result looks like there are two things hitting the device. Do you have another Pi or installation (maybe Fermentrack?) that's also connected?

 

[blau]

Hello, It is true that I always start from the same system restoration. If the problem is earlier, we could be working on a problem without knowing it. I have reviewed my procedure prior to starting point. My installation only consists of 1- Linux installation. 2- install xrdp server (sudo apt-get install xrdp) 3- install Remote.it services After this I made the backup with the system prepared to connect well with all possible means. Do you think any of this could cause problems?

 

[LBussy]

Do you think any of this could cause problems?

No, that is fine. We will get you fixed.

Can you please look in your /home/brewpi/logs/stderr.log and /home/brewpi/logs/stdout.log during that time? It would be good to post both so I can fully review.

 

[blau]

Hello,
Here are the files. It seems that the only recurring message is a problem opening the serial port.
2021-04-12 22:38:12 [E] Starting BrewPi.
Error(s) while opening serial port:
Could not find compatible serial device.

 

[LBussy]

It seems that the only recurring message is a problem opening the serial port.

This looks like a more basic issue of either the config.cfg file not being correct, or the controller itself not responding on the network.

 

[blau]

You can see the configuration in post # 185. the file only has one line with the configuration of my ip. ESP responds to Ping. Today there is nothing new configured.

 

[LBussy]

All I can tell you is that it is not connecting. Have you tried to telnet to the device to see if you can connect?

 

[LBussy]

0.7.5 Bug Fix Release

The primary changes in this release address a rather frustrating bug that prevented users of BrewPi ESP8266 controllers from saving device configurations.

Secondarily, users who choose to install both BrewPi Remix and Fermentrack, or any other project which may use a different web server, may now choose to have Apache serve pages on a different port than the default port 80.

Also, some cleaning up was done to the aliases installed by the scripts. Users may now use the command bpactivate to activate the BrewPi virtual environment when logged in as the Pi user.

Upgrading

Existing users of BrewPi Remix 0.5.3 and above may upgrade with:

sudo /home/brewpi/utils/doUpdate.sh

If you are not on version 0.5.3 or above (or if you have no idea what version you are on,) use the following command to upgrade to the latest version:

curl -L upgrade.brewpiremix.com | sudo bash

You must run this from within your /home/brewpi directory or from each chamber's directory in multi-chamber mode.

Details

As this is a project in several parts, below are the changes in the individual repositories.

Note: Commit conflicts caused some commits from the previous release to be re-pulled into this diff. Only the changes which were actually made since 0.7.4 are listed in the commit summaries below.

Tools

Commit Summary

• No significant changes

File Changes

• M bootstrap.sh (3)
• M install.sh (32)

Patch Links

• https://github.com/brewpi-remix/brewpi-tools-rmx/pull/57.patch
• https://github.com/brewpi-remix/brewpi-tools-rmx/pull/57.diff

Scripts

Commit Summary

• ba59f56 Increase initial timeout for iSpindel to one hour
• 3a43cb9 Set iSpindel timeout to 3.5 times the interval after receiving JSON
• 23f408e Round timeout value
• 962ffd3 Add message to log when re-setting timeout
• 627f7ac Fix .bash_aliases (#172, #173, #176)
• 8a627d5 Address nginx detection (#179)
• 13e3790 Update tool scripts descriptions

File Changes

• M .gitignore (1)
• M BrewPiProcess.py (4)
• A ConvertBrewPiDevice.py (104)
• M MigrateSettings.py (6)
• M Tilt.py (30)
• M autoSerial.py (12)
• M backgroundserial.py (3)
• M brewpi.py (260)
• M brewpiVersion.py (10)
• R gitHubReleases.py (1)
• M inc/asroot.inc (6)
• M inc/help.inc (2)
• M programController.py (36)
• M requirements.txt (1)
• R terminal.py (0)
• M tests/versionTest.py (9)
• R updateFirmware.py (20)
• R updater.py (0)
• M utils/README.md (22)
• M utils/doDepends.sh (131)
• A utils/doFlash.sh (164)
• M utils/doUpdate.sh (2)

Patch Links

• https://github.com/brewpi-remix/brewpi-script-rmx/pull/182.patch
• https://github.com/brewpi-remix/brewpi-script-rmx/pull/182.diff

Web UI

Commit Summary

• 267ceb4 Use integers for device settings
• 51307b2 Refresh devices after application

File Changes

• M get-gitinfo.php (1)
• M js/device-config.js (4)

Patch Links:

• https://github.com/brewpi-remix/brewpi-www-rmx/pull/69.patch
• https://github.com/brewpi-remix/brewpi-www-rmx/pull/69.diff

 

[day_trippr]

Hypothetically speaking, if one had installed from your dev branch, would the upgrade commands above still work?
Asking for a friend...

Cheers!

 

[LBussy]

Hypothetically speaking, if one had installed from your dev branch, would the upgrade commands above still work?

It will, however, it will upgrade you to the late Dev branch which may be a little more bleeding edge than you intend.

If anyone wants to move to master from dev (or the other way around by replacing the obvious parts) use the following:

cd ~/brewpi-tools-rmx/
git fetch --all
git checkout master
cd /home/brewpi
sudo git fetch --all
sudo git checkout master
cd /var/www/html
sudo git fetch --all
sudo git checkout master
cd ~
sudo /home/brewpi/utils/doPerms.sh
sudo systemctl restart brewpi

(Multi-chamber users should modify the two paths above as well as the daemon name to fit their installation and this will need to be done once per chamber)

It's a good time to point out that the doPerms.sh script fixes a whole host of issues that you may see and I always recommend folks run it if they see strangeness. The sudo systemctl restart brewpi part restarts BrewPi, or you can always stop/start in the web UI if it's running.

At this point you will have the master branch current to the same point in time as you installed devel - which may not be the best place. To update at this point, you can issue the command from above:

sudo /home/brewpi/utils/doUpdate.sh

Some of the Legacy users may be thinking there used to be a script that did this, you are correct. Because of the significant changes to the application since then, that script is no longer viable in its current state. Fixing it is "on the list" however I have been prioritizing making the master branch the most viable place for users and eliminating the need to worry about swapping back and forth.

 

[duncan.brown]

@LBussy I finally got some time to get my hardware set up for BrewPi Remix. It looks like you've merged the glycol code into the devel branch, so should I go ahead and use the firmware here?

https://github.com/brewpi-remix/brewpi-firmware-rmx/tree/devel/firmware
Do I need the devel branch of the web sever code and utilities as well or just the firmware? I don't see any obvious commits related to glycol in the former.

 

[LBussy]

I finally got some time to get my hardware set up for BrewPi Remix. It looks like you've merged the glycol code into the devel branch, so should I go ahead and use the firmware here?

Pretty sure that's right. It's been a day from hell so I'll check in the AM and verify. I have not yet added it to the firmware flash script.

Do I need the devel branch of the web sever code and utilities as well or just the firmware? I don't see any obvious commits related to glycol in the former.

Right now it just zeroes out some PID values and removes the short-cycle (which has proven to be what was needed with other BrewPi derivatives.) As soon as @day_trippr quits creating bugs I can get on to what will amount to visual changes to indicate that the UI is serving glycol and some other similar changes. So, you can use Master branch of the Pi repos, and hopefully, I can get to some fun stuff soon.

 

[day_trippr]

lmao!

 

[LBussy]

0.7.6 Bug Fix Release

The most important user-facing bug fixed in this release is a nagging iSpindel bug that would happen in certain circumstances like a reboot/power outage. The iSpundel value would be null and cause one of the JavaScripts to error out.

Upgrading

Existing users of BrewPi Remix 0.5.3 and above may upgrade with:

sudo /home/brewpi/utils/doUpdate.sh

If you are not on version 0.5.3 or above (or if you have no idea what version you are on,) use the following command to upgrade to the latest version:

curl -L upgrade.brewpiremix.com | sudo bash

You must run this from within your /home/brewpi directory or from each chamber's directory in multi-chamber mode.

Tools

No significant changes

Scripts

Commit Summary

• d8a41b6 Add .local to exclusions
• 168cfa6 Add toolPath to config
• 7bb0589 Whitespace cleanup
• 3dd2d27 Remove trailing comma after null (#174)
• 03ca630 Add gitInfo.py for future use
• 4c93d3e Skip perms on venv (#185)

File Changes

• M .gitignore (1)
• M BrewPiUtil.py (7)
• M Tilt.py (2)
• M brewpi.py (2)
• M brewpiJson.py (2)
• A gitInfo.py (132)
• M programController.py (2)
• M settings/defaults.cfg (1)
• M utils/doCleanup.sh (8)
• M utils/doDaemon.sh (8)
• M utils/doDepends.sh (12)
• M utils/doIndex.sh (10)
• M utils/doMenu.sh (6)
• M utils/doPerms.sh (16)
• M utils/doUpdate.sh (30)
• M utils/doWiFi.sh (10)

Patch Links:

• https://github.com/brewpi-remix/brewpi-script-rmx/pull/186.patch
• https://github.com/brewpi-remix/brewpi-script-rmx/pull/186.diff

Web UI

No changes

 

[balrog]

0.7.5 Bug Fix Release

As soon as @day_trippr quits creating bugs I can get on to what will amount to

lmao!

0.7.6 Bug Fix Release

You two crack me up to no end.

 

[LBussy]

Well, I guess I can't blame this one on him.

 

[day_trippr]

We like to have fun here

 

[Brewski_59]

0.7.6 Bug Fix Release

Oh no, your not getting me again, last time I did an update it broke it.

 

[day_trippr]

The gauntlet is thrown?

 

[Brewski_59]

The gauntlet is thrown?

Nah

We like to have fun here

 

[LBussy]

Oh no, your not getting me again, last time I did an update it broke it.

Cut me to da bone!

 

[LBussy]

I dropped a hotfix into 0.7.5 master to address an issue where new OneWire sensors would not save correctly. There is no reason to update unless you have been bit by this (and I know of only one person who has been);

Everyone else can wait for a new release.

If you get bit by this, you will have to reset the Arduino to Factory Defaults (Maintenance Panel -> Advanced Settings -> Control Constants -> [Reset Arduino to factor defaults] button.)

 

[blau]

Hi, I have reinstalled.
Good display appearance. I connect the relay, it recognizes it well and it is installed, then I connect the probe to A0 but it is not recognized (I have tested with each of my 3 probes separately)
Tell me if you want me to reset the Arduino with the advanced settings button and flash the firmware again.

 

[LBussy]

The hotfix I referenced is to deal with saving a ghost device only. If your sensors are not showing up, I suggest going back to the test sketch I shared with you and address whatever may be preventing the sensors from being detected. Assuming you have the I2C firmware installed (if the LCD works it is) and you are connected to A0, they should show up.

 

[blau]

Ok, It only occurs to me that the probes are bad. Can you think of a way to check this? We wait for the new probe? any other test? I follow the path that you indicate to me.
Yes I installed I2C and the LCD works fine.