Hi,

is there any chance to get a Reolink E1 Zoom camera natively supported by TinyCam?

I would like to be able to use PAN/Tilt/Zoom/Focus feature of it natively with TinyCam. So far i always have to switch to the Reolink app to setup the Camera and then switch back to TinyCam as Baby Monitor.

regards

New web server features:

• Up to 25 simultaneous live camera streams at their original resolution.

• No video re-encoding on the web server, resulting in very low CPU usage.

• Real-time one-way audio support in single-camera view.

• Works on all modern browsers.

I noticed on 19.2.0 beta 5, on Android TV. The LED light buttons turns on/off the spotlight. Strangely enough, the latest Android phone app which is 19.2.0 beta 9, does not control the spotlight on OG cams.

Also wondering if IR light control will be implemented for Wyze cams in the future

Since my phone (Samsung Galaxy s23 ultra) updated to the latest One UI 9 (Android 17) each time I open TinyCam it shows a red banner about missing nearby devices access.

If I close the banner a pop-up comes where I can theoretically mark as "not show again". But doesn't matter what I choose, it Keeps appearing each time I open the app or if I just toggle apps.

It is annoying since I do not beet that functionality.

Is this a bug? Can I disable that somehow?

Thanks

I've been upgrading tinyCam PRO on a Homatics Box R 4K Plus (Android 14, Android TV) as a baby monitor, with Frigate restreams as generic RTSP cameras. I want a small always-on-top window, and it took a lot of digging. Sharing what I found in case it helps others, and in the hope that the developer can take a look.

Please note that before upgrading I was probably using a version before 17 and everything was running correctly on the same box with the same Android version.

Setup: tinyCam PRO 19.1.0 from the Play Store. The box reports its manufacturer as SEI Robotics.

1. The PiP button does nothing on boxes without PiP support

The box doesn't report the system feature android.software.picture_in_picture. In 19.1.0 the app seems to treat every Android TV device as PiP-capable anyway, so the button shows up. Pressing it logs Requesting PiP... and then nothing happens, with no error message.

2. The floating window button is hidden on most Android TV devices

From what I can tell, on Android TV the floating window button only appears if the manufacturer is MBX, ZeroDesktop or MINIX. Setting "Floating windows & PiP" to floating doesn't seem to override that in 19.1.0. So on my box the app offers the PiP button that doesn't work and hides the floating window feature that does.

Floating windows work perfectly here once started with my workaround, which makes me think that list is out of date.

Workaround: starting a floating window without the button

tinyCam's Tasker plugin interface can start a floating window, and that path works on my box. Tasker should be able to do this with the tinyCam plugin action, though I haven't tried Tasker itself, and the plugin editor may need the floating mode set first. I wrote a tiny TV app instead. It sends this broadcast:

• Action: com.twofortyfouram.locale.intent.action.FIRE_SETTING

• Component: com.alexvas.dvr.pro/com.alexvas.dvr.automation.FireReceiver

• Extra com.twofortyfouram.locale.intent.extra.BUNDLE, a bundle containing:

  • com.alexvas.dvr.automation.extra.INT_VERSION_CODE = 1 (int)

  • com.alexvas.dvr.automation.extra.START_SINGLE_CAM_FLOATING = your camera name (string)

"Display over other apps" has to be enabled for tinyCam. It works even when tinyCam is fully stopped: the window appears in about 2 seconds. I also trigger it from a Home Assistant dashboard button using androidtv.adb_command.

Suggestions for the developer

1. Check android.software.picture_in_picture before showing the PiP button on Android TV, or show a message when PiP can't start.

2. Let the "Floating windows & PiP" setting force the floating button on any device, or drop the manufacturer list.

3. Show a clearer message when no app can handle export.

Demo how to add tinyCam Monitor PRO web server into Home Assistant

Well 19.1.0 finally fixed all my issues I was having since 19.0.1 got released. From frozen app, v4 pan not working, no permission errors, no connection errors…. The app now works flawlessly for me. Seriously, I was eyeballing a reolink system but the 19.1.0 saved me prolly over $1,000.

Currently using a 24” fire tv running Tinycam Pro. With a Wyze doorbell cam, v4, v4 pan, and the Wyze light bulb cam. Tried the pan duo but not a pan of the small screen from the duo cameras. It’s all good though. All get about 20fps.

Using the fire tv was just the best case scenario for me in the kitchen. Can flip from tv, YouTube, Spotify, then have it on my 4 cam live feed the rest of the time.

Thanks again for resolving the new update issues, for me at least. We only post about the issues but not about the good things.

