NEW StrangeBrew Elsinore Thread

Can you not see it? it should be visible. If it's not I have no idea why.

 

Well that makes 2 of us. I am moving from my desktop to a new chromebook and I will try again. One last question - when I click Lock to exit the edit screen I lose the shutdown Elisinore and Shutdown System buttons. Is this another sign that my system is haunted.

Anyway- I understand that this is specific to something I have done and not a criticism of your software. I also appreciate how you have gone out of your way to help. I am sure I will share a laugh when I figure out just what I have done. I maybe cursed from using Windows too long. My first installed versions was Windows 286. I may suffer from a case of no setup.exe and years of making snide jokes at the expense of software people. That may be the answer.

Time to go pitch the yeast in my Lambic. Cheers

 

The shutdown buttons should only be visible in edit mode, this is to prevent mistakenly pressing the buttons when you're using Elsinore.

 

Added some doc for trigger profiles: http://dougedey.github.io/2015/05/11/Mash_Profiles_And_Triggers/

 

Keep going Doug! I'll preparing my E-Biab control panel, with auto and manual mode, i'll post some schematics when i test it.

 

Control has been regained over /r/StrangeBrew and some changes have been made to it - post tagging, and a wiki has been enabled. Let me know if you'd like to contribute the wiki!

 

DS18S20 support added, I didn't realize they were a different family (10) compared to the DS18B20 (28). But everything else should be the same. I don't have any to test with.

 

I'm Back....
Was running my SBE last night (still have the GUI issue) and for whatever reason I checked the Update button. When I re started my system it wouldn't start. I get this message about one of my sensors which had been working fine, is suddenly not seen as a temp sensor.

May 13, 2015 1:44:17 PM com.sb.elsinore.LaunchControl startDevice
WARNING: 28-000006777ac0 is not a temperature probe
Problems parsing device HLT
May 13, 2015 1:44:17 PM com.sb.elsinore.LaunchControl$1 run
WARNING: Shutting down. Saving configuration

If I run bbb_setup.sh, all four of my DS18B20's are detected.

./bbb_setup.sh: line 5: echo: write error: File exists
Cape Manager updated, list of devices:
total 0
-rw-r--r-- 1 root root 4096 May 13 13:43 uevent
lrwxrwxrwx 1 root root 0 May 13 13:43 subsystem -> ../../bus/w1
lrwxrwxrwx 1 root root 0 May 13 13:43 driver -> ../../bus/w1/drivers/w1_maste r_driver
drwxr-xr-x 3 root root 0 May 13 13:43 28-000006777ac0
-r--r--r-- 1 root root 4096 May 13 13:43 w1_master_timeout
-r--r--r-- 1 root root 4096 May 13 13:43 w1_master_slaves
-r--r--r-- 1 root root 4096 May 13 13:43 w1_master_slave_count
-rw-rw-r-- 1 root root 4096 May 13 13:43 w1_master_search
-rw-rw-r-- 1 root root 4096 May 13 13:43 w1_master_remove
-rw-rw-r-- 1 root root 4096 May 13 13:43 w1_master_pullup
-r--r--r-- 1 root root 4096 May 13 13:43 w1_master_pointer
-r--r--r-- 1 root root 4096 May 13 13:43 w1_master_name
-r--r--r-- 1 root root 4096 May 13 13:43 w1_master_max_slave_count
-r--r--r-- 1 root root 4096 May 13 13:43 w1_master_attempts
-rw-rw-r-- 1 root root 4096 May 13 13:43 w1_master_add
drwxr-xr-x 2 root root 0 May 13 13:43 power
drwxr-xr-x 3 root root 0 May 13 13:43 28-0000065bc3cc
drwxr-xr-x 3 root root 0 May 13 13:43 28-0000065c31fa

I deleted my chamber probe so only 3 are listed, but they are listed.

Any reason besides my machine being haunted. I just ordered a new BBB and will retry, I like to have a spare anyway.

 

