<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: VMB 4000 - Pro 2 in Arlo Pro 2</title>
    <link>https://community.arlo.com/t5/Arlo-Pro-2/VMB-4000-Pro-2/m-p/2338485#M62407</link>
    <description>&lt;P&gt;If you had been around as long as some of us have, you'd have read of others that had to (re)create their accounts to clear out whatever was causing the problem. It doesn't happen often (as far as I can tell) but it does happen. And when doing so causes the problem to disappear, there's some proof in the pudding.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Just because it assaults your sense of right and wrong doesn't mean it doesn't happen. You're always free to apply to Arlo to fix things for the rest of us...&lt;/P&gt;</description>
    <pubDate>Sun, 16 Jun 2024 13:59:41 GMT</pubDate>
    <dc:creator>jguerdat</dc:creator>
    <dc:date>2024-06-16T13:59:41Z</dc:date>
    <item>
      <title>VMB 4000 - Pro 2</title>
      <link>https://community.arlo.com/t5/Arlo-Pro-2/VMB-4000-Pro-2/m-p/2338380#M62400</link>
      <description>&lt;P&gt;All attempts failed. But I found a solution.&lt;BR /&gt;I made a new account. I followed the boot procedure and update. Base was now recognized - So, no internet or router problems, etc....&lt;BR /&gt;Remarks: Arlo makes it difficult for users of "end of life" devices so that subscriptions are forced. The new format is less clear and user-unfriendly. Thanks ARLO, but the trust is gone!&lt;/P&gt;</description>
      <pubDate>Sat, 15 Jun 2024 03:36:45 GMT</pubDate>
      <guid>https://community.arlo.com/t5/Arlo-Pro-2/VMB-4000-Pro-2/m-p/2338380#M62400</guid>
      <dc:creator>Mir54026</dc:creator>
      <dc:date>2024-06-15T03:36:45Z</dc:date>
    </item>
    <item>
      <title>Re: VMB 4000 - Pro 2</title>
      <link>https://community.arlo.com/t5/Arlo-Pro-2/VMB-4000-Pro-2/m-p/2338409#M62404</link>
      <description>&lt;P&gt;Sorry but EOL devices don't need to be "forced" into a subscription. There never has been an issue with this. That said, recent issues have popped up with at least some legacy devices leading to more drastic measures to recover from them. In your case it rather sounds like your account was somehow corrupted so the new account was needed (it shouldn't have been needed) to get around the issue.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It's not a subscription thang...&lt;/P&gt;</description>
      <pubDate>Sat, 15 Jun 2024 13:47:30 GMT</pubDate>
      <guid>https://community.arlo.com/t5/Arlo-Pro-2/VMB-4000-Pro-2/m-p/2338409#M62404</guid>
      <dc:creator>jguerdat</dc:creator>
      <dc:date>2024-06-15T13:47:30Z</dc:date>
    </item>
    <item>
      <title>Re: VMB 4000 - Pro 2</title>
      <link>https://community.arlo.com/t5/Arlo-Pro-2/VMB-4000-Pro-2/m-p/2338440#M62406</link>
      <description>&lt;P&gt;&lt;a href="https://community.arlo.com/t5/user/viewprofilepage/user-id/378"&gt;@jguerdat&lt;/a&gt;&amp;nbsp;WTF? Account was corrupted? What nonsense is that?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It's unacceptable of a company to do something to their firmware that requires users to reset the whole system and set it up from scratch. In this situation, the deployment of firmware should have been stopped. It wasn't.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 15 Jun 2024 21:59:56 GMT</pubDate>
      <guid>https://community.arlo.com/t5/Arlo-Pro-2/VMB-4000-Pro-2/m-p/2338440#M62406</guid>
      <dc:creator>Edinburgh_lad1</dc:creator>
      <dc:date>2024-06-15T21:59:56Z</dc:date>
    </item>
    <item>
      <title>Re: VMB 4000 - Pro 2</title>
      <link>https://community.arlo.com/t5/Arlo-Pro-2/VMB-4000-Pro-2/m-p/2338485#M62407</link>
      <description>&lt;P&gt;If you had been around as long as some of us have, you'd have read of others that had to (re)create their accounts to clear out whatever was causing the problem. It doesn't happen often (as far as I can tell) but it does happen. And when doing so causes the problem to disappear, there's some proof in the pudding.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Just because it assaults your sense of right and wrong doesn't mean it doesn't happen. You're always free to apply to Arlo to fix things for the rest of us...&lt;/P&gt;</description>
      <pubDate>Sun, 16 Jun 2024 13:59:41 GMT</pubDate>
      <guid>https://community.arlo.com/t5/Arlo-Pro-2/VMB-4000-Pro-2/m-p/2338485#M62407</guid>
      <dc:creator>jguerdat</dc:creator>
      <dc:date>2024-06-16T13:59:41Z</dc:date>
    </item>
  </channel>
</rss>

