Climate Solutions Community

The newly displayed " Aktiver Warmwassermodus" remains ON all the time. It really looks like that I need to parse the actual schedule in order to get the needed info.😣 ... Mehr anzeigen

This datapoint shows ON  all the time when DHW is selected niglecting the local schedule, it seems that I really have to parse the schedule in order to get the info wether hotwater production is actually scheduled or not. Just saw the new update of ViCare does show what I need,  " Aktiver Warmwassermodus" is displayed only if the schedule is on. ... Mehr anzeigen

Thanks for the quick answer! I was using subcategories of heating.dhw already but not this upper level datapoint. It seems to me that using this one you get several sub datapoints as well. I'll check for the desired outputs (in both parts of the schedule😉) when back @hhome and report. Thanks. ... Mehr anzeigen

What makes you think so?   Try something like that:   var returnvalue = HTTP.sendHttpGetRequest(url, headers, 10*1000); logger.info("returnvalue: {}", returnvalue); //var arr=returnvalue; returnvalue = JSON.parse(returnvalue); var count = returnvalue.data.length; logger.info("count: {}", count); try { for (var i = 0; i < count; i++) { switch (returnvalue.data[i].feature) { case "heating.sensors.temperature.outside": var temp = returnvalue.data[i].properties.value.value; events.postUpdate('OutsideTemperature', temp); logger.info("DataIndex: {}, ExtTemp: {}", i,temp); break; case "heating.dhw.sensors.temperature.hotWaterStorage": var temp = returnvalue.data[i].properties.value.value; events.postUpdate('BoilerTemperature', temp); logger.info("DataIndex: {}, HotWaterStorageTemp: {}", i, temp); break; case "heating.dhw.oneTimeCharge": var temp = returnvalue.data[i].properties.active.value; temp = (temp === true) ? 'on' : 'off'; events.postUpdate('IsOneTimeCharge', temp); logger.info("DataIndex: {}, OneTimeCharge: {}",i, temp); break; case "heating.dhw.pumps.circulation": temp = returnvalue.data[i].properties.status.value; events.postUpdate('DhwPumpsCirculation', temp); logger.info("DataIndex: {}, DhwPumpsCirculation: {}",i, temp); break; case "heating.burners.0.statistics": temp = returnvalue.data[i].properties.hours.value; events.postUpdate("HeatingBurnerStatistics_Hours",temp); logger.info("DataIndex {}, Hours: {}", i, temp); temp = returnvalue.data[i].properties.starts.value; events.postUpdate("HeatingBurnerStatistics_Starts",temp) logger.info("DataIndex: {}, Starts: {}", i, temp); break; case "heating.circuits.0.operating.modes.active": temp= returnvalue.data[i].properties.value.value; events.postUpdate("ActiveMode", temp); logger.info("DataIndex: {}, ActiveMode: {}", i, temp); break; default: logger.info("DataIndex: {}, Data not used: {}",i, returnvalue.data[i].feature); }   I'm using those lines after the request posted above. Sorry for no code tags, can't find them using my smartphone😎. ... Mehr anzeigen

Quote: "however it is not clear if the JSON order will preserve."   That is assured, the order does change so you can't use the array index for parsing the results! ... Mehr anzeigen

Quote: "Do you already have experience in controlling your system, especially the climate in your home, using PIR sensors?" Controlling the climate and using PIR, no. Controlling my (rather minimal) home automation system, yes. I'm using openHAB, so I'm not limited to the heating system and can react with any connected device on any implemented trigger condition. For example by using the (connected) smartphones as alarm devices (Wecker), my system can check 10 minutes prior the next alarm wether hotwater is already on, if not OneTimeCharge gets activated.   The needed time for implementing such a new function is perfectly understood. A headsup if this request will be implemented at all or not not would be nice. ... Mehr anzeigen

@nigolcabej  schrieb:    It was not easy because the redirect_uri redirects immediatellay to an other site  You did set that url! Why didn't you use localhost?   ... Mehr anzeigen

You can call for one datapoint, several points or all! See this example from my javascript rule which is requesting several datapoints: url ="https://api.viessmann.com/iot/v1/equipment/installations/"+ installationID +"/gateways/" +gatewaySerial + "/devices/0/features?regex=heating.(sensors.temperature.outside%7Cdhw.(oneTimeCharge%7Csensors.temperature.hotWaterStorage%7Cpumps.circulation)%7Cburners.0.statistics%7Ccircuits.0.operating.modes.active)";   The "%7" is used instead of the "|" character. ... Mehr anzeigen

Note that the returned JSON array order is not assured! Initially I used the array indices  as well and had to change my code afterwards! ... Mehr anzeigen

Moin, m.E. ist die Anzeige im Vitoguide unverändert (siehe Anhang, meine Anlage ist immer noch im Modus "dhw"). Es handelt sich dabei um die Gas-Kachel und nicht die Details-Anzeige, dort wird es richtig angezeigt. Beim Starten von Vitoguide kam relativ zügig die Meldung das eine neue Version zur Verfügung stünde, diese wurde auch genutzt (Version 2.4.0). Sorry! ... Mehr anzeigen

