I'm having a similar problem.
I have two Beyonwiz machines, an S1 and a P1.
Most of my recordings are set to record on the S1 which has the larger drive, but some shows which are very clearly set in IceTV to record on the S1 are recording on the P1 instead.
Is anyone else still encountering such a problem?
yes, I have.
I have reported this to Beyonwiz. Who were emailing a query off to the developers.
...
They also posted about it in the Beyonwiz beta tester's forum 
One suggested workaround there was to change the IceTV device ID on the Beyonwizes, then change it back.
If the post was only in the last few days, then it may have been after I talked with BW support during this last week about the problem.
On my devices, (devicii?) the problem only manifests itself on an intermittent basis. Sometimes goes for a week or so before I notice it.
I'm not sure if changing the ID on the BW would resolve this permanently, and if that's the requirement to resolve it, how do you predict when to do this?
I'm assuming what is meant that is that you select the opposing device in the setup, and then immediately reselect the correct one?
I talked with support at IceTV, and they suggested that the BW was causing this when doing the scheduler fetch by inadvertantly selecting the first device in the list (ID0), when it should select the second one (ID1). This would mean that the second device in the list would be receiving the timers that should go to the first device.
This is just for info only, probably wont help us fix the problem
Apparently. the request identifies which of the devices Ice tables to pull the timers from, by ID number, not device name.
