Yet another DYI Plato scale

Homebrew Talk

Help Support Homebrew Talk:

This site may earn a commission from merchant affiliate links, including eBay, Amazon, and others.
1000001203.png
1000001203.png
 
What does your hardware setup look like ? I see you have 4 displays, how many of those are connected to kegmon ?
I have 2 esp's for kegmon to support 3 scales (one have 2 scales and another 1 scale) ... 4th screen is Arduino code looking into 3 pressure inputs so not related to kegmon (will be nice to add pressure readings to kegmon in future 😁)
 
I have 2 esp's for kegmon to support 3 scales (one have 2 scales and another 1 scale) ... 4th screen is Arduino code looking into 3 pressure inputs so not related to kegmon (will be nice to add pressure readings to kegmon in future 😁)
That explains the setup then, thanks. Well pressure sensor is a project that I have been working on for a while but more focused on fermentation. I will do some tests to see if I can figure out why the graphs are not rendering correctly. Can you capture and share some logs from the serial that would help to figure out what is happening. you can DM me instead of putting in the forum
 
That explains the setup then, thanks. Well pressure sensor is a project that I have been working on for a while but more focused on fermentation. I will do some tests to see if I can figure out why the graphs are not rendering correctly. Can you capture and share some logs from the serial that would help to figure out what is happening. you can DM me instead of putting in the forum
Great, will do it as DM today evening (CET). Thanks a lot
 
Finally KegMon now has a new vue based user interface similar to Gravitymon and my other projects. Feel free to reach out with any issues, I still have the docs to update

https://github.com/mp-se/kegmon/releases/tag/v1.0.0-beta1
ESP32s2:
Upgraded from 0.8 via web interface.
The 20x4 LED displays went slooow, like on the first v0.8
Web interface turned black in Firefox - and Vivaldi, on my Linux Mint PC.
Tried to flash 1.0.0b1 via esptool.py. Same result.
I forgot to try an erease_flash before write_flash. Maybe that would give a working result.
I guess partitions is the same as on 0.8 (?)
Reverted to 0.8 via esptool.py
 
ESP32s2:
Upgraded from 0.8 via web interface.
The 20x4 LED displays went slooow, like on the first v0.8
Web interface turned black in Firefox - and Vivaldi, on my Linux Mint PC.
Tried to flash 1.0.0b1 via esptool.py. Same result.
I forgot to try an erease_flash before write_flash. Maybe that would give a working result.
I guess partitions is the same as on 0.8 (?)
Reverted to 0.8 via esptool.py
Update:
I grabbed my old kegmon box with 0.96" displays. This one also has/had v0.8.
Updated via web interface to v1.0.0b1. Success!
 
Last edited:
ESP32s2:
Upgraded from 0.8 via web interface.
The 20x4 LED displays went slooow, like on the first v0.8
Web interface turned black in Firefox - and Vivaldi, on my Linux Mint PC.
Tried to flash 1.0.0b1 via esptool.py. Same result.
I forgot to try an erease_flash before write_flash. Maybe that would give a working result.
I guess partitions is the same as on 0.8 (?)
Reverted to 0.8 via esptool.py
Thanks for the update, i will check that and do an upgrade from 0.8. The partitions are the same so that should not cause any issues.
 
Update:
I grabbed my old kegmon box with 0.96" displays. This one also has/had v0.8.
Updated via web interface to v1.0.0b1. Success!
ok, good to know. I have not tested the LCD option in a while (i dont have a build for that) but I will test that on the different boards then.
 
ok, good to know. I have not tested the LCD option in a while (i dont have a build for that) but I will test that on the different boards then.
I can confirm that the LCD update is slow both in 0.9 and 1.0 but I have not changed any code since 0.8 in that part so the source is probably something in the arduino version which will require some detective work to figure out why.....
 
beta2 on ESP32s2/ 20x4 LED's:
Upping wire speed to 400MHz made a good improvement of the LED's rendering!
I still have the same issues with web interface as in beta1. Just turns black in the browser. Sometimes I get a correct view if I use url for one of the submenus. Sometimes the box even reboots during tinkering with the url's.
 
beta2 on ESP32s2/ 20x4 LED's:
Upping wire speed to 400MHz made a good improvement of the LED's rendering!
I still have the same issues with web interface as in beta1. Just turns black in the browser. Sometimes I get a correct view if I use url for one of the submenus. Sometimes the box even reboots during tinkering with the url's.
Can you open the developer console and see if there are any errors?
 
Can you open the developer console and see if there are any errors?
Looks normal:
12282 I: Main: Setup completed.
13778 I: WEB : webServer callback /api/status.
17217 I: WEB : webServer callback for /index.html (Memory).
17268 I: WEB : webServer callback for /app.js (Memory).
17283 I: WEB : webServer callback for /app.css (Memory).
17767 I: LOOP: Reading data

I flashed once more using esptool with same result.
Maybe there are some v0.8 data stored that affects this version.
I can give it a try by erasing the s2mini completely first
 
Looks normal:
12282 I: Main: Setup completed.
13778 I: WEB : webServer callback /api/status.
17217 I: WEB : webServer callback for /index.html (Memory).
17268 I: WEB : webServer callback for /app.js (Memory).
17283 I: WEB : webServer callback for /app.css (Memory).
17767 I: LOOP: Reading data

