509 | | If that's not it, there is probably another reason why '''augment_timezone''' can't figure out which version of MythTV you have. Look in ~/.shepherd/log/shepherd.log (or whichever log file corresponds to Shepherd's most recent full run) under "augment_timezone". |
| 509 | If that's not it, there is probably another reason why '''augment_timezone''' can't figure out which version of MythTV you have. One reason might be that you run Shepherd on a remote system. In that case, in ~/.shepherd/log/shepherd.log (or whichever log file corresponds to Shepherd's most recent full run), you'll see something like this: |
| 510 | {{{ |
| 511 | : ERROR: Could not find info to establish database connection to MythTV. |
| 512 | : ERROR: Missing essential DB connection info. |
| 513 | : No valid response from MythTV. |
| 514 | : Assuming MythTV's timezone is "None". |
| 515 | : *** If this is wrong, guide data may be in wrong timezone! *** |
| 516 | : |
| 517 | : - Target timezone is "None". No need to do anything. |
| 518 | }}} |
| 519 | And to fix, you will need to manually instruct '''augment_timezone''' which zone to stamp its times with. You can do this with the command to set default options, e.g.: |
| 520 | {{{ |
| 521 | tv_grab_au --component-set augment_timezone:timeoffset=Auto |
| 522 | }}} |
| 523 | The above tells '''augment_timezone''' to try to figure out your timezone based on its local system. If this isn't the same as your MythTV box, it will probably get things wrong. You can specify a timezone by replacing "Auto" in the above command with something like "+1000"; however, bear in mind this may become inaccurate during Daylight Savings Time changes. |