Yes this was confirmed by Dave H on the FB group. They have no intention of fixing it because 2 series is EOL. Which really pisses me off as there are so many 2 series D3 jobs out in the wild running perfectly for years. A simple program change shouldnt break a basic module that weve all been using for years. One of the things I like about Crestron is unlike some other brands (ahem Savant...) their older modules and hardware arent usually broken by software updates. Until this.?
So from that FB post heres what you need to make the scheduler work again:
Only CresDB rollback was required to address the issue. The working versions noted by TS Agent were: D3 3.05.01 / **CresDB 212.00.002** / DevDB 200.230.001?