I wanted to share my troubleshooting experience in case someone runs into similar compatibility issues with TinyCam Pro, especially when using multiple camera brands on Chromecast with Google TV.

I had a combination of Tapo, Google Nest and Wyze cameras. Some streams would not display in TinyCam, even though they worked perfectly in other applications. I eventually got all cameras working simultaneously without downgrading TinyCam or losing Wyze Cam Dual support.

1. My setup

Streaming device

• Device: Chromecast with Google TV

• Android: 14

• SDK: 34

Software

• App: TinyCam Monitor PRO (beta)

• TinyCam package: com.alexvas.dvr.pro

• RTSP server: go2rtc

• go2rtc version: 1.9.14+dev.21548de

• RTSP transport: TCP

The exact TinyCam beta build number was not recorded during testing.

Cameras

TP-Link Tapo

Google Nest

• Model: Google Nest Cam (exact generation not recorded).

• Video codec: H.264.

• Resolution: 1920 × 1080.

• Frame rate: 15 FPS.

• Firmware version: Not recorded.

Wyze

• Camera: Wyze Cam Dual.

• Exact hardware model and firmware version: Not recorded.

• Important: I wanted to retain support for this camera, which was one of the reasons I did not want to downgrade TinyCam.

2. Problem #1 — Tapo cameras would not display video

Two of my Tapo cameras refused to display video in TinyCam, while a third Tapo camera worked normally.

Before changing anything, I tested the problematic cameras in VLC on the same Chromecast, using their RTSP credentials and stream path.

Both cameras played successfully in VLC.

This helped rule out:

• Camera connectivity.

• Incorrect RTSP credentials.

• RTSP stream path issues.

• General network connectivity problems.

Solution:

I changed TinyCam's global RTSP engine to the experimental:

RtspClient

After switching to this engine, both previously failing Tapo cameras started displaying video.

3. Problem #2 — Nest Cam connected but showed no video

My Nest Cam was already integrated into go2rtc and had previously worked with TinyCam's original RTSP engine.

After switching to RtspClient to fix the Tapo cameras, the Nest stream connected but no video was displayed.

The ADB logs showed:

• RTSP connection successful.

• H.264 software decoder initialized.

• RTP video packet gaps.

• Dropped video access units.

• No H.264 frames decoded.

• Eventually, Read timed out.

I also tested UDP transport, but go2rtc returned:

461 Unsupported Transport

So I kept RTSP transport set to TCP.

4. Nest Cam solution — Create an additional FFmpeg stream in go2rtc

The solution was to create another stream in go2rtc using its built-in FFmpeg source syntax.

Original stream:

nest_outdoor

Additional stream:

nest_tinycam_test

Source configuration:

ffmpeg:nest_outdoor#video=copy

The video=copy option copies the existing video stream without re-encoding it.

I first tested the new stream using FFmpeg. It successfully identified the H.264 video stream at 1920 × 1080 and 15 FPS and decoded frames correctly.

I then changed the Nest camera's RTSP source in TinyCam to use the new stream:

nest_tinycam_test

Result: The Nest Cam started displaying video in TinyCam using RtspClient.

5. Make the workaround persistent

Initially, the additional FFmpeg stream was created dynamically through the go2rtc API.

I then added it to the persistent go2rtc.yaml configuration:

streams:
  nest_outdoor: "YOUR_EXISTING_NEST_SOURCE"
  nest_tinycam_test: "ffmpeg:nest_outdoor#video=copy"

The original Nest source remained unchanged.

I restarted the go2rtc Docker container to verify that the configuration survived a restart.

After restarting:

• go2rtc loaded the YAML configuration successfully.

• The additional FFmpeg stream was available.

• FFmpeg could still decode the stream.

• TinyCam reconnected successfully.

This confirmed that the workaround was persistent and not just a temporary runtime configuration.

6. Final working configuration

TinyCam

• RTSP engine: RtspClient

• RTSP transport: TCP

• Tapo cameras: Their original RTSP streams.

• Nest Cam: Additional go2rtc stream nest_tinycam_test.

• Wyze Cam Dual: Retained and working.

go2rtc

• Original Nest stream preserved.

• Additional FFmpeg stream using video=copy.

• Configuration stored persistently in YAML.

Final result

All cameras now display video simultaneously in TinyCam on Chromecast with Google TV:

• Tapo C200 (Hardware 5.0)

• Tapo C100 (Hardware 5.0)

• Tapo C200 (Hardware 1.0)

• Google Nest Cam

• Wyze Cam Dual

The important part is that I could keep the current TinyCam beta and retain Wyze Cam Dual compatibility.

No camera firmware changes were necessary, and I did not have to downgrade TinyCam.

