ET Nice DC Blue Advanced e-comms

[kerbero]

Home Assistant : Q&A, Tips & Tricks, Your Configs

Not really, there are projects for getting a modbus TCP gateway running on ESP32 but most people use the ESP32 Dev kit: https://tasmota.github.io/docs/Modbus-Bridge/ https://github.com/zivillian/esp32-modbus-gateway That can then theoretically be used with https://github.com/kellerza/sunsynk...

mybroadband.co.za

I have captured the output on the Data+ terminal of my DC Blue Advanced with a logic analyser in PulseView. Data- stays low all the time, so it does not have data on it. Maybe Data- is the RX of the Motor.

The PulseView captures are attached for the following scenarios:
* Garage door open - we can see a minutely "check in"
* Garage door closed, opening, opened, until the light goes out
* Garage door openend, closing, closed, until the light goes out

It looks like a 1024 baud UART, but perhaps it's something else. The motor transmits a "check in" or "keep alive" message every 60 seconds. We see a message when the door starts to open, when it finished opening and when the light goes out. Same for the closing scenario.

Does anyone have any other idea what this is? It does not look like the T4 CAN protocol like described at https://github.com/xdanik/Nice_BusT4

 

[Gambit]

Home Assistant : Q&A, Tips & Tricks, Your Configs

Not really, there are projects for getting a modbus TCP gateway running on ESP32 but most people use the ESP32 Dev kit: https://tasmota.github.io/docs/Modbus-Bridge/ https://github.com/zivillian/esp32-modbus-gateway That can then theoretically be used with https://github.com/kellerza/sunsynk...

mybroadband.co.za

View attachment 1680789

I have captured the output on the Data+ terminal of my DC Blue Advanced with a logic analyser in PulseView. Data- stays low all the time, so it does not have data on it. Maybe Data- is the RX of the Motor.

The PulseView captures are attached for the following scenarios:
* Garage door open - we can see a minutely "check in"
* Garage door closed, opening, opened, until the light goes out
* Garage door openend, closing, closed, until the light goes out

It looks like a 1024 baud UART, but perhaps it's something else. The motor transmits a "check in" or "keep alive" message every 60 seconds. We see a message when the door starts to open, when it finished opening and when the light goes out. Same for the closing scenario.

Does anyone have any other idea what this is? It does not look like the T4 CAN protocol like described at https://github.com/xdanik/Nice_BusT4

@kerbero this looks interesting, did you manage to figure what the protocol is?

 

[hilt_ctn]

What's the ultimate goal here ?

 

[Gambit]

Currently use an esp32 and magnetic contact sensor to automate my garage door with home assistant. If I could connect the esp32 directly the dc blue advanced and get open, close, is opening, is closed states directly from the MCU then it would make my automation a quite more smarter and I could ditch the magnetic contact sensor.

 

[Brandon]

Recently got a DC Blue Advanced, was also hoping to use the e-coms data for HA integration.

Got some very different readings to the OP's though, wondering if something has changed with the firmware?

On mine, only ever seen 2 message types transmitted and they relate to the courtesy light being on or off regardless of door position or movement, even on activation or at the end of a cycle - these messages only change with the light.

Light is on:


Light is off:


So not very encouraging. But what is interesting is the manual mentions "open/close status indication", will try contacting them to find out more.

Also, Data- is ground. Data+ sends data out continuously.

Otherwise I'm considering getting the status readings from the 7 segment, either non invasively with a bunch of photocells or void it's warranty and connect directly.
Even then this thing only shows "opening", "closing" and "stopped" so mag sensors or limit switches on the rail / door at both end positions would also be needed to get "open" and "closed" states.

 

[D4N_CPT]

This video shows the E-Coms module and port in action.

The presenter said something in the line of "The e-coms module will now duplicate what is done on the DC Blue Advance." This might explain why @Brandon is getting different msgs from @kerbero

Did anyone make any progress on this project?

I am about to install an ESP Control Panel close to my motor and I am wondering if I should run a serial line to the Motor Control or just tap the alarm's magnetic reed switches.

 

[Gambit]

This video shows the E-Coms module and port in action.

The presenter said something in the line of "The e-coms module will now duplicate what is done on the DC Blue Advance." This might explain why @Brandon is getting different msgs from @kerbero

Did anyone make any progress on this project?

I am about to install an ESP Control Panel close to my motor and I am wondering if I should run a serial line to the Motor Control or just tap the alarm's magnetic reed switches.

I started putting together a prototype using an esp32 dev board and esphome while I was on leave in December but I haven't had a chance to test it yet as we had the inlaws visiting for the last 2 weeks

 

[kerbero]

I have implemented the protocol according to what I saw from my motor as an ESPhome component:

GitHub - jpmeijers/dc-blue-esphome: ET/Nice DC Blue Advanced garage door motor component for ESPhome

ET/Nice DC Blue Advanced garage door motor component for ESPhome - jpmeijers/dc-blue-esphome

github.com

I also made a PCB:

DC Blue Advanced ESPhome

10 new items · Album by JP Meijers

photos.app.goo.gl

Testing still needs to be done on another DC Blue Advanced. I know someone in town with one where I need to get to.

The messages change depending on the lock settings of the DC Blue Advanced. But I have seen default ones that are always sent, and those are the ones I currently interpret.

 

[Gambit]

I have implemented the protocol according to what I saw from my motor as an ESPhome component:

GitHub - jpmeijers/dc-blue-esphome: ET/Nice DC Blue Advanced garage door motor component for ESPhome

ET/Nice DC Blue Advanced garage door motor component for ESPhome - jpmeijers/dc-blue-esphome

github.com

I also made a PCB:

DC Blue Advanced ESPhome

10 new items · Album by JP Meijers

photos.app.goo.gl

Testing still needs to be done on another DC Blue Advanced. I know someone in town with one where I need to get to.

The messages change depending on the lock settings of the DC Blue Advanced. But I have seen default ones that are always sent, and those are the ones I currently interpret.

This is looks like awesome work. Going to take a look this weekend. I see you went with an optocoupler for the data connection. I just did a basic voltage divider with resistors. Was thinking of using an optocoupler for safety but was to lazy to order one for my prototype.

 

[kerbero]

I ordered some extra assembled PCBs, so if anyone wants to take one over at cost (including case and connectors), give me a shout.

 

[Gambit]

I ordered some extra assembled PCBs, so if anyone wants to take one over at cost (including case and connectors), give me a shout.

Hi @kerbero , I have sent you a private message.