New day, new problem - Home switch Z axis gets ignored?

Hello guys,
another day on my CNC router starts with a problem, coming out of nowhere, but this time i will try to make it as short as possible, but after 4 hours of trying to fix it, i am already a bit confused.

So, my cnc router has this home sequence: 
1. Z Axis
2. X and Y-tandem together

Usually, when my Z axis was at the uppest position, the proximity switch was already active so the Z axis was waiting until the other axis has been homed, but now when the Z axis is already in the HOME-Position, it drives into the other direction (into the table) trying to find the switch, but why? It was already on the Home switch.
When the Z axis is not in the Home position and the proximity switch is not active, it drives up and the switch gets ignored and drives into the physical end of the axis. I checked in HALmeter and it shows that the switch is FALSE when active (same as the X and Y aixs) and TRUE when NOT-Active.
I tested it with a new Proximity switch, even if HALmeter showed that the original one is working, but same behaviour.

I have tried a couple of things like changing the direction, even i thought this makes no sense because the homing sequnce was always working since the beginning and i compared the INI with one from 5 years ago and everything is same.
I just dont get it.

The last changes i did was when trying to set up the A axis, but i have a seperate settings-folder. (i tried to run that config, but the homing problem is same)

I have attached my INI and my HAL.
Hope you can help me out again.

EDIT;
I was wrong, the proximity switch seems to be broken.
I will install a new switch and then it should work.

I checked in HALmeter and it shows that the switch is FALSE when active (same as the X and Y aixs) and TRUE when NOT-Active.

That seems wrong, The home switch should be active (yellow in halshow)  when activated.

Sounds like you need to invert the inputs

Its working like that, not sure why its setup that way, but its working perfectly. (edit: i believe its because its a NO switch?)

I also have found the fault - broken wires (sensor was okay). Fixed it now and its working again.