scs_bridge Intercom in HA

[MattWestb]

First thanks for great work done !!!

I trying implementing one ESP32C3 for sniffing the house intercom and have getting great steps forward and some no go scenarios.

First it looks your code is braking RISC-V support in ESPHome (looks like many integrations / parts have that problem).
From the ESPHome compiling log:

Processing esp32-c302 (board: esp32-c3-devkitm-1; framework: arduino; platform: platformio/espressif32@5.4.0)
--------------------------------------------------------------------------------
HARDWARE: ESP32C3 160MHz, 320KB RAM, 4MB Flash
 - toolchain-riscv32-esp @ 8.4.0+2021r2-patch5

Compiling .pioenvs/esp32-c302/src/esphome/components/scs_bridge/scs_bridge.cpp.o
Compiling .pioenvs/esp32-c302/src/esphome/components/scs_bridge/scs_cover.cpp.o
src/esphome/components/scs_bridge/scs_bridge.cpp: In function 'void esphome::scs_bridge::tx_isr()':
src/esphome/components/scs_bridge/scs_bridge.cpp:149:5: error: 'timer1_write' was not declared in this scope
     timer1_write(TX_0RZ_TICKS);
     ^~~~~~~~~~~~
src/esphome/components/scs_bridge/scs_bridge.cpp:149:5: note: suggested alternative: 'timerWrite'
     timer1_write(TX_0RZ_TICKS);
     ^~~~~~~~~~~~
     timerWrite
src/esphome/components/scs_bridge/scs_bridge.cpp:162:7: error: 'timer1_write' was not declared in this scope
       timer1_write(TX_0_TICKS);
       ^~~~~~~~~~~~
src/esphome/components/scs_bridge/scs_bridge.cpp:162:7: note: suggested alternative: 'timerWrite'
       timer1_write(TX_0_TICKS);
       ^~~~~~~~~~~~
       timerWrite
src/esphome/components/scs_bridge/scs_bridge.cpp:176:7: error: 'timer1_write' was not declared in this scope
       timer1_write(TX_1_TICKS);
       ^~~~~~~~~~~~
src/esphome/components/scs_bridge/scs_bridge.cpp:176:7: note: suggested alternative: 'timerWrite'
       timer1_write(TX_1_TICKS);
       ^~~~~~~~~~~~
       timerWrite
src/esphome/components/scs_bridge/scs_bridge.cpp:181:7: error: 'timer1_write' was not declared in this scope
       timer1_write(TX_0_TICKS);
       ^~~~~~~~~~~~
src/esphome/components/scs_bridge/scs_bridge.cpp:181:7: note: suggested alternative: 'timerWrite'
       timer1_write(TX_0_TICKS);
       ^~~~~~~~~~~~
       timerWrite
src/esphome/components/scs_bridge/scs_bridge.cpp:193:5: error: 'timer1_write' was not declared in this scope
     timer1_write(TX_STOP_TICKS);
     ^~~~~~~~~~~~
src/esphome/components/scs_bridge/scs_bridge.cpp:193:5: note: suggested alternative: 'timerWrite'
     timer1_write(TX_STOP_TICKS);
     ^~~~~~~~~~~~
     timerWrite
src/esphome/components/scs_bridge/scs_bridge.cpp:204:5: error: 'timer1_write' was not declared in this scope
     timer1_write(TX_FRAME_REPEAT_DELAY);
     ^~~~~~~~~~~~
src/esphome/components/scs_bridge/scs_bridge.cpp:204:5: note: suggested alternative: 'timerWrite'
     timer1_write(TX_FRAME_REPEAT_DELAY);
     ^~~~~~~~~~~~
     timerWrite
src/esphome/components/scs_bridge/scs_bridge.cpp: In member function 'virtual void esphome::scs_bridge::SCSBridge::setup()':
src/esphome/components/scs_bridge/scs_bridge.cpp:254:3: error: 'timer1_isr_init' was not declared in this scope
   timer1_isr_init();
   ^~~~~~~~~~~~~~~
src/esphome/components/scs_bridge/scs_bridge.cpp:254:3: note: suggested alternative: 'timerisset'
   timer1_isr_init();
   ^~~~~~~~~~~~~~~
   timerisset