What kind of values for the outsidd temperature do you see when manually checking it on the heating device and in ViCare? Are rhey different to the values you are getting from the API? If the heating System is reporting the same values as you get from the API it is probably the sensor, If only ViCare shows the same values but Not the heating System it is somewhere in the interface from the heating System to the API. My guess is the later one ( accounting for your other problems). ... Mehr anzeigen

@CustomerCareChris  schrieb:   ... Wenn ich es richtig sehe betrifft der Anzeigefehler lediglich die Kachel auf dem Dashboard, sobald man diese über "Details und Einstellungen" öffnet wird für Heizung kein Gasverbrauch mehr angezeigt..... Richtig, ich bin noch nicht mal auf die Idee gekommen da noch "tiefer" zu gehen. Keine Eile mit der Rückmeldung, die Ausgangsfrage ist ja gelöst. ... Mehr anzeigen

That all sounds like a problem with your system, especially when reading your other posts. However I'm just a customer as you are, keeping fingers crossed that Viessmann will find the cause.  ... Mehr anzeigen

I get the exact same response as in your OP when doing the POST call. I asked for the parts of your GET call. Are you saying that the call to activate the OneTimeCharge via ViCare is also unsuccessful? In other words this function is starting ONLY when commanding from the control station of the heating system? ... Mehr anzeigen

If I understand correctly the blue outside temperature line is from an external source and the pink line is the API reading. That looks odd. My API readings for the outside temperature are fluctuating as your  blue line, I can "see" when the sun is blocked from the sensor (at 10:00 local). ... Mehr anzeigen

I am using the API call for OneTimeCharge (as tested now), I do get the result as you posted in the OP however my System goes into OneTimeCharge ( Vitodens 333F). This is also shown in the return of a GetRequest to the API. Please post the final part of your GetRequest ( the part after: / devices/0/features.. "). ... Mehr anzeigen

VitoConnect 7571381700298105 (aber das hätte man doch wohl auch anhand Installationsnummer finden können, oder?). Die fehlerhafte Anzeige ist aber wie gesagt nur auf Vitoguide zu sehen. Gibt es dort keine Stromkachel wie bei ViCare? Danke für die Antwort, ich werde dann mal einen Mauerdurchbruch im Heizungskeller angehen. ... Mehr anzeigen

Ich frage mich ob es wirklich eine Lösung ist die Zirkulationspumpe erst dann anzustellen, wenn der Bedarf da ist. So kommt dann ja auch erstmal nur kaltes Wasser aus der Leitung, wäre m.E. keine Verbesserung gegenüber keiner Zirkulationspumpe. Oder trügt mich da mein Verständniss? Oder wird die Ersparnis nur durch das Abschalten erreicht ( was in meinem Fall durch die negativen Kommentare meiner [ gefühlt kalt duschenden] Frau aufgewogen würde).   Ansonsten kann ich nur die Nutzung der API empfehlen, hier kann man (fast) alle Daten auslesen und dann ggf. andere Aggregate selber steuern. Bei mir z. B.: StandardWecker ist das Handy, dessen nächste Weckzeit wird von der Hauautomation überwacht. Diese prüft 5 Minuten vor den nächsten Wecken ob Warmwasser bereit steht, wenn nicht wird "Ich will Warmwasser" eingestellt. ... Mehr anzeigen

OK. Nun ist die Anzeige in ViCare wieder normal (Deiner Anlage geht es gut). In Vitoguide fehlt die Anzeige des Stromverbrauchs und die graphische Anzeige des Gasverbrauchs ist merkwürdig ( obwohl nur Warmwasserbetrieb genutzt wird und auch nur solcher Verbrauch numerisch geloggt wird, zeigt die Graphik immer wieder Anzeigeblöcke  für den Heizbetrieb). Ob dies beides nicht schon vorher war kann ich aber nicht sagen. Gibt es nocheineAntwort zur Nachfrage bzgl. der Kabellänge? Ansonsten Danke. ... Mehr anzeigen

Yes, the Viessmann developers are answering here. I can't say why my system (Vitodens 333F) is giving the statistics data and your doesn't. Your "I keep the heater in "dhw" mode (warm water only, no heating)" doesn't seem to related to the posted return of your used operating Mode😉. ... Mehr anzeigen

Why are you using the redirect_uri "everest", the example in the docs show  http://localhost:4200/ EDIT: I should have posted while at my system! Looking at the returns I get I see also the ""api-viessmann-platform.io" ( I had that as well when using the wrong url. Sorry for that. Using the request for the "'heating.burner' data point:" on my system does give me virtually the same result you have except the finishing:  "timestamp": "2021-07-24T17:05:06.581Z",         "isEnabled": true,         "isReady": true,         "deviceId": "0"   Using a request for: "../devices/0/features?regex=heating.(sensors.temperature.outside%7Cdhw.(oneTimeCharge%7Csensors.temperature.hotWaterStorage%7Cpumps.circulation)%7Cburners.0.statistics%7Ccircuits.0.operating.modes.active)%7Cventilation.operating.programs.active" I get a completly useable result, did you try such a request?   ... Mehr anzeigen

The returned url with "api-viessmann-platform.io" sounds suspicious. It got such when calling this url, using the correct url did give the correct results. Are you sure to have used the correct new url? ... Mehr anzeigen