I don't understand if this is a bug or I am doing somenthing wrong, but after upgrading from 6.4.17 to 7.0.2 (and the error is still present in 7.0.3) I am seeing an error if I use a MACRO string in the value field of an item's custom interval. MACRO string was ok in version 6, I've been using it for at least a couple of years.
Example
I have a MACRO defined like this:
{$INVERTER_CHECK} = 1-7,05:50-21:00
The MACRO is used in an item's custom interval value:
Type = Flexible
Interval = 60
Period = {$INVERTER_CHECK}
This configuration was working fine in version 6.
After upgrading to version 7 the MACRO string value is not accepted anymore. The item is not run and this error appears:
Invalid scheduling interval "{$INVERTER_CHECK}"
The item runs without errors if the MACRO string is substituted with the actual value:
Type = Flexible
Interval = 60
Period = 1-7,05:50-21:00
Example
I have a MACRO defined like this:
{$INVERTER_CHECK} = 1-7,05:50-21:00
The MACRO is used in an item's custom interval value:
Type = Flexible
Interval = 60
Period = {$INVERTER_CHECK}
This configuration was working fine in version 6.
After upgrading to version 7 the MACRO string value is not accepted anymore. The item is not run and this error appears:
Invalid scheduling interval "{$INVERTER_CHECK}"
The item runs without errors if the MACRO string is substituted with the actual value:
Type = Flexible
Interval = 60
Period = 1-7,05:50-21:00
Attached Files
Comment