bsimmo
commented
9 months ago Odd, I've not had problems sending sensor data or others data over mqtt when this has also been running.
Just don't the send code and add to that.
On Thu, 5 Oct 2023, 16:30 Hans, @.***> wrote:
I am looking for placeholder spots in the code where i can add additional data points coming from the RPI. This is to leverage the GPIO functionality more and used the MQTT push RPI-Reporter uses to share the info to HA
An example will be an I2C environment sensor module or a RPI UPS module.
The problem is that MQTT is very finiky when you have multiple pushes coming from the same end-point (same RPI). Request is easily identifiable spots where to add custom code without breaking the core RPI-Reporter functionality
— Reply to this email directly, view it on GitHub https://github.com/ironsheep/RPi-Reporter-MQTT2HA-Daemon/issues/111, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACYAXN45FJSJ6P3FYXTSTQLX53HCVAVCNFSM6AAAAAA5UOSJZCVHI2DSMVQWIX3LMV43ASLTON2WKOZRHEZDQNJWGQ2DGNA . You are receiving this because you are subscribed to this thread.Message ID: @.***>
I am looking for placeholder spots in the code where i can add additional data points coming from the RPI. This is to leverage the GPIO functionality more and used the MQTT push RPI-Reporter uses to share the info to HA
An example will be an I2C environment sensor module or a RPI UPS module.
The problem is that MQTT is very finiky when you have multiple pushes coming from the same end-point (same RPI). Request is easily identifiable spots where to add custom code without breaking the core RPI-Reporter functionality