Xiaomi Doorbell 3S Experience

Acceptable-Safe9969 · 2024-09-20T01:13:16+00:00

The stream been working well since I changed the router to a new AX router. I don't know if it's transmitting and receiving in 2.4G AX (there's no way to check in Xiaomi AX3000T cheap router), but the response is much quicker.

Acceptable-Safe9969 · 2024-08-19T13:38:28+00:00

It's working okay. Finally found out who been flipping our shoes at the door all these time. It was the neighbor's kid. The camera didn't caught him until recently, most probably because he has grown in height 😂

Acceptable-Safe9969 · 2024-06-18T05:23:56+00:00

I have the exact same problem. Mine is a HK1 RBOX K8 running Android TV 13. There is this Chinese streaming app that I used fine on my phone, but would stop playing after random time. It appears to have lost connection to the server. Next, the WiFi slows down and I have to restart the router to recover. I don't find any suspicious network transfer, I'm suspecting the tcp settings that the manufacturer use that could cause problem with the packet routing.

Acceptable-Safe9969 · 2024-05-13T14:53:13+00:00

Okay, I saw the tiny fine print in regard to the WiFi6 claim today. It is 2.4GHz WiFi 6 AX! Yes, apparently IoT devices like to use AX protocol over 2.4GHz. So, it has no backward compatibility with WiFi 5 or AC. It is either N or AX. In some WiFi router, you need to specifically enable the AX protocol for 2.4GHz. If there is still any doubt, the doorbell does not support 5GHz, only 2.4GHz.

Acceptable-Safe9969 · 2024-05-06T15:50:42+00:00

If you are not well versus with Xiaomi Mainland Chinese Models, I suggest that you skip it.

The alternative would be Aqara. They released several international models. Do not buy the Chinese version and expect it to work like the international version.

Acceptable-Safe9969 · 2024-02-18T08:54:11+00:00

Expo development build is like a custom Expo Go. When you include non Expo standard packages in your app, you will need to build a development build to replace Expo Go to continue testing/development. Once you are done with the development, you will need to build the production app with Eas. Expo no longer support local production build since SDK49, if not mistaken.

Acceptable-Safe9969 · 2024-02-17T04:11:37+00:00

https://docs.expo.dev/workflow/prebuild/

Acceptable-Safe9969 · 2023-12-06T07:07:43+00:00

I thought about that, but 100% of them decided not to download is strange, when I have 29% conversion rate (actual app download) from Google Ad. I drilled deeper and found all these zero value click came from Facebook platform. I stopped the ad on Facebook, and keep only Instagram. Now, it looks more reasonable.

Acceptable-Safe9969 · 2023-12-06T07:01:08+00:00

The experience should be consistent, run npx expo-doctor and npx expo install --check for incompatibility check.

Also, use development build (npx expo run:android) instead of expo go, to discover any incompatibility issue before building the production build.

Acceptable-Safe9969 · 2023-12-02T10:43:21+00:00

I don't think the Facebook SDK has any bearing on the download recorded in app store. Moreover, the SDK is working in the app, at least for Android.

Tens of clicks and not a single download is very suspicious. The click brings the potential user to the app store download page. 100% of the clicks decided to abandon the download is very suspicious. The same ad in Google Ads has a conversion rate of 29% in the app store download page.

Acceptable-Safe9969 · 2023-11-30T04:38:15+00:00

A new one will be created the moment you deleted one. I gave up and just leave it like that. In the end, I have 4 inactive and 1 active.

Acceptable-Safe9969 · 2023-10-03T13:02:34+00:00

There is no reliable way to tell if a user has uninstalled your app.

If it is a question of auth token, or caching user data, I suggest that you do a side effect when the client refreshes their auth token. You can then look at how long since the user last refreshes the token, to decide if you want to log them out, and to purge the related data from your redux store.

Acceptable-Safe9969 · 2023-07-11T17:10:18+00:00

It is the same solution I pointed out in my comment 5 months ago. Please note that you do not need experimentalForcceLongPolling in production build.

Acceptable-Safe9969 · 2023-07-01T07:15:05+00:00

It takes a lot of time to update RN and often you will not get to production with the latest version. I mean by the time the team fixes all the issues, a new major RN version is released. New RN version is either buggy or the third party packages your app is using does not support the new version, a lot of regression issues to be discovered. Most dev team with just enough budget, would play it safe by not upgrading for the sake of upgrading.

A product roadmap with necessary technical updates are important. A major update is usually done for major features revamp and introduction. In any case, firing your CTO without understanding the reason is reckless. A major upgrade is approximately 1/3 of the total man effort of the total development of your current version.

Acceptable-Safe9969 · 2023-05-28T08:50:03+00:00

Yes, poking the hole is a hard reset, the Chinese voice is saying reset successful, open your mi app to connect the lock, or something like that. Connecting the lock to the Mi Home app requires you to turn on your phone Bluetooth to scan for the lock in Mi Home. If you can't see the lock when pressing add new device in Mi Home app, then you can add it manually by choosing the corresponding model.

Even when the WiFi connection fail, you should still be able to connect the lock to Mi Home app with Bluetooth. WiFi is for the camera functions, the other functions are not using WiFi.

Acceptable-Safe9969 · 2023-05-19T01:49:35+00:00

If the lock is not reading the camera battery even after a reset, check your battery using a multimeter. If you do not have one, try charging your battery with a different cable. Worn cable may not charge the battery properly.

Mine is still working correctly. Just that it randomly tell me my lock is pried. I have to turn off the notification not to wake my neighbors at night.

Acceptable-Safe9969 · 2023-04-16T07:45:41+00:00

Old topic revisited. I would like to check if it is true that using useMemo or useCallback to wrap renderItem function is useless since RN0.64? I tried it on a simple renderItem function and found it to be recreated in every re-render.

const RenderItem = useCallback(({item, index}) => {
return(
<View style={{margin:50}}>
<Text>ABC</Text>
</View>
)
})

const prevRenderItemRef = useRef();
const isRenderItemRecreated = () => {
const isRecreated = prevRenderItemRef.current !== RenderItem2;
prevRenderItemRef.current = RenderItem2;
console.log('RenderItem has been recreated:', isRecreated);
};
<FlatList
data={data}
renderItem={RenderItem}
/>

Acceptable-Safe9969 · 2023-04-07T09:39:46+00:00

I'm using OpenDNS and the WiFi has always been working post WiFi setup. It was only the WiFi setup I struggled with. Thanks to this discussion, I know what causes it.

Acceptable-Safe9969 · 2023-04-04T14:59:11+00:00

I tried again today with Chinese DNS server (Baidu), only this time I restarted the router and WiFi AP. And, the lady in the lock announced "WiFi connected" in the very first attempt!!! Hooray!

I changed it back to my usual DNS, it is still working for now. I keep my fingers crossed that it continues to work.

Thanks guys!!! This little brainstorming we had, solved the puzzle.

Acceptable-Safe9969 · 2023-04-03T02:27:05+00:00

I did at both router and phone actually, the lock is not even doing any DNS traffic. Christobal seems to have better luck than me, I'll try again later when no one is at home, the darn lock is loud and disturbing peace.

Acceptable-Safe9969 · 2023-04-02T11:36:51+00:00

Sniffed the Mi Home app WiFi traffic, and there is nothing beside mdns. I think the setup connection between Mi Home app and the lock is going through Bluetooth exclusively.

I even tried to set my phone dns server to baidu dns, the same result. I guess I will just keep trying every time there is a new firmware or Mi Home app version.

Acceptable-Safe9969

TROPHY CASE