Listening to the bus is realy unreliable as I often (60% of the time) have no code in the log.

I can see the LED on the board react when picking up the phone or pressing the bell but no entry in the logbook.

I have reinstalled the mqtt-broker (as the device disappeared sometimes and I hoped to fix booth problems) and even installed a different one but no improvement for now for this problem (the esp stopped disappearing).

This is the wiring at the moment with external powersupply and without the parts for button and led.

Building for D1 mini failed with the following error:

src\main.cpp: In function 'void callback(char*, byte*, unsigned int)':
src\main.cpp:389:14: warning: unused variable 'pressed' [-Wunused-variable]
  389 |         bool pressed = strncmp((char *)payload, g_mqttView.getDiagnosticsResetButton().getPressState(), length) == 0;
      |              ^~~~~~~
src\main.cpp: In lambda function:
src\main.cpp:511:9: error: 'esp_task_wdt_reset' was not declared in this scope
  511 |         esp_task_wdt_reset();
      |         ^~~~~~~~~~~~~~~~~~
*** [.pio\build\d1_mini\src\main.cpp.o] Error 1

I think it has to do something with the most recent changes in the code..

Help Wanted (as I can not add labels)

Is it possible to integrate the E line into the microcontroller, which is used for the bell button in front of the apartment door, so I can work with it in Homeassistant?

I would only want it to be the same like the the bell button on the front door, but I guess this one does not run over the bus, so it would only need to register if there is a signal or not which I then would use to create a signal in Homeassistant I can automate with.

This is my first little project and pretty much my first time wiring, soldering and programming stuff like this so it´s a little to much for me.
Im only asking for help with the wiring, the programming I would probably manage by myself somehow.

I had some questions regarding functions, I can split the issue if needed and I would try to add it to the Readme if that would be okay (I like documentation)

1:
How exactly do I create a pattern to be recognized? If I understand description on the "codes" page running on the ESP they should be a hexadezimal number, how do I write a pattern in hexadezimal, or is it meant as "if this code is detected..."?

2:
If I understood the project-code correctly, if I press one of the "Controls" on the device in Homeassistant the ESP sends the configured code on the bus and the correlating function should happen (door opener, bell rings) right? If not the text after this can be ignored as its written with the assumption that it works that way.

Its not working for me as it does not happen with any "Control" I try to activate, no bell and no opener.
I can see that the code change on the bus but nothing else happens.

I have checked the codes multiple times and they should be correct so I dont know why it does not work.

The wifi reconnect feature uses esp_restart which is not able to compile on an ESP8622.

Description:
When building the project for a d1-mini in VsCode with Platformio on Windows I get the following error message.

I have tried finding where that file comes from but I can only find it online as part of this github "https://github.com/pycom/esp-idf-2.0/blob/master/components/esp32/include/esp_task_wdt.h".
Is it part of some ESP32 libraries which cant be used on a ESP8266 board?

Trace:

Processing d1_mini (platform: espressif8266; board: d1_mini; framework: arduino)
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------Verbose mode can be enabled via `-v, --verbose` option
CONFIGURATION: https://docs.platformio.org/page/boards/espressif8266/d1_mini.html
PLATFORM: Espressif 8266 (4.2.1) > WeMos D1 R2 and mini
HARDWARE: ESP8266 80MHz, 80KB RAM, 4MB Flash
PACKAGES:
 - framework-arduinoespressif8266 @ 3.30102.0 (3.1.2)
 - tool-esptool @ 1.413.0 (4.13)
 - tool-esptoolpy @ 1.30000.201119 (3.0.0)
 - toolchain-xtensa @ 2.100300.220621 (10.3.0)
LDF: Library Dependency Finder -> https://bit.ly/configure-pio-ldf
LDF Modes: Finder ~ chain, Compatibility ~ soft
Found 44 compatible libraries
Scanning dependencies...
Dependency Graph
|-- ArduinoJson @ 6.21.5
|-- PubSubClient @ 2.8.0
|-- libesplog @ 0.0.1+sha.335d30f   
|-- libmqttdisco @ 0.0.1+sha.af15d5c
|-- ArduinoOTA @ 1.0
|-- DNSServer @ 1.1.1
|-- ESP8266mDNS @ 1.2
|-- ESP8266WebServer @ 1.0
|-- ESP8266WiFi @ 1.0
|-- LittleFS @ 0.1.0
|-- tcsbus
|-- pattern
Building in release mode
Compiling .pio\build\d1_mini\src\main.cpp.o
Archiving .pio\build\d1_mini\lib328\libPubSubClient.a
Archiving .pio\build\d1_mini\lib316\libesplog.a
Archiving .pio\build\d1_mini\lib1d7\libmqttdisco.a
Compiling .pio\build\d1_mini\liba26\ESP8266WiFi\WiFiClientSecureBearSSL.cpp.o
Compiling .pio\build\d1_mini\liba26\ESP8266WiFi\WiFiServer.cpp.o
Compiling .pio\build\d1_mini\liba26\ESP8266WiFi\WiFiServerSecureBearSSL.cpp.o
Compiling .pio\build\d1_mini\liba26\ESP8266WiFi\WiFiUdp.cpp.o
Compiling .pio\build\d1_mini\liba26\ESP8266WiFi\enable_wifi_at_boot_time.cpp.o
Compiling .pio\build\d1_mini\lib938\ESP8266mDNS\ESP8266mDNS.cpp.o
Compiling .pio\build\d1_mini\lib938\ESP8266mDNS\LEAmDNS.cpp.o
Compiling .pio\build\d1_mini\lib938\ESP8266mDNS\LEAmDNS_Control.cpp.o
Compiling .pio\build\d1_mini\lib938\ESP8266mDNS\LEAmDNS_Helpers.cpp.o
Compiling .pio\build\d1_mini\lib938\ESP8266mDNS\LEAmDNS_Structs.cpp.o
Compiling .pio\build\d1_mini\lib938\ESP8266mDNS\LEAmDNS_Transfer.cpp.o
Compiling .pio\build\d1_mini\lib85e\ArduinoOTA\ArduinoOTA.cpp.o
Compiling .pio\build\d1_mini\lib720\DNSServer\DNSServer.cpp.o
Compiling .pio\build\d1_mini\lib3ba\ESP8266WebServer\detail\mimetable.cpp.o
Compiling .pio\build\d1_mini\lib68b\LittleFS\LittleFS.cpp.o
Archiving .pio\build\d1_mini\lib3ba\libESP8266WebServer.a
src\main.cpp:27:10: fatal error: esp_task_wdt.h: No such file or directory

