ERD50
Give me a museum and I'll fill it. (Picasso) Give me a forum ...
I used Google's Gemini AI to help design my latest Home Automation Project.
Bottom line, AI was extremely helpful for this project, and the more I used it the more I saw ways to use it to fine tune the project. It really became like working with a team of engineers, it would respond with suggestions that would open up new ideas to me, and vice-versa. I am very pleased with its assistance, but was also surprised at some of the stupid mistakes it would make. You need to keep a close watch on it, to get the results you want! I would have run out of patience to make all the changes and refinements as the project developed, and would have just had a far less polished, bare-bones implementation. It was a lot of effort just testing each code release, and figuring out what a 'fix' should look like, and what features should be added/removed. Doing the all that coding would have worn me out, but Gemini spits it out a major revision in a minute or two.
Background (Optional/skip): I've done a few home automation projects with these little Arduino compatible boards. In my previous home, I used one to report on the run time of our private well, as I once had an underground leak that went undetected until it got so bad the pump was running 24/7 and my water pressure dropped off (this was 10 years ago, using MicroPython). My current home has a finished basement, so I have one monitoring the sump pumps, emailing me a status report 3x a day (so I know it's 'alive'), and emailing me on the hour when active, or immediately if certain “out of normal” conditions occur (long/short run times). For these I used the NodeMCU, which has built in WiFi (so I can email the reports over my local WiFi network).
I've also done a few other projects with the ProMicro, which has 9 analog inputs, which I needed for some projects, but no WiFi.
https://www.amazon.com/dp/B08BJNV1J3?th=1 Each of these are ~ $6 each.
// End of “Background info ^^^^^^^^^^^^^^^^^
This Project: I run a dehumidifier (DH) in our basement in the summer months, to keep the humidity below 60% for comfort and to avoid musty/moldy smells in things we store there. The problem I have is if I use the 'Auto' setting on the DH, it cycles ON/OFF every 3 or 4 minutes once it is near its set-point. This is apparently a common issue due to the RH sensor being contained inside the unit, so it senses the drier air nearby. Gemini estimated the short cycles were reducing efficiency by about 40~50% compared to a 2x/day cycle, plus the start-up stresses that could affect the life of the DH. Rewiring for a remote sensor could be tricky (and warranty voiding) since it is all self contained.
My simple solution was to run it on continuous mode, with a mechanical timer that can be set by the hour. I'd set it to run starting at 7AM and 7PM, and adjust the hours after that to keep the humidity in a ~55~58 average. Typically, I'd set the 2x/day “ON” hours for 2 hours in drier periods, to about 6 hours during more humid periods. But this meant checking and manually adjusting every few days.
My Arduino based idea: Use one of the readily available, inexpensive, temperature/humidity sensors, and an Arduino compatible controller (MCU) to keep the humidity below a maximum defined level, with minimums set for the ON/OFF times to avoid short cycling. I'd remote the sensor on a long enough cord so it would sense the room humidity, not the direct dry air from the DH. And send a few email reports each day for humidity and run times for each hour, for the past 24 hours.
Additional Peak Hour Rate feature: Last November, I switched to our electrical supplier's (ComEd) Hourly Rate plan (it's dynamic, rates updated every hour). According to their data, with no changes at all to my usage patterns, I would have saved $150 last year. So I figured why not, and since the DH is something I could shift to the typical lower rate hours (late morning to mid day, and midnight to early AM), I could get some additional savings there. While I could poll ComEd for current rates, and adjust the run times dynamically, there are some complications to that, and it seemed to offer little benefit over just blocking the DH from running based on the typical lower rate hours. So I decided to keep it simple, for now. My DH uses ~ 330 watts in the continuous, 'Turbo' mode.
I'll put the next in a follow up post to keep this from getting too long....
Bottom line, AI was extremely helpful for this project, and the more I used it the more I saw ways to use it to fine tune the project. It really became like working with a team of engineers, it would respond with suggestions that would open up new ideas to me, and vice-versa. I am very pleased with its assistance, but was also surprised at some of the stupid mistakes it would make. You need to keep a close watch on it, to get the results you want! I would have run out of patience to make all the changes and refinements as the project developed, and would have just had a far less polished, bare-bones implementation. It was a lot of effort just testing each code release, and figuring out what a 'fix' should look like, and what features should be added/removed. Doing the all that coding would have worn me out, but Gemini spits it out a major revision in a minute or two.
Background (Optional/skip): I've done a few home automation projects with these little Arduino compatible boards. In my previous home, I used one to report on the run time of our private well, as I once had an underground leak that went undetected until it got so bad the pump was running 24/7 and my water pressure dropped off (this was 10 years ago, using MicroPython). My current home has a finished basement, so I have one monitoring the sump pumps, emailing me a status report 3x a day (so I know it's 'alive'), and emailing me on the hour when active, or immediately if certain “out of normal” conditions occur (long/short run times). For these I used the NodeMCU, which has built in WiFi (so I can email the reports over my local WiFi network).
I've also done a few other projects with the ProMicro, which has 9 analog inputs, which I needed for some projects, but no WiFi.
https://www.amazon.com/dp/B08BJNV1J3?th=1 Each of these are ~ $6 each.
// End of “Background info ^^^^^^^^^^^^^^^^^
This Project: I run a dehumidifier (DH) in our basement in the summer months, to keep the humidity below 60% for comfort and to avoid musty/moldy smells in things we store there. The problem I have is if I use the 'Auto' setting on the DH, it cycles ON/OFF every 3 or 4 minutes once it is near its set-point. This is apparently a common issue due to the RH sensor being contained inside the unit, so it senses the drier air nearby. Gemini estimated the short cycles were reducing efficiency by about 40~50% compared to a 2x/day cycle, plus the start-up stresses that could affect the life of the DH. Rewiring for a remote sensor could be tricky (and warranty voiding) since it is all self contained.
My simple solution was to run it on continuous mode, with a mechanical timer that can be set by the hour. I'd set it to run starting at 7AM and 7PM, and adjust the hours after that to keep the humidity in a ~55~58 average. Typically, I'd set the 2x/day “ON” hours for 2 hours in drier periods, to about 6 hours during more humid periods. But this meant checking and manually adjusting every few days.
My Arduino based idea: Use one of the readily available, inexpensive, temperature/humidity sensors, and an Arduino compatible controller (MCU) to keep the humidity below a maximum defined level, with minimums set for the ON/OFF times to avoid short cycling. I'd remote the sensor on a long enough cord so it would sense the room humidity, not the direct dry air from the DH. And send a few email reports each day for humidity and run times for each hour, for the past 24 hours.
Additional Peak Hour Rate feature: Last November, I switched to our electrical supplier's (ComEd) Hourly Rate plan (it's dynamic, rates updated every hour). According to their data, with no changes at all to my usage patterns, I would have saved $150 last year. So I figured why not, and since the DH is something I could shift to the typical lower rate hours (late morning to mid day, and midnight to early AM), I could get some additional savings there. While I could poll ComEd for current rates, and adjust the run times dynamically, there are some complications to that, and it seemed to offer little benefit over just blocking the DH from running based on the typical lower rate hours. So I decided to keep it simple, for now. My DH uses ~ 330 watts in the continuous, 'Turbo' mode.
I'll put the next in a follow up post to keep this from getting too long....