Comments (9)
The reason they are send out is that they are part of the status byte message, I have no way of know if a system has them or not, they are just part of the protocol.
I am not planning to leave them out at this point or making it configurable. Besides a bit of bandwidth waste.
from otgw-firmware.
Hello Ruud,
I'd liked to reopen this issue, or maybe open a new issue.
Due to the large ammount of OTGW messages it looks like Domoticz is running out of memory which ends in a Domoticz Crash.
The problem is that slowly the memory increases, and, after 12 hours, a crash. This process cycles every 12 hours.
I use OTGW-Domoticz-MQTT-Client from proditaki to get the MQTT messages from OTGW Firmware via my MQTT-broker in Domoticz.
Yesterdag morning I stopped the OTGW MQTTClient hardware, and the memory issue stopped.
Proditaki asked me to address the issue here.
I think limiting the messages to only the one used by the specific boiler/thermostat will solve this problem.
Thank you
from otgw-firmware.
Isn't this more of a Domoticz (or OTGW-Domoticz-MQTT-Client) issue? reducing the amount of messages won't 'solve' domiticz bug, but just slow down the point time it takes to run out of memory?
from otgw-firmware.
It's only with this hardware. That's why I started with a issue at OTGW-Domoticz-MQTT-Client from proditaki.
He asked me to issue this here.
from otgw-firmware.
@PvdGulik, I hate to tell you but this looks like a memory bug in Domoticz or the plugin as @DaveDavenport already mentioned. Even if the messages would be reduced it might not fix your issue but just postpone it.
For now, you can reduce the amount messages by
- unchecking the
MQTT OT msg Enable
option on the config page. - going to the File explorer, downloading mqttha.cfg, removing all entities you don't want in Domoticz*, uploading it via file explorer with the original filename (overwriting the original) and rebooting the OTGW nodeMCU
*looking at how @proditaki implemented the plugin, he is parsing the Home Assistant Discovery. So whatever is NOT in the HA autodiscovery, will not show up in your Domoticz and won't accelerate the Domoticz Memory Bug.
from otgw-firmware.
First I tried is the "unchecking the MQTT OT msg Enable option on the config page"
I'll report tomorrow the result.
Next step will editing mqttha.cfg.
Keep you informed.
from otgw-firmware.
Well, that didn't solve anything, same result ;-(
I'll try editing mqttha.cfg
from otgw-firmware.
Oke, I've edited mqttha.cfg. I disabled all with // at the beginning of the line.
Then only actived the ones I use and rebooted. Also in Domoticz all the devices created which I don't use are disabled.
After reboot Domoticz and OTGW NodeMCU, still 34 Sensors and Switch which I don't use in Domoticz are updated on regular basis. 15 of them are updated every 3 seconds.... Why?
These are:
1344 | OTGW MQTT Client | 00270019 | 25 | OTGW MQTT Client - OTGW_Fault | Light/Switch | Switch | Off | - | - | 2021-03-27 12:36:41 | ||
---|---|---|---|---|---|---|---|---|---|---|---|---|
1345 | OTGW MQTT Client | 0027001A | 26 | OTGW MQTT Client - OTGW_Central_Heating | Light/Switch | Switch | Off | - | - | |||
1346 | OTGW MQTT Client | 0027001B | 27 | OTGW MQTT Client - OTGW_Domestic_Hot_Water | Light/Switch | Switch | Off | - | - | |||
1347 | OTGW MQTT Client | 0027001C | 28 | OTGW MQTT Client - OTGW_Flame | Light/Switch | Switch | Off | - | - | |||
1348 | OTGW MQTT Client | 0027001D | 29 | OTGW MQTT Client - OTGW_Cooling | Light/Switch | Switch | Off | - | - | |||
1349 | OTGW MQTT Client | 0027001E | 30 | OTGW MQTT Client - OTGW_Central_Heating_2 | Light/Switch | Switch | Off | - | - | |||
1350 | OTGW MQTT Client | 0027001F | 31 | OTGW MQTT Client - OTGW_Diagonostic_Indicator | Light/Switch | Switch | Off | - | - | |||
1355 | OTGW MQTT Client | 00270024 | 36 | OTGW MQTT Client - OTGW_central_heating_2_enable | Light/Switch | Switch | Off | - | - | |||
1437 | OTGW MQTT Client | 00270076 | 118 | OTGW MQTT Client - OTGW_Status_Slave | General | Custom Sensor | 0 # | - | - | |||
1354 | OTGW MQTT Client | 00270023 | 35 | OTGW MQTT Client - OTGW_OTC_enable | Light/Switch | Switch | Off | - | - | |||
1351 | OTGW MQTT Client | 00270020 | 32 | OTGW MQTT Client - OTGW_Central_Heating_enable | Light/Switch | Switch | Off | - | - | |||
1352 | OTGW MQTT Client | 00270021 | 33 | OTGW MQTT Client - OTGW_Domestic_Hot_Water_enable | Light/Switch | Switch | Off | - | - | |||
1353 | OTGW MQTT Client | 00270022 | 34 | OTGW MQTT Client - OTGW_Cooling_enable | Light/Switch | Switch | Off | - | - | |||
1436 | OTGW MQTT Client | 00270075 | 117 | OTGW MQTT Client - OTGW_Status_Master | General | Custom Sensor | 0 # | - | - | |||
1413 | OTGW MQTT Client | 0027005E | 94 | OTGW MQTT Client - OTGW_Return_water_temperature | Temp | LaCrosse TX3 | 1.0 C | - | - |
I don't use them, because the give no real info e.g. Return_water_temperature 1.0C. They are updated every 3 seconds. Why? And is this why I have a Domoticz_memory problem? The memory-use is already rising again ;-(
from otgw-firmware.
I think @proditaki needs to look at the domoticz plug-in. As your memory issue is not cause by the messages itself. Reducing the number of message will only delay the problem.
The root cause needs to be addressed.
The sensors and switches are generated based on the specification. As the setup is generic and standard based. It generates topics based in the messages that are being send.
It’s also different for each thermostat and boiler. So making it less generic or more configurable over complicates the whole setup.
The amount of messages and frequency should not be an issue, filtering can be done downstream.
I push on change approach. The real problem with that is when you lose connectivity or values do not change for a long time. Than you could be out of sync.
from otgw-firmware.
Related Issues (20)
- Settings menu not loading HOT 6
- Home Assistant 20223.5.0 now throwing exception HOT 21
- Web Interface 'PIC firmware' view empty after firmware upgrade HOT 1
- Domoticz gives multiple Connection reset messages HOT 4
- Cannot upgrade firmware HOT 1
- MQTT hotwater settopic value description incorrect HOT 1
- Home Assistant mqtt errors HOT 1
- Web UI Gateway Mode always false HOT 2
- Adding commands to serial data causes problems with native HA integration HOT 1
- OTGW OTA firmware upgrade failed HOT 2
- OTGW HW reboot cause: Exception (2) - Access to invalid address (29) HOT 2
- Ping problems HOT 10
- OTGW connection is lost HOT 10
- Feature: expose current DHW tank temperature to MQTT HOT 2
- Status_master expected to be numeric by Home Assistant HOT 6
- Report return water temperature from OTGW using MQTT HOT 4
- No MQTT updates after reboot HA or Domoticz HOT 5
- RelModLevel not sent over MQTT (but present in API) HOT 2
- Gateway stops working after a few days of not being used HOT 18
- Firmware of V2 hardware HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from otgw-firmware.