MQTT AT command debug for KC868-A8S:

publish message to MQTT broker:

1. AT+CMQTTSTART
2. AT+CMQTTACCQ=0,"KinCony1"
3. AT+CMQTTCONNECT=0,"tcp://iot.kincony.com:1883",120,1,"mqtt","123"
4. AT+CMQTTTOPIC=0,18
5. > relay8/12345/state
6. AT+CMQTTPAYLOAD=0,19
7. > {"relay1":{"on":1}}
8. AT+CMQTTPUB=0,1,60

this is puslish a message for update MQTT broker relay state when relay1 is ON

subscribe topic from MQTT broker:

AT+CMQTTSUB=0,16,1,1
relay8/12345/set

will receive example message:

+CMQTTRXSTART: 0,16,3
+CMQTTRXTOPIC: 0,16
relay8/12345/set
+CMQTTRXPAYLOAD: 0,3
abc
+CMQTTRXEND: 0

this is demo for receive message: abc

+CMQTTRXSTART: 0,16,19
+CMQTTRXTOPIC: 0,16
relay8/12345/set
+CMQTTRXPAYLOAD: 0,19
{"relay1":{"on":0}}
+CMQTTRXEND: 0

this is demo for receive message: {"relay1":{"on":0}}


here is arduino IDE source code: 
  mqtt-relay.zip (Size: 1.35 KB / Downloads: 642)

  SIM7500_SIM7600 Series_MQTT_ATC_V1.01.pdf (Size: 740.41 KB / Downloads: 746)

send SMS text:

1. turn on/off one relay:

relay1-on    turn ON relay1
relay1-off    turn OFF relay1
relay2-on    turn ON relay2
relay2-off    turn OFF relay2
relay3-on    turn ON relay3
relay3-off    turn OFF relay3
relay4-on    turn ON relay4
relay4-off    turn OFF relay4
relay5-on    turn ON relay5
relay5-off    turn OFF relay5
relay6-on    turn ON relay6
relay6-off    turn OFF relay6
relay7-on    turn ON relay7
relay7-off    turn OFF relay7
relay8-on    turn ON relay8
relay8-off    turn OFF relay8

2. turn on/off all relay:

all-on  turn ON relay1-8
all-off  turn OFF relay1-8

3. read current temperature value:

temper      read DS18B20 temperature sensor data

4. digital input for sensor trigger output

a. if input1 trigger, (siren) relay1 ON -> 3 seconds -> relay1 OFF -> send SMS: door sensor is triggered,someone in the room!
b. if input2 trigger, (siren) relay1 ON -> 3 seconds -> relay1 OFF -> send SMS: window sensor is triggered,someone in the room!
c. if input3 trigger, send SMS: sensor3 is triggered,someone in the room!
d. if input4 trigger, send SMS: sensor4 is triggered,someone in the room!
e. if input5 trigger, send SMS: sensor5 is triggered,someone in the room!
f.  if input6 trigger, send SMS: sensor6 is triggered,someone in the room!
g. if input7 trigger, send SMS: sensor7 is triggered,someone in the room!
h. if input8 trigger, send SMS: sensor8 is triggered,someone in the room!


here is arduino IDE source code: 
  sms-relay.zip (Size: 1.71 KB / Downloads: 696)

1. Test

AT

2. make a CALL

ATD13100000000;

3. receive a CALL

RING            display receive information
ATA              Answer the phone
AT+CHUP    Hang up

4. receive a SMS

+CMTI: "SM",1    display receive information
AT+CMGR=1        read No.1 SMS
AT+CMGL="ALL"  read all SMS
AT+CMGD=1        delete No.1 SMS
AT+CMGD=1,4    delete all SMS

5. send a SMS

AT+CMGF=1  set SMS mode=TEXT
AT+CMGS="phone number"
> this is a text sms from KinCony
send Ctrl+Z or HEX (0x1A)

arduino IDE source code for GSM serial port debug:
  AT-debug.zip (Size: 282 bytes / Downloads: 599)

  SIM7500_SIM7600 Series_AT_Command_Manual _V1.10.pdf (Size: 4.53 MB / Downloads: 811)

Attached Files

  AT-SSCOM.zip (Size: 410.09 KB / Downloads: 612)

Hello,

When I use the momentary switch of a relay in combination with Mqtt, I am able to make the kincony ethernet "hang".


It seems to occur when the Kincony had to process commands during the momentary switch.
  - Note: while I do not receive the state on mqtt, the relay have well-executed the momentary switch
  - When a bug occurs:
     - the ethernet is completely stuck; no ping, no HTTP server, no mqtt
     - HTTP UI for wifi (on another IP is still working)
     - Only possible recovery is a Hard reboot (reset of wifi is not working)


