No more movement through screen

[MichielioZ]

I've been using the Klipper branch linked here (https://github.com/gbkwiatt) for a while now on my Ender 7 and it has been working great. Even bed mesh worked out of the box for me (only if you have 5x5 in your printer.cfg).
Unfortunately, there was a recent update that broke the "Move" menu and also the "Levelling" menu, everything else seems to still work fine. The screen still beeps when I touch the tiles, but it doesn't open the menu.
Hoping anybody can verify if I'm not the only one with this problem and maybe some hints on how to fix this ?

Update:
As per your impressive walk-through, I configured KIAUH to use the custom repository. I found out you can actually revert Klipper a certain number of commits through KIAUH>advanced>rollback. It seems that at least on my printer I had to rollback to v0.12.0-369. (before the 5 commits on June 8th, so 18 commits back at the time of writing, calculated through this graph)
So it seems the problem occurred for the first time at build >= v0.12.0-411 for me ... Hope this helps ?!

P.S. I still would like to update to the latest of course, so any help is appreciated :-)

[adrianjdebono]

Thank you so much @MichielioZ i spent the last 15 hours trying to figure out why my other machines were working fine but the new machine i installed wasn't working.
You saved the day. I think i did 79 reverts haha

[MichielioZ]

No problem @adrianjdebono 👍

Just in case someone more knowledgeable than me looks at this, it seems like the problem is probably to do with using a probe for Z-axis homing and probing. The only thing in the changelog that made sense to me concerning Klipper v0.12.0 build 411 is that it seems something changed on the probe code to accommodate for the Eddy current sensors that support was added for. Hopefully either @fryc88 or @gbkwiatt sees my issue and finds the time to look at it ?!

[fryc88]

Problem would be probably with renamed macros for homing or something like that, I'm not too sure. For the screen firmware I don't have project unfortunately, and I'm not really touching this GitHub anymore as I don't even have this screen to play with it anymore.

…

On Fri, 25 Oct 2024 at 16:09, MichielioZ ***@***.***> wrote: No problem @adrianjdebono <https://github.com/adrianjdebono> 👍 Just in case someone more knowledgeable than me looks at this, it seems like the problem is probably to do with using a probe for Z-axis homing and probing. The only thing in the changelog that made sense to me concerning Klipper v0.12.0 build 411 is that it seems something changed on the probe code to accommodate for the Eddy current sensors that support was added for. Hopefully either @fryc88 <https://github.com/fryc88> or @gbkwiatt <https://github.com/gbkwiatt> sees my issue and finds the time to look at it ?! — Reply to this email directly, view it on GitHub <#15 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMB23JERMVGBP3X4VBAPN4DZ5JNLFAVCNFSM6AAAAABLHFM5W6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZYGA4DAOJTGM> . You are receiving this because you were mentioned.Message ID: ***@***.***>