New Plugin [pimatic-vvo]

---

Hello community,

after a few days of work I managed it to write my first plugin in CoffeeScript.

There is only one little thing missing to make it work.
If I add/uncomment the business logic (lines 84-109), there is an unknown reference to the “setSchedule” method. Maybe one of the other @developer could have a look on it.

You could find the plugin here: https://github.com/saxn-paule/pimatic-vvo
Use stopid 33000335 for testing purposes or the mockhtml object (line 10 in line 107)

Thanks in advance

@saxnpaule I think the problem is that you try to call @setSchedule (basically the same as this.setSchedule()) instance member in a different context, namely the context of the callback function passed to the Request.get call. To use the context of the outer function you can simply use the => instead of the -> operator in line 86 as follows:

Request.get url, (error, response, body)  =>

...

    @setSchedule(placeholderContent)

What is this plugin for?

@gleno0h It provides time & status information for public transport in the Dresdnen area. https://www.vvo-online.de/en
See also https://forum.pimatic.org/topic/3866/vvo-dvb-iframe-solution

Would be nice to have this on a global scale for different locations similar to what Öffi provides for Android. https://oeffi.schildbach.de/index.html

@mwittig Thank you for the explaination. I also thought in this direction, but didn’t know how to solve. The call works now, but it seems, that the frontend template isn’t used at all.
The HTML isn’t shown - I don’t see the placeholder DIVs and the emit isn’t cought
In the past it already worked. Do you have an idea?

Does pimatic has a an internal template cache?

@Gleno0h as @mwittig already discribed, its for bus and tram schedules for the area around Dresden. At first I also wanted to have a generic solution, but I couldn’t find a matching API for getting the data. If you could provide one, I could give it a try.

@saxnpaule said in New Plugin [pimatic-vvo]:

At first I also wanted to have a generic solution, but I couldn’t find a matching API for getting the data.

It might be possible using the googlemaps API, but I am not sure about this.

nice! thx @SaxnPaule
and yes indeed, such a plugin for a general information for different public transport companys and locations would be interesting.

@saxnpaule said in New Plugin [pimatic-vvo]:

The HTML isn’t shown - I don’t see the placeholder DIVs and the emit isn’t cought
In the past it already worked. Do you have an idea?

I’ll have a look shortly

@saxnpaule said in New Plugin [pimatic-vvo]:

The HTML isn’t shown - I don’t see the placeholder DIVs and the emit isn’t cought
In the past it already worked. Do you have an idea?

See my PR - https://github.com/saxn-paule/pimatic-vvo/pull/1

The template for the device was missing. Moreover, attribute value change subscription need to be done in the afterRender method as they may raise an undefined exception oat initialization time otherwise.

Thank you! The Html template is rendered now, but its strange, I always get errors :?
I did no changes to your code except deleting the 2nd placeholder div.

@saxnpaule Sorry, seems like it only worked for me when I had completely removed the attribute value subscription as I am seeing the same error now. Actually the attribute declaration was missing as part of device class implementation - see PR https://github.com/saxn-paule/pimatic-vvo/pull/2

Great, it works. Thanks. I’ll publish a first version to npm soon.

I added some changes for supporting multiple departures/devices at the same time and added a readme.

Publishing to npm has been done, so the plugin should be available tomorrow.

At the moment the schedule is displayed after the first reload (30 seconds). That has to be changed. Coming soon…stay tuned

released new version 0.0.2 with fix in package.json

version 0.0.4 released 2017-11-27

• Fixed responsive design

Some errors …

16error [pimatic]: An uncaught exception occurred: Error: connect EHOSTUNREACH 212.111.241.212:443
at Object.exports._errnoException (util.js:907:11)
at exports._exceptionWithHostPort (util.js:930:20)
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1081:14)
From connect
at TLSSocket.connect (/home/pi/pimatic-app/node_modules/pimatic/startup.coffee:55:29)
at Object.TLSSocket._init.ssl.onclienthello.ssl.oncertcb.exports.connect (_tls_wrap.js:1048:11)
at Agent.createConnection (https.js:79:22)
at Agent.createSocket (_http_agent.js:188:16)
at Agent.addRequest (_http_agent.js:157:23)
at new ClientRequest (_http_client.js:142:16)
at Object.exports.request (http.js:31:10)
at Object.socket.once.exports.request (https.js:189:15)
at Request.start (/home/pi/pimatic-app/node_modules/pimatic-vvo/node_modules/request/request.js:748:32)
at Request.end (/home/pi/pimatic-app/node_modules/pimatic-vvo/node_modules/request/request.js:1512:10)
at end (/home/pi/pimatic-app/node_modules/pimatic-vvo/node_modules/request/request.js:561:14)
at Immediate._onImmediate (/home/pi/pimatic-app/node_modules/pimatic-vvo/node_modules/request/request.js:575:7)
at processImmediate [as _immediateCallback] (timers.js:396:17)
This is most probably a bug in pimatic or in a module, please report it!

version 0.0.5 released 2017-12-16

• Handled connection error that causes pimatic to crash if VVO-API is not available

Another error. Maybe the same problem like last time?

error [pimatic-vvo]: { [Error: connect EHOSTUNREACH 212.111.241.212:443]
code: ‘EHOSTUNREACH’,
errno: ‘EHOSTUNREACH’,
syscall: ‘connect’,
address: ‘212.111.241.212’,
port: 443,
__trace: ‘Error: From connect\n at TLSSocket.connect (/home/pi/pimatic-app/node_modules/pimatic/startup.coffee:55:29)\n at Object.TLSSocket._init.ssl.onclienthello.ssl.oncertcb.exports.connect (_tls_wrap.js:1048:11)\n at Agent.createConnection (https.js:79:22)\n at Agent.createSocket (_http_agent.js:188:16)\n at Agent.addRequest (_http_agent.js:157:23)\n at new ClientRequest (_http_client.js:142:16)\n at Object.exports.request (http.js:31:10)\n at Object.socket.once.exports.request (https.js:189:15)\n at Request.start (/home/pi/pimatic-app/node_modules/pimatic-vvo/node_modules/request/request.js:748:32)\n at Request.end (/home/pi/pimatic-app/node_modules/pimatic-vvo/node_modules/request/request.js:1512:10)\n at end (/home/pi/pimatic-app/node_modules/pimatic-vvo/node_modules/request/request.js:561:14)\n at Immediate._onImmediate (/home/pi/pimatic-app/node_modules/pimatic-vvo/node_modules/request/request.js:575:7)\n at processImmediate [as _immediateCallback] (timers.js:396:17)’ }

Yes, the error is still logged but pimatic shouldn’t die any longer.

Do you have DSL with nightly disconnect?

No dsl. Kabelanschluss.