[NEW UPDATE] Magister for Homey (v2.0.7)

Eternity

Why do I receive this error:


I am able to log into my sons Magister account using his credentials (or mine).

gruijter_dev

@Eternity What version app are you using, and what version firmware are you on?

By the way: you should always use the students' credentials, and not the parents'.

Eternity

@gruijter_dev ;

I use the latest firmware 0.9.3 and latest App from the App store (0.0.9).

gruijter_dev

You could try to install the latest app version from GitHub and see if that fixes it. I cannot publish this version yet because of a problem in the appstore.

[Deleted User]

Did Athom tell you when they expect to solve this app store issue? (I'm waiting for 0.1 as well)

gruijter_dev

They didn't tell me, but Soon!!!!

Eternity

Thanks! I will use the github version! 

Eternity

@gruijter_dev ;
Installed the 0.0.10 version from Git, but get the same error.
It might be an authentication issue, I will look into that first.

gruijter_dev

@Eternity please let me know if the github version indeed solves your issue

Eternity

@gruijter_dev ;
No, I get the same error with the v1.0.10 version (that is the latest on Git, I believe).

gruijter_dev

fw 0.0.10 just submitted for approval in the appstore. A number of bugfixes and compatibility for fw 0.9.3.

[Deleted User]

The flow I use to send a push notification and tell the roster at 07:30:

The function of the boolean is to make sure Homey will only tell the roster once a day if there are one or more changes.

This morning Homey did send the push notification but did say the roster of yesterday instead of the expected roster of today (as configured). Any idea?

gruijter_dev

@hnijveen yes, I found a problem in the roster change detection and the internal roster download function. This is solved with the new version I have already posted on GitHub (v0.0.11). And I just uploaded it to the store.

gruijter_dev

Nice flow by the way! 

ThijsDeJong

what are the triggers for the boolean? To get it on True?

[Deleted User]

Simple: a roster change

[Deleted User]

and @gruijter_dev , it is the app! Thx for that.

ThijsDeJong

Clear THNX for the answer

gruijter_dev

version 0.0.11 has just been approved and is available in the appstore

[Deleted User]

@gruijter_dev : Say roster of today still does tell the roster of yesterday in my flow. Strange thing is it did not do anything last Monday although the boolean was true. I can change the flow to say the roster of tomorrow but well, that is not as it should be. (yes, latest version firmware and app).

MarcelTimmermans

The last view days I get the following error:

Stack trace:

TypeError: Cannot read property 'fullName' of undefined
at /drivers/student/driver.js:665:49
at /node_modules/magister.js/lib/node/magister-node.js:2470:22
at /node_modules/magister.js/lib/node/magister-node.js:5253:18
at /node_modules/magister.js/lib/node/magister-node.js:2484:24
at Request._callback (/node_modules/magister.js/lib/node/magister-node.js:5381:16)
at Request.self.callback (/node_modules/magister.js/node_modules/request/request.js:198:22)
at emitTwo (events.js:87:13)
at Request.emit (events.js:172:7)
at Request.<anonymous> (/node_modules/magister.js/node_modules/request/request.js:1073:14)
at emitOne (events.js:82:20)

gruijter_dev

@hnijveen Thx for reporting. It seems the roster is indeed always one day behind. I will have to fix that. 

@MarcelTimmermans these types of errors are really difficult for me to tackle. They are probably caused because every school fills in the data differently and I have to catch all kinds of exceptions. I posted an experimental version on GitHub that is trying to cope with this. Could you try it out?

Eternity

removed

gruijter_dev

@Eternity : and with removed you mean.... No more "cannot read property" errors with the experimental version???

MarcelTimmermans

gruijter_dev said:

@MarcelTimmermans these types of errors are really difficult for me to tackle. They are probably caused because every school fills in the data differently and I have to catch all kinds of exceptions. I posted an experimental version on GitHub that is trying to cope with this. Could you try it out?

Hi,

Ok will try this. Will be tomorrow. 

[Deleted User]

Not 100% sure yet, but I think a Roster Change using the card The Roster has Changed is not triggering as expected.

I did change my flow to Say Roster of tomorrow (if there is a change). Result: Homey says: Roster of Tomorrow is:  followed by the roster of yesterday.

gruijter_dev

Well, I'm looking into the roster thing again. I might have to completely rewrite the code for this, because somehow I cannot get it right it seems   

Besides that I do see a flaw in your flow. #flawedflows . The trigger card "roster change" now only supports a change in today's roster. So if tomorrows roster changes, the flow would not be triggered.

[Deleted User]

Agree, if you want me to help / test let me know.

gruijter_dev

@hnijveen I did a rewrite, wrote some special code to test midnight (change of day situations), and wrote some special code to test a change in roster. And as far as I could test with all of this it now seems to work. The proof is in the real pudding now.... If you want to give it a try, it is posted in GitHub

[Deleted User]

Ok, will do: