New plugin [pimatic-tv-program]

---

Hello community,

today I built a small plugin that shows whats on TV today.
The data is based on tvspielfilm.de RSS feeds.

You could decide, whether you want to see, whats on TV now or 20:15 or 22:00 o’clock.

The plugin could be tested from git master branch https://github.com/saxn-paule/pimatic-tv-program

@developer One last thing needs to be done. How is it possible to trigger the TvProgramDevice reloadSchedule method from the afterRender method of the tvProgramDeviceItem? So that there is no need to wait 5 minutes until the first request is done.

could none of the @developer answer my question?
I know that it has something to do with the @device.rest call. But what needs to be done to make it work?

@saxnpaule Hi. I have just quickly browsed through your code. My suggestion is to call @reLoadSchedule() right before registering the timer callback using the setInterval() function. This way the schedule should be loaded right away on dive initialization

Thank you, but that only works for the pimatic start. If you open a new tab or press Ctrl+F5 the page is empty until you wait 30 seconds. So it necessarily needs to be called from the afterRender method.

@mwittig he need the hint for the rest.api

@SaxnPaule in your device class define an action:

class TvProgramDevice extends env.devices.Device
   attributes:
      schedule:
        description: 'the schedule data'
        type: t.string

    actions:
      reLoadSchedule:
        description: "reload"

now you can trigger it in the frontend class

	class tvProgramDeviceItem extends pimatic.DeviceItem

		afterRender: (elements) ->
                  @device.rest.reLoadSchedule(global: no)
                  .done(ajaxShowToast)
                  .fail(ajaxAlertFail)

@saxnpaule said in New plugin [pimatic-tv-program]:

Thank you, but that only works for the pimatic start. If you open a new tab or press Ctrl+F5 the page is empty until you wait 30 seconds. So it necessarily needs to be called from the afterRender method.

Ok, but there is no need to trigger an action from the the frontend. You can simply read the attribute value of the schedule. That’s a lot simpler if you combine it with my other suggested change.

renderSchedule = (newval) => $("#"+@id+"_vvo_placeholder").html(newval)
renderSchedule(@getAttribute('schedule').value())
@getAttribute('schedule').value.subscribe(renderSchedule)

@mwittig Thats the cleanest way to go in my opinion. It works. Thank you.
@kosta Thank you for the example. I’m sure I could use it in other scenarios.

Btw. suggested change work fine for me. If you like I can file them to a PR.

Note, the current, pending PR is only about a few other minor improvements

I already added the code and published the first version to npm. Thx

Ah, now I see your PR. It’s the VVO plugin

I change it in the other plugins as well.

version 0.0.3 released 2017-11-23

• Added interval option to decide the refresh interval
• Added “short” option to hide images and description

cool thx for the nice plugin.

Is it possible to implement a rule handler to check if a specific series or tv show is running?

Would also be nice, if we could filter on which senders we want to be listet.

Filter for specific stations should be possible. But how do you want to configure it? You need to know the exact names, because the only way would be a string lookup. Or do you have a better idea?

@saxnpaule You could implement an alias for each station or use a list with true/false inputs in the config.

version 0.0.4 released 2017-11-24

• Added option to show only selected stations

Consider Readme for further details.

version 0.0.5 released 2017-11-27

• avoid pimatic to crash on connection error
• fixed responsive design

version 0.1.0 released 2018-01-06

• changed xml parser library due to install issues of xml2json

@saxnpaule My advice is not to use “latest” as part of the plugin’s package dependencies, but specify a version range which excludes major versions, at least. This way you can avoid sudden installation issues when a major version of a package including breaking changes is released. See semver for more details about specifying version ranges.

Yes, I know this. Don’t know why I’m doing this for private projects :-? I’ll change this with the next release.