src/esphome/components/scs_bridge/scs_bridge.cpp:255:3: error: 'timer1_attachInterrupt' was not declared in this scope
   timer1_attachInterrupt(tx_isr);
   ^~~~~~~~~~~~~~~~~~~~~~
src/esphome/components/scs_bridge/scs_bridge.cpp:255:3: note: suggested alternative: 'timerAttachInterrupt'
   timer1_attachInterrupt(tx_isr);
   ^~~~~~~~~~~~~~~~~~~~~~
   timerAttachInterrupt
src/esphome/components/scs_bridge/scs_bridge.cpp:256:17: error: 'TIM_DIV16' was not declared in this scope
   timer1_enable(TIM_DIV16, TIM_EDGE, TIM_SINGLE);
                 ^~~~~~~~~
src/esphome/components/scs_bridge/scs_bridge.cpp:256:28: error: 'TIM_EDGE' was not declared in this scope
   timer1_enable(TIM_DIV16, TIM_EDGE, TIM_SINGLE);
                            ^~~~~~~~
src/esphome/components/scs_bridge/scs_bridge.cpp:256:38: error: 'TIM_SINGLE' was not declared in this scope
   timer1_enable(TIM_DIV16, TIM_EDGE, TIM_SINGLE);
                                      ^~~~~~~~~~
src/esphome/components/scs_bridge/scs_bridge.cpp:256:38: note: suggested alternative: 'MEM_SIZE'
   timer1_enable(TIM_DIV16, TIM_EDGE, TIM_SINGLE);
                                      ^~~~~~~~~~
                                      MEM_SIZE
src/esphome/components/scs_bridge/scs_bridge.cpp:256:3: error: 'timer1_enable' was not declared in this scope
   timer1_enable(TIM_DIV16, TIM_EDGE, TIM_SINGLE);
   ^~~~~~~~~~~~~
src/esphome/components/scs_bridge/scs_bridge.cpp:256:3: note: suggested alternative: 'timerAlarmEnable'
   timer1_enable(TIM_DIV16, TIM_EDGE, TIM_SINGLE);
   ^~~~~~~~~~~~~
   timerAlarmEnable
src/esphome/components/scs_bridge/scs_bridge.cpp: In member function 'virtual void esphome::scs_bridge::SCSBridge::loop()':
src/esphome/components/scs_bridge/scs_bridge.cpp:269:5: error: 'ETS_INTR_LOCK' was not declared in this scope
     ETS_INTR_LOCK();
     ^~~~~~~~~~~~~
src/esphome/components/scs_bridge/scs_bridge.cpp:269:5: note: suggested alternative: 'ESP_LWIP_LOCK'
     ETS_INTR_LOCK();
     ^~~~~~~~~~~~~
     ESP_LWIP_LOCK
src/esphome/components/scs_bridge/scs_bridge.cpp:287:9: error: 'timer1_write' was not declared in this scope
         timer1_write(TX_TRIGGER_TICKS);
         ^~~~~~~~~~~~
src/esphome/components/scs_bridge/scs_bridge.cpp:287:9: note: suggested alternative: 'timerWrite'
         timer1_write(TX_TRIGGER_TICKS);
         ^~~~~~~~~~~~
         timerWrite
src/esphome/components/scs_bridge/scs_bridge.cpp:302:13: error: 'timer1_write' was not declared in this scope
             timer1_write(TX_TRIGGER_TICKS);
             ^~~~~~~~~~~~
src/esphome/components/scs_bridge/scs_bridge.cpp:302:13: note: suggested alternative: 'timerWrite'
             timer1_write(TX_TRIGGER_TICKS);
             ^~~~~~~~~~~~
             timerWrite
src/esphome/components/scs_bridge/scs_bridge.cpp:315:5: error: 'ETS_INTR_UNLOCK' was not declared in this scope
     ETS_INTR_UNLOCK();
     ^~~~~~~~~~~~~~~
src/esphome/components/scs_bridge/scs_bridge.cpp:315:5: note: suggested alternative: 'SIG_UNBLOCK'
     ETS_INTR_UNLOCK();
     ^~~~~~~~~~~~~~~
     SIG_UNBLOCK
src/esphome/components/scs_bridge/scs_bridge.cpp:387:5: error: 'timer1_write' was not declared in this scope
     timer1_write(TX_TRIGGER_TICKS);  // schedule the tx isr
     ^~~~~~~~~~~~
src/esphome/components/scs_bridge/scs_bridge.cpp:387:5: note: suggested alternative: 'timerWrite'
     timer1_write(TX_TRIGGER_TICKS);  // schedule the tx isr
     ^~~~~~~~~~~~
     timerWrite
*** [.pioenvs/esp32-c302/src/esphome/components/scs_bridge/scs_bridge.cpp.o] Error 1
========================= [FAILED] Took 53.17 seconds =========================

But i was trying with one D1 Mini and it compiling OK so the code is working OK only some comparability glitches..

Now i can getting frames in HA but was struggling logging then so can making automatons of them.
The trigger is very easy but the action was taking more work getting in place:

alias: SCS Test
description: ""
triggers:
  - trigger: event
    event_type: esphome.scs_frame
    event_data:
      device_id: c90ac6afd1cd049a27e194bf9924b8cc
conditions: []
actions:
  - action: notify.persistent_notification
    metadata: {}
    data:
      title: SCS Bridge
      message: "Data from Bridge: \"{{ trigger.event.data.payload }}\""
  - action: system_log.write
    metadata: {}
    data:
      level: warning
      message: "  message: \"Data from SCS: '{{ trigger.event.data.payload }}'\""
mode: single

I getting in the log:

Logger: homeassistant.components.system_log.external
Source: components/system_log/__init__.py:331
integration: System Log (documentation, issues)
First occurred: 13:44:38 (33 occurrences)
Last logged: 13:44:56

message: "Data from SCS: 'A896A06FA4FDA3'"
message: "Data from SCS: 'A8B6086008D6A3'"
message: "Data from SCS: 'A896A06FA0F9A3'"
message: "Data from SCS: 'A8B5086008D5A3'"
message: "Data from SCS: ''"

Plus many (55) Persistent Notification like this:

SCS Bridge
Data from Bridge: "A8B5086008D5A3"
4 minutes ago

That is great to knowing that the neighbor was called and also open the entry door !!

I was finding one German that was taking the data to the MCU in the intercom and also the internal 5V, The data part is working OK but the 5V wad not stable and the ESP was having problem. Putting in one 5-30V to 5V buck converter (on the large capacitor its 27V) and now its stable.
Also hi was taking the opening button to on GPIO but its not needed then the intercom is sending the command and is getting the framed from it in HA.

I only like getting the external call button but looks being tricky with the D1 Min GPIO (5V logic and very high impedance on the MCU) but better with ESP32C3 with analogue input so need your code up and running on it

If you have time looking on the RISC-V code support it wold being great the the ESP32C3Super Mini is fitting very nice in the intercom and its looks more stable ad the old D1 Minis.

One more great thanks for you work !!!!!

[MattWestb]

Intercom / door bell in multi level bus system commands.

All frames is seen from the apartment so most system things are not seen.
All frames is sent 3 times only one i used.
The start, checksum and end bits is stripper from the frame (SCS-bus standard) so only pure commends is used here.
System commands that is not of interesting is not shown like handshake door controller <-> bridges.

Interesting Commands then calling my apartment:

91016008 91 Calling from door to apartment (01)
B5A06F08 B5 No answer from apartment > End
B3016008 B3 Off Hock from apartment (01)
B6016018 B6 Sending command link to door (01) (next command -> door)
96A06FA4 96 Command Open pressed (the same for all addresses)
B6016008 B6 Sending command link to door (01) (next command -> door)
96A06FA0 96 Command Open released (the same for all addresses)
B5016008 B3 On Hock (01) > End

Its looks if opening then some calling and not doing off / on hock the system is ending with:
B5A06F08 (address 60, 6F and A0 is bridge, system / door controller) after sending normal open sequence (the same as no answer).

If not being on the same bus only command seen is:
96 Open pressed
B6XX Sending command link to door (with apartment address)
96 Open released
B5XX End (with apartment address)

91XX (Calling from door) looks only being seen if being on the same bus or one level up / down as the apartment called.

So can see the the door calling neighbors if being on the same bus.
See if one apartment is sending command open door = have being called.

Only need figuring out the apartment numbers/system addresses.

The Italians have forgotten the privacy thing but its no problem for me !!!

Also very Italian is source and destination addressees is not always in the same position in the frame (Pasta logic !!).