New plugin for control of Intergas Incomfort Lan2RF gateway

---

@mwittig i will try that tomorrow!

I discovered that the temperature shown in the thermostat in the gui takes quite a long time before it gets to the setted value on the physic thermostat.

@mwittig i removed all mode buttons so that is working for me.
No i’m only facing the problem that when i change the physical thermostat the thermostat in the gui doesn’t change at all.
I thought it was working yesterday before i uploaded the changed software

@derksuh Yesterday I got the tellback from values set by the physical thermostat to work. I just want to give it a bit more testing before I release the changes.

TLDR: I know that updates effectuate a bit on the slow side. Unfortunately I can’t really help it.

To give you an idea, the following setpoints are in play:

• Physical thermostat setpoint
• Actual heater setpoint according to Lan2RF (read only)
• ‘Override’ setpoint set in Lan2RF
• Pimatic setpoint
• App setpoint

Through experimentation I have found they are used in the following manner:

Setting a value on physical thermostat may take up to a few minutes to be visible on actual setpoint in Lan2RF.

Setting a setpoint in the app takes up to a few minutes to be visible in the override setpoint, which then takes up to a few minutes to be visible as the actual setpoint in Lan2RF.

Setting a setpoint in Pimatic immediately sets the override setpoint, which then takes up to a few minutes to be visible as the actual setpoint in Lan2RF.

Besides these (i.m.h.o. pretty long) response times, we are by default polling the values on Lan2RF once every minute (this is configurable in the settings though…).

The approach I’m currently following (in the coming update) is to always immediately show actual heating point as received from Lan2RF, unless we have just set a value ourselves. In that case, we keep our value for 5 minutes (which should at some point become the actual setpoint), until we give up and accept the incoming setpoint again, as it may have been set externally through physical thermostat.

@Moustaggio i’m looking forward for the updated version!

I just managed to publish a (working) new version 0.2.2 to the npm repository.
Fixed are:

• setpoint updates from physical thermostats
• Pimatic v0.9 compatibility
• mandatory eco and comfy temp by removing default
• some minor bugfixes.

When I did npm publish ./ in my plugin dir to publish it to the npm repository it somehow left out the main intergasincomfort.coffee file. Very weird since I used this method to release the initial version of this plugin and also several versions of my other rflink plugin. Performing npm pack did however create a tgz with the file included. A second try did not change anything. I eventually just published that tgz package directly. Does this sound in any way familiar to anyone?

@Moustaggio

I updated to the new version and its working great!

For anyone who installs this plugin you have to keep in mind that it kan take a couple of minutes before the physical thermostat takes over the value you entered in pimatic.