Also, is there a way to automatically start this as a service? I.e. when I plug in my control box the service just starts as part of a RC file
I played with it but couldn't get it to work ... maybe since it starts in interactive mode?
But still very cool so far.
Thanks for all the work
I've never seen it hang, but clearing at the moment is done by restarting the server, I've been trying to work out the best way to reset the timers, it's not too hard to do.
I think the best way it to have a row of reset buttons for each of the timers (I may have it so each timer has it's own row) and a pop up to confirm the reset. Any thoughts?
Also, is there a way to automatically start this as a service? I.e. when I plug in my control box the service just starts as part of a RC file
I played with it but couldn't get it to work ... maybe since it starts in interactive mode?
But still very cool so far.
Thanks for all the work
Doug, Can you set it in the config so we can just add timers and name them ourselves like you do pumps. Click on the button and it changes color and from start to stop and reset. Have the time above the button. What do you think.
Brewer44
[timers]
mash
boil
chill
I haven't added the colour change but I have changed the timers to be set from the config file.
Add a [timers] section with the names of the timers (no value needed at this point)
Code:[timers] mash boil chill
The order you set them is the order they are displayed.
Todo: Allow you to set count up or count down timers (with a duration pop up), and change the colour when you start/stop/reset.
OK, Got it to work this way.
[timers]
mash =
boil =
You can now chose which port to run elsinore on, append your command line with "--port <number>" and elsinore no longer dies when you hit enter.
This is what I did and it did work on port 3131 and also 8080
If it's on 8080 at the same time you have a seperate process running
aux = <GPIO>
New feature enabled: Auxilliary mode for PIDs
Add a GPIO using:
Code:aux = <GPIO>
To a PID control setup and you'll find a new button in the PID control area called "AUX" which you can use to toggle an output.
I'm also going to be moving to YAML config files (I'm going to leave the .cfg method active, but you'll get a message telling you to move to YAML)
YAML allows case sensitivity in config files, and it's easier to read in my opinion.
Doug, After doing a git pull I get this now.
New feature enabled: Auxilliary mode for PIDs
Add a GPIO using:
Code:aux = <GPIO>
To a PID control setup and you'll find a new button in the PID control area called "AUX" which you can use to toggle an output.
I'm also going to be moving to YAML config files (I'm going to leave the .cfg method active, but you'll get a message telling you to move to YAML)
YAML allows case sensitivity in config files, and it's easier to read in my opinion.
Doug, I guess I don't get the Aux function. Would this turn it on and off the GPIO so we don't have to stop or click off then back to Auto to set another temp setting.
If you don't get it, don't use it It was a request from a few people to be able to have a secondary element control manually.
I get it now, That would be great as I do use an extra Heat Stick plugged in to the wall for faster heating. Thanks for the addition.
Is there a request for step mashing with timer. I now have to stop the Auto to change the temp and restart it.
Doug, I added the Aux function to my config file under my HERMS pid and it doesn't do anything. I can click on it but nothing happens. It stays at Aux Off.
You have to be able to provide me more details, what did you add to the config file? Can you provide debug output (add -d to the end of the command line, please try to trim down to where you click the Aux button).
The aux button maps directly to which ever GPIO you specified it for, so it reads directly what the GPIO Value is to tell you if it's on or off.
So what it does is read the output then invert it (if it's set to true, it goes to false, false -> true)
Can you get the output from the getstatus page? (i.e. brewery:9091:/getstatus
Both before and after you toggle it? I wonder if the JS isn't parsing it.
edit; Looking at it I think it's a JS problem, I've pushed a new version of the client side JS, try pulling it in (you shouldn't need to restart the server) and do a refresh of the control page.
I'm also going to be moving to YAML config files (I'm going to leave the .cfg method active, but you'll get a message telling you to move to YAML)
YAML allows case sensitivity in config files, and it's easier to read in my opinion.
Doug, When do you think you're going to the YAML format.
Sometime this week, but support for config will still be there. YAML will just make things easier.
I'm hoping to get a cfg -> YAML section sorted too.
--config <name>
<device id="kettle">
<device id="Kettle">
Doug, I did the pull and it first said it couldn't find config file. I renamed the rpibrew.cfg to elsinore.cfg then it asked me questions about OWFS. It did convert the file to XML but I now start the server and all my probes are 00.00 no readings.
If I use the old rpibrew.cfg with the --config it works fine. But this is not in XML format
Enter your email address to join: