Zipabox triggering rules from v2 after migration to v3

Alberto Macias shared this problem ago

Known

I have had zipato products for a long time now, until yesterday I refused to migrate to V2 due all the known issues on the community, I had a zipatile2 and zipamicro running a few rules on V3 for months but decided to migrate my main system using my zipatile2 as master and adding my zipabox (that was running in v2) as slave, migration seem to happen flawlessly (of course loosing al rules and virtual devices, it was expected), after migration, setting up a few rules on v3 to my surprise I see that old rules from v2 are still being triggered from my zipabox, anyone else have had this issue? how to erase those rules without resetting to factory settings? (I have tried to sync both ways and also upgrade firmware, which doesnt work also, without luck) any advice?

The same problem 0

Replies (1)

Alberto Macias ●

Anyone else having this issue?

Reply URL

Erik M ●

Yes I had the same issue.....I gave up and started over.

URL

Chucky ●

Hello,
You've hit upon a tricky and frustrating issue, which unfortunately isn't entirely uncommon with Zipato migrations, especially when dealing with legacy devices like the Zipabox. Here's a breakdown of the problem and potential troubleshooting steps, focusing on avoiding a full factory reset:

Understanding the Problem:

Residual V2 Rules: Even after a successful migration, some remnants of the V2 configuration can persist on the Zipabox. This is likely due to the firmware or internal storage not being fully overwritten during the migration process.
Synchronization Issues: While synchronization is intended to align configurations, it may not effectively remove residual V2 data. This is particularly true when dealing with significant version differences.
Firmware Glitches: Firmware updates can sometimes be unreliable in clearing out old data, especially when dealing with complex migrations. JPMCB Card Services

URL