I flashed once more using esptool with same youresult.
Maybe there are some v0.8 data stored that affects this version.
I can give it a try by erasing the s2mini completely first
There is new config file for 1.0, you can browse, delete and upload files under the tools menu. You can download a backup file and try a full erase before flashing, this can sometimes fix problems.

There is also an option to do a hardware scan (not fully implemented for all hw options yet), that could give some clues to what can be detected
 
There is new config file for 1.0, you can browse, delete and upload files under the tools menu. You can download a backup file and try a full erase before flashing, this can sometimes fix problems.

There is also an option to do a hardware scan (not fully implemented for all hw options yet), that could give some clues to what can be detected
I think I found an issue:
After installing from scratch and cloning config from my other spare beta2 -box, I ended up with the same black webpage as before.
(This is in Firefox or Vivaldi on a Linux Mint 20.3 laptop).

Tried to access the box from my phone (Android/Firefox) - Success!
Tried from my wife's Win10/Firefox - Success!

I suspect there are some java incompatibilities vs Linux.
Maybe some libraries has been changed between v0.8, which worked ok in Linux, and v1.0
 
I think I found an issue:
After installing from scratch and cloning config from my other spare beta2 -box, I ended up with the same black webpage as before.
(This is in Firefox or Vivaldi on a Linux Mint 20.3 laptop).

Tried to access the box from my phone (Android/Firefox) - Success!
Tried from my wife's Win10/Firefox - Success!

I suspect there are some java incompatibilities vs Linux.
Maybe some libraries has been changed between v0.8, which worked ok in Linux, and v1.0
The ui has been rewritten from scratch and should support modern (newer) web browsers. This is the min version required in the current setup (browsers that support the core javascript functions). What was the version that failed older than this?
  • Chrome >=87
  • Firefox >=78
  • Safari >=14
  • Edge >=88
 
The ui has been rewritten from scratch and should support modern (newer) web browsers. This is the min version required in the current setup (browsers that support the core javascript functions). What was the version that failed older than this?
  • Chrome >=87
  • Firefox >=78
  • Safari >=14
  • Edge >=88
Firefox 130.0.1 in both Linux and the Android phone.
I did see a difference between config backups from the box with 0.96" displays and the freshly installed one with 20x4 displays.
Do not know if it makes any difference.

0.96:
"http_post_header1": "",
"http_post2_header1": "Content-Type: application/json",
20x4:
"http_post_header1": "Content-Type: application/json",
"http_post2_header1": "Content-Type: application/json",

From the browser's console, I see these messages:

Loading failed for the module with source “http://192.168.165.xxx/js/app.js”. 192.168.165.xxx:1:341
Source map error: Error: NetworkError when attempting to fetch resource.Resource URL: http://192.168.165.xxx/css/app.cssSource Map URL: bootstrap.css.map
Error in parsing value for '-webkit-text-size-adjust'. Declaration dropped.

I wonder why this only happens connecting to the 20x4 box.
The 0.96" behaves normal.
Anyway, this is not a big issue. Both boxes have working MQTT and displays, and now I know a way around my web access challenge
 
Firefox 130.0.1 in both Linux and the Android phone.
I did see a difference between config backups from the box with 0.96" displays and the freshly installed one with 20x4 displays.
Do not know if it makes any difference.

0.96:
"http_post_header1": "",
"http_post2_header1": "Content-Type: application/json",
20x4:
"http_post_header1": "Content-Type: application/json",
"http_post2_header1": "Content-Type: application/json",

From the browser's console, I see these messages:

Loading failed for the module with source “http://192.168.165.xxx/js/app.js”. 192.168.165.xxx:1:341
Source map error: Error: NetworkError when attempting to fetch resource.Resource URL: http://192.168.165.xxx/css/app.cssSource Map URL: bootstrap.css.map
Error in parsing value for '-webkit-text-size-adjust'. Declaration dropped.

I wonder why this only happens connecting to the 20x4 box.
The 0.96" behaves normal.
Anyway, this is not a big issue. Both boxes have working MQTT and displays, and now I know a way around my web access challenge
The config entries is for the intergrationa so that should not matter.

It looks like it fails to load the css file which is strange. But since this file is compressed it could be that on some devices it fails with the decompression and it stops trying to start the application

I will see if i can find some info on that
 
@mper As a matter of interest,why do you switch the DS18B20 power supply from an IO and not leave it permanently powered from 3v3 like in most other designs that use this sensor ?
 
@mper As a matter of interest,why do you switch the DS18B20 power supply from an IO and not leave it permanently powered from 3v3 like in most other designs that use this sensor ?
The design supports multiple sensors and some others are less stable which sometimes require a restart to function so thats why. If you use a ds18 you can power it from 3v
 
Is there something special to do with green hx711 cant get it to comminicate with esp...
 

Attachments

  • 20241211_203526.jpg
    20241211_203526.jpg
    3 MB
It started to work... i hawe no idea why... happy camper..
 

Attachments

  • Screenshot_20241227_203742_Chrome.jpg
    Screenshot_20241227_203742_Chrome.jpg
    344.5 KB
Back
Top