New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documentation related to auto ventilation #10
Comments
@decontamin4t0R have you played with these values?
|
I think that 225 indicates that one of the protections is active, and 226 is either the protection itself or the sensor which caused the protection to go active... Do you still have the value of 230 handy? They are the ventilation constraints, so the bit 27 should be 1... |
I wasn't logging 230 unfortunately. How did you get this number, and how did you found out about the bits? Have you perhaps documented this somewhere? |
230 isn't even in the RPDO_TYPE_MAP, so I don't know the size. I've created that map some time ago by using the app and going trough most menus and capturing what each sensor size was. |
The App contains the 230 as ventilation config constraints, UINT64, bitfield. The 27 is the bit for either VentConfConstraintHumidityProtectionLong or VentConfConstraintHumidityProtection. |
oops, just checked my notes again: |
Did you succeed in decompiling of the app? I've tried this approach, and it gave me the protocol buffers file, but I could never find the PDO ID's. |
yeah... you can just take the decompiled source, its obfuscated but i was able to give the classes and packages distinguishable names, so you know that the class c072a or so is used there etc. |
Yes, just confirmed. When you set humidity protection to on or to autoonly and have the ventilation in auto, 225 is 1. 0 if humidity protection = disabled or autoonly and manual. |
Hello, I have a "good" deobfuscated set off an older app. My problem ist, that I am not a programmer. I can not find the correct class, where the description is. |
I've tried a lot of tools to deobfuscate the app, but due to a lot of setters and getters, and passing around of objects, it's not to easy to understand it. I recently took a new look at it, and there is one class with all the pdo's, but these pdos tend to get replaced with constants from the java libs. |
If you search for something or have a question, just ask, that is probably easier than looking into the code and getting a hang of it |
I can agree to: My Operation Idea: I search for the correct ventilation mode: SENSOR_OPERATING_MODE_BIS = 49 I found these in the file UnbalanceDetailFragment_ViewBinding.java: I found these in the file VentControlDetailFragment_ViewBinding.java: I will show on my central monitor these condition warnings: I found these lines in the file SensorVentDetailFragment_ViewBindings.java: |
My notes:
for the unbalance bit, check pdo 230 at bit 62 |
thank you. I found in the file DescriptorProtos.java: |
Frost protection unbalanced not working. |
Can you tell me more about your implementation? How do you monitor the values? |
I found out some new values (I hope they are correct ;) ): SENSOR_PROFILE_TEMPERATURE = 67 ==> temperatureprofile (0=normal; 1=cold; 2 = warm) |
Added some of the PDOs (those I also tried) indicated by hme0354 in post michaelarnauts#10 (comment)
Added some of the PDOs (those I also tried) indicated by hme0354 in michaelarnauts#10 (comment)
Added some of the PDOs (those I also tried) indicated by hme0354 in post #10 (comment)
Added some of the PDOs (those I also tried) indicated by hme0354 in #10 (comment)
My ComfoAirQ has a 'Comfofond' (https://tinyurl.com/y9ug34ao) attached. |
I think the best way is to just try out some sensors id's and compare the values with what you see in the app. That's how I found out the existing sensors. |
Checkout the following:
|
In relation to #10 (comment), I've monitored PDO 225, 226 and 230 over the past days, because I know my system increases fan speed every time we take a shower (after the manual boost mode period has passed). And indeed, I see the same behavior as HalliHalloSchatz describes in his earlier post (#10 (comment)):
I'll continue monitoring PDO 225 and 226 to see if HumidityComfort or TemperaturePassive triggers different behavior. Monitoring PDO 230 did NOT result in any messages pushed. Perhaps I haven't configured it properly, since it is not in the RPDO map, I needed to guess its type and set it to 3. But I'm not even sure UINT64 as indicated by decontamin4t0R is supported in the present release. |
PDO 230 should in fact be pushed regularly - everytime you have a ventilation constraint affecting the current airflow. My ventilation pushes 230 when I manually select level 3 as 0x600000000402, it limits the airflow because my bypass is active. (Bit 1 = general constraint? and Bit 10 = VentConfConstraintBypass, or Bit 45 = general long constraint? and Bit 10 = VentConfConstraintBypassLong). PS: I could not find where comfoconnect should not work with UINT64. Maybe try INT64? |
Changing the RPDO type to 4 now results in 64 bit values being pushed, just 0s so far, but i'll keep monitoring it and see what follows. Thx. |
I've noticed
225
and226
are related to the automatic mode.My ventilation was running with a low fan speed, and in auto mode with humidity protection active.
Detected a high humidity (SENSOR mode active). The fan started spinning high.
225 = 2
226 = 300
Fell back to normal mode.
225 = 1
226 = 100
The text was updated successfully, but these errors were encountered: