Activity

1. GreenGrassBlueOcean commented on Oct 20, 2026

   

   GreenGrassBlueOcean

   on Oct 20, 2026

   Contributor

   More actions

   Hi, thanks for the report!

   1. This isn't in b14, but should land in b16. b14 and b15 have no door entry (WHO 6 / WHO 8) support. The next pre-release, 2.0.0b16 (#703), is planned to add:

   • a dedicated myhome_doorbell_event that fires when someone rings at an entrance panel, so you can trigger automations and notifications from it
   • a lock platform for door entry electric strikes

   b16 depends on an OWNd release that isn't out yet, so I can't give a date. It's coming, though.

   2. The trace is missing the ring. *6*9**## is WHO 6 WHAT 9, which means "camera off". The system sends it when the call or video ends, not when someone rings, so this frame alone can't tell us about the doorbell.

   We've already captured a doorbell press on another plant. The full sequence looks like this:

   *8*1#1#4*74##   ← entrance panel 74 calls (the actual ring)
   *8*9#1#4*73##   ← handset hangs up
   *6*9##          ← camera off
   

   b16 fires myhome_doorbell_event on that first *8*1#… frame. Could you recapture the trace like this?

   1. Clear the Bus Monitor and remove any WHO filter.
   2. Press the doorbell once and let the call ring out (or answer and hang up).
   3. Post every frame from that window, not just the WHO 6 ones.

   Most importantly, we need to see whether your F453AV puts a *8*1#… (or *6*6*…) frame on the bus when someone rings. If it does, b16 should pick it up as-is. If it doesn't, that trace will tell us what your system sends instead.
2. nce2704 commented on Oct 21, 2026

   

   nce2704

   on Oct 21, 2026

   Author

   More actions

   I've now run the trace. It looks like there's something wrong with my system. I can ring the doorbell. I turned on the camera. I opened the gate and spoke to the outdoor unit, but there's no traffic on the bus. Unfortunately, I can't help with that right now.

   Best regards

   myhome_trace_F453AV_all_2026-10-21T05-55-44.json
3. GreenGrassBlueOcean commented on Oct 21, 2026

   

   GreenGrassBlueOcean

   on Oct 21, 2026

   Contributor

   More actions

   Thanks for uploading the trace! Nothing is broken in your door entry system — the trace actually explains what is happening in your installation:

   1. What is in your 31-second trace (05:55:11Z – 05:55:42Z)

   • Every 5 seconds: Another controller/client on your network is polling your F453AV (*#13**15*12##) and querying point lights one by one (*1*0*16##, *1*0*29##, *1*0*58##, etc.).
   • 05:55:23.075Z: *25*31#1*31## followed 107 ms later by *1*1*63## — sensor/contact 31 triggered and switched on light 63 (likely your entrance motion sensor or dry-contact interface triggering the entrance light).
   • 05:55:32.193Z (+9.1 s): *6*9**## — WHO 6 WHAT=9 (Camera OFF) when the video channel switched off.

   2. Why you don't see the ring / speech / gate-open frames on the bus

   In a 2-wire BTicino Video Door Entry + MyHOME Automation system, the Video Door Entry riser (outdoor entrance panel, Axolute indoor video unit, F441 audio/video node) is separated from the MyHOME Automation bus by an F422 SCS/SCS interface:

   • Depending on how the F422 is configured (M / I3 / I4 configurators) and whether the F453AV's dedicated SCS AV IN terminal and TiF453AV Internal unit address / Answering machine parameters are configured, internal 2-wire door-entry signaling (ringing, audio conversation, local lock release) stays isolated on the video riser.
   • Only cross-bus broadcast frames like *6*9**## (camera off / video channel release) cross onto the automation bus monitor session. (We see this exact same behavior on other installations separated by an F422.)

   3. How to trigger a Home Assistant automation from *6*9**##

   1. Note that myhome_bus_event does not exist — the raw event name in Home Assistant is myhome_message_event.
   2. In Settings → Devices & Services → MyHOME → Configure:
      • Enable Generate raw bus events (generate_events), and
      • Make sure WHO 6 is not excluded in your active WHO filter, then reload the integration.
   3. Listen to myhome_message_event in Developer Tools → Events and you will receive:

      event_type: myhome_message_event
      data:
        gateway: "<your_F453AV_ip>"
        message: "*6*9**##"
        who: 6
        what: 9
        where: "*"

      You can use that directly as an Event trigger in your automations (event_type: myhome_message_event with event_data: { who: 6, what: 9 }).
4. nce2704 commented on Oct 21, 2026

   

   nce2704

   on Oct 21, 2026

   Author

   More actions

   The event is triggered. Then I'll build the automation based on that.

   event_type: myhome_message_event
   data:
     gateway: 192.168.0.155
     message: '*6*9**##'
     family: Event
     type: Status
     who: 6
     where: '*'
     what: 9
   origin: LOCAL
   time_fired: '2026-10-21T11:07:50.518610+00:00'
   context:
     id: 01M5F2ARBP4Q0RJMSMTWYCB3FC
     parent_id: null
     user_id: null

   05:55:23.075Z: 2531#131## followed 107 ms later by 1163## — sensor/contact 31 triggered and switched on light 63 (likely your entrance motion sensor or dry-contact interface triggering the entrance light).

   63 is the actuator that opens the entrance gate via a impulse.

   The polling is handled by easyscs. Once I've finished configuring home assistant, I'll turn off easyscs. I used to have an ISAAC.

   Thanks again
5. GreenGrassBlueOcean

   closed this as completedon Oct 21, 2026