This is probably because of a change I made to support the DS18S20s, I'll double check when I get home.

 

Fix is in.

 

This question is for anyone that has installed a touchscreen. I am in the process of building my controller and trying to decide if I should install a touchscreen. I found this one http://www.chalk-elec.com/?page_id=...ce-LCD-with-capacitive-touchscreen/p/36248806.

Do any of you regret installing the touchscreen?

Thanks

 

I think I am close to getting all my issues at least identified. If someone could either post or PM me the contents of their elsinore.cfg to aide in my trouble shooting I will gladly email you a beer.

Doug, one of my issues was permissions. One of the files I had copied off to my desktop and when I moved it back SBE no longer had access to it. Couldn't even (sudo su) to access it. I knew it was something stupid I did. Late nights, beer and linux don't always work.

 

Why did you copy it? Not sure what you need from the config file, it's XML and you shouldn't be modifying it directly.

 

I wanted to see if editing the cfg file directly would have any effect on my GUI display issue. I was told by someone other than yourself back in the beginning that editing the cfg would work??

 

I don't see how. I haven't gotten around to writing an XSD yet so any changes you make may be invalid and cause issues.

Please use the UI to setup Elsinore from scratch, and if you're moving files around and causing permission issues, use chown -R <user>:<group> SB_Elsinore_Server
to reset the file permissions.

 

OK, but I had the same issue when I was using the GUI. I do use chown now once I saw what happened.

 

I finally have a little time to work on this now. I have the bbb up and running with ubuntu and the app is up. I'm now trying to figure out how to wire this 1 wire A/D converter. The disc that came with it is broke and unreadable not to mention nothing on the Chinese site... I'm hoping someone here is using it. its a model is 1wad-5v from pcsensor.com. Any help will be greatly appreciated. Also, and most importantly great work Doug since I've last looked you been busy.

*** Updated*** Not sure why I didn't think about it before but I took it apart and traced them back to the ic. I suggest you do the same thing in case they are different for you. For this one it goes:

black = ground
yellow = data
red = Vcc

 

Seriously, I have no idea what you're doing, but I suggest that you look into what is going wrong before posting in here, it's distracting.

 

You got it. Consider this thread un-followed.

 

Will someone, anyone please document their Elsinore build? I want to do one myself but with new baby and moving between houses i dont have as much time to research the parts needed etc. Yes i know there are a lot of different parts you could use, but even just seeing peoples parts lists and circuits would be great. I know ive asked before but ill ask again anyways

 

Just posted a detailed walkthrough of my personal process here:

http://www.reddit.com/r/StrangeBrew/comments/36a3bp/control_panel_and_brewery_build/

 

There doesn't appear to be anything there currently, but look forward to it. I'm not overly familiar with Linux, but I'm good at typing in the commands others give!

My goal is to set up a system using the new Raspberry Pi. I downloaded Raspbian (NOOBS), extracted it to my MicroSD card, plugged it into the Pi, and installed it. After installing it I installed RealVNC so I could play around with the Pi without being in front of it.

Once NOOBS was installed I tried to go to the setup link for the Raspberry Pi in the first post to this thread, but it's an invalid link. I'm guessing it intends to go to http://dougedey.github.io/2014/03/22/Raspberry-Pi-Basic-Setup/.

I made these changes: sudo modprobe w1-gpio sudo modprobe w1-therm
If you’re on a newer kernel you may need to edit your /boot/config.txt
sudo nano /boot/config.txt
Add this line
dtoverlay=w1-gpio,gpiopin=4

After installing StrangeBrew, I connected my temperature probe, and started it up. It all worked, or so I thought. I have an issue now that I can't get more than 1 timer or switch to survive shutdown. I'll keep reading the posts here and see what I missed. From github I see a few more instructions that I don't see in the initial post, (like installing Java). No idea if that step was required.

 

I got to the photos. Try clicking on the reddit posts title it should link to an album.

 

