Jalle19 / eda-modbus-bridge

An HTTP/MQTT bridge for Enervent EDA ventilation units
GNU General Public License v3.0
15 stars 3 forks source link

Repeated alerts after enabling this bridge #56

Closed odelma closed 1 year ago

odelma commented 1 year ago

Hi, first of all thank you for this excellent bridge 👍

The bridge seems to be working well, but I have a strange issue that started at the same time as I installed it. I've been getting the following alert approximately every few days (sometimes twice a day, sometimes once per week):

TE20 YlÀraja Palovaara Tuloilma on kuumaa.

This stops the machine which is quite inconvenient and I am quite certain it is not a "true" alert (in reality the air temp is normal). Machine is from 2009, Enervent Pingvin Eco EDE and I have not seen this error before since starting to use the bridge. Any ideas what could be causing it and how to mitigate it?

Jalle19 commented 1 year ago

Unfortunately I have the same issue. I haven't found a workaround. Sometimes it can be many months between occurences so I've managed so far.

Jalle19 commented 1 year ago

We could try tweaking how often the alarm related registers are read to see if the issue goes away. Now that we have two confirmed cases of this happening with the same model I could also contact Enervent and ask for advice.

tomrosenback commented 1 year ago

I have not experienced this on my Pandion, I have however had the interval set to 60s

Jalle19 commented 1 year ago

It feels like this could be a Pingvin specific issue since I have the exact same model. @JohanElmis have you experienced this problem?

Jalle19 commented 1 year ago

@odelma can you try changing the publish interval setting to 30 seconds?

Jalle19 commented 1 year ago

I sent this to Enervent, let's see what they say:

Hej!

Jag har gjort ett program för att styra Enervent ventilationsmaskiner frÄn Home Assistant (en populÀr hemautomationsplattform) och har upptÀckt ett problem som det visar sig att Àven andra har, nÀmligen:

DÄ man lÀser alarmregistren pÄ en Pingvin Eco EDE sÄ kan maskinen fÄ för sig att aktivera "TE20 YlÀraja, palovaara" alarmet, vilket leder till att hela enheten stÀngs av. Det hÀr kan hÀnda flera gÄnger pÄ dygn, eller sÄ kan det gÄ flera mÄnader mellan alarmen.

https://github.com/Jalle19/eda-modbus-bridge/issues/56 hÀr Àr en annan person som har exakt samma maskin och konfiguration (Pingvin Eco EDE) som jag och som upplever samma problem.

Har ni nÄgon erfarenhet av just den hÀr typen av problem? Finns det nÄnting jag kan göra för att förhindra att enheten gÄr i alarmlÀge? Hittills har jag lÀst av alla 20 "alarmslottar", 7 register i taget, var 10:e sekund. Kan det hÀr pÄverka pÄ nÄgot sÀtt?

Ytterst tacksam för svar!

Med vÀnliga hÀlsningar Sam Stenvall

odelma commented 1 year ago

@odelma can you try changing the publish interval setting to 30 seconds?

Sure thing, changed it to 30 seconds now. Thanks for the prompt reply. I'll report back after a week or so (or sooner if it keeps happening more frequently) if this did the trick. Also hoping Enervent will reply to your query 👍

Jalle19 commented 1 year ago

Got a reply from Enervent:

Ted kan hÀnda att TE20 alarm kommer nÀr man har Modbus kopplat om man inte har en temperaturgivare eller ett motstÄnd kopplad till temperaturgivar-anslutningen pÄ styrpanelen. Man kan anvÀnda en NTC10 givare eller ett motstÄnd pÄ 10kohm för att förhindra detta fenomen.

Translation: the TE20 alarm can be tripped when Modbus is used and no temperature sensor or resistor is plugged in to the main board. Adding an NTC10 sensor or a 10 kiloohm resistor should alleviate the issue completely.

Guess I'll be buying a resistor then.

odelma commented 1 year ago

@odelma can you try changing the publish interval setting to 30 seconds?

Sure thing, changed it to 30 seconds now. Thanks for the prompt reply. I'll report back after a week or so (or sooner if it keeps happening more frequently) if this did the trick. Also hoping Enervent will reply to your query 👍

So far so good, no more errors since then â˜ș

odelma commented 1 year ago

I think that at least from my viewpoint this can be closed. Enervent has provided (a sort of) explanation for the issue and from the looks of it, setting the interval to 30(+) seconds fixes at least the frequent alerts.