02-17-2023, 09:13 PM
That's what I experienced when editing the schedule as well, after 24 hours it was fine.
I do plan on keeping groups together, just didn't do it now as I want to see how this goes and didn't want to spend all the time on the UI till I know this will work for most. I may still add a few options on the group schedule that could affect the layout. I know having pages of schedules definitely isn't ideal. When I change I can use the custom name to find groups.
Don't know what to think about the 2nd sensor other than it happened to die. Do you see both sensors in the /sys/bus/w1/devices/ folder and can you read it from there?
If so maybe go in the database, delete it from the DS18B20 table, reboot the controller and see if it finds it again. If your start the app with sudo ./robotank you'll see output of how many sensors are detected. Maybe it shows up there just not in the UI. I haven't touched the temp system for a long time so I don't think I just caused it, maybe an older bug causing it.
I do plan on keeping groups together, just didn't do it now as I want to see how this goes and didn't want to spend all the time on the UI till I know this will work for most. I may still add a few options on the group schedule that could affect the layout. I know having pages of schedules definitely isn't ideal. When I change I can use the custom name to find groups.
Don't know what to think about the 2nd sensor other than it happened to die. Do you see both sensors in the /sys/bus/w1/devices/ folder and can you read it from there?
If so maybe go in the database, delete it from the DS18B20 table, reboot the controller and see if it finds it again. If your start the app with sudo ./robotank you'll see output of how many sensors are detected. Maybe it shows up there just not in the UI. I haven't touched the temp system for a long time so I don't think I just caused it, maybe an older bug causing it.
