No motion detection through RTSP confifuration in OpenHAB

No motion detection through RTSP confifuration in OpenHAB

No motion detection through RTSP confifuration in OpenHAB
No motion detection through RTSP confifuration in OpenHAB
2025-09-12 14:57:21
Model: Tapo C320WS  
Hardware Version: V2
Firmware Version: 1.3.5 Build 250522 Rel. 45630n

My camera is not sending an ffmpegMotionAlarm by any kind of configuration settings so for. I have 3 Tapo Cameras with 2 C320WS outside and 1 C225 inside, which is working well. The main difference betwen the outside and inside cameras is the Micro SD Card. The functioning C225 camera has no SD card installed. All cameras are connected by LAN cables. Even when I disable the SD cards on the C320WS cameras, I got no MotionAlarm through my OpenHab application, whereas the Tapo App alarms works fine. 

 

The logging of the C320WS in case of an alarms sags the following:

 

2025-09-12 15:58:00.476 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Aussen_Cam1_ffmpegMotionAlarm' changed from NULL to OFF

 

The logging of the C225 camera in case of an alarm says:

025-09-12 16:42:38.963 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Innen_Cam1_ffmpegMotionAlarm' changed from NULL to OFF

2025-09-12 16:42:43.974 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Innen_Cam1_ffmpegMotionAlarm' changed from OFF to ON

.....

025-09-12 16:42:51.791 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Innen_Cam1_ffmpegMotionAlarm' changed from ON to OFF

 

I assume it has to do with the installation of the Micro SD Card in the C320WS cameras, even I explicitly disabled them through the Tapo App.

On the other hand I found forum entries, which say, that the activation of the Tapo Cloud Storage is blocking the ffmpeg/ rtsp motionalarm functionality. But all my cameras newer had Tapo Cloud data storage. 

I would like to keep the SD Cards in the outside cameras in order to reactivate the local storage in case of problems. And I do not want to climb up to the these roof- top cameras and insert/ remove the SD cards.

 

Do you any adice how to overcome this problem?

  0      
  0      
#1
Options
5 Reply
Re:No motion detection through RTSP confifuration in OpenHAB
3 weeks ago

  @TheoMUC 

Hi,
Please confirm the following information about the reported case.


  1. Can you establish the Onvif stream on your OpenHab app with the Tapo C225? Is the motion alarm feature on your OpenHab app working when the Tapo C225 detects events?
  2. How do you disable the SD card on the Tapo C320WS? By disabling the Local Recording option on the camera's Device Settings > Storage & Recording feature?
  3. After you disable the SD card on a Tapo C320WS, can you establish the Onvif stream on your OpenHab app with the Tapo C320WS?

 

Please note that on most Tapo cameras, including the Tapo C320WS and C225, Tapo Care, SD card, and Onvif software cannot be used simultaneously to record videos or stream. You can only choose two of them at the same time.

 

Best Regards

  0  
  0  
#2
Options
Re:No motion detection through RTSP configuration in OpenHAB
2 weeks ago

  @Solla-topee 

 

Dear Support- Team,

 thank you for your support. I have reconfigured the Tapo C320WS camera in such a way, that I'm using ONVIF now.

At first I used ISPY for testing the ONVIF interface and it works fine for both C320WS cameras for displaying each video stream.

 

Then I adapted the OpenHAB configuration for the first C320WS camera from RSTP to ONVIF The display of a video stream works fine.

But not the motion event.

 

Answering your questions:

 

2. How do you disable the SD card on the Tapo C320WS? By disabling the Local Recording option on the camera's Device Settings > Storage & Recording feature?

 

yes

 

3. After you disable the SD card on a Tapo C320WS, can you establish the Onvif stream on your OpenHab app with the Tapo C320WS?

 

yes, but the motion alert is not working.

 

Here the log file (trace) in case of a motion alert:

 

2025-09-23 10:51:27.105 [DEBUG] amera.internal.onvif.OnvifConnection - ONVIF Event Topic: RuleEngine/PeopleDetector/People, Data name: IsPeople, Data value: true
2025-09-23 10:51:27.105 [DEBUG] amera.internal.onvif.OnvifConnection - Please report this camera has an un-implemented ONVIF event. Topic: RuleEngine/PeopleDetector/People
2025-09-23 10:51:27.105 [TRACE] amera.internal.onvif.OnvifConnection - Sending ONVIF request: PullMessages to <camera IP address>:1024/event-1024_1024

 

How to proceed now?

 

Thank you in advance.

 

best regards,

 

Theo

 

  0  
  0  
#3
Options
Re:No motion detection through RTSP configuration in OpenHAB
2 weeks ago

  @TheoMUC 

Hi,
From the provided log, it seems the camera detects a person rather than motion. Please try disabling Person Detection on the Tapo C320WS and enabling Motion Detection. Then, check if you can receive a motion notification on the OpenHab app when the camera detects motion.


You can also establish an Onvif connection with the iSpy app for comparison (check if the iSpy app receives motion notification when the camera detects motion).


Best Regards

  0  
  0  
#4
Options
Re:No motion detection through RTSP configuration in OpenHAB
2 weeks ago

  @Solla-topee 

