Cameras Not Working in Apple Home

[harris_kevin]

Arlo recently had a firmware update in the last week and for whatever reason non of my Arlo cameras are showing a feed on Apple home any longer. Wireless floodlight, ultra 3, wireless doorbell etc. Anyone else?

[BrookeN]

Sounds like you need a token reset. I've sent a token reset request to your base station that should resolve the issue. Please reboot your base station (remove and reapply power) allow the base station to come back online and try setting up HomeKit again using these instructions:
 

https://kb.arlo.com/000063184 
 

[harris_kevin]

That did not help. It actually made it worse. After removing both of my Arlo smart hubs I was able to add one of them again but the other one will not connect to Apple home. 

The one that did connect is having the same issue. It shows the floodlights and I can control them just fine like it previously did and detects motion on the Apple home app but the camera feed does not come through. 

It has worked seamlessly for years, cameras, doorbells, floodlights, motion etc. Then all of a sudden the camera feed stopped working but the floodlights and motion worked on all cameras with both smart hubs. Now one smart hub won’t connect at all and the other one is having the exact same issues as I’ve had the last few days 

[harris_kevin]

And now it’s saying on the one that won’t connect that it is already connected to another Apple home. I’ve had literally no issues for years and now I update the Arlo firmware and it’s garbage

[BrookeN]

Can you tell me which firmware you are on?

[harris_kevin]

My VMB4540r3 is on 

1.30.0.0_1950_a99cbf6

My VMB5000r6 is on 

1.30.0.0_1976_a99cbf6

I spoke to support last night and I got them to send another token to VMB5000r6 and I got it all connected to Apple home again so both bases and their cameras, floodlights etc are back in Apple home. Just like before though the camera feed and previews show “no response” but the floodlights and motion sensors all work how they have for years. 

Support had no idea why it just started having this issue. 

[BrookeN]

Thank you for the update, I am glad you got it working as expected.