Contrôler sa VMC StorkAir / ComfoAir / zehnder via sa domotique

jcoenen · 24 Novembre 2015

SpigoloN;1057130 a dit:
Il semblerait que ça soit en option sur les comfoair mais de série sur les WHR. en tout cas ça pourrait expliquer que mon disjonction 2A claque et que j'ai observé une pointe à 1200W (total maison mais je crois qu'il n'y avait rien de spécial d’allumé)

Ok, c'est possible, et effectivement, j'ai aussi une pompe a chaleur avec une résistance interne qui se mettait en route sans prévenir ( 8KW) et me faisait disjoncter le général, comme c'est bien caché on peine a trouvé la raison.

listhor · 25 Novembre 2015

I used dashboard, but did not know about the drag and drop, cheers for that.

SVG plots, looks like the update changed the definition of the SVG file. Create a new one is not that complicated, you need to display the device's log file in the main window and create a new plot (there's a Create SVG plot link)

Hi jcoenen,

As long as dashboard area (row, column) is wider and higher than module being moved - you can drag it.
In regard to SVG plots, I've created new ones (for speedtest and weather

) and by comparing, I think that in my case the reason behind error in VMC logs is simply because they are empty (VMC is not connected yet). There are no columns to choose from and in plot settings drop down column menu isn't available. So, I'll wait till I'm back home and connect everything...

jcoenen · 25 Novembre 2015

listhor;1057409 a dit:
Hi jcoenen,

As long as dashboard area (row, column) is wider and higher than module being moved - you can drag it.
In regard to SVG plots, I've created new ones (for speedtest and weather ) and by comparing, I think that in my case the reason behind error in VMC logs is simply because they are empty (VMC is not connected yet). There are no columns to choose from and in plot settings drop down column menu isn't available. So, I'll wait till I'm back home and connect everything...

OK, obvisously when the log file where data is stored is empty, there's no way the system can get the data contents ...

Smack this into the file /opt/fhem/log/VMC-2015-11.log (each line starts with the date)

2015-11-01_00:04:19 VMC Bypass_Faktor: 0 2015-11-01_00:04:19 VMC Bypass_Stufe: 0 2015-11-01_00:04:19 VMC Bypass_Korrektur: 0 2015-11-01_00:04:19 VMC Bypass_Sommermodus: nein 2015-11-01_00:04:19 VMC Proz_Zuluft: 55 2015-11-01_00:04:19 VMC Proz_Abluft: 55 2015-11-01_00:04:19 VMC UPM_Zuluft: 1986 2015-11-01_00:04:19 VMC UPM_Abluft: 1932 2015-11-01_00:04:20 VMC Temp_Komfort: 21 2015-11-01_00:04:20 VMC Temp_Aussen: 11 2015-11-01_00:04:20 VMC Temp_Zuluft: 19.5 2015-11-01_00:04:20 VMC Temp_Abluft: 22 2015-11-01_00:04:20 VMC Temp_Fortluft: 12.5 2015-11-01_00:04:20 VMC Temp_Flag: 15 2015-11-01_00:04:20 VMC Temp_EWT: 25 2015-11-01_00:04:20 VMC Proz_Abluft_abwesend: 15 2015-11-01_00:04:20 VMC Proz_Abluft_niedrig: 55 2015-11-01_00:04:20 VMC Proz_Abluft_mittel: 72 2015-11-01_00:04:20 VMC Proz_Zuluft_abwesend: 15 2015-11-01_00:04:20 VMC Proz_Zuluft_niedrig: 55 2015-11-01_00:04:20 VMC Proz_Zuluft_mittel: 72 2015-11-01_00:04:20 VMC Proz_Abluft_aktuell: 55 2015-11-01_00:04:20 VMC Proz_Zuluft_aktuell: 55 2015-11-01_00:04:20 VMC Stufe: niedrig 2015-11-01_00:04:20 VMC Zuluft_aktiv: 1 2015-11-01_00:04:20 VMC Proz_Abluft_hoch: 96 2015-11-01_00:04:20 VMC Proz_Zuluft_hoch: 97 2015-11-01_00:09:19 VMC Bypass_Faktor: 0 2015-11-01_00:09:19 VMC Bypass_Stufe: 0 2015-11-01_00:09:19 VMC Bypass_Korrektur: 0 2015-11-01_00:09:19 VMC Bypass_Sommermodus: nein 2015-11-01_00:09:19 VMC Proz_Zuluft: 55 2015-11-01_00:09:19 VMC Proz_Abluft: 55 2015-11-01_00:09:19 VMC UPM_Zuluft: 1936 2015-11-01_00:09:19 VMC UPM_Abluft: 1929 2015-11-01_00:09:20 VMC Temp_Komfort: 21 2015-11-01_00:09:20 VMC Temp_Aussen: 11 2015-11-01_00:09:20 VMC Temp_Zuluft: 19.5 2015-11-01_00:09:20 VMC Temp_Abluft: 22 2015-11-01_00:09:20 VMC Temp_Fortluft: 12.5 2015-11-01_00:09:20 VMC Temp_Flag: 15 2015-11-01_00:09:20 VMC Temp_EWT: 25 2015-11-01_00:09:20 VMC Proz_Abluft_abwesend: 15 2015-11-01_00:09:20 VMC Proz_Abluft_niedrig: 55 2015-11-01_00:09:20 VMC Proz_Abluft_mittel: 72 2015-11-01_00:09:20 VMC Proz_Zuluft_abwesend: 15 2015-11-01_00:09:20 VMC Proz_Zuluft_niedrig: 55 2015-11-01_00:09:20 VMC Proz_Zuluft_mittel: 72 2015-11-01_00:09:20 VMC Proz_Abluft_aktuell: 55 2015-11-01_00:09:20 VMC Proz_Zuluft_aktuell: 55 2015-11-01_00:09:20 VMC Stufe: niedrig 2015-11-01_00:09:20 VMC Zuluft_aktiv: 1 2015-11-01_00:09:20 VMC Proz_Abluft_hoch: 96 2015-11-01_00:09:20 VMC Proz_Zuluft_hoch: 97
And you'll be able to define your new svg plot.

