- This topic has 55 replies, 11 voices, and was last updated 6 years, 4 months ago by
.
-
Posts
-
Covered up box infra red receiver yesterday with black vinyl tape to see if a possible rogue infra red source is causing the issue. LED lights were left on in the room when it booted with no one present.
Had no random boots in last 24 hrs. Previously box was booting 2 or 3 times a day. Seems very likely it has to be external infra red causing the issue. I will leave another day to be sure before removing the tape.
I have a led gizmo that gives the appearance that a TV is on in the room. It’s possible that this was responsible for the boots when no one was in.
Mine is still responding to the Topfield remote. It did it again a few minutes ago. Pressed the ‘On’ button for the Toppy and under a second later the 5000T LED changed from red to blue.
A1944 – 4 minutes ago »
Mine is still responding to the Topfield remote. It did it again a few minutes ago. Pressed the ‘On’ button for the Toppy and under a second later the 5000T LED changed from red to blue.
Trying to eliminate the box switching itself on without any other remote activity. Confidant it does boot from other remotes and it’s looking like it could also boot from other infra red sources like say low energy lighting. My other 4 Humax boxes Two HDR-FOX-T2’s, HDR-1000S and Foxsat-HDR aren’t affected at all. Try changing the infra red code set used by the 5000T, this may stop the Toppy remote booting the box.
http://myhumax.org/forum/topic/multi-code-function-hdhdr-remote-2#post-9750
grahamlthompson – 55 minutes ago »
A1944 – 4 minutes ago »
Mine is still responding to the Topfield remote. It did it again a few minutes ago. Pressed the ‘On’ button for the Toppy and under a second later the 5000T LED changed from red to blue.
Try changing the infra red code set used by the 5000T, this may stop the Toppy remote booting the box.
I have already tried that with no change in the problem. Changed it from code 1 to 6. (See post 25)
A1944 – 51 minutes ago »
grahamlthompson – 55 minutes ago »
A1944 – 4 minutes ago »
Mine is still responding to the Topfield remote. It did it again a few minutes ago. Pressed the ‘On’ button for the Toppy and under a second later the 5000T LED changed from red to blue.
Try changing the infra red code set used by the 5000T, this may stop the Toppy remote booting the box.
I have already tried that with no change in the problem. Changed it from code 1 to 6. (See post 25)
It’s been a long time since I owned a Toppy. Try booting from it’s remote by pressing zero twice rather than the power key.
Zero twice doesn’t do anything, not sure if it is supposed to. I have just programmed one button of a spare universal with the Toppy power button to see if that triggers the 5000T as well, or if it is just the Toppy remote.
A1944 – 26 minutes ago »
Zero twice doesn’t do anything, not sure if it is supposed to. I have just programmed one button of a spare universal with the Toppy power button to see if that triggers the 5000T as well, or if it is just the Toppy remote.
Some boxes will boot if you enter a valid channel on the remote, in the case of many Humax boxes they will boot from zero and because it’s not a valid channel boot to the last used channel. It’s a handy discrete power on command for programmeable remotes to use a macro consisting of two zeros to boot the box, as it works every time where a single power on toggle can be missed. Does the Toppy boot if you enter a valid channel number on the remote ?
In my experience various buttons on a number of different remotes can switch on a 4000T (and a 4000T running 5000T software), but only after the sequence detailed in my post #22. Has anyone experiencing this problem checked if this is when their box is affected?
David.
aciddad – 13 minutes ago »
In my experience various buttons on a number of different remotes can switch on a 4000T (and a 4000T running 5000T software), but only after the sequence detailed in my post #22. Has anyone experiencing this problem checked if this is when their box is affected?
David.
I have – but never found a repeatable action (so far). And mine has booted with no one in the house as well.
Incidentally – Guessing I don’t have to make a recording to emulate the issue. It’s known the cached epg is cleared overnight and only gets refreshed when the box wakes to make a recording. I have a power on/off sequence 07:00-07:15 so when I get to use the box the epg is fully populated.
Try Power On 07:00 BBC 1 HD Volume 20 with a Power Off at 07:15. Can you now boot the box without it making a recording ?
aciddad – 1 day ago »
In my experience various buttons on a number of different remotes can switch on a 4000T (and a 4000T running 5000T software), but only after the sequence detailed in my post #22. Has anyone experiencing this problem checked if this is when their box is affected?
David.
Not sure, David, but you may have a point here. I will continue checking for a while to confirm, one way or the other.
Losing the will to live. All day after uncovering the IR window, the 5000T has remained firmly in sby. I checked around 22:00 hrs box had gone into sby with red LED after last recording of the day.
Watching Death In Paradise recording on Freesat just noticed 5000T is fully booted with blue led at 22:55.
I have paused Death In Paradise a few times while watching. No idea which if any of the this caused the boot. Based on previous it must be some IR interaction.
Just checked at 23:08 box has gone back into full sby. Need to check that auto power off is still disabled. Might have forgotten to turn it off after last reset.
Checked this morning and Auto Power Off is set to on. This is default so has been on since the recent reset.
This makes last nights boot hard to understand. The unit was recording to 21:02. The unit shut itself down at 23:08 presumably due to auto power off. This means the last remote interaction was 4 hrs before at 19:08. At this time the unit was recording so if a power on command was given at this time the box should have shown blue after the completion of the last recording at 21:02. This didn’t happen, so why didn’t the rogue boot command reset the 4 hr countdown of the auto power off sequence ?
- You must be logged in to reply to this topic.