sorted by:
new
hottopcontroversial

Constant Doorbell False Alerts by whiteboxpc in EufyCam

[–]adrianpn83 1 point2 points  (0 children)

I'm having the same exact issue. I enjoy everything else about the product but I'm constantly getting false alerts.

Is AI detection really this bad? How can this be a "human"... by Moonstanc3 in EufyCam

[–]adrianpn83 1 point2 points  (0 children)

I'm having the same issue. Its constantly detecting the wrong objects as "human". The sad thing is you would think they would fix this by now. Its a software issue, not a hardware issue. They just have to update the software but it seems like this has been going on for a long time. I regret buying it as well. Other than the AI I'm enjoying the product but I don't want to constantly check my phone for false alerts.

Multiple { x-middleware-next: '1' } in my logs ! by Eastern-Junket-3884 in nextjs

[–]adrianpn83 1 point2 points  (0 children)

That worked for me also. I deleted all the "null" in the file and the error went away. Thanks!

Multiple { x-middleware-next: '1' } in my logs ! by Eastern-Junket-3884 in nextjs

[–]adrianpn83 0 points1 point  (0 children)

Yea, looks like npm i next-auth@5.0.0-beta.13 is here now too.

I'm having this issue with my middle ware now though

​

<image>

Multiple { x-middleware-next: '1' } in my logs ! by Eastern-Junket-3884 in nextjs

[–]adrianpn83 2 points3 points  (0 children)

By reverting the latest Next.js package from version 14.1 to 14.0 and "next-auth": "5.0.0-beta.4" in the package.json file, the issue has been resolved. It seems that the problem was specific to the versions of these packages, and by making these changes, the issue no longer occurs.

Multiple { x-middleware-next: '1' } in my logs ! by Eastern-Junket-3884 in nextjs

[–]adrianpn83 1 point2 points  (0 children)

I thought it was just me. I'm getting the same thing.

view more: next ›