listhor · 26 Novembre 2015

Smack this into the file /opt/fhem/log/VMC-2015-11.log (each line starts with the date)

Ok, after a few tries I managed to put your data in. And as usual, the root cause was somewhere else. I had chosen as Source, FileLog_VMCTemp and FileLog_VMCFAN respectively instead of just FileLog_VMC. I did copy settings from install files and now I don't get back any errors.
BTW, what are FileLog_VMCTemp and FileLog_VMCFAN for??

jcoenen · 26 Novembre 2015

listhor;1057888 a dit:
Ok, after a few tries I managed to put your data in. And as usual, the root cause was somewhere else. I had chosen as Source, FileLog_VMCTemp and FileLog_VMCFAN respectively instead of just FileLog_VMC. I did copy settings from install files and now I don't get back any errors.
BTW, what are FileLog_VMCTemp and FileLog_VMCFAN for??

The device log gives all readings so I defined the temp and fan logs to limit the logged values to the temperatures and fan readings, that speeds up the graphics generation ...

I found a typo in the FAN log definition UMP was written instead of UPM ...

listhor · 26 Novembre 2015

Ok, in such a case which logs to be set as Source, respectively FAN & temp? Can we just change regexp to UPM?
I think I'll wait until they are full of readings...

jcoenen · 26 Novembre 2015

listhor;1057902 a dit:
Ok, in such a case which logs to be set as Source, respectively FAN & temp? Can we just change regexp to UPM?
I think I'll wait until they are full of readings...

VMCFAN.log you need to redefine it (or easier change it in the config file and rereadcfg)

When all parameters of the VMC are polled, the log file gets really big, as the CVG plots read it, the bigger the slower, so it's best to either limit the number of parameters polled (using the attributes) or log the parameters to be plotted in another log file.

I use VMCTemp for the temperature plots and FAN for the motor speed.

listhor · 26 Novembre 2015

I use VMCTemp for the temperature plots and FAN for the motor speed.

That's what I did again. Despite of having your data in general FileLog_VMC:

2015-11-24_05:14:07 FileLog_VMC addRegexpPart Prognoza temperature:.*
2015-11-01_00:04:19 VMC Bypass_Faktor: 0 2015-11-01_00:04:19 VMC Bypass_Stufe: 0 2015-11-01_00:04:19 VMC Bypass_Korrektur: 0
2015-11-01_00:04:19 VMC Bypass_Sommermodus: nein 2015-11-01_00:04:19 VMC Proz_Zuluft: 55 2015-11-01_00:04:19 VMC Proz_Abluft: 55
2015-11-01_00:04:19 VMC UPM_Zuluft: 1986 2015-11-01_00:04:19 VMC UPM_Abluft: 1932 2015-11-01_00:04:20 VMC Temp_Komfort: 21
2015-11-01_00:04:20 VMC Temp_Aussen: 11 2015-11-01_00:04:20 VMC Temp_Zuluft: 19.5 2015-11-01_00:04:20 VMC Temp_Abluft: 22
And so on...

