You have to wonder sometimes!
Son wanted Dad's taxi to take him back to uni the other day. When we got there I commented that it was a bit chilly in the house. He said, yes the heating was not working so the landlord had sent a "heating engineer" to fix it. They diagnosed a problem with the thermostat, and fitted a new Salus wireless programmable stat as a replacement, but it was still not working.
So I had a look a the stat, seemed to be mostly setup ok aside from displaying the wrong day of the week.
So had a look at the boiler end of it, and that was switched to "manual" on the receiver. So flipped it to auto, and hit the manual override button on the wireless stat, and the first problem became obvious - the wired and wireless bits were not actually paired.
So after a bit of RTFM, I managed to find the magic sequence of power on/off and button hold down sequences to get them paired. Yahoo, now at least the green light on the receiver would light in sympathy with the stat coming "on".
That then left the problem that the boiler was still not firing. The combi boiler itself seemed to be working, and doing DHW ok. Just no CH. So I pondered for a bit wondering if it was possible that they had not wired the receiver correctly? The wires at least looked like they were heading in the right direction and the stats receiver was being powered from the boiler ok. Then I thought to open the front panel flap on the boiler and found a mechanical rotary time switch, set to timed mode, but with all the timing pips in the "off" position. So I flipped that to "always" on, and it all started working as it should. (I had to explain to the local audience that "always on" did not mean massive gas bills - just that the stat was programmable for time and temperature and made the time in the boiler redundant!)
Finally took the liberty of setting the stat to the right day so they did not get their longer warmer weekend temperature setup on Wednesday and Thursday when they were all out at lectures.
I have a suspicion that the heating engineer found it did not respond to the wired stat that was there, and assumed the stat was the problem rather than the internal timer. He probably changed it, found it still did not fix it, then did a runner! (or took one look at the process of pairing them and thought sod that).