Domoticz

i am thinking about trading my isense for a honnywell

From the OTGW website:

Work-around many of the iSense quirks/bugs/misfeatures:

A remote override setpoint cannot be changed
The gateway will first cancel any existing remote setpoint before setting the new one.

Manual change of a remote override setpoint restarts the schedule
When a manual change is detected, the gateway will continue to send the override setpoint so the iSense doesn't resume the schedule.

Program change does not override a temporary remote setpoint
The iSense uses the previously received remote override function (MsgID 100) bitmap at the time the remote override setpoint (MsgID 9) is set. Just like with the remote override setpoint, it doesn't update the remote override function when it receives a new bitmap. The gateway uses the same trick as with the remote override setpoint: After sending the new remote override function bitmap, it cancels the remote override setpoint and sets it again.
Note that the iSense only requests the remote override function about once every 12 minutes. So it may take that long before a remote override is fully instated.

Note: These work-arounds will only be applied if a Remeha iSense thermostat has been detected. So owners of other thermostats will not suffer the negative side-effects (like temporarily canceling the remote override setpoint) of these work-arounds.

Auto-detect the Remeha thermostat type and apply the relevant work-arounds. There is no more need to use the Remeha-specific TR or TQ commands. In fact, those commands are not accepted anymore.
Note: Detection of the thermostat type (especially with a Celcia20) takes some time, so sending a setpoint command soon after a power failure or reconnecting the thermostat may not work correctly.

You can use the 'PR=R' command to determine which thermostat the gateway thinks is connected. It will report:
Default, not a Remeha thermostat
Remeha iSense
Remeha Celcia20
Other Remeha thermostat

gizmocuz wrote:?? bump.... the dunit is still set.... nothing changed....

gizmocuz wrote:Yes, but how/where to enter the setpoint values.

I do like the way the iSense is doing it...

Create a schedule program, for example 'Normal', or 'Holiday',
Edit the schedule
Monday
07:00 Temp=20
10:00 Temp=15
17:30 Temp=20
22:00 Temp=15

Tuesday
....

Then you need to activate one of the schedule programs, for example when you go on holiday you activate the 'Holiday' program

That nice scheduler you have could work nicely for light/switches