Nothing is pulled out to FileLog_VMCTemp and FileLog_VMCFAN. I'm not so sure, whether NOTIFYDEV is correct:

Shouldn't it be pointing at VMC FileLog?

jcoenen · 26 Novembre 2015

listhor;1057977 a dit:
That's what I did again. Despite of having your data in general FileLog_VMC:

Nothing is pulled out to FileLog_VMCTemp and FileLog_VMCFAN. I'm not so sure, whether NOTIFYDEV is correct:

Shouldn't it be pointing at VMC FileLog?

The TEMP and FAN are empty as fhem has not recevied any data from the VMC.

The way it works is like this.

VMC is sampled, message gets in FHEM
FHEM writes to VMC log file VMC-2015-11.log
When a temperature is detected in the written data (from the VMC:Temp.* regexp) it is written to the TEMP log file
When a Fan speed is detected in the written data (from the VMC:UPM.* regexp) it is written to the FAN log file

When you write directly in the log file, the data does not get through the FHEM filters and thus are not written to the TEMP and FAN logs

you can either fill the TEMP and FAN log manually with data or use the VMClog file in the SVG plots. (watch out for the file attributes when using root access)

VMCtemp file sample

2015-11-26_11:35:48 VMC Temp_Komfort: 21 2015-11-26_11:35:48 VMC Temp_Aussen: 13 2015-11-26_11:35:48 VMC Temp_Zuluft: 15 2015-11-26_11:35:48 VMC Temp_Abluft: 19.5 2015-11-26_11:35:48 VMC Temp_Fortluft: 14.5 2015-11-26_11:35:48 VMC Temp_Flag: 15 2015-11-26_11:35:48 VMC Temp_EWT: 25 2015-11-26_11:40:48 VMC Temp_Komfort: 21 2015-11-26_11:40:48 VMC Temp_Aussen: 13 2015-11-26_11:40:48 VMC Temp_Zuluft: 15 2015-11-26_11:40:48 VMC Temp_Abluft: 19.5 2015-11-26_11:40:48 VMC Temp_Fortluft: 14.5 2015-11-26_11:40:48 VMC Temp_Flag: 15 2015-11-26_11:40:48 VMC Temp_EWT: 25 2015-11-26_11:45:48 VMC Temp_Komfort: 21 2015-11-26_11:45:48 VMC Temp_Aussen: 13 2015-11-26_11:45:48 VMC Temp_Zuluft: 15 2015-11-26_11:45:48 VMC Temp_Abluft: 19.5 2015-11-26_11:45:48 VMC Temp_Fortluft: 14.5 2015-11-26_11:45:48 VMC Temp_Flag: 15 2015-11-26_11:45:48 VMC Temp_EWT: 25 2015-11-26_11:50:48 VMC Temp_Komfort: 21 2015-11-26_11:50:48 VMC Temp_Aussen: 13 2015-11-26_11:50:48 VMC Temp_Zuluft: 15.5 2015-11-26_11:50:48 VMC Temp_Abluft: 19.5 2015-11-26_11:50:48 VMC Temp_Fortluft: 14.5 2015-11-26_11:50:48 VMC Temp_Flag: 15 2015-11-26_11:50:48 VMC Temp_EWT: 25 2015-11-26_11:55:48 VMC Temp_Komfort: 21 2015-11-26_11:55:48 VMC Temp_Aussen: 13 2015-11-26_11:55:48 VMC Temp_Zuluft: 15.5 2015-11-26_11:55:48 VMC Temp_Abluft: 19.5 2015-11-26_11:55:48 VMC Temp_Fortluft: 14.5 2015-11-26_11:55:48 VMC Temp_Flag: 15 2015-11-26_11:55:48 VMC Temp_EWT: 25 2015-11-26_12:00:48 VMC Temp_Komfort: 21 2015-11-26_12:00:48 VMC Temp_Aussen: 13 2015-11-26_12:00:48 VMC Temp_Zuluft: 15.5 2015-11-26_12:00:48 VMC Temp_Abluft: 19.5 2015-11-26_12:00:48 VMC Temp_Fortluft: 14.5 2015-11-26_12:00:48 VMC Temp_Flag: 15 2015-11-26_12:00:48 VMC Temp_EWT: 25

Sample of VMCFan log file

