Sensor for Vallox DigitSE RS485 ventilation system with integration into FHEM.

[boehrian]

Hi, my output ist now:

0 MCO:BGN:INIT REPEATER,CP=RNNRA--,VER=2.1.1
3 TSM:INIT
4 TSF:WUR:MS=0
12 TSM:INIT:TSP OK
13 TSF:SID:OK,ID=42
15 TSM:FPAR
52 TSF:MSG:SEND,42-42-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
2059 !TSM:FPAR:NO REPLY
2061 TSM:FPAR
2098 TSF:MSG:SEND,42-42-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
4105 !TSM:FPAR:NO REPLY
4107 TSM:FPAR
4143 TSF:MSG:SEND,42-42-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
6151 !TSM:FPAR:NO REPLY
6153 TSM:FPAR
6189 TSF:MSG:SEND,42-42-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
8197 !TSM:FPAR:FAIL
8198 TSM:FAIL:CNT=1
8200 TSM:FAIL:PDT
18203 TSM:FAIL:RE-INIT
18205 TSM:INIT
18212 TSM:INIT:TSP OK
18214 TSF:SID:OK,ID=42
18216 TSM:FPAR
18253 TSF:MSG:SEND,42-42-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
20261 !TSM:FPAR:NO REPLY
20263 TSM:FPAR
20300 TSF:MSG:SEND,42-42-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
22307 !TSM:FPAR:NO REPLY
22309 TSM:FPAR
22346 TSF:MSG:SEND,42-42-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
24353 !TSM:FPAR:NO REPLY
24355 TSM:FPAR
24392 TSF:MSG:SEND,42-42-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:

I get no reply from the Vallox.
Is your original Vallox controller online

[Heinz]

The "no reply" message is from the mysensors library, but I don't know what it means.
The line "started cyclic update timer" indicates that the sensor initialized successfully, but it is missing in your output.

My latest code is online at
https://github.com/windkh/valloxserial/blob/master/examples/mysensors/ValloxSensor.ino

[hek]

Use the log parser to help you interpret the log.

[ausbremen]

@heinz
Hi Heinz, the SVG_FileLog_Vallox_#.gplot files are empty ...probably the link is dead...could you reup them? Or could you send them tio me?

Thanks, Holger

[ausbremen]

@heinz
Sorry...everything is fine with the gplot files...it was my fault trying to look at them with the crimpson editor...instead of FHEM gplot

[captaindork]

Hello Heinz, all,
first of all thank you for sharing your work in this thread!
I have not to much skills around programming and arduino, but was however able to build this and integrate my Vallox 90 SE into ioBroker. Absolutely Great!
You mentioned the bypass damper above and I see you have visualized it in fhem. I found the Value to set the Threshold temp for this (31), however I wonder where you got the actual bypass position from. Which Value shows if its open or closed?
I do not want to control it, i just would like to log the Position Status to see when it happens.

Thanks a lot i feel blind :)

[Heinz]

Hi @captaindork
sorry for delay,.... the position of the damper (which is the bypass) is indicated through a single bit of the multi purpose IO-Port 2. The library defines that as property 38 DamperMotorPositionProperty.
In the mysensors example it is published as
const uint8_t DAMPER_MOTOR_POSITION = 42;
The value is either 1 or 0.

I mapped it in FHEM as follows

attr MYSENSOR_Vallox mapReading_DamperMotorPosition 42 value1

define MYSENSOR_Vallox_DamperMotorPosition dummy
attr MYSENSOR_Vallox_DamperMotorPosition alias WRG-Bypass
attr MYSENSOR_Vallox_DamperMotorPosition devStateIcon 1:rc_GREEN 0:rc_BLANK
attr MYSENSOR_Vallox_DamperMotorPosition event-on-update-reading state
attr MYSENSOR_Vallox_DamperMotorPosition group Status
attr MYSENSOR_Vallox_DamperMotorPosition icon vent_bypass
attr MYSENSOR_Vallox_DamperMotorPosition room Lüftung
attr MYSENSOR_Vallox_DamperMotorPosition sortby 3
define MYSENSOR_Vallox_DamperMotorPosition_Notify notify MYSENSOR_Vallox:DamperMotorPosition:.* { my $d = sprintf ("%.0f", ReadingsVal("MYSENSOR_Vallox","DamperMotorPosition", 0));; fhem("set MYSENSOR_Vallox_DamperMotorPosition $d");;}
define MYSENSOR_Vallox_DamperMotorPosition_Notify2 at +*00:01:00 { my $d = sprintf "%.0f", ReadingsVal("MYSENSOR_Vallox","DamperMotorPosition", 0);; fhem("set MYSENSOR_Vallox_DamperMotorPosition $d");;}

[RHead]

Hi.

Can you make exact parts list for this setup.

[Heinz]

Ok ... after my holidays.

[Heinz]

Well basically the part list is very simple

1x Arduino Mega 2560
1x NRF24L01+
1x Pushbutton
2x MAX485 Module TTL Switch Module (one for sender, one for receiver)
(e.g. https://protosupplies.com/product/max485-ttl-to-rs-485-interface-module/)

The 1x Resistor 120Ohms is only neccessary if not already mounted on the MAX485 Module. It depends on what module
you bought. So have a look at the layout and check if there is a 120Ohms resistor mounted between pins A and B.
The module (https://protosupplies.com/product/max485-ttl-to-rs-485-interface-module/) already contains that resistor.

Optionally you can add a capacitor between + and - to stabilize the voltage level if your power supply is a weak one.
Anyone will do like 10uF, 100uF...

[Heinz]

Note that you can make use of any MAX485 module that is suitable for the arduino (5V). Basically they are all the same except for a few minor tweaks like LEDs or other non relevant stuff.

[MasMat]

I found this old thread and since I have a Vallox machine it's interesting. RS485 is new to me but MySensors isn't.

Can I have a node like this described by Heinz parallel with the "mickey mouse"-display? Using the display's connector? Or is it one or the other?

I'd feel better having both (manual display&buttons and connection to MySensors=>Domoticz, in my case).