- 1,769
- 355
- NAS
- DS 718+, 2x-DS 720+
- Router
- RT2600ac
- Operating system
- Windows
- Mobile operating system
- iOS
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
As an Amazon Associate, we may earn commissions from qualifying purchases. Learn more...
check this replySo it shows both SS AND CAMERA
Motion detect both? I’d it work?
Please post a screenshot
Support just confirmed yet again that SS as motion detect has been removed in total for both 264 & 265
The support for H.265 cameras will undergo the following changes, while H.264 cameras are not affected,
I’d try it if I could go back! I CANT, so I ask Support, and Support says it’s going away!
If I can’t test it, is Support wrong for saying it’s been removed? (And the Supervisor who took over the ticket, too?)
Then someone PROVE IT! Post pictures as I did above showing H264 camera showing SS as Motion detect algorithm: AFTER UPDATE: is still operational!
This is nuts that an end user should get such contradictory information!
Have not done that before, so now is not time to try and experiment!
I’ve gone through 3 people on my trouble ticket, including one manager. I’ve told them I’m switching back to H264 on all cameras, and that’s when they sent me the png picture I posted before, saying SS Motion Detect is no longer, and decision to remove came from up high.
So I’m going back to all H264, and I’m prepared to go two ways:
IF Support is correct: SS No longer an option, I will attempt to switch cams to camera motion detect. If Successful to a the extent I’m at now or better: UPGRADE
IF NOT: Stay where I am!
Please contact beta testers who were using H264 cameras for me. Golly! Someone must have tried this! Refer to my pix as to where to set motion detect sourceAnd I have not a H264 cam but i'm on 7.2.2
It could be the Docker version that is running on the NAS. Version 24.x of Container manager is in beta atm so the 20.10 might have issues with Portainer 2.21Not sure if this is due to 7.2.2 or not, but after upgrading my Portainer instance to the new 2.21.0 LTS release, the agents running on my NAS units all refuse to connect, yet all my non-NAS agents are fine (all agents are the same version.
From what I see, a lot of people are having issues with the new Portainer release, so I'm more inclined to think it is Portainer at fault, but throwing this here in case anyone else can confirm their system is working, or if they are also having issues.
It looks like my issue is a combination of the older non-beta) Docker version, and Portainer 2.21.0 not doing DNS lookups successfully (despite the host being fine).It could be the Docker version that is running on the NAS. Version 24.x of Container manager is in beta atm so the 20.10 might have issues with Portainer 2.21
We use essential cookies to make this site work, and optional cookies to enhance your experience.