2015-11-25_09:09:09 VMC UPM_Zuluft: 560 2015-11-25_09:09:09 VMC UPM_Abluft: 517 2015-11-25_09:39:11 VMC UPM_Zuluft: 548 2015-11-25_09:39:11 VMC UPM_Abluft: 521 2015-11-25_10:09:07 VMC UPM_Zuluft: 569 2015-11-25_10:09:07 VMC UPM_Abluft: 536 2015-11-25_10:39:10 VMC UPM_Zuluft: 554 2015-11-25_10:39:10 VMC UPM_Abluft: 537 2015-11-25_11:09:12 VMC UPM_Zuluft: 532 2015-11-25_11:09:12 VMC UPM_Abluft: 535 2015-11-25_11:39:11 VMC UPM_Zuluft: 552 2015-11-25_11:39:11 VMC UPM_Abluft: 543 2015-11-25_13:39:13 VMC UPM_Zuluft: 555 2015-11-25_13:39:13 VMC UPM_Abluft: 541 2015-11-25_15:09:13 VMC UPM_Zuluft: 559 2015-11-25_15:09:13 VMC UPM_Abluft: 519 2015-11-25_17:09:14 VMC UPM_Zuluft: 553 2015-11-25_17:09:14 VMC UPM_Abluft: 521 2015-11-25_18:59:25 VMC UPM_Zuluft: 1241 2015-11-25_18:59:25 VMC UPM_Abluft: 1378 2015-11-26_07:09:19 VMC UPM_Zuluft: 1261 2015-11-26_07:09:19 VMC UPM_Abluft: 1390 2015-11-26_07:39:22 VMC UPM_Zuluft: 1227 2015-11-26_07:39:22 VMC UPM_Abluft: 1386 2015-11-26_09:07:08 VMC UPM_Zuluft: 551 2015-11-26_09:07:08 VMC UPM_Abluft: 531 2015-11-26_09:07:39 VMC UPM_Zuluft: 552 2015-11-26_09:07:39 VMC UPM_Abluft: 527 2015-11-26_09:10:25 VMC UPM_Zuluft: 545 2015-11-26_09:10:25 VMC UPM_Abluft: 534 2015-11-26_09:36:22 VMC UPM_Zuluft: 556 2015-11-26_09:36:22 VMC UPM_Abluft: 520 2015-11-26_09:49:42 VMC UPM_Zuluft: 556 2015-11-26_09:49:42 VMC UPM_Abluft: 535 2015-11-26_09:52:13 VMC UPM_Zuluft: 556 2015-11-26_09:52:13 VMC UPM_Abluft: 535

listhor · 26 Novembre 2015

Hi again,

It seems like a success!

I think I owe you a good wine or whisky ;-)
The last f....g questions (sorry):
How do you present bypass position on the plot? Which variable do you use and plot style?
Does enthalpy settings are also possible to be presented?

jcoenen · 26 Novembre 2015

listhor;1058016 a dit:
Hi again,

It seems like a success!

I think I owe you a good wine or whisky ;-)
The last f....g questions (sorry):
How do you present bypass position on the plot? Which variable do you use and plot style?
Does enthalpy settings are also possible to be presented?

Time and patience take care of everything !

