04-06-2023, 12:39 AM
I've got all kinds of plans. :)
I'm actually going to drop the group schedules and redesign it to work similar to cron jobs. Even with the ability to delete groups it's not so nice having possible hundreds of schedules, it also takes lots of memory in the backend which isn't necessary.
Just so everyone knows I'm still working on this, the last couple weeks I've been trying to improve things I've had on the list, one thing I'm really happy about, as I attempted this a few times, I have the dygraphs reading from the database now so no more CSV files. The nice thing is from day one I had the temp and pH saving to database along with the CSV so after update you'll still have all the data. This is huge because now I can allow custom charts, a person can put as many parameters on one chart and toggle them on/off. As someone suggested to me, I'm going to add ability for users to manually record other parameters so they can use data with the charts. I added a bar chart for the dosing pumps, when a dosing pump is added the chart is created. it shows how many seconds the pump ran for and how many milliliters. Seconds shown is actual time when pump turned on and off so it'll be obvious if something isn't working properly.
Top chart is 7 day view and bottom is 3 day view. The charts do have a few anomalies as the backend wasn't always running.
![[Image: charts4.PNG]](https://www.robo-tank.ca/pictures/screenshots_app/Updated_Version/charts4.PNG)
Unfortunately I did waste a good week+ trying to get the websocket working bidirectionally. Currently the frontend can only initiate the messages but I want/need the backend to send messages to frontend but I'm unable to get a listener working.
Anyways back to schedules, my plan is first I'm going to get a heater and ATO system in place then I'm going to tackle the schedules and then add some extra features to the custom rules.
I'm actually going to drop the group schedules and redesign it to work similar to cron jobs. Even with the ability to delete groups it's not so nice having possible hundreds of schedules, it also takes lots of memory in the backend which isn't necessary.
Just so everyone knows I'm still working on this, the last couple weeks I've been trying to improve things I've had on the list, one thing I'm really happy about, as I attempted this a few times, I have the dygraphs reading from the database now so no more CSV files. The nice thing is from day one I had the temp and pH saving to database along with the CSV so after update you'll still have all the data. This is huge because now I can allow custom charts, a person can put as many parameters on one chart and toggle them on/off. As someone suggested to me, I'm going to add ability for users to manually record other parameters so they can use data with the charts. I added a bar chart for the dosing pumps, when a dosing pump is added the chart is created. it shows how many seconds the pump ran for and how many milliliters. Seconds shown is actual time when pump turned on and off so it'll be obvious if something isn't working properly.
Top chart is 7 day view and bottom is 3 day view. The charts do have a few anomalies as the backend wasn't always running.
Unfortunately I did waste a good week+ trying to get the websocket working bidirectionally. Currently the frontend can only initiate the messages but I want/need the backend to send messages to frontend but I'm unable to get a listener working.
Anyways back to schedules, my plan is first I'm going to get a heater and ATO system in place then I'm going to tackle the schedules and then add some extra features to the custom rules.
