12-28-2023, 12:07 AM
Hi,
I do not seem to be able to edit AC outlet schedules. Surprisingly, I could not find anything relevant on the forum; looks like I'm the only one experiencing this issue. I run a fresh installation of RoboTank 6.6 on Raspbian Bullseye, following installation instructions posted in the documentation and a couple of forum posts.
I added simple on/off AC outlet schedules, but whenever I try to modify on/off time on the existing schedule and click the Save button, robotank process crashes with error.
Dec 28 00:14:10 robotank startup[1613]: incomingCommand = 71, 7, 1, CO2 ON, 39661, 1, 1, 1, 1, 1, 1, 1, 1, 1, 0, 0, null,
Dec 28 00:14:10 robotank startup[1613]: terminate called after throwing an instance of 'std::invalid_argument'
Dec 28 00:14:10 robotank startup[1613]: what(): stof
Dec 28 00:14:11 robotank startup[1611]: Aborted
Systemd immediately restarts the process, but changes are not saved. Fortunately, I can still delete the schedule and recreate it with a new time, but still quite annoying. Any ideas what the issue could be? Any troubleshooting suggestions?
Thanks
I do not seem to be able to edit AC outlet schedules. Surprisingly, I could not find anything relevant on the forum; looks like I'm the only one experiencing this issue. I run a fresh installation of RoboTank 6.6 on Raspbian Bullseye, following installation instructions posted in the documentation and a couple of forum posts.
I added simple on/off AC outlet schedules, but whenever I try to modify on/off time on the existing schedule and click the Save button, robotank process crashes with error.
Dec 28 00:14:10 robotank startup[1613]: incomingCommand = 71, 7, 1, CO2 ON, 39661, 1, 1, 1, 1, 1, 1, 1, 1, 1, 0, 0, null,
Dec 28 00:14:10 robotank startup[1613]: terminate called after throwing an instance of 'std::invalid_argument'
Dec 28 00:14:10 robotank startup[1613]: what(): stof
Dec 28 00:14:11 robotank startup[1611]: Aborted
Systemd immediately restarts the process, but changes are not saved. Fortunately, I can still delete the schedule and recreate it with a new time, but still quite annoying. Any ideas what the issue could be? Any troubleshooting suggestions?
Thanks