For eurotronic spirit users

[samuelAN]

Hello!

I have installed 5 spirit valves I'm my house. Within domoticz, on zwave point of view they work perfectly : setpoints, mode,... are directly received by the valve.

Nevertheless, I have a small regulation issue. When I come from a low setpoint value(ex 18°) to a comfort value (21), the valve does not move directly but takes some time (hours!) To begin to regulate the new set point. And often with an negative offset... seems very difficult to reach the setpoint.

At beginning I thought that it was due to the fact that I was not using the "heat eco" mode (I was in heat mode and working between a low and comfort value), but using it, the same issue is present. Example this morning, after a night in eco mode (18° setpoint), switching to heat mode with 21°set point has not trigged the valve movement. Even after one half hour. Removing batteries and replacing them at this moment will force the valve to take the set point into account and in this case it works directly (but I will not remove/replace batteries for all my 5 valves at each set point variation... )

Any experience to share ?

Ps : I have the same issue for all my valves...

Thanks for your help

[pvklink]

Hi, perhaps you can use my script...
I use only one setpoint and i dont change the heat mode, only the temperature

Code: Select all

--  altijd op thermo mode op  mode heat zetten..
--  setpoint pakken dat bij heat hoort als huidige adhoc stand 
--  andere setpoints verwijderen, springen soms op 0 en heb je niets aan
--  dz.devices('Slaapkamer_thermostaat_mode').updateMode('Manufacturer Specific')
--  dz.devices('Slaapkamer_thermostaat_mode').updateMode('Heat')
--  dz.devices('Slaapkamer_thermostaat_mode').updateMode('Heat Eco')
--  dz.devices('slaapkamer_heat_temp').updateSetPoint(21)
--  dz.devices('slaapkamer_heat_temp').setPoint     uitlezen van setpoint
--  de hook is los van dz_verwarming gemaakt zodat de schakelaar zelf ook aangepast wordt bij een webhook call voor dashticz

    local hook1     = 'Hook_DZ_dag'
    local hook2     = 'Hook_DZ_nacht'
    local OffTimer1 = 'at 22:05 on mon,tue,wed,thu,sun'
    local OffTimer2 = 'at 22:50 on fri,sat'

return {
    	on =    {   
    	            devices = {'Default_heating', 'pc-niels-ga*'},
	                httpResponses = {hook1,hook2},
                    timer = {OffTimer1, OffTimer2}   
	            },

    logging =   { level   = domoticz.LOG_ERROR ,                  -- Uncomment to override the dzVents global logging setting
                  marker  = "verwarming"},
	
    execute = function(dz, item, info)
    local dagnorm   = 20
    local nachtnorm = 16
    local messageTable = {}
    
    local countpc = dz.devices().reduce(function(acc, device)
        if  dz.helpers.matchesWildCardedString(dz,device.name, 'pc-niels*') then
            if device.state == 'On' then 
                acc = acc + 1 
            end
       end
       return acc -- always return the accumulator
    end, 0) -- 0 is the initial value for the accumulator

    if item.isDevice then 
        if (item.name == 'Default_heating') then
                if (item.state == 'dag') then
                    dz.devices('Niels_slaapkamer_thermostaat_instelling').updateSetPoint(dagnorm)              -- via default heating de echte opdracht
                else    
                    dz.devices('Niels_slaapkamer_thermostaat_instelling').updateSetPoint(nachtnorm)
                end

        else    -- er is een pc van niels aangezet of uitgezet 
            if dz.time.matchesRule('at 06:00-22:05') then
                if countpc >0 and dz.devices('Default_heating').state == 'nacht' then   -- er is een pc van niels aan en heating staat op nacht
                    dz.helpers.globalMessage2(dz,item,info,messageTable,'add', ' VERWARMING: radiator zolder wordt op ' .. item.state .. 'stand(' .. tostring(dagnorm) .. ') gezet door: ' .. item.name)
    	            dz.devices('Default_heating').switchSelector('dag')                                        -- via pc-niels devices via switch selector aansturen, die komt dan nogmaals door dit script via default heating
                end
            else    -- het is buiten 06:00 en 22.05
                if dz.devices('Default_heating').state == 'dag' then
    	            dz.devices('Default_heating').switchSelector('nacht')                                        -- via pc-niels devices via switch selector aansturen, die komt dan nogmaals door dit script via default heating
                    dz.devices('Niels_slaapkamer_thermostaat_instelling').updateSetPoint(nachtnorm)
                end                    
            end
        end

    elseif item.isTimer then       
        dz.helpers.globalMessage2(dz,item,info,messageTable,'add', ' VERWARMING: Verwarming wordt op nachtstand gezet door: ' .. item.trigger,0)                     -- uitgezet krijgt melding via switchselector/devices if then else
	    dz.devices('Default_heating').switchSelector(20)

    elseif item.isHTTPResponse then
        local hookwaarde = item.trigger
        if      hookwaarde == hook1 then dz.devices('Default_heating').switchSelector(10)
        elseif  hookwaarde == hook2 then dz.devices('Default_heating').switchSelector(20)
        end
        dz.helpers.globalMessage2(dz,item,info,messageTable,'add', ' VERWARMING: Verwarming wordt op ' .. hookwaarde .. ' stand gezet door httpResponses..')
    end
    dz.helpers.globalMessage2(dz,item,info,messageTable,'chg') -- dump

end
}

[pvklink]

here is a short dump of my device

heat.png (14.73 KiB) Viewed 1369 times

[samuelAN]

Hello,

Thanks for your answer and your useful script,

In fact, using the eco mode or reducing the setpoint in heat mode produce the same problem : when a setpoint of 21 is applied after a low value setpoint, the valve does not move sufficiently fast after the change, takes some hours to begin to move..

[samuelAN]

Example : switching from 19 to 21. Valve opening percentage stay to off even after 30 min. Begin to open slightly 2....3...4% after 1 hour). Setpoint reached after maybe 2 hours.

I precise that hot water flow is made available all the time. Mechanical valve stud is OK.

[samuelAN]

My office setpoint has been set to 21.5 since 14PM. It is now 19PM, and the temperature has not increased, there is still 20°. Valve opening still at OFF. Display on the valve displays well the setpoint (21.5)

[micha_pr]

Additional idea:

What happen if you in the morning set the Setpoint for two minutes to 24 degree - and then to 21 degree?
Is it the same delay?

I do not have any problems here with my 5 Spirit since a long time, but all of them have Version 0.15.
And I'm working only in Heat mode.

Michael

[samuelAN]

Thank you Micha.

I will give it a try tomorrow.

I am thinking about an integrator saturation inside regulation loops.. if no anti windup is implemented , it takes a huge time to recover the integrator result...

If this is confirmed other people should have the same behavior...

[samuelAN]

Thank you Micha.

I will give it a try tomorrow.

I am thinking about an integrator saturation inside regulation loops.. if no anti windup is implemented , it takes a huge time to recover the integrator result...

If this is confirmed other people should have the same behavior...

[samuelAN]

Small test in my office : put the setpoint to 25 --> valve react immediately at 60%opening. Set back to 21.5 --> valve closed. (Ambiant temp report = 20.7)

[micha_pr]

You can set the Parameter
8. Measured Temperature Offset:
I think to -1.5 or -2 (not sure negative is right or not )

Michael