Thanks, I was looking within the reddit post itself for something!

Attached is the hardware I'm experimenting with.

View attachment Electric brewery.pdf

 

Ok I have the ds2450 up and running. Now when I run ./launch.sh it see the non-temp (mpx5010) and ask if it wants me to setup owfs. Beleow is what I get. I can go to ip:2121 and see the ds2450 and my two dallas temp sensors.

I'm sure I've done something stupid but can find it.

Code:

Detected a non temp probe.20-00000006b5a0
Do you want to setup OWFS? [y/N]
y
May 17, 2015 8:42:59 PM com.sb.elsinore.LaunchControl createOWFS
WARNING: Creating the OWFS configuration.
May 17, 2015 8:42:59 PM com.sb.elsinore.LaunchControl createOWFS
WARNING: What is the OWFS server host? (Defaults to localhost)

May 17, 2015 8:43:00 PM com.sb.elsinore.LaunchControl createOWFS
WARNING: What is the OWFS server port? (Defaults to 4304)

May 17, 2015 8:43:05 PM com.sb.elsinore.LaunchControl addNewElement
INFO: Creating element of owfs_server
May 17, 2015 8:43:05 PM com.sb.elsinore.LaunchControl addNewElement
INFO: on general
May 17, 2015 8:43:05 PM com.sb.elsinore.LaunchControl addNewElement
INFO: Creating element of owfs_port
May 17, 2015 8:43:05 PM com.sb.elsinore.LaunchControl addNewElement
INFO: on general
Exception in thread "main" java.lang.NullPointerException
at com.sb.elsinore.LaunchControl.createOWFS(LaunchControl.java:1595)
at com.sb.elsinore.LaunchControl.listOneWireSys(LaunchControl.java:1329)
at com.sb.elsinore.LaunchControl.updateDeviceList(LaunchControl.java:1373)
at com.sb.elsinore.LaunchControl.updateDeviceList(LaunchControl.java:1363)
at com.sb.elsinore.LaunchControl.readConfig(LaunchControl.java:709)
at com.sb.elsinore.LaunchControl.<init>(LaunchControl.java:423)
at com.sb.elsinore.LaunchControl.main(LaunchControl.java:315)

Code:

 

Did you type anything in for the OWFS Port?

 

Ok. I'm an idiot.... I thought when it said defaults to that if I hit enter that is what it would use. I have it working now. Thanks Doug.

 

Forgive my ignorance... I recently moved my brewery to the garage and disconnected everything, installed a fresh copy of Elsinore and now I'm having issues with what appears to be OWSF here is what appears. I'm thinking when I went in and deleted the old Elsinore I must have screwed something up. I've checked and rechecked the physical connection of the temp probes; although initially I noticed the connection had come loose. Any help would be appreciated. Thanks for you time





