Pleased to have the M30 all up and running as expected on a dozen-plus DC loads (12V and 24V). But a few of the loads are over 10A - some as high as 30A - and I'd still like to monitor them. 

It looks to me like the KinCony CTs are only for alternating current? (https://shop.kincony.com/products/25a-cu...eter-board)

Is there a DC option? If so, is there one I can purchase directly? Or a specific part / part-number to look for? 


Alternatively, would I be better off trying to interface RS485 to a separate device of some sort? I see options for JXT CTs with RS485 as another option. 


Thank you.

Is it possible to disable Ethernet and status LEDs (LEDG+ & LEDY+) to reduce power consumption?

Also, can someone confirm if P3 and P8 header pinouts share the same I2C bus?

Thanks

Good morning, I would need to disable the wifi part of the system, as the device must be installed in an area where the presence of wifi systems is not authorized for security reasons. The entire operation of the system is entrusted to physical wiring. Is there such a possibility and how should I proceed? Thank you in advance.

Hello. In the KC868-A2 circuit, the protective diodes D9, D11 are connected in parallel to the transistors, not the relay coils. Is this an error or a feature of the circuit?

Attached Files

Thumbnail(s)
   

Hello,

Greetings from good old Germany.

My question: 

Is it possible to debug the code in Platformio via USB? 

What are the settings in platformio.ini ?

Best regards
Bernd

enable ALR/KC868-A6v3 board LoRaWAN protocol. 
You can set ALR/KC868-A6v3 board work with each other by LoRa "server" or "client" mode.

Attached Files

  KCS_ALR_V3.10.0.zip (Size: 1,001.43 KB / Downloads: 643)
  KCS_A6V3_V3.10.0.zip (Size: 1 MB / Downloads: 696)

Hi!

I've been using the G1 with 4G SIM as a gate opener for a few months now.  Some time ago, the G1 stopped registering incoming calls (RING +441234567890 etc not appearing on screen) and the number was not being sent to my MQTT broker.  I reflashed with the latest firmware available at the time (3.9.1) and everything started working OK again.  The problem has returned.  I've reflashed with the latest firmware (3.9.2) but the incoming call isn't being registered on the screen or being sent over MQTT.  I can send and receive text messages OK and the 4G online signal is 64%.  I can also make a test call from the G1 to my mobile which does cause my phone to ring.

When I first installed the G1, calls to it rang until I cancelled the call.  Shortly after, incoming calls were rejected after 1 ring but the SSID was displayed on the screen and passed over MQTT, a better solution for my use case.  The incoming calls are still rejected after 1 ring, but the call isn't being registered.

Is there something that I can do to return the incoming call/CallerID functionality?

Thanks,

Bodad

Hello

 I have a KC868-A8 that I'm using with Homeassistant via Tasmota.

I'm trying to use it to operate my garage doors and see the reed switches on the doors for status, while still also having my alarm panel work with the doors and reed switches.

The outputs are easy, they work fine, but when I try to share a reed switch the alarm panel isn't happy when I tie in the ESP, and can't see the switch change state and thinks the doot is always open, I'm thinking this is because the inputs on 868 have pull-up turned on!?

Can I change the template string to set all the inputs to no pull-up ? or what do I need to do ?

Template I'm using ; {"NAME":"KC868-A8","GPIO":[32,0,1120,0,640,608,0,0,0,1,1,1152,0,0,5600,0,0,0,0,5568,0,0,0,0,0,0,0,0,1,1,0,0,1,0,0,1],"FLAG":0,"BASE":1,"CMND":"EthClockMode 3 | EthAddress 0 | EthType 0 | I2CDriver2 1"}

Thanks

Justin

Hello all,

Trying to connect a flow meter to the KC868-a6-v1.3sp board. I expect around 500 Hz.
Are there any GPIO pins available for this on the board?

Thank you!

Has anyone else experienced the following behaviour with the ESP32-S3 Core Board:

1. Connect the ESP32-S3 Core Board to the development PC via a USB serial cable.
   
2. Compile the program and upload the binary to the ESP32-S3 Core Board.
   
3. Observation #1: If the development PC is left connected for 2 to 3 hours, the ESP32-S3 Core Board reboots or it goes into an inoperable state that requires a hard reset.
   
4. Observation #2: If the USB serial port's connection is cycled, from connected to disconnected, and then reconnected a couple of times, the ESP32-S3 Core Board reboots.
   
5. Observation #3: If the USB serial cable is disconnected, the ESP32-S3 Core Board operates flawlessly.  The ESP32-S3 Core Board was left powered for a 7-day burn-in with no reboots or memory leaks.