Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
MQTT(HA) update Cycle
#1
Hello,

I have a Kincony A16v3. I use the native mqtt integration for home assistant. ( MQTT(HA): ) and can see that the device is continuously updating the binary_sensors. I was wondering why you do this....

I would expect only mqtt messages are send when changes occur... not all the time. So if the input changes, then only at that time a mqtt message is send.

Can this be altered please? I'm considering buying the KC868 but then the mqtt broker will be flooded with messages.

Thanks in advance
Stijn
Reply
#2
if you downloaded KCS v3 firmware, mqtt message will only update when input state is changed or analog data is changed. please take a photo of your mqtt message.
Reply
#3
Hi,

I uploaded multiple screenshots. One of my firmware version, second mqtt explorer (you see a lot of messages and I just started it 20min ago ...) and last ones are 2 screenshots of home assistant broker who is listening to all incoming messages.
Did I miss a firmware version here?

Thanks
Stijn


Attached Files Image(s)
               
Reply
#4
can you test with newest verison v3.9.1 : https://www.kincony.com/forum/showthread.php?tid=7931
Reply
#5
(05-03-2025, 07:55 AM)admin Wrote: can you test with newest verison v3.9.1 : https://www.kincony.com/forum/showthread.php?tid=7931

Sorry, I'm afraid it's the same with v.3.9.1.


Attached Files Image(s)
   
Reply
#6
just power on controller, mqtt message will always upload looply? if YES, i will test it.
Reply
#7
(05-04-2025, 11:22 PM)admin Wrote: just power on controller, mqtt message will always upload looply? if YES, i will test it.

Hello,

I removed all connectors and restarted the device. Messages keep being send towards HA.

Thanks for your test.

Stijn
Reply
#8
you can test with this new firmware fixed mqtt bug, if have any problem after you tested, feedback at here.

.zip   KCS_A16V3_V3.9.2_beta_20250506-211025.zip (Size: 1.08 MB / Downloads: 255)
Reply
#9
Thumbs Up 
Hello,

I can confirm your fix is working perfectly for the digital input and outputs. No updates anymore for states that doesn't change. Smile

I'm afraid the threshold value isn't working for the analog signals. I just discovered this feature today.

For example: adc1
I have following threshold values for my motion detector connected to adc1:
- Custom value1 ( value when adc/dac is 0 ): 0
- Custom value2 ( value when adc/dac is max range ): 0
- Threshold ( Send mqtt when the change of sampling value is greater than it ): 100

I got a result between 1910 & 1950 when no motion is detected and 1500 - 1550 when motion is detected. I can see all changes between 1910 - 1950.
Thanks for the investigation. Great work!!!

Maybe one nice to have to conclude Big Grin ...
If someone changes the name of the input/output/adc within kincony ui, then it would be ideal that this is changed in the "name" field of the discovery message. (I don't think the unique name should change ...)

e.g.
Now
{
  "uniq_id": "D83BDAA886BC_switch_output02",
  "~": "homeassistant/switch/D83BDAA886BCoutput02",
  "name": "output02",
  "device": {
    "name": "A16v3",
    "identifiers": "D83BDAA886BC",
    "manufacturer": "KinCony",
    "model": "A16v3"
  },
  "config_topic": "~/config",
  "avty_t": "D83BDAA886BC/avail",
  "stat_t": "~/state",
  "cmd_t": "~/set",
  "payload_on": "on",
  "payload_off": "off",
  "state_on": "on",
  "state_off": "off"
}

Nice to have name
{
  "uniq_id": "D83BDAA886BC_switch_output02",
  "~": "homeassistant/switch/D83BDAA886BCoutput02",
  "name": "CUSTOM NAME",
  "device": {
    "name": "A16v3",
    "identifiers": "D83BDAA886BC",
    "manufacturer": "KinCony",
    "model": "A16v3"
  },
  "config_topic": "~/config",
  "avty_t": "D83BDAA886BC/avail",
  "stat_t": "~/state",
  "cmd_t": "~/set",
  "payload_on": "on",
  "payload_off": "off",
  "state_on": "on",
  "state_off": "off"
}
Reply
#10
yes, we will update firmware in future, let the KCS monitor webpage's name update to home assistant by mqtt.
Reply


Forum Jump:


Users browsing this thread:
1 Guest(s)