[email protected] ~/SB_Elsinore_Server $ ./launch.sh
Starting Elsinore as pi
May 18, 2015 8:44:38 AM com.sb.elsinore.LaunchControl main
INFO: Running Brewery Controller.
May 18, 2015 8:44:38 AM com.sb.elsinore.LaunchControl readConfig
INFO: CFG IS NULL
May 18, 2015 8:44:38 AM com.sb.elsinore.LaunchControl readConfig
INFO: DOC IS NULL
Detected a non temp probe.28-0000066a41ee
Do you want to setup OWFS? [y/N]
y
May 18, 2015 8:44:40 AM com.sb.elsinore.LaunchControl createOWFS
WARNING: Creating the OWFS configuration.
May 18, 2015 8:44:40 AM com.sb.elsinore.LaunchControl createOWFS
WARNING: What is the OWFS server host? (Defaults to localhost)
10.0.1.32
May 18, 2015 8:44:45 AM com.sb.elsinore.LaunchControl createOWFS
WARNING: What is the OWFS server port? (Defaults to 4304)
8080
May 18, 2015 8:44:48 AM com.sb.elsinore.LaunchControl addNewElement
INFO: Creating element of general
May 18, 2015 8:44:48 AM com.sb.elsinore.LaunchControl addNewElement
INFO: Creating on configDoc base
May 18, 2015 8:44:48 AM com.sb.elsinore.LaunchControl addNewElement
INFO: Creating element of owfs_server
May 18, 2015 8:44:48 AM com.sb.elsinore.LaunchControl addNewElement
INFO: on general
May 18, 2015 8:44:48 AM com.sb.elsinore.LaunchControl addNewElement
INFO: Creating element of owfs_port
May 18, 2015 8:44:48 AM com.sb.elsinore.LaunchControl addNewElement
INFO: on general
May 18, 2015 8:44:48 AM com.sb.elsinore.LaunchControl setupOWFS
INFO: Connecting to 10.0.1.32:8080
May 18, 2015 8:44:48 AM com.sb.elsinore.LaunchControl createConfig
WARNING: Could not find any one wire devices
Please check you have the correct modules setup
May 18, 2015 8:44:48 AM com.sb.elsinore.LaunchControl createConfig
WARNING: http://dougedey.github.io/2014/11/24/Why_Cant_I_Use_Elsinore_Without_Temperature_Probes/
May 18, 2015 8:44:48 AM com.sb.elsinore.LaunchControl$1 run
WARNING: Shutting down. Saving configuration
[email protected] ~/SB_Elsinore_Server $

 

is your owserver listening on 8080? Unless you changed that it should be 4304.

 

Do a check for updates, you're on a version with a bug.

 

No, it should have defaulted to 4304, and it should've checked for blank inputs. I've added debug incase it happens again to tell me what it picked up.

 

I though I installed it using this (from the first page of this thread)

https://github.com/DougEdey/SB_Elsinore_Server

I'll give it another go
Thanks

 

Same problem; is there a different way to get the update than using "git clone https://github.com/DougEdey/SB_Elsinore_Server"
I went into Pi and deleted everything Elsinore and basically starting from scratch. I'm unable to update via web server due to the above error (it won't start)

 

Updates have been pushed to get the current sha on launch to help me debug.
I've also added an update command to launch.sh: launch.sh update

 

All is working! Thanks for the help!

 

I'm attempting a new install, can someone confirm that I'm on the right path? I am using the new Raspberry Pi 2. I'm running into the same issue as I did earlier with the configuration not properly saving when I exit.

Connected HDMI, keyboard, mouse, Ethernet, and a temperature sensor (GPIO 4, +5, ground, with appropriate resistor). Power on, install Raspbain (NOOBS).

In raspi-config, change locale to en_US.UTF8, enable device tree, enable I2C.

After Raspbian is installed, type:

Code:

sudo modprobe w1-gpio sudo modprobe w1-therm

then type:

Code:

sudo nano /boot/config.txt

Add this line:

Code:

dtoverlay=w1-gpio,gpiopin=4

then type:

Code:

sudo nano /etc/modules

and add these lines to the bottom of the file /etc/modules:

Code:

w1-gpio
w1-therm

then type:

Code:

sudo reboot

Run:

Code:

git clone https://github.com/DougEdey/SB_Elsinore_Server

then type:

Code:

cd SB_Elsinore_Server

then run:

Code:

sudo ./launch.sh

Do I need to run the last command as su? The instructions don't say to, but I see examples of it in the thread.

Do I need to install OWFS? If so, are there instructions somewhere? Do I need to install Java, and finally, how about lshw?

Here's what I get when I initially sudo ./launch.sh:

Code:

~/SB_Elsinore_Server $ sudo ./launch.sh
Starting Elsinore as root
May 19, 2015 12:50:46 AM com.sb.elsinore.LaunchControl main
INFO: Running Brewery Controller.
May 19, 2015 12:50:46 AM com.sb.elsinore.LaunchControl getShaFor
INFO: Checking for sha for HEAD
May 19, 2015 12:50:46 AM com.sb.elsinore.LaunchControl getShaFor
INFO: 29aada6a571b2050e3a7c71d1d5d99c49ba529f7
May 19, 2015 12:50:46 AM com.sb.elsinore.LaunchControl main
INFO: Currently at: 29aada6a571b2050e3a7c71d1d5d99c49ba529f7
May 19, 2015 12:50:46 AM com.sb.elsinore.LaunchControl readConfig
INFO: CFG IS NULL
May 19, 2015 12:50:46 AM com.sb.elsinore.LaunchControl readConfig
INFO: DOC IS NULL
May 19, 2015 12:50:46 AM com.sb.elsinore.LaunchControl listOneWireSys
INFO: Checking for 28-000005f3b7b4
May 19, 2015 12:50:46 AM com.sb.elsinore.Temp <init>
INFO: Adding28-000005f3b7b4
May 19, 2015 12:50:46 AM com.sb.elsinore.Temp <init>
INFO: 28-000005f3b7b4 added.
May 19, 2015 12:50:46 AM com.sb.elsinore.Temp setScale
WARNING: Cut off is: -999
May 19, 2015 12:50:46 AM com.sb.elsinore.Temp setScale
WARNING: Cut off is now: -999
1) 28-000005f3b7b4May 19, 2015 12:50:47 AM com.sb.elsinore.LaunchControl displaySensors
INFO:  70.925
May 19, 2015 12:50:47 AM com.sb.elsinore.LaunchControl createConfig
WARNING: Please go to the Web UI to the web UI http://VashPi:8080/controller
May 19, 2015 12:50:47 AM com.sb.elsinore.LaunchControl <init>
INFO: CONFIG READ COMPLETED***********
May 19, 2015 12:50:47 AM com.sb.elsinore.BrewServer <init>
INFO: Launching on port 8080
May 19, 2015 12:50:47 AM com.sb.elsinore.BrewServer <init>
INFO: Enabled logging at level:WARNING

After I access my site, add 2 timers (90 Minute at time 90, and 60 Minute at time 60, and 2 elements with Element 1 at GPIO 17, and Element 2 at GPIO 24), and shut down, here is what I see in the console:

Code:

~/SB_Elsinore_Server $ sudo ./launch.sh
Starting Elsinore as root
May 19, 2015 12:50:46 AM com.sb.elsinore.LaunchControl main
INFO: Running Brewery Controller.
May 19, 2015 12:50:46 AM com.sb.elsinore.LaunchControl getShaFor
INFO: Checking for sha for HEAD
May 19, 2015 12:50:46 AM com.sb.elsinore.LaunchControl getShaFor
INFO: 29aada6a571b2050e3a7c71d1d5d99c49ba529f7
May 19, 2015 12:50:46 AM com.sb.elsinore.LaunchControl main
INFO: Currently at: 29aada6a571b2050e3a7c71d1d5d99c49ba529f7
May 19, 2015 12:50:46 AM com.sb.elsinore.LaunchControl readConfig
INFO: CFG IS NULL
May 19, 2015 12:50:46 AM com.sb.elsinore.LaunchControl readConfig
INFO: DOC IS NULL
May 19, 2015 12:50:46 AM com.sb.elsinore.LaunchControl listOneWireSys
INFO: Checking for 28-000005f3b7b4
May 19, 2015 12:50:46 AM com.sb.elsinore.Temp <init>
INFO: Adding28-000005f3b7b4
May 19, 2015 12:50:46 AM com.sb.elsinore.Temp <init>
INFO: 28-000005f3b7b4 added.
May 19, 2015 12:50:46 AM com.sb.elsinore.Temp setScale
WARNING: Cut off is: -999
May 19, 2015 12:50:46 AM com.sb.elsinore.Temp setScale
WARNING: Cut off is now: -999
1) 28-000005f3b7b4May 19, 2015 12:50:47 AM com.sb.elsinore.LaunchControl displaySensors
INFO:  70.925
May 19, 2015 12:50:47 AM com.sb.elsinore.LaunchControl createConfig
WARNING: Please go to the Web UI to the web UI http://VashPi:8080/controller
May 19, 2015 12:50:47 AM com.sb.elsinore.LaunchControl <init>
INFO: CONFIG READ COMPLETED***********
May 19, 2015 12:50:47 AM com.sb.elsinore.BrewServer <init>
INFO: Launching on port 8080
May 19, 2015 12:50:47 AM com.sb.elsinore.BrewServer <init>
INFO: Enabled logging at level:WARNING
~/SB_Elsinore_Server $ sudo ./launch.sh
Starting Elsinore as root
May 19, 2015 12:50:46 AM com.sb.elsinore.LaunchControl main
INFO: Running Brewery Controller.
May 19, 2015 12:50:46 AM com.sb.elsinore.LaunchControl getShaFor
INFO: Checking for sha for HEAD
May 19, 2015 12:50:46 AM com.sb.elsinore.LaunchControl getShaFor
INFO: 29aada6a571b2050e3a7c71d1d5d99c49ba529f7
May 19, 2015 12:50:46 AM com.sb.elsinore.LaunchControl main
INFO: Currently at: 29aada6a571b2050e3a7c71d1d5d99c49ba529f7
May 19, 2015 12:50:46 AM com.sb.elsinore.LaunchControl readConfig
INFO: CFG IS NULL
May 19, 2015 12:50:46 AM com.sb.elsinore.LaunchControl readConfig
INFO: DOC IS NULL
May 19, 2015 12:50:46 AM com.sb.elsinore.LaunchControl listOneWireSys
INFO: Checking for 28-000005f3b7b4
May 19, 2015 12:50:46 AM com.sb.elsinore.Temp <init>
INFO: Adding28-000005f3b7b4
May 19, 2015 12:50:46 AM com.sb.elsinore.Temp <init>
INFO: 28-000005f3b7b4 added.
May 19, 2015 12:50:46 AM com.sb.elsinore.Temp setScale
WARNING: Cut off is: -999
May 19, 2015 12:50:46 AM com.sb.elsinore.Temp setScale
WARNING: Cut off is now: -999
1) 28-000005f3b7b4May 19, 2015 12:50:47 AM com.sb.elsinore.LaunchControl displaySensors
INFO:  70.925
May 19, 2015 12:50:47 AM com.sb.elsinore.LaunchControl createConfig
WARNING: Please go to the Web UI to the web UI http://VashPi:8080/controller
May 19, 2015 12:50:47 AM com.sb.elsinore.LaunchControl <init>
INFO: CONFIG READ COMPLETED***********
May 19, 2015 12:50:47 AM com.sb.elsinore.BrewServer <init>
INFO: Launching on port 8080
May 19, 2015 12:50:47 AM com.sb.elsinore.BrewServer <init>
INFO: Enabled logging at level:WARNING
Warning: NLS unused message: CHANGE_SCALE in: com.sb.elsinore.nls.messages
Warning: NLS unused message: DUTY in: com.sb.elsinore.nls.messages
Warning: NLS unused message: CALIBRATION in: com.sb.elsinore.nls.messages
Warning: NLS unused message: HIDE in: com.sb.elsinore.nls.messages
Warning: NLS unused message: SHOW in: com.sb.elsinore.nls.messages
Warning: NLS unused message: INVERT_COOL in: com.sb.elsinore.nls.messages
Warning: NLS unused message: INVERT_HEAT in: com.sb.elsinore.nls.messages
Warning: NLS unused message: INVERT_GPIO in: com.sb.elsinore.nls.messages
Warning: NLS unused message: UPDATE_GRAVITY in: com.sb.elsinore.nls.messages
Warning: NLS unused message: DESCRIPTION in: com.sb.elsinore.nls.messages
Warning: NLS unused message: TARGET in: com.sb.elsinore.nls.messages
Warning: NLS unused message: SHUTDOWN in: com.sb.elsinore.nls.messages
Warning: NLS unused message: SHUTDOWN_SYSTEM in: com.sb.elsinore.nls.messages
Couldn't execute lshw to identify board
Cannot run program "lshw": error=2, No such file or directory
No definitions file found, assuming direct mapping
Couldn't execute lshw to identify board
Cannot run program "lshw": error=2, No such file or directory
No definitions file found, assuming direct mapping