**********************************************************************
* Looking for esp_task_wdt.h dependency? Check our library registry!
*
* CLI  > platformio lib search "header:esp_task_wdt.h"
* Web  > https://registry.platformio.org/search?q=header:esp_task_wdt.h
*
**********************************************************************

   27 | #include <esp_task_wdt.h>
      |          ^~~~~~~~~~~~~~~~
compilation terminated.
*** [.pio\build\d1_mini\src\main.cpp.o] Error 1
======================================================================================================== [FAILED] Took 3.43 seconds ========================================================================================================

Hey,

first, thanks for the project/work.

I wanted to start using it, but have no clue how to compile/build the project and how to flash it.
Would it be possible to write a short guide/documentation on how to build and flash it?

Thanks in advance.

Hi,

erstmal vielen Dank für dieses Projekt 💯

Ich bin derzeit dabei mit Hilfe deines Codes eine ESPHome Komponente zu schreiben (Ich werde das Ergebnis dann gern zur Verfügung stellen wenn alles funktioniert) und habe dabei auch im allgemeinen versucht die Hardware weitestgehend zu verkleinern und auf das Minimum zu reduziere, damit das ganze problemlos in eine Unterputzdose hinter der Gegensprechanlage passt.

Nun hoffe ich dass ich dabei alle Verbindungen und Komponenten berücksichtigt habe und noch alles korrekt verbunden ist.
Der D1 Mini ist jetzt zum aufstecken vorgesehen, falls es mal zu einem Defekt kommen sollte.

Habe ich irgendwas beim Schaltplan vergessen?

Hello,
i'm in the process of using the project.
Reading the bus is no problem, but writing doesn't work in my case.
When I send the code to open the door, nothing happens.

am i the only one with the problem?

Best Regards
Julian

Hello,
I am enthusiastic about your project and have soldered together a board according to the instructions. Flashing the d1mini also worked without any problems. The connection to Homeassistant also works. Unfortunately, I do not get any values displayed in the TCS bus. Is it possible to narrow down the source of the error?
I have attached a picture of the circuit board and the wall unit.

I tried it with USB power supply, and also flashed different d1 minis. for the 147kohm I connected 100 and 47 in series.

Regards

New Thread für die TC30 Integration von Koch

Ziel:

• Test ob Doorman mit TC30 funktioniert Out of the box

Folgendes wurde bereits geklärt in Issue Board Design Frage mit @AzonInc

• TC30 KOCH ist die CH (Schweizer) version von TCS
• a (DC+) und b (DC-) sind auf 24v
• 6ms, 2ms, 4ms datenblöcke sind vorhanden
• Steuergerät ist vermutlich BVS20

TC30 Anschluss Platte

Anmerkung zum Bild: bei a + b sind ein schwarzes und weisses Kabel zusätzlich angehängt - diese sind separat und gehören nicht zur TC30 installation. Sie wurden für die Nello installation verwendet.

Tür Öffnungs Trigger

Hier noch die Schemas von TC:Bus plus Beiblatt
Schema TC_Bus _ 1 Eingang, Anbindung an IP-Netzwerk, pot.freier Türöffnerkontakt - TC204_AVS 2100_LR12ACF.pdf
Beiblatt zu Schemas TCBus.pdf
Beiblatt zu Schemas TCBus.pdf
Schema TC_Bus _ 1 Eingang, Anbindung an IP-Netzwerk, pot.freier Türöffnerkontakt - TC204_AVS 2100_LR12ACF.pdf

Um die Diskussion von 3d Gehause und PCB etwas zu isolieren hier das Issue fuers 3d Case.

Hi, can you please explain to me how exactly the TCS Reader works? Unfortunately I am not very familiar with the used language in this project as is. As I am working on a similar project (but on raspberry pico with micropython), and my approach is not really working (I get a different message every time I ring my bell), I appreciate any help and/or explanation. What really confuses me is the fact, that one message I have recorded seems to be the correct one, If I am writing this message to the bus, my bell rings. But as I said, my reader reads a different message every time (and therefore it is not reliable). thank you very much!