Well I though Slivovitz was your own special thing over there, I still remember my first sip of it (and that's wayyyyyy back, aouch it hurts !!!) X-p :mh:

Anyways, the plotting of the bypass position is trickier as so far it can be 0 or 100 (%) open. So the line will either be at the bottom or the top of the graph and not visible. One way around this is to use IOFill style for the data display, it fills the area under the value of the data with the choosen colour, it's also translucid so you can see other plotted data within the area.
You would then know that the bypass is open or closed with the coulour indication.
Other then that I can't figure out what to use to plot a boolean value like this.

Any value returned by the VMC to fhem can be plotted (they are all logged in VMC log file), I think enthalpy is EWT, thus Temp_EWT can be plotted, I don't have an enthalpy system from them so I have no data on my VMC.

On the other hand, you were going to put a page for the VMC on ou fibaro HC, you could also implement the plotting on the HC, getting the data from the server directly (via a VMCbinjson.cgi call). SebCbien does exactly that (he has not implemented FHEM).

listhor · 27 Novembre 2015

Well, I think Slivovitz is more popular in Hungary and Czech but I like it too

Yes, you remember right, main goal is to set Fibaro but I wanted to explore the "new possibilities" using FHEM. And I want to log speedtest results - it looks like that my ISP has stopped providing a good quality access. I want to prove it...

So, once I'm back home, I'll start annoying SebCbien on Fibaro forum, at least I'll try.

sebcbien · 30 Novembre 2015

You can try, once RaspiVMC is running, just install my VD and maybe setup emonCMS.
It's 10 minutes work ;-)

rjcab · 1 Décembre 2015

Bonjour,

JCOENEN dit:

OK, bon si tu te connectes sur le RJ45 ou le port PC (dB9 de la version luxe), les niveaux sont en RS232, pour voir si le hardware est fonctionnel, je broche parfois le RX avec le TX, lance un client et regarde si la requête de commande est bien reçue par le Pi.

Alors j'ai mon adaptateur branché en USB sur mon raspberry.
Je lance tout comme il faut:

root@jeedom:/var/log# ps -ef | grep server
www-data 458 1 1 21:28 ? 00:00:03 /usr/bin/nodejs /usr/share/nginx/www/jeedom/core/nodeJS/server.js
root 1610 1 14 21:28 ? 00:00:23 /usr/bin/python /usr/bin/fail2ban-server -b -s /var/run/fail2ban/fail2ban.sock -p /var/run/fail2ban/fail2ban.pid
www-data 1798 1 2 21:28 ? 00:00:03 /usr/bin/python /usr/share/nginx/www/jeedom/plugins/openzwave/core/class/../../ressources/zwaveserver/openZWave.py --pidfile=/tmp/openzwave.pid --device=/dev/ttymxc0 --log=Error --port=8083 --config_folder=/usr/share/nginx/www/jeedom/plugins/openzwave/core/class/../../ressources/openzwave/config --data_folder=/usr/share/nginx/www/jeedom/plugins/openzwave/core/class/../../data --callback=http://127.0.0.1:80/plugins/openzwave/core/php/jeeZwave.php --apikey=kpbtld36w4krm6g2gbaw --serverId=0
root 1873 1823 83 21:28 pts/0 00:01:58 /usr/bin/python ./server.py
root 2390 1823 0 21:31 pts/0 00:00:00 grep server
root@jeedom:/var/log# vi VMClog.log

Puis coté RS232 / RJ45 je m'amuse a les relier mais rien ne sort dans les logs.

01/12/15 21:18:23 : closing ('127.0.0.1', 40735) after reading no data
01/12/15 21:28:45 : socat
01/12/15 21:28:45 : PTY,mode=666,link=/tmp/ttyVMC
01/12/15 21:28:45 : TCP-CONNECT:127.0.0.1:10009
01/12/15 21:28:45 : new client connection from ('127.0.0.1', 33773)
01/12/15 21:28:59 : new client connection from ('127.0.0.1', 33774)
01/12/15 21:28:59 : received 07f000690016070f ('127.0.0.1', 33774) from client ('127.0.0.1', 33774) retained is 07f000690016070f
01/12/15 21:28:59 : Processing msg from queue ('127.0.0.1', 33774)
01/12/15 21:28:59 : Sending frame 07f000690016070f to VMC from Client ('127.0.0.1', 33774)
01/12/15 21:28:59 : Command code: 69 reply is True
01/12/15 21:28:59 : expecting a reply
01/12/15 21:28:59 : received from VMC
01/12/15 21:28:59 : No frame detected in
01/12/15 21:29:47 : closing ('127.0.0.1', 33774) after reading no data

Avez vous une autre combine ?

Merci

rjcab · 1 Décembre 2015

Heu pas trop compréhensible mon poste, a relier la patte 2 et 3

jcoenen · 1 Décembre 2015

On en est toujours a déboguer la connexion matérielle ...

Si on relie le 2 et le 3 de l'adaptateur USB (sans le connecter a la VMC) le log doit montrer les trames envoyées qui reviennent (le TX étant connect au RX c'est normal).

La manip c'est juste pour voir si le convertisseur USB est fonctionnel.

Après connecter le RX VMC au TX convertisseur et vice versa, et la masse bien entendu.

Dans le log je vois les trames sortir mais pas revenir (soit le TX n'est pas couplé au RX, soit la config n'est pas juste (ttyUSB ? ttyAMA0 ?), soit le convertisseur esr HS), difficile de faire un diagnostic d'içi.

listhor · 2 Décembre 2015

You can try, once RaspiVMC is running, just install my VD and maybe setup emonCMS.
It's 10 minutes work

So, you have different VD than SebCbien? What is a difference?
Is emonCMS necessary?

sebcbien · 2 Décembre 2015

??? I'm SebCbien ... ???

jcoenen · 2 Décembre 2015

sebcbien;1059824 a dit:
??? I'm SebCbien ... ???

Mais en es tu bien certain ?

listhor · 2 Décembre 2015

Haha, that's how ends up writing in a hurry, while being at work. Sorry for that!

Rechercher

Rechercher

Contrôler sa VMC StorkAir / ComfoAir / zehnder via sa domotique

jcoenen

listhor

jcoenen

listhor

jcoenen

listhor

jcoenen

listhor

jcoenen

listhor

jcoenen

listhor

sebcbien

rjcab

rjcab

jcoenen

listhor

sebcbien

jcoenen

listhor

Sujet semblables

Notre sélection