After I run sudo ./launch.sh again, here is what I see in the console:

Code:

~/SB_Elsinore_Server $ sudo ./launch.sh
Starting Elsinore as root
May 19, 2015 12:54:17 AM com.sb.elsinore.LaunchControl main
INFO: Running Brewery Controller.
May 19, 2015 12:54:17 AM com.sb.elsinore.LaunchControl getShaFor
INFO: Checking for sha for HEAD
May 19, 2015 12:54:17 AM com.sb.elsinore.LaunchControl getShaFor
INFO: 29aada6a571b2050e3a7c71d1d5d99c49ba529f7
May 19, 2015 12:54:17 AM com.sb.elsinore.LaunchControl main
INFO: Currently at: 29aada6a571b2050e3a7c71d1d5d99c49ba529f7
May 19, 2015 12:54:17 AM com.sb.elsinore.LaunchControl readConfig
INFO: CFG IS NULL
Couldn't execute lshw to identify board
Cannot run program "lshw": error=2, No such file or directory
No definitions file found, assuming direct mapping
May 19, 2015 12:54:18 AM com.sb.elsinore.LaunchControl parseXMLSections
INFO: Checking section timers
May 19, 2015 12:54:18 AM com.sb.elsinore.LaunchControl parseXMLSections
INFO: Checking section switches
May 19, 2015 12:54:18 AM com.sb.elsinore.LaunchControl parseXMLSections
INFO: Checking section phSensors
May 19, 2015 12:54:18 AM com.sb.elsinore.LaunchControl parseXMLSections
INFO: Checking section general
May 19, 2015 12:54:18 AM com.sb.elsinore.LaunchControl parseXMLSections
INFO: Checking section device
May 19, 2015 12:54:18 AM com.sb.elsinore.LaunchControl parseDevice
INFO: Parsing XML Device: 28-000005f3b7b4
May 19, 2015 12:54:18 AM com.sb.elsinore.LaunchControl parseDevice
INFO: min: null
May 19, 2015 12:54:18 AM com.sb.elsinore.LaunchControl parseDevice
INFO: Not enough volume data points, 0 found
May 19, 2015 12:54:18 AM com.sb.elsinore.Temp <init>
INFO: Adding28-000005f3b7b4
May 19, 2015 12:54:18 AM com.sb.elsinore.Temp <init>
INFO: 28-000005f3b7b4 added.
May 19, 2015 12:54:18 AM com.sb.elsinore.LaunchControl startDevice
INFO: Adding 28-000005f3b7b4 Heat GPIO is (null)
May 19, 2015 12:54:18 AM com.sb.elsinore.LaunchControl startDevice
INFO: Adding 28-000005f3b7b4 Cool GPIO is (null)
May 19, 2015 12:54:18 AM com.sb.elsinore.Temp setScale
WARNING: Cut off is: -999
May 19, 2015 12:54:18 AM com.sb.elsinore.Temp setScale
WARNING: Cut off is now: -999
May 19, 2015 12:54:18 AM com.sb.elsinore.LaunchControl <init>
INFO: CONFIG READ COMPLETED***********
May 19, 2015 12:54:18 AM com.sb.elsinore.BrewServer <init>
INFO: Launching on port 8080
May 19, 2015 12:54:18 AM com.sb.elsinore.BrewServer <init>
INFO: Enabled logging at level:WARNING
Warning: NLS unused message: CHANGE_SCALE in: com.sb.elsinore.nls.messages
Warning: NLS unused message: DUTY in: com.sb.elsinore.nls.messages
Warning: NLS unused message: CALIBRATION in: com.sb.elsinore.nls.messages
Warning: NLS unused message: HIDE in: com.sb.elsinore.nls.messages
Warning: NLS unused message: SHOW in: com.sb.elsinore.nls.messages
Warning: NLS unused message: INVERT_COOL in: com.sb.elsinore.nls.messages
Warning: NLS unused message: INVERT_HEAT in: com.sb.elsinore.nls.messages
Warning: NLS unused message: INVERT_GPIO in: com.sb.elsinore.nls.messages
Warning: NLS unused message: UPDATE_GRAVITY in: com.sb.elsinore.nls.messages
Warning: NLS unused message: DESCRIPTION in: com.sb.elsinore.nls.messages
Warning: NLS unused message: TARGET in: com.sb.elsinore.nls.messages
Warning: NLS unused message: SHUTDOWN in: com.sb.elsinore.nls.messages
Warning: NLS unused message: SHUTDOWN_SYSTEM in: com.sb.elsinore.nls.messages

