@KinCony: can you please have a look at what is happening with the Mqtt Broker Password setting?
Today, again, the password got changed somehow from
cgAn6fAJW9LWqDX
to
cgAn6fAJW94赙kHX�
in the webUI
It’s not only an aesthetic change because the relay module does not respond and only after changing the password again, it works.
which controller model you are using? H32B? H32BS? what’s firmware version you are using?
KC868-H16 with F/W H16B_V4.29
It seems that every time the relay is cut from power the MQTT password is changed by swapping the end part with the same characters.
you can download newest firmware V4.35 for update: KC868-H16B V4.35 new firmware update
new firmware have solved your problem.
Any progress on the watchdog ?
My KC868-H32B is losing its MQTT connection despite having removed all the valves from the relays.
can you draw a photo how your valve connect with RC snubber? I think it is the best way to solve the problem in essence according to circuit. Adding a watchdog is only the final helpless way
I would not ask for a watchdog if I had not already tried everything (as show here, I followed your instructions for the RC snubber).
take a photo of your controller and valve connection and draw a diagram on the paper how you wire.
just click on the link on my previous message
when your MQTT can’t use, whether http work well, you can also login with your ip in web browser use webpage to turn on/off. please confirm this.
Circumventing a buggy MQTT implementation by having Home Assistant constantly poll the Kincony device for relay status changes is preposterous.
I bought the KC868-32HB because it included MQTT and trusted it would work flawlessly given its price tag.
If I had known that I’d have to use its http API, I would have kept working on way cheaper SR-201 boards.
Just putting it out there, could this be a problem with back EMF from the coils in the relays.
Looking at the schematic there’s only free wheeling protection on the ULN2003 Darlington arrays. There should be a back EMF diode protection directly at the terminals of each relay coil.
Theres been some discussion about snubber circuits but i think the problem lays on the coil side of the relays.
Could the electrical noise from the coils be causing this corruption in the code (password credentials)?
give me your email, i send you new firmware updated for H32B, Mqtt is optimized.
I updated the firmware on Saturday and the MQTT connection froze again after less than 48 hours.
when froze, do you have controled your relay then begin froze? or do nothing , just wait a long time will froze?
What I mean by frozen is that the Kincony device disconnects from MQTT and does not let any relay be operated through MQTT commands.
The only way to recover the MQTT service is to power-cycle it.
Note that it happened twice this morning within 40 minutes.
UPDATE: it’s been working without freezing for 14 days in a row
Webserver of kincony is constantly crashing … spend way to many money in kincony. It’s unstable and not reliable .
Hi Jordy.
Since the last firmware update, MQTT has been pretty stable on my KC868-H32.
What for do you use the web interface ?
Apart from setting up the device initially, I did not use it anymore.