My new Homebase 3 now reports 0GB available of 0GB total storage.
Homebase 3 S380 v 3.3.0.3 with 1TB Toshiba hard drive installed and formatted paired with 2K wireless doorbell T8210 v 1.1.1.7.
Used to tell me something like 986 GB free. Then
App told me - to paraphrase: new faces recorded, pick those you know. There were three images of “me”. One was clear the other two fuzzy.
I picked the clear one and told homebase it was “me” and it was added to known. Tried to add the other two and got message - does not meet image quality criteria. Also in trying to add, fuzzy image, chose to name it “me” also and app offered to “merge” with first “me” image. Anyway, none of the fuzzy images could be added. Deleted two fuzzy images.
Sometime later returned to app and now was told 0GB of 0GB on homebase 3. Clicking on more storage details gives spinning circle/lines and never gives details. Cold reboot homebase 3, no change.
Still recording new events on wireless doorbell that I believe must be playing from homebase 3.
Also puzzling, clicking on homebase 3 shows 1 known face and 0 unknown faces. But app AI edge shows 0 familiar faces and 0 unknow faces
Seems like Homebase 3 is confused about what storage it has.
Suggestions?
Also - get rid of annoying full screen ad for homebase 3 every time opening the app
last night my HB3 lost connection to my cameras. my HB2"s were still working normally but the HB3 would not display cameras. i tried rebooting the modem the router & the HB3 with no luck. after about 2 hours 1 by one the cameras started coming back until the system was back up and running. my guess for my problem is a eufy (amazon servers in the usa) server issue. for you try this, just for kicks, could you reboot your modem and router. it may show your connected to the internet, but you may be dropping packets and not connecting with the eufy servers. another thing to try would be to power down your HB3 then remove your toshiba drive and see if when you reboot the internal storage will show up. beyond that i would contact eufy support. you may be heading for a factory reset or return.
To verify Toshiba HDD working, removed and “deep” formatted on Windows machine. It reads and writes fine.
Installed known good PNY 120 GB SSD in Homebase 3. It was correctly identified as 120 SSD in Homebase 3 and I was told to format. 3 hours later still formatting. Closed app and reopened app and was told “Format Failure”
Ok, looking like Homebase 3 problem, not my HDD/SDD problem.
Tried to start email support ticket with Eufy. Forced to choose device with problem from a “list”. Search for S380 or homebase found nothing. Can only choose from various webcams or doorbells. HA HA Homebase2 and Homebase3 must need no support.
Yikes! and getting really, really annoying to get full page ad on opening app.
when i first put the HB3 into service i tried an old but new wd velociraptor enterprise hd with no luck. it seems at present the supported hd list is short. good luck.
An update: Eufy Server/Communication Issues as the cause?
to answer JD, Confused by your question - Eufy Homebase3 must “format” any “new” drive HDD/SDD before it can be added to available storage. Upon inspection, Homebase 3 made some proprietary partitions, two 480GB one 30GB and left some free space on my 1TB Toshiba HDD. So previously formatted drive will work only after Homebase 3 “blesses” it with new formatting.
maybe 0GB message has nothing to do with drive (or formatting) and is related to bad communication between Homebase 3 and or broken Eufy cloud servers?
Dpoppo’s information above about Homebase3 cameras going offline and then coming back possibly related to communication issues with Eufy servers made me think
All the time my Homebase3 reported 0GB, all local services like viewing live or even recorded video and recording of new detected motion worked OK
opening app, and clicking on Homebase3, it takes a few seconds to populate info about xGB of yGB storage (need to phone home?)
For kicks, I reinstalled my old/new (now with NTFS) Toshiba drive in Homebase3. HB3 offered to format, and 5 minutes later - viola 986 GB of storage available. That was two days ago - all still working and reporting well
I speculate that there is bidirectional communication between HomeBase3 and Eufy servers, when servers or communication is compromised, Eufy app and access to video/configurations/settings is impaired.
While Eufy is advertised as “local security” it won’t fully work without a connection to to the Internet, and more importantly, a working Eufy server. Hope Eufy never decides to start charging for access. (see below)
PS good move on removing full page ad for Eufy on opening app. Please counsel decisionmakers to avoid similar blunders in the future. Change business model and users will leave.
@noteufy thanks for the update on expandable storage.
Yes, I’ve noticed that too. When the eufy servers are down you are unable to view recorded videos even though they advertise it as secure local storage.
So you think the update borked your hard drive?
That’s what it sounds like to me… firmware updating bug causing HD to be unrecognized.
The HD does have some partitions on it that the OS is using and possibly that’s where it’s storing facial recognition.
So - re-re-reformatted my 1TB Toshiba HDD and it seems to be working.
Yes I believe this firmware update borked HDD.
A thoughtful strategy might be to keep “important” information, like config files, facial recognition data, and settings (for attached devices) only on the imbedded 16GB storage (16GB seems like enough for that)
Only put video data files on add-in storage devices. Hose the HDD, lose only video, not config/setup data.
Oh well - I look forward to Eufy retroactively asking for a subscription fee to access my old recorded videos.
The strategy you mentioned sounds logical.
I wonder if the firmware update caused the HB3 to “restart”? Thus making the HDD inaccessible… That would be a terrible flaw.
I suppose you could test that out… Shut OFF the HB3 and then turn it back ON.
I read it has a CPU: Quad-core ARM Cortex-A55, so when eufy pushes out an update can it be considered a bios update that gets flashed onto the EPROM of the motherboard that the CPU uses to perform start up procedures?