And here is my elsinore.cfg file after shutting down:

Code:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<elsinore>
  <timers>
    <timer id="60 Minute" position="-1" target="60"/>
  </timers>
  <switches>
    <switch gpio="GPIO24" name="Element%202" position="-1">
      <invert>false</invert>
    </switch>
  </switches>
 <phSensors/>
  <general>
    <pagelock>false</pagelock>
    <scale>F</scale>
    <recorder>false</recorder>
    <recorderDiff>0.15</recorderDiff>
    <recorderTime>5000</recorderTime>
  </general>
  <device id="28-000005f3b7b4">
    <probe>28-000005f3b7b4</probe>
    <position>-1</position>
    <cutoff>-999</cutoff>
    <calibration>0F</calibration>
    <hidden>false</hidden>
  </device>
</elsinore>

The first picture is the initial site, the second picture is the site after I make my configurations, and the third picture is after I shutdown Elsinore and rerun sudo ./launch.sh.

Thanks everyone, sorry for the long post, just really want to get this working. I'm trying to piece together what's in this thread and in the various files on github.

 

I saw this on reddit and its nice, but again...circuit diagram

 

Markgm Doug,
I am also running rpi2
And I use windows with chrome on my PC

I have had the same minor bug as you in that Elsinore will only save one timer and one switch when you properly shut it down.

I have checked my outputs on console and log and they are the same as yours so I won't post them again

There is a very simple fix that I am currently using. You can simply edit the Elsinore.cfg directly from the console. Just copy and paste the timer and switch code and change the name a gpio for each as required. Restart and the switches and timers will appear. Add as many as you want

However if you use the shutdown button from the gui or you use Ctrl c to shut down Elsinore from the console screen you end up with only one switch and one timer again. if you pull the power and restart they are still there. It seems that when Elsinore is shutting down properly using the guitar or ctrl c that it is only saving one switch and timer or it is deleting it from the Elsinore.cfg file - same thing I suppose. This only started Doug after a relatively recent update you made when you mentioned you had been having problems in the way Elsinore saves things on shutdown it might just be a pi thing as no one else has mentioned it

As I leave mine running 24/7 it's not a problem for me once I'm set up



I'm currently 3 days into my first Elsinore brew and it's going very well indeed so I'm a very happy man !!!!

Thanks for all your work again Doug

Cheers

Mike

 

Ps mark your doing everything correctly as far as I can see

It's what I did anyway

Cheers

Mike

 

Need one piece of information if someone could help. My system was doing what I needed until I ran an update for the second type of one wire sensor. Since then I have been unable to launch SBE to pull down the fix. Want to git checkout the latest commit so I can get it running again. What is the commit as I am very new to the checkout process.

Said I wouldn't wouldn't bug you again Doug - just want to get back to a functional system without starting from scratch.