I disabled PersonDetection and now I only have MotionDetection. In the attached open HAB logfile ( Tapo_forum_errormsg_Sep25.txt) you see that the camera is sending an IsMotion event for a period of time. 

 

2025-09-25 15:38:39.916 [DEBUG] - ONVIF Event Topic: RuleEngine/CellMotionDetector/Motion, Data name: IsMotion, Data value: true
2025-09-25 15:38:39.917 [TRACE] - Sending ONVIF request: PullMessages to ptth//000.111.222.157:1024/event-1024_1024
2025-09-25 15:38:39.930 [TRACE]  - ONVIF PullMessages reply is: 

....

this block is repeated many times

 

At the end of the alarm it is this:

 

2025-09-25 15:38:43.548 [DEBUG]  ONVIF Event Topic: RuleEngine/CellMotionDetector/Motion, Data name: IsMotion, Data value: false

 

Remark: I didn't succeed to send you a subset of the original log- file because of an error message about external links. Even I had manipulated the http calls, it didn't work.

Thus it would save a lot of time, if you can publish a list of unwanted keywords.

 

 

In parallel the ISYP log looks as following for the same camera:


11:36:25
Hausseite: OpenWriter: StartSaving
11:36:25
Hausseite: .ctor: Using stream timestamps for this recording
11:36:25
Open: OPEN RECORD
11:36:25
Open: written header
11:36:25
Hausseite: Open: Recording (Raw Writer CoreLogic.Sources.Combined.RawMonitor)
11:36:25
Hausseite: WarnClock: Dropped packet as out of order - set Use System Clock on recording tab if you have problems
11:36:25
Hausseite: RecorderRecordingOpened: Recording Opened
11:36:42
Hausseite: RecorderRecordingClosed: Recording Closed
11:36:42
Hausseite: Close: Record stop
11:48:04
StorageManager: Running Storage Management
11:48:04
CleanDirectory: Skip storage management on /home/theo/AgentDVR/Media/WebServerRoot/Media/ as it is disabled
12:48:05
StorageManager: Running Storage Management
12:48:05
CleanDirectory: Skip storage management on /home/theo/AgentDVR/Media/WebServerRoot/Media/ as it is disabled
13:48:05
StorageManager: Running Storage Management
13:48:05
CleanDirectory: Skip storage management on /home/theo/AgentDVR/Media/WebServerRoot/Media/ as it is disabled
14:48:05
StorageManager: Running Storage Management
14:48:05
CleanDirectory: Skip storage management on /home/theo/AgentDVR/Media/WebServerRoot/Media/ as it is disabled
15:38:40
Hausseite: OpenWriter: StartSaving
15:38:40
Hausseite: .ctor: Using stream timestamps for this recording
15:38:40
Open: OPEN RECORD
15:38:40
Open: written header
15:38:40
Hausseite: Open: Recording (Raw Writer CoreLogic.Sources.Combined.RawMonitor)
15:38:40
Hausseite: RecorderRecordingOpened: Recording Opened
15:38:40
Hausseite: WarnClock: Dropped packet as out of order - set Use System Clock on recording tab if you have problems
15:38:56
Hausseite: RecorderRecordingClosed: Recording Closed
15:38:56
Hausseite: Close: Record stop
15:48:05
StorageManager: Running Storage Management
15:48:05
CleanDirectory: Skip storage management on /home/theo/AgentDVR/Media/WebServerRoot/Media/ as it is disabled
16:00:59
Hausseite: OpenWriter: StartSaving
16:00:59
Hausseite: .ctor: Using stream timestamps for this recording
16:00:59
Open: OPEN RECORD
16:00:59
Open: written header
16:00:59
Hausseite: Open: Recording (Raw Writer CoreLogic.Sources.Combined.RawMonitor)
16:00:59
Hausseite: WarnClock: Dropped packet as out of order - set Use System Clock on recording tab if you have problems
16:00:59
Hausseite: RecorderRecordingOpened: Recording Opened
16:01:14
Hausseite: RecorderRecordingClosed: Recording Closed
16:01:14
Hausseite: Close: Record stop

 

At 16:00 I repeated the same procedure, but this time I changed the sensivity of this camera by a Dimmer to 60% in order to get an alert in OpenHab as well. But as always, the OpenHAB application gets no alert by the rule if have configured.

 

I configured onvifport=2020 for all Tapo cameras. Is this correct? Or does each camera have different ONVIF port?

 

Please advice.

 

best regards,

 

Theo

 

  0  
  0  
#5
Options
Re:No motion detection through RTSP configuration in OpenHAB
2 weeks ago - last edited 2 weeks ago

  @TheoMUC 

Hi, 
I have escalated your case to our tech team, and they will contact you via email to further assist you. Please wait patiently.
After you receive the email, please send the openHAB log file to our tech team via email.

 

Our Tapo camera's ONVIF service port is 2020, and only in special scenarios, you need to establish an ONVIF connection with our camera on a different port. For example, when you remotely establish ONVIF connections with multiple Tapo cameras on the same network, you need to open ports for each camera on the front-end router. On the port forwarding entries, the internal port is 2020, and the external port needs to be set to a different port for each camera.


Best Regards

  0  
  0  
#6
Options