How are price changes detected in Fredy?

[gorgobacka]

Hi @orangecoding,
I'm quite new to the field of real estates checking and I'm wondering how robust the detection of price changes is.

I read the issue #102 and I understand the solution that you are calculating a hash for the ID based on the real ID and the price - if the price changes, the ID will change and it's a new listing.

But Fredy parses only the first page of a provider. Are entries with (price) changes pushed to the top again and therefore parsed again? Or does it only work, if a small number of entries was added to the provider?

Btw: From a data analysis point of view, it would be good, if the original ID is also saved to the database. Then it can be used to match those listings.

[orangecoding]

Hey @gorgobacka
Since I’ve switched Fredy’s storage from LowDB to SQLite, prices are now stored as well. If a price changes, I’m not entirely sure whether the provider (like ImmoScout) resets it to the original value, but I doubt it.

With the new Listings table introduced in this release https://github.com/orangecoding/fredy/releases/tag/12.2.0, I could theoretically add a "watch" feature. Listings marked as "watching" would then be regularly checked for price changes until they’re set to inactive.

That would be a larger feature, but I do think it would benefit everybody. That said, the UI is getting increasingly complex, probably the right moment for someone with actual design skills to take a closer look. :D

[orangecoding]

1 step closer @gorgobacka
#215

[gorgobacka]

Thanks for update. I will try it out as soon as I'm back from vacation.