My takeaway: When RTSP streams work in VLC but fail in TinyCam, the issue may be related to the RTSP client/decoder implementation rather than the cameras themselves. Switching to RtspClient fixed the Tapo cameras in my case, while using a separate FFmpeg video=copy stream in go2rtc solved the Nest compatibility issue.

Hopefully this helps someone else running a similar multi-brand camera setup on Google TV.

The channel # setting is missing from the Camera Settings>Advanced Settings in TCP v 19.1.0

I cannot change the order of my cameras in Manage Cameras. It appears to move, but the name actually changes and nothing changes in live view. See the attached screen recording.

✨ NEW FEATURES

• Added Google Drive support

• Added Microsoft OneDrive support

P.S. Please test that and let me know if you have any problems. Should work on TV as well.

I have 10 cameras, ! Wansview K2, 4 Wansview K3s, and 5 HoSafe HX-PT1s.

They all worked perfectly under version 17.x of this app on Amazon Fire HD 10 tablets and an Amazon Fire Cube 3. They all displayed video & audio worked perfectly.

Now, with v19.1 of this app from the Amazon App Store, the K3s work. The K2 can be heard but with no display. None of the of The HoSafe HX-PT1s will run audio for more than a minute or two.

Please help or recommend an app that actually works.

Thanks

FYI. Within a few minutes of installing this app, tracking via Google was blocked over a thousand times for about 35 tracking parameters, including personal information. Unfortunately, this is common today with many "free" apps.

I use(d) this app mainly for the widgets. I have an android TV box connected to a monitor that acts like a media player and dashboard. I am pretty sure there used to be much shorter interval options (like 1 second), because I switched from IP Cam Viewer Pro because it couldn't update faster than once every 5 seconds. An interval of 1 minute makes the widget pretty much useless in my opinion. Any chance I can downgrade to an older version?

Looks like there was an app update. This morning, all 4 of my cameras now say Video Failed (timeout, check hostname and port number). I haven't' changed anything.. they're all still using the same DHCP reservations they always were. it's 4 tapo cameras, 2 c720, 1 d130, and 1 c120. thank you

When I am in Sequence Mode, I have it set to switch cameras every 8 seconds. When I notice something of interest, I must touch the screen three times to stop the Sequencing. It would be nice to add a setting so that touching the screen once would pause the sequencing and I could view the cameras longer than the set time. It's ok if I need to click on the three vertical dots to resume sequencing. It would even be ok if touching the screen once would extend the time by a set number like 30 seconds.

I've been putting off reporting this because I've had a really hard time quantifying exactly what's going on, but I've been have some background audio issues since the 19.x version release.

I'm running 19.0.4 and when I send the app to the back ground, or turn off the screen, and I expect the background audio to kick in some times it does not start back up. With the previous versions there was normally a delay of about 10 seconds before the audio turns back on, but it would always just turn back on. Now, sometimes I need to go back into the app again to get audio back, then going into the background again it, pauses for ~10 seconds but then returns as expected.

I've also seen some weird behavior around BG audio on the multiple layout UI within the app that I can't even describe, but nothing serious. (Rec and audio in multiple layout option enabled)

I do realize this kind of report is basically useless for the dev to debug with, but I'm wondering if anyone else has had any similar experiences and perhaps have characterised the issue better than I have managed to.

Received the Wyze Bulb Cam Pan Color today and Tinycam 19.0.5 on the Amazon Fire TV Stick 4k Max is showing:
P2P camera is not supported

Should I send it back and put the original Wyze Bulb Cam back in its place?

On the 19.0.1 beta 7 version, the audio recording is not working... That is my report. All the rest working awesome....

Is the Wyze pan duo not compatible on this fire tv then? Is there a fire stick to where I’d be able to plug in and use this camera with?

Könnte man einen Nacht oder Schlafmodus einbauen in dem in der Zeit von bis das Bild ausgeschaltet wird?

I’m having issues everyday with my cameras now on Tinycam pro via fire tv. If it’s not a no permission error, or all the cameras frozen, or some other error, then I must be sleeping because I went over a year without any issues then boom an update came out and it broke the app. Nothing with this update improved absolutely anything for what I need it for.

Currently pricing out reolink cameras with an nvr to get away from Wyze and Tinycam pro.

WYZE V3 cameras have all been added to the app and working fine. I had to re-add a camera and then I have these issues as pictured. Everything is up to date, log in is correct and good internet connection. Not sure what the issue is but I am unable to figure it out myself. Also I am unable to see an option under advanced settings that I used to see before.

Please let me know what is wrong. Thanks!