Tvheadend

Meindert Oldenburger wrote:

The need for this is because i like to schedule my PC more efficiënt, without retrieving the info from differend places.

It would be great if I could retrieve the following information in my solution (script) from tvheadend:
- Top x near feature recordings. I need this to plan when the PC must be switched on (RTC);
- Current recordings. To prevent shutting down the PC;
- Current Live TV streams. To prevent shutting down the PC;
- Current post processings ...

I'm only using DVB-S2 so the list above is not all (HTTP (VLC, MPlayer), HTSP (Kodi, Movian) and SAT>IP)

Like I said in the forums you can get most of this information via the JSON API.

Current live streams can be viewed via http://ip:9981/api/status/subscriptions
which outputs

{"entries":[{"id":784,"start":1433924548,"errors":0,"state":"Running","hostname":"192.168.1.40","title":"VLC/2.2.0 LibVLC/2.2.0","channel":"BBC One HD","service":"DVB-T2 Waltham/770MHz/BBC ONE HD"}],"totalCount":1}

Upcoming & currently active recordings http://ip:9981/api/dvr/entry/grid_upcoming

As for post processing I think you'll have to get your external script to notify that it's finished etc.

It is true there are some urls that I can use, but they are not complete and point to different places . Also do I have the feeling that it is not stable as I would aspect from an API.

Summorize:
- Top x near feature recordings. I need this to plan when the PC must be switched on (RTC);

• .../api/dvr/entry/grid_upcoming
  - Current recordings. To prevent shutting down the PC;
• .../status.xml
  - Current Live TV streams. To prevent shutting down the PC;
• .../api/status/subscriptions
  - Current recording streams. To prevent shutting down the PC;
• ?
  - Current post processings ...
• ?