MQTT Sync Issue

Use this forum to discuss possible implementation of a new feature before opening a ticket.
A developer shall edit the topic title with "[xxx]" where xxx is the id of the accompanying tracker id.
Duplicate posts about the same id. +1 posts are not allowed.

Moderators: leecollings, remb0

Post Reply
User avatar
emme
Posts: 909
Joined: Monday 27 June 2016 11:02
Target OS: Raspberry Pi / ODroid
Domoticz version: latest
Location: Milano, Italy
Contact:

MQTT Sync Issue

Post by emme »

I use to sync status between KNX and devices from MQTT

I do sometines have issues with some loops due to repeated telegrams between domoticz/in and domoticz/out topics.

If I switch on a device via MQTT and this device is already On, it generates a telegram in the MQTT topic domoticz/out.

Could it be possible to avoid those kind of messages (or configure it for each device) in case of no state change?

thanks
ciao
M
The most dangerous phrase in any language is:
"We always done this way"
User avatar
FireWizard
Posts: 1905
Joined: Tuesday 25 December 2018 12:11
Target OS: Raspberry Pi / ODroid
Domoticz version: Beta
Location: Voorthuizen (NL)
Contact:

Re: MQTT Sync Issue

Post by FireWizard »

How do you connect KNX to Domoticz?
Are you using Mosquitto as MQTT broker?
If so do you use Node-Red to prepare the topics for Domoticz?
In that case you could probably use a node called RBE (Report by Exception).
User avatar
emme
Posts: 909
Joined: Monday 27 June 2016 11:02
Target OS: Raspberry Pi / ODroid
Domoticz version: latest
Location: Milano, Italy
Contact:

Re: MQTT Sync Issue

Post by emme »

I use KNXJS Node to connect and I already use RBE in the flow to ensure not to send equals payload and send/receive in MQTT to domoticz

I have 2 issues with the flow:
1) same status on the telegrams generate a useless information (blocked by RBE)

2) quick push on the KNX side will generate a loop of 0 / 1 on payload that are not blocked by RBE
this evening I will try insert a delay node of 200ms to see if this could solve the issue

but the problem persists:
Scenario: KNX Off - Domoticz ON
ACTIONS: ON on KNX ==> send ON to domoticz ==> receive ON From Domoticz ==> send ON to KNX ==> Device status does not reply to same status
The receive ON is quite useless

ACTION:
Quick ON/OFF on KNX ==> [KNX] send On to Dz ==> [KNX] send OFF to Dz ==> [DZ] Receive ON ==> [Dz] Receive Off ==> [Dz] Send ON to KNX ==> [KNX] Send ON to Dz==> [Dz] send Off to KNX
Result: LOOP!!!!

this is a big deal to me... but will dig my way out
The most dangerous phrase in any language is:
"We always done this way"
Post Reply

Who is online

Users browsing this forum: Bing [Bot] and 1 guest