Page 1 of 1
Evohome
Posted: Monday 27 May 2019 15:48
by PaulOckenden
It's great that dzVents has built-in awareness of Evohome. I can use it for reading and manipulating setpoints.
I'm struggling, though, to set the overall controller mode.
I can read it using domoticz.devices('Evo Color').state but I haven't been successful in changing the mode.
Anyone know how?
BTW, I'm using an HGI80 to talk to Evohome, rather than cloud API.
Thanks,
Paul.
Re: Evohome
Posted: Monday 27 May 2019 19:19
by PaulOckenden
BTW, I realise I can do this by making a domoticz.openURL request to the Domoticz API:
/json.htm?type=command¶m=switchmodal&idx=1&status=AutoWithEco&action=1&ooc=0
It would just be nicer to do it 'properly'.
Re: Evohome
Posted: Monday 27 May 2019 19:27
by waaren
PaulOckenden wrote: ↑Monday 27 May 2019 15:48
I can read it using domoticz.devices('Evo Color').state but I haven't been successful in changing the mode.
Anyone know how?
Just curious, doesn't the standard dzVents handling as described
here specifically updateSetPoint(setPoint, mode, until) do the job at hand ?
If not can you please generate a dzVents device dump for this ?
Code: Select all
domoticz.devices('Evo Color').dump()
Re: Evohome
Posted: Monday 27 May 2019 21:44
by PaulOckenden
Thanks for replying.
No, updateSetPoint() doesn't allow you to set the system-level mode (the mode in that function is a quite different zone level mode).
This is the result of dump():
ruleIsAtCivilDayTime()
rawTime: 20:35:01
raw: 2019-05-27 20:35:01
month: 5
ruleIsAtNight()
day: 27
ruleIsAtSunset()
milliSeconds: 0
ruleIsBeforeCivilTwilightEnd()
seconds: 1
minutes: 35
dDate: 1558985701
ruleIsBeforeSunset()
yday: 147
ruleIsAtCivilNight()
ruleIsAfterSunrise()
year: 2019
ruleIsBeforeSunrise()
ruleIsAtSunrise()
sec: 1
ruleIsAfterCivilTwilightEnd()
ruleIsBeforeCivilTwilightStart()
ruleIsAfterSunset()
ruleIsAfterCivilTwilightStart()
millisecondsAgo: 3904
ruleIsAtCivilTwilightStart()
ruleIsOnDay()
ruleMatchesTime()
ruleIsInWeek()
ruleMatchesTimeRange()
isToday: true
compare()
matchesRule()
ruleIsAtDayTime()
wday: 2
hoursAgo: 0
getISO()
isUTC: false
minutesAgo: 0
ruleIsOnDate()
switchSelector()
dimTo()
deviceType: Heating
disarm()
setRGB()
switchOn()
updateSoundLevel()
deviceSubType: Evohome
updateHumidity()
rawData:
_state: AutoWithEco
baseType: device
getColor()
updateLux()
isVariable: false
setNightMode()
hardwareTypeValue: 39
startPlaylist()
updateRain()
setValues()
updateVisibility()
updateAirQuality()
armAway()
volumeDown()
open()
updateWeight()
setDiscoMode()
hardwareID: 2
setColorBrightness()
setColor()
setHex()
decreaseBrightness()
setWhiteMode()
onkyoEISCPCommand()
updateVoltage()
deviceId: 52c74
updatePercentage()
setDescription()
updateSetPoint()
stop()
updateDistance()
toggleSwitch()
updateTempHumBaro()
volumeUp()
playFavorites()
hardwareName: Evo
pause()
setState()
isTimer: false
bState: false
updateRadiation()
armHome()
cancelQueuedCommands()
updateSoilMoisture()
state: AutoWithEco
timedOut: false
isDevice: true
hardwareId: 2
It appears that the value I need is in both state and _state.
But my experiments so far show that setState() doesn't update this system-wide mode.
Thanks again for your help.
I've been coding for many decades but I'm new to dzVents (which is great, by the way!)
Paul.
Re: Evohome
Posted: Monday 27 May 2019 22:21
by waaren
PaulOckenden wrote: ↑Monday 27 May 2019 21:44
This is the result of dump():
It seems that there is some data missing from the dump. Can you please try and grab all (only possible if you also log to an OS file and not only to internal domoticz memory) .
Are you able to access the domoticz database directly (using sqlite3 or another DB browser) and do a
Code: Select all
sqlite> .he on
sqlite> select * from devicestatus where name = 'Evo Color';
It would also help if your state you Domoticz / dzVents version.
Re: Evohome
Posted: Monday 27 May 2019 22:42
by PaulOckenden
I grabbed the dump() data from the log (but I stripped the dates/times out, to make it smaller to post). The wiki says that dump() outputs to the domoticz log. How do I make it do anything else? What's missing? (Sorry if I'm being a bit of a noob).
The database select reports:
ID|HardwareID|DeviceID|Unit|Name|Used|Type|SubType|SwitchType|Favorite|SignalLevel|BatteryLevel|nValue|sValue|LastUpdate|Order|AddjValue|AddjMulti|AddjValue2|AddjMulti2|StrParam1|StrParam2|LastLevel|Protected|CustomImage|Description|Options|Color
1|2|52c74|0|Evo Color|1|69|0|0|0|255|255|1||2019-05-27 20:35:01|1|0.0|1.0|0.0|1.0|||0|0|0|||
Domoticz V4.10717, dzVents dzVents Version: 2.4.19 (I'm trying to run known stable versions)
Thanks for your help - I really appreciate it!
Re: Evohome
Posted: Monday 27 May 2019 22:50
by PaulOckenden
Follow-up:
domoticz.devices('Evo Color').state returns 'AutoWithEco', which is correct.
But if I do something like domoticz.devices('Evo Color').setState('Auto')
('Auto' being distinct from 'AutoWithEco' on Evohome)
The Controller stays in Eco mode, and domoticz.devices('Evo Color').state still returns 'AutoWithEco'.
Literally, three lines of code:
domoticz.log(domoticz.devices('Evo Color').state)
domoticz.devices('Evo Color').setState('Auto')
domoticz.log(domoticz.devices('Evo Color').state)
returns:
2019-05-27 21:48:53.065 Status: dzVents: Info: AutoWithEco
2019-05-27 21:48:53.065 Status: dzVents: Info: AutoWithEco
So the setState() isn't working for this device, despite te data sitting within state.
Re: Evohome
Posted: Monday 27 May 2019 23:58
by waaren
PaulOckenden wrote: ↑Monday 27 May 2019 22:42
I grabbed the dump() data from the log (but I stripped the dates/times out, to make it smaller to post). The wiki says that dump() outputs to the domoticz log. How do I make it do anything else? What's missing? (Sorry if I'm being a bit of a noob).
dump() is indeed sending to the log but the log can be only in domoticz internal internal or also to an OS file. This is set in the /etc/init.d/domoticz.sh
domoticz.log(domoticz.devices('Evo Color').state)
domoticz.devices('Evo Color').setState('Auto')
domoticz.log(domoticz.devices('Evo Color').state)
returns:
2019-05-27 21:48:53.065 Status: dzVents: Info: AutoWithEco
2019-05-27 21:48:53.065 Status: dzVents: Info: AutoWithEco
dzVents does not send these commands directly in the script. They are passed to domoticz in a commandArray and executed when the script finish. So you cannot see the result from commands entered in the script from within the same script (exceptions are none domoticz commands like os.execute, io.popen, math.sin, etc.). Manipulations to domoticz.data.xxxx are also direct.
Re: Evohome
Posted: Tuesday 28 May 2019 9:15
by PaulOckenden
I didn't realise that the script actions don't happen immediately, although this isn't the issue here - if I run the script a second time the status still hasn't changed.
Here's the output of dump() when the log goes to a file:
Code: Select all
2019-05-28 08:08:16.890 Status: dzVents: > pause()
2019-05-28 08:08:16.890 Status: dzVents: > _data:
2019-05-28 08:08:16.890 Status: dzVents: > name: Evo Color
2019-05-28 08:08:16.890 Status: dzVents: > rawData:
2019-05-28 08:08:16.890 Status: dzVents: > deviceType: Heating
2019-05-28 08:08:16.890 Status: dzVents: > switchTypeValue: 0
2019-05-28 08:08:16.890 Status: dzVents: > baseType: device
2019-05-28 08:08:16.890 Status: dzVents: > subType: Evohome
2019-05-28 08:08:16.890 Status: dzVents: > batteryLevel: 255
2019-05-28 08:08:16.890 Status: dzVents: > data:
2019-05-28 08:08:16.890 Status: dzVents: > hardwareType: Evohome USB (for HGI/S80)
2019-05-28 08:08:16.891 Status: dzVents: > unit: 0
2019-05-28 08:08:16.891 Status: dzVents: > _state: AutoWithEco
2019-05-28 08:08:16.891 Status: dzVents: > hardwareName: Evo
2019-05-28 08:08:16.891 Status: dzVents: > hardwareTypeValue: 39
2019-05-28 08:08:16.891 Status: dzVents: > hardwareID: 2
2019-05-28 08:08:16.891 Status: dzVents: > _nValue: 1
2019-05-28 08:08:16.891 Status: dzVents: > icon: override_mini
2019-05-28 08:08:16.891 Status: dzVents: > protected: false
2019-05-28 08:08:16.891 Status: dzVents: > maxDimLevel: 0
2019-05-28 08:08:16.891 Status: dzVents: > lastLevel: 0
2019-05-28 08:08:16.891 Status: dzVents: > timedOut: true
2019-05-28 08:08:16.891 Status: dzVents: > signalLevel: 255
2019-05-28 08:08:16.891 Status: dzVents: > description:
2019-05-28 08:08:16.891 Status: dzVents: > switchType: On/Off
2019-05-28 08:08:16.891 Status: dzVents: > lastUpdate: 2019-05-27 20:35:01
2019-05-28 08:08:16.891 Status: dzVents: > id: 1
2019-05-28 08:08:16.891 Status: dzVents: > deviceID: 52c74
2019-05-28 08:08:16.891 Status: dzVents: > changed: false
2019-05-28 08:08:16.891 Status: dzVents: > kodiPlayPlaylist()
2019-05-28 08:08:16.891 Status: dzVents: > state: AutoWithEco
2019-05-28 08:08:16.891 Status: dzVents: > updateBarometer()
2019-05-28 08:08:16.891 Status: dzVents: > nValue: 1
2019-05-28 08:08:16.891 Status: dzVents: > switchSelector()
2019-05-28 08:08:16.891 Status: dzVents: > icon: override_mini
2019-05-28 08:08:16.891 Status: dzVents: > close()
2019-05-28 08:08:16.891 Status: dzVents: > startPlaylist()
2019-05-28 08:08:16.891 Status: dzVents: > updateCounter()
2019-05-28 08:08:16.892 Status: dzVents: > setColorBrightness()
2019-05-28 08:08:16.892 Status: dzVents: > baseType: device
2019-05-28 08:08:16.892 Status: dzVents: > volumeUp()
2019-05-28 08:08:16.892 Status: dzVents: > kodiSetVolume()
2019-05-28 08:08:16.892 Status: dzVents: > switchOff()
2019-05-28 08:08:16.892 Status: dzVents: > setWhiteMode()
2019-05-28 08:08:16.892 Status: dzVents: > untilDate: n/a
2019-05-28 08:08:16.892 Status: dzVents: > updateRadiation()
2019-05-28 08:08:16.892 Status: dzVents: > maxDimLevel: 0
2019-05-28 08:08:16.892 Status: dzVents: > armAway()
2019-05-28 08:08:16.892 Status: dzVents: > update()
2019-05-28 08:08:16.892 Status: dzVents: > updateTemperature()
2019-05-28 08:08:16.892 Status: dzVents: > updateUV()
2019-05-28 08:08:16.892 Status: dzVents: > kodiSwitchOff()
2019-05-28 08:08:16.892 Status: dzVents: > mode: nil
2019-05-28 08:08:16.892 Status: dzVents: > updateWetness()
2019-05-28 08:08:16.892 Status: dzVents: > isGroup: false
2019-05-28 08:08:16.892 Status: dzVents: > updateP1()
2019-05-28 08:08:16.892 Status: dzVents: > isHTTPResponse: false
2019-05-28 08:08:16.892 Status: dzVents: > setNightMode()
2019-05-28 08:08:16.892 Status: dzVents: > kodiPlay()
2019-05-28 08:08:16.892 Status: dzVents: > kodiStop()
2019-05-28 08:08:16.892 Status: dzVents: > kodiPause()
2019-05-28 08:08:16.892 Status: dzVents: > kodiExecuteAddOn()
2019-05-28 08:08:16.892 Status: dzVents: > kodiPlayFavorites()
2019-05-28 08:08:16.892 Status: dzVents: > updateMode()
2019-05-28 08:08:16.892 Status: dzVents: > protected: false
2019-05-28 08:08:16.892 Status: dzVents: > setIcon()
2019-05-28 08:08:16.892 Status: dzVents: > updateText()
2019-05-28 08:08:16.892 Status: dzVents: > updateWind()
2019-05-28 08:08:16.893 Status: dzVents: > stop()
2019-05-28 08:08:16.893 Status: dzVents: > play()
2019-05-28 08:08:16.893 Status: dzVents: > playFavorites()
2019-05-28 08:08:16.893 Status: dzVents: > dimTo()
2019-05-28 08:08:16.893 Status: dzVents: > dump()
2019-05-28 08:08:16.893 Status: dzVents: > deviceId: 52c74
2019-05-28 08:08:16.893 Status: dzVents: > timedOut: true
2019-05-28 08:08:16.893 Status: dzVents: > updateTempHum()
2019-05-28 08:08:16.893 Status: dzVents: > increaseBrightness()
2019-05-28 08:08:16.893 Status: dzVents: > bState: false
2019-05-28 08:08:16.893 Status: dzVents: > updateRain()
2019-05-28 08:08:16.893 Status: dzVents: > changed: false
2019-05-28 08:08:16.893 Status: dzVents: > getColor()
2019-05-28 08:08:16.893 Status: dzVents: > updateWaterflow()
2019-05-28 08:08:16.893 Status: dzVents: > hardwareType: Evohome USB (for HGI/S80)
2019-05-28 08:08:16.893 Status: dzVents: > disarm()
2019-05-28 08:08:16.893 Status: dzVents: > setColor()
2019-05-28 08:08:16.893 Status: dzVents: > deviceSubType: Evohome
2019-05-28 08:08:16.893 Status: dzVents: > updateDistance()
2019-05-28 08:08:16.893 Status: dzVents: > updateVoltage()
2019-05-28 08:08:16.893 Status: dzVents: > updateVisibility()
2019-05-28 08:08:16.893 Status: dzVents: > updateTempHumBaro()
2019-05-28 08:08:16.893 Status: dzVents: > decreaseBrightness()
2019-05-28 08:08:16.893 Status: dzVents: > updateTempBaro()
2019-05-28 08:08:16.893 Status: dzVents: > open()
2019-05-28 08:08:16.893 Status: dzVents: > rawData:
2019-05-28 08:08:16.893 Status: dzVents: > _nValue: 1
2019-05-28 08:08:16.894 Status: dzVents: > toggleSwitch()
2019-05-28 08:08:16.894 Status: dzVents: > switchOn()
2019-05-28 08:08:16.894 Status: dzVents: > updateSoundLevel()
2019-05-28 08:08:16.894 Status: dzVents: > updateSoilMoisture()
2019-05-28 08:08:16.894 Status: dzVents: > unit: 0
2019-05-28 08:08:16.894 Status: dzVents: > armHome()
2019-05-28 08:08:16.894 Status: dzVents: > updateWeight()
2019-05-28 08:08:16.894 Status: dzVents: > isVariable: false
2019-05-28 08:08:16.894 Status: dzVents: > setRGB()
2019-05-28 08:08:16.894 Status: dzVents: > setHue()
2019-05-28 08:08:16.894 Status: dzVents: > switchType: On/Off
2019-05-28 08:08:16.894 Status: dzVents: > isDevice: true
2019-05-28 08:08:16.894 Status: dzVents: > updateElectricity()
2019-05-28 08:08:16.894 Status: dzVents: > setHex()
2019-05-28 08:08:16.894 Status: dzVents: > setDiscoMode()
2019-05-28 08:08:16.894 Status: dzVents: > lastUpdate:
2019-05-28 08:08:16.894 Status: dzVents: > dDate: 1558985701
2019-05-28 08:08:16.894 Status: dzVents: > isToday: false
2019-05-28 08:08:16.894 Status: dzVents: > ruleIsAtSunset()
2019-05-28 08:08:16.894 Status: dzVents: > isUTC: false
2019-05-28 08:08:16.894 Status: dzVents: > ruleIsAtNight()
2019-05-28 08:08:16.894 Status: dzVents: > sec: 1
2019-05-28 08:08:16.894 Status: dzVents: > minutes: 35
2019-05-28 08:08:16.894 Status: dzVents: > utils:
2019-05-28 08:08:16.894 Status: dzVents: > LOG_MODULE_EXEC_INFO: 2
2019-05-28 08:08:16.894 Status: dzVents: > stringSplit()
2019-05-28 08:08:16.894 Status: dzVents: > urlDecode()
2019-05-28 08:08:16.894 Status: dzVents: > print()
2019-05-28 08:08:16.894 Status: dzVents: > LOG_FORCE: 0.5
2019-05-28 08:08:16.895 Status: dzVents: > LOG_ERROR: 1
2019-05-28 08:08:16.895 Status: dzVents: > urlEncode()
2019-05-28 08:08:16.895 Status: dzVents: > DZVERSION: 2.4.19
2019-05-28 08:08:16.895 Status: dzVents: > toJSON()
2019-05-28 08:08:16.895 Status: dzVents: > osExecute()
2019-05-28 08:08:16.895 Status: dzVents: > LOG_INFO: 3
2019-05-28 08:08:16.895 Status: dzVents: > dumpTable()
2019-05-28 08:08:16.895 Status: dzVents: > rgbToHSB()
2019-05-28 08:08:16.895 Status: dzVents: > hsbToRGB()
2019-05-28 08:08:16.895 Status: dzVents: > LOG_DEBUG: 4
2019-05-28 08:08:16.895 Status: dzVents: > fileExists()
2019-05-28 08:08:16.895 Status: dzVents: > log()
2019-05-28 08:08:16.895 Status: dzVents: > fromJSON()
2019-05-28 08:08:16.895 Status: dzVents: > isdst: true
2019-05-28 08:08:16.895 Status: dzVents: > compare()
2019-05-28 08:08:16.895 Status: dzVents: > year: 2019
2019-05-28 08:08:16.895 Status: dzVents: > millisecondsAgo: 41595750
2019-05-28 08:08:16.895 Status: dzVents: > milliSeconds: 0
2019-05-28 08:08:16.895 Status: dzVents: > current:
2019-05-28 08:08:16.895 Status: dzVents: > year: 2019
2019-05-28 08:08:16.895 Status: dzVents: > min: 8
2019-05-28 08:08:16.895 Status: dzVents: > isdst: true
2019-05-28 08:08:16.895 Status: dzVents: > sec: 16
2019-05-28 08:08:16.895 Status: dzVents: > yday: 148
2019-05-28 08:08:16.895 Status: dzVents: > month: 5
2019-05-28 08:08:16.895 Status: dzVents: > day: 28
2019-05-28 08:08:16.895 Status: dzVents: > wday: 3
2019-05-28 08:08:16.895 Status: dzVents: > hour: 8
2019-05-28 08:08:16.896 Status: dzVents: > ruleIsAfterSunrise()
2019-05-28 08:08:16.896 Status: dzVents: > ruleMatchesBetweenRange()
2019-05-28 08:08:16.896 Status: dzVents: > ruleMatchesTimeRange()
2019-05-28 08:08:16.896 Status: dzVents: > ruleIsAtCivilTwilightEnd()
2019-05-28 08:08:16.896 Status: dzVents: > secondsAgo: 41595
2019-05-28 08:08:16.896 Status: dzVents: > ruleMatchesTime()
2019-05-28 08:08:16.896 Status: dzVents: > ruleMatchesHourSpecification()
2019-05-28 08:08:16.896 Status: dzVents: > ruleMatchesMinuteSpecification()
2019-05-28 08:08:16.896 Status: dzVents: > day: 27
2019-05-28 08:08:16.896 Status: dzVents: > ruleIsAtDayTime()
2019-05-28 08:08:16.896 Status: dzVents: > ruleIsAtCivilDayTime()
2019-05-28 08:08:16.896 Status: dzVents: > ruleIsBeforeSunrise()
2019-05-28 08:08:16.896 Status: dzVents: > hour: 20
2019-05-28 08:08:16.896 Status: dzVents: > ruleIsAfterSunset()
2019-05-28 08:08:16.896 Status: dzVents: > minutesAgo: 693
2019-05-28 08:08:16.896 Status: dzVents: > ruleIsAtCivilNight()
2019-05-28 08:08:16.896 Status: dzVents: > ruleIsAtSunrise()
2019-05-28 08:08:16.896 Status: dzVents: > week: 22
2019-05-28 08:08:16.896 Status: dzVents: > getISO()
2019-05-28 08:08:16.896 Status: dzVents: > ruleIsAfterCivilTwilightEnd()
2019-05-28 08:08:16.896 Status: dzVents: > ruleIsBeforeCivilTwilightEnd()
2019-05-28 08:08:16.896 Status: dzVents: > yday: 147
2019-05-28 08:08:16.896 Status: dzVents: > seconds: 1
2019-05-28 08:08:16.896 Status: dzVents: > month: 5
2019-05-28 08:08:16.896 Status: dzVents: > rawDate: 2019-05-27
2019-05-28 08:08:16.896 Status: dzVents: > min: 35
2019-05-28 08:08:16.896 Status: dzVents: > ruleIsBeforeCivilTwilightStart()
2019-05-28 08:08:16.896 Status: dzVents: > ruleIsAtCivilTwilightStart()
2019-05-28 08:08:16.896 Status: dzVents: > ruleIsOnDate()
2019-05-28 08:08:16.897 Status: dzVents: > daysAgo: 0
2019-05-28 08:08:16.897 Status: dzVents: > raw: 2019-05-27 20:35:01
2019-05-28 08:08:16.897 Status: dzVents: > milliseconds: 0
2019-05-28 08:08:16.897 Status: dzVents: > ruleIsInWeek()
2019-05-28 08:08:16.897 Status: dzVents: > matchesRule()
2019-05-28 08:08:16.897 Status: dzVents: > secondsSinceMidnight: 74101
2019-05-28 08:08:16.897 Status: dzVents: > wday: 2
2019-05-28 08:08:16.897 Status: dzVents: > hoursAgo: 11
2019-05-28 08:08:16.897 Status: dzVents: > ruleIsBeforeSunset()
2019-05-28 08:08:16.897 Status: dzVents: > msAgo: 41595750
2019-05-28 08:08:16.897 Status: dzVents: > dayAbbrOfWeek: mon
2019-05-28 08:08:16.897 Status: dzVents: > ruleIsAfterCivilTwilightStart()
2019-05-28 08:08:16.897 Status: dzVents: > rawTime: 20:35:01
2019-05-28 08:08:16.897 Status: dzVents: > ruleIsOnDay()
2019-05-28 08:08:16.897 Status: dzVents: > setPoint: 0
2019-05-28 08:08:16.897 Status: dzVents: > setVolume()
2019-05-28 08:08:16.897 Status: dzVents: > updatePressure()
2019-05-28 08:08:16.897 Status: dzVents: > updatePercentage()
2019-05-28 08:08:16.897 Status: dzVents: > _adapters:
2019-05-28 08:08:16.897 Status: dzVents: > 1: Evohome device adapter
2019-05-28 08:08:16.897 Status: dzVents: > updateSetPoint()
2019-05-28 08:08:16.897 Status: dzVents: > onkyoEISCPCommand()
2019-05-28 08:08:16.897 Status: dzVents: > isSecurity: false
2019-05-28 08:08:16.897 Status: dzVents: > _state: AutoWithEco
2019-05-28 08:08:16.897 Status: dzVents: > name: Evo Color
2019-05-28 08:08:16.897 Status: dzVents: > volumeDown()
2019-05-28 08:08:16.897 Status: dzVents: > updateYouless()
2019-05-28 08:08:16.897 Status: dzVents: > isScene: false
2019-05-28 08:08:16.897 Status: dzVents: > updateAirQuality()
2019-05-28 08:08:16.898 Status: dzVents: > updateGas()
2019-05-28 08:08:16.898 Status: dzVents: > active: false
2019-05-28 08:08:16.898 Status: dzVents: > cancelQueuedCommands()
2019-05-28 08:08:16.898 Status: dzVents: > hardwareId: 2
2019-05-28 08:08:16.898 Status: dzVents: > updateHumidity()
2019-05-28 08:08:16.898 Status: dzVents: > switchTypeValue: 0
2019-05-28 08:08:16.898 Status: dzVents: > isTimer: false
2019-05-28 08:08:16.898 Status: dzVents: > setKelvin()
2019-05-28 08:08:16.898 Status: dzVents: > hardwareTypeValue: 39
2019-05-28 08:08:16.898 Status: dzVents: > description:
2019-05-28 08:08:16.898 Status: dzVents: > updateCustomSensor()
2019-05-28 08:08:16.898 Status: dzVents: > updateAlertSensor()
2019-05-28 08:08:16.898 Status: dzVents: > setState()
2019-05-28 08:08:16.898 Status: dzVents: > hardwareName: Evo
2019-05-28 08:08:16.898 Status: dzVents: > deviceType: Heating
2019-05-28 08:08:16.898 Status: dzVents: > hardwareID: 2
2019-05-28 08:08:16.898 Status: dzVents: > idx: 1
2019-05-28 08:08:16.898 Status: dzVents: > setValues()
2019-05-28 08:08:16.898 Status: dzVents: > id: 1
2019-05-28 08:08:16.898 Status: dzVents: > setDescription()
2019-05-28 08:08:16.898 Status: dzVents: > updateLux()
Again, thanks for your help.
Paul.
Re: Evohome [Solved]
Posted: Tuesday 28 May 2019 15:14
by waaren
PaulOckenden wrote: ↑Monday 27 May 2019 19:19
BTW, I realise I can do this by making a domoticz.openURL request to the Domoticz API:
/json.htm?type=command¶m=switchmodal&idx=1&status=AutoWithEco&action=1&ooc=0
It would just be nicer to do it 'properly'.
@PaulOckenden
Happy to implement this as native dzVents method (something like setStatus(status, until, action, ooc) but need someone to test. Is that something you could help with ?
Re: Evohome
Posted: Tuesday 28 May 2019 15:22
by PaulOckenden
Thanks @Waaren, I'd be more than happy to help!
P.