03-04-2025, 06:38 AM
(This post was last modified: 03-04-2025, 06:40 AM by afterburner.)
ACTUALLY, scratch using "START", use Set Demand instead.
In terms of setup.
The GPIO output #1 must be set to "User mode", double checking that the drive mode is set as "Digital" (Hold down when on the mode selection to open the sub menu).
In the timer, enter the edit mode, then set at the very bottom for GPIO: "Output #1"
eg:
Mode: Set Demand
Start time: as desired
Stop time: +1 minute over start time.
Repeat: Yes
Days: Everyday ( depends on how Repeat is set - may be "Next" if repeat is No)
Target: "Usual C" - hold down to reach 0 to set this if a specific value is defined.
GPIO: Output #1
This will simply set the thermostat to the usual setting (ala do nothing), but most importantly does not set the ON status which may well incorrectly change standby to suspended
But using set demand, and "Usual C" as the target means do nothing, but do activate the GPIO signal.
This of course was tested here. That's how I figured out the incorrect "ON" being memorised after reboot, when using START.
In terms of setup.
The GPIO output #1 must be set to "User mode", double checking that the drive mode is set as "Digital" (Hold down when on the mode selection to open the sub menu).
In the timer, enter the edit mode, then set at the very bottom for GPIO: "Output #1"
eg:
Mode: Set Demand
Start time: as desired
Stop time: +1 minute over start time.
Repeat: Yes
Days: Everyday ( depends on how Repeat is set - may be "Next" if repeat is No)
Target: "Usual C" - hold down to reach 0 to set this if a specific value is defined.
GPIO: Output #1
This will simply set the thermostat to the usual setting (ala do nothing), but most importantly does not set the ON status which may well incorrectly change standby to suspended
But using set demand, and "Usual C" as the target means do nothing, but do activate the GPIO signal.
This of course was tested here. That's how I figured out the incorrect "ON" being memorised after reboot, when using START.