My reproduction method: 
 - Put Relay1 with momentary switch 1 seconds
 - send 2 mqtt command:
    - `mosquitto_pub -t "relay32/dddd/set` -m "{\"relay1\":1}" 
    - `sleep 0.5`
    - `mosquitto_pub -t "relay32/dddd/set` -m "{\"relay1\":1}"


I also reproduced it with the embedded HTTP page just by insisting when relay state is "wrong".

I tried to update to the latest version (44) but it does not seem to help.


Have you any idea on how to mitigate that?

home assistant MQTT breaking changes RC 2022.6

before MQTT config format:

switch:
  - platform: mqtt
    name: 'relay11'
    unique_id: relay11
    state_topic: 'relay32/80f9caa4068e78059e31c622/state'
    command_topic: 'relay32/80f9caa4068e78059e31c622/set'
    payload_on: '{"relay1":{"on":1}}'
    payload_off: '{"relay1":{"on":0}}'
    value_template: '{{ value_json.relay1.on }}'
    state_on: 1
    state_off: 0


new MQTT config format:

mqtt:
  switch:
  - name: 'relay11'
    unique_id: relay11
    state_topic: 'relay32/80f9caa4068e78059e31c622/state'
    command_topic: 'relay32/80f9caa4068e78059e31c622/set'
    payload_on: '{"relay1":{"on":1}}'
    payload_off: '{"relay1":{"on":0}}'
    value_template: '{{ value_json.relay1.on }}'
    state_on: 1
    state_off: 0


new MQTT config for two switches format:

mqtt:
  switch:
  - name: 'relay11'
    unique_id: relay11
    state_topic: 'relay32/80f9caa4068e78059e31c622/state'
    command_topic: 'relay32/80f9caa4068e78059e31c622/set'
    payload_on: '{"relay1":{"on":1}}'
    payload_off: '{"relay1":{"on":0}}'
    value_template: '{{ value_json.relay1.on }}'
    state_on: 1
    state_off: 0
   
  - name: 'relay22'
    unique_id: relay22
    state_topic: 'relay32/80f9caa4068e78059e31c622/state'
    command_topic: 'relay32/80f9caa4068e78059e31c622/set'
    payload_on: '{"relay2":{"on":1}}'
    payload_off: '{"relay2":{"on":0}}'
    value_template: '{{ value_json.relay2.on }}'
    state_on: 1
    state_off: 0

Attached Files

Thumbnail(s)
       

  before.txt (Size: 354 bytes / Downloads: 508)
  now-2-switches.txt (Size: 695 bytes / Downloads: 565)
  now.txt (Size: 352 bytes / Downloads: 563)

Hi, I have some questions regarding the KC868-A16 board, please answer as follows:

1. I have a INPUT signal which is either connected to (common) GND or 5V. Will the inputs recognize this correctly?

2. I have an actor, type 1 (OUTPUT) which supports 5V and needs to be connected to GND when switched. Will this work?

3. I have an actor, type 2 (OUTPUT) which will need 15V output. Will this voltage be okay (instead of 12V)?

1. latch mode: Button1

    on_press:
      then:
      - switch.toggle: e16s_output1


2. inching mode: Button2

    on_press:
      then:
      - switch.turn_on: e16s_output2
    on_release:
      then:
      - switch.turn_off: e16s_output2 


3. momentary mode: Button3

    on_turn_on:
    - delay: 1000ms
    - switch.turn_off: e16s_output3


4. interlocking mode: Button4-Button5

interlock: [e16s_output5]

interlock: [e16s_output4]


  KC868-E16S-ESPHome-Config-buttons-work-mode.txt (Size: 6.36 KB / Downloads: 582)

Are there any plans to add TWAI (CANBUS) controler e.g.with SN65HVD23x instead of RS-232/RS-485? 

With CANBUS it's easy to daisy-chain any number of boards whereas RS-232/RS-485 are tricky to add more than just 1 additional board. 
I would preffer setup with several smaller boards - e.g. 4-6 relays/inputs and ability to add more when needed rather than aiming for maximum planned IOs.

Please add comments if anyone else would be ineterested in it.

To enable the USB 2.0 ports on the Compute Module 4, you need to edit the boot config file (/boot/config.txt) and add:

dtoverlay=dwc2,dr_mode=host
Then reboot the Pi. Now you should be able to use the built-in USB 2.0 ports!