nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Joule Feature Request

Matt_540815

i wasn't sure if this has been asked before, but I am a new Joule user and thought a great feature for the Joule app would be to notify the user of when to clean their Joule. This could be a push notification and could be based on the hours of usage or at the very least a calendar.

I think this would be helpful to the users as well as a good way to potentially reduce the number of future warranty or support requests.

Find more posts tagged with

How To Joule

Comments

pd3ski_278514

Like 👍

torridice_498271

I like it. It would probably have to be sensor and algorithm based rather then just use count. Everyone's water is different in terms of hardness so some people have to clean more often than others.

brian_martin2001

While this would be convenient, you'd really need to have some new hardware in the device itself. There is a broad variance in the water hardness of users. I would think you'd need to have some kind of a sensor in the device to analyse the amount of buildup on the parts that matter.

tmacy1656

Speaking of this, would it be possible to have a Clean Cycle as one of the guides? For some reason I have no problem remembering to use equal parts white vinegar and water but I cannot remember what temperature to set it to and I have to look it up every time. Pathetic, I know, but...

Shachar_183567

Or just log an average time to certain temperature (assuming the same container), and if you reach the point that it takes significantly longer to reach that température, then cleaning would be advised. You can just implement it on instances where you select a recipe that you've already cooked.

brian_martin2001

The only thing with this would be there are different levels of hardness. If one is using distilled water, you wouldn't need to clean it more than maybe once or twice a year. If you live in an area like I do, you need to clean it a couple times a month.

Shachar_183567

I meant, you can adjust to the hardness by amount of additional heating time/normal usage power consumption (keeping at temperature). The more limescale, the bigger the gradient between heater temp and what the water "feel" from the heater. We actually calculated it for a statistical mechanics and thermodynamics course

brian_martin2001

@Shachar_183567 looks like the post eating monster got my last post.

So if your not concerned with the actual buildup on the heating element, then you're either going to be recommending cleaning when the unit doesn't need to be cleaned for some folks, and you're not going to be recommending a cleaning when it is needed for others. That sound about right? If you are just comparing various times and temperatures with only a few different water hardness levels, you're going to get grossly inaccurate data for almost every other area, with exception to the few areas that were compared. Depending on how much of a variance there is in the levels of water hardness, if might even be inaccurate to the areas tested in this data collection.

Shachar_183567

@brian_100903 - Let me clarify why what you state won't happen. I AM interested in the buildup, I'm just measuring it indirectly. The amount of extra time needed to heat the water is directly proportional to the amount of scale buildup. The reason it will take more time, is because the effective temperature of the heater would be lower than expected, since you develop a thermal gradient between the heater's surface all the way through the lime scale, so effectively the water "see less heat" (for simplicity). The beauty of large numbers, and doing averages and comparisons correctly, you won't deal with inaccurate data. If I see from gathered data over the last 6 months for a certain area that there's the same degradation in performance, than you can classify that area as of the same water hardness. You can now use the data that a long-time user gathered already in some area, that now the device knows the estimated time between cleaning cycles, and use it as a rough estimate (that would improve with time, and adjusted according to his frequency/duration of operation) for a new user that popped up in that area. This way, deviations like people who use distilled/whatever water would average out (unless suddenly everyone will start to use distilled water all of a sudden). I'd be happy to do the math, but I don't think anyone here should suffer through that

brian_martin2001

That makes a bit more sense, but you'd also need to be able to somehow either enter in the amount of water you're heating up, or have all the data collected be with the same volume of water. You would also need to extrapolate for folks to cover vs. not cover their cooking container, and for those who put their food in the water before the water is heated up. If you want to start crunching numbers, go for it. I do understand averages, bell curves, the whole shebang, but with the amount of variables that could have an affect on the time it takes to heat up the water, and then have that somehow integrated, either into the software, or provide a conversion chart to users, i think that's far more work than anyone other than you, even cares enough to start investing in. If you think you know how to fix it all, run with it.

Shachar_183567

I agree 100%. I'll try and see what I can extract from my Joule the moment they reply about the API. Not in a rush or anything, I just like playing with hardware and data

Since water's heat capacity is rather large, I think a short heating routine in a mug/beaker (something like their joke about Joule-in-a-mug) with a defined minimal amount might yield some fast and reliable data and could be incorporated as a "testing" program, and the time extracted from there. I'll try and see if I get consistent numbers from different mugs/etc, for a small, precise amount of water, so running it should be rather fast/easy with a small enough error.

There are so many parameters to take into consideration, but most of the time you can neglect most of it if they are of a higher order of correction, so for now I guess I'll try and see what sort of deviation is caused by same amount of water with different containers (with roughly the same shape, it's obvious that a very tall/narrow container is very different to a very shallow/wide one in regard to heat losses without some sort of cover). I'd be happy to share results when they'll give access to the API. A more pressing interest of mine is some sort of a logger to check out the temperature variance along the cooking process (something that is missing right now).

I know it might be an overkill, because you can just decide on cleaning it every X period of time, like an automatic action of honing your knives before/after cutting stuff.