[PUBLISHED] Harmony Hub App (v1.0.4)

Menno

@brinkie   auw crash while trying to add an activity to flow

Stack trace:

TypeError: Cannot read property 'id' of undefined
at Object.module.exports.autocompleteActivity (/drivers/hub/driver.js:206:23)
at Object.<anonymous> (/app.js:28:63)
at emitTwo (events.js:87:13)
at Object.emit (events.js:172:7)
at /homey-app/manager/flow.js:23:37
at /homey-app/helpers/client.js:1:1077
at Array.forEach (native)
at process.<anonymous> (/homey-app/helpers/client.js:1:1046)
at emitTwo (events.js:87:13)
at process.emit (events.js:172:7)

Exit code: 1
Exit signal: null

Menno

Again crach now while sending command 

Stack trace:

TypeError: Cannot read property 'id' of undefined
at Object.module.exports.autocompleteDevice (/drivers/hub/driver.js:243:23)
at Object.<anonymous> (/app.js:34:63)
at emitTwo (events.js:87:13)
at Object.emit (events.js:172:7)
at /homey-app/manager/flow.js:23:37
at /homey-app/helpers/client.js:1:1077
at Array.forEach (native)
at process.<anonymous> (/homey-app/helpers/client.js:1:1046)
at emitTwo (events.js:87:13)
at process.emit (events.js:172:7)

Exit code: 1
Exit signal: null

Fire69

Fire69 said:

@brinkie, you're not alone, it has been running fine here for days also. 

Spoke too soon, it crashed yesterday 

Menno said:

Again crach now while sending command 

Don't mind installing 1.0.1 from git, but this doesn't look very promising

brinkie

Fire69 said:

Fire69 said:

@brinkie, you're not alone, it has been running fine here for days also. 

Spoke too soon, it crashed yesterday 

Menno said:

Again crach now while sending command 

Don't mind installing 1.0.1 from git, but this doesn't look very promising

Wat was the error?
It doesn't look promising yet, but I'll have another look on Wednesday.

Fire69

brinkie said:

Fire69 said:

Fire69 said:

@brinkie, you're not alone, it has been running fine here for days also. 

Spoke too soon, it crashed yesterday 

Menno said:

Again crach now while sending command 

Don't mind installing 1.0.1 from git, but this doesn't look very promising

Wat was the error?
It doesn't look promising yet, but I'll have another look on Wednesday.

I didn't check, it was late and I jist wanted to turn everything off so I restarted the app and everything worked again  

Eternity

I had a lot off crashes, after updating to v1.0.0

Yesterday I got fed up and did the following again:
- Remove hub as device
- uninstall the app
- PTP (this was new!)
- install the app
- add the hub
- repaired my flows

And now it hasn't crashed in 24 hours, so seems to work again :-)


BTW @brinkie
I just discovered that IF now also works!

Bumblez

@Eternity thanks... I'll give that a try one of these days (as soon as I have a bit of time on my hands).

Eternity

@Bumblez
Better to use a different AND card...:

Bumblez

@Eternity sorry, I wasn't referring to that flow... I was referring to the first half of your email, on how to get the app working again  (I tried exactly the same steps, without the PTP, and that didn't solve the problem...).

bvdbos

In general: if one de-installs and re-installs an app, it's always wise to reboot. I noticed all settings were kept if I didn't wait long enough or didn't reboot. PTP is even better, then you're sure the memory is empty...

Panda

@brinkie For me the app runs fine, one app crash occured, this was because I changed from wall outlet.

If you could find a way to catch the unhandled connection error's by retrying to connect to the hub for a few tries all will be fine I guess

brinkie

Panda said:

@brinkie For me the app runs fine, one app crash occured, this was because I changed from wall outlet.

If you could find a way to catch the unhandled connection error's by retrying to connect to the hub for a few tries all will be fine I guess

I have! The code is currently testable on GitHub. I'd love to get your feedback.

Menno

@brinkie did a new try from GITHUB with ptp still same problem the error that I get is:



After that the app crashes

What I wonder the people who says that it is working did they use the APP store or GITHUB (version 1.0.0 or 1.0.1)
If there is something to test let me know!

Error:

Stack trace:

TypeError: Cannot read property 'id' of undefined
at Object.module.exports.autocompleteActivity (/drivers/hub/driver.js:206:23)
at Object.<anonymous> (/app.js:28:63)
at emitTwo (events.js:87:13)
at Object.emit (events.js:172:7)
at /homey-app/manager/flow.js:23:37
at /homey-app/helpers/client.js:1:1077
at Array.forEach (native)
at process.<anonymous> (/homey-app/helpers/client.js:1:1046)
at emitTwo (events.js:87:13)
at process.emit (events.js:172:7)

Exit code: 1
Exit signal: null

aelsenaar

Menno said:

@brinkie did a new try from GITHUB with ptp still same problem the error that I get is:



After that the app crashes

What I wonder the people who says that it is working did they use the APP store or GITHUB (version 1.0.0 or 1.0.1)
If there is something to test let me know!

Error:

Stack trace:

TypeError: Cannot read property 'id' of undefined
at Object.module.exports.autocompleteActivity (/drivers/hub/driver.js:206:23)
at Object.<anonymous> (/app.js:28:63)
at emitTwo (events.js:87:13)
at Object.emit (events.js:172:7)
at /homey-app/manager/flow.js:23:37
at /homey-app/helpers/client.js:1:1077
at Array.forEach (native)
at process.<anonymous> (/homey-app/helpers/client.js:1:1046)
at emitTwo (events.js:87:13)
at process.emit (events.js:172:7)

Exit code: 1
Exit signal: null

Just tested the github 1.0.1 version with the same result.

Fire69

Yep, same here

MrDutchfighter

Error on my 1.0.0 version, maybe helps in finding the root cause, maybe you already solved this one with 1.0.1

Stack trace:
No stack trace available

Exit code: null
Exit signal: SIGABRT

brinkie

Sorry @Menno, @aelsenaar and @Fire69 on the autocomplete error. That was my error. I just updated the code on GitHub. Would you mind pulling the code and do some more testing?

Fire69

Autocomplete is working again

brinkie

Fire69 said:

Autocomplete is working again

Ok, now we need to find out if this version is more stable (connection wise) than the one currently in the app store.

brinkie

Phuturist said:

Could it be that the issue where the app crashes is caused by the app not being able to reach the hub? I power down all my AV equipment over night, so the Hub is not online. This morning the app had crashed again with the following stacktrace.

Error: read ECONNRESET
at exports._errnoException (util.js:907:11)
at TCP.onread (net.js:557:26)

Exit code: 1
Exit signal: null

@Phuturist Would you mind installing the current GitHub code and do some testing? For me the app can now recover from a PTP of the hub (and put it back in ofcouse ).

spoelly

@brinkie installed the github version working fine over here!

Phuturist

brinkie said:

Phuturist said:

Could it be that the issue where the app crashes is caused by the app not being able to reach the hub? I power down all my AV equipment over night, so the Hub is not online. This morning the app had crashed again with the following stacktrace.

Error: read ECONNRESET
at exports._errnoException (util.js:907:11)
at TCP.onread (net.js:557:26)

Exit code: 1
Exit signal: null

@Phuturist Would you mind installing the current GitHub code and do some testing? For me the app can now recover from a PTP of the hub (and put it back in ofcouse ).

Roger that, will do so straight away and let you know.

brinkie

Phuturist said:

brinkie said:

Phuturist said:

Could it be that the issue where the app crashes is caused by the app not being able to reach the hub? I power down all my AV equipment over night, so the Hub is not online. This morning the app had crashed again with the following stacktrace.

Error: read ECONNRESET
at exports._errnoException (util.js:907:11)
at TCP.onread (net.js:557:26)

Exit code: 1
Exit signal: null

@Phuturist Would you mind installing the current GitHub code and do some testing? For me the app can now recover from a PTP of the hub (and put it back in ofcouse ).

Roger that, will do so straight away and let you know.

Great!

Menno

@brinkie just did uninstall + unplug +install (github) and now I see my activities again and can add them to my flows.
So for now it looks good! I will do some more testing tomorrow

Menno

Hmmm received an error working with bitflips:

Stack trace:

ReferenceError: device_data_id is not defined
at Object.module.exports.sendCommandToDevice (/drivers/hub/driver.js:332:15)
at Object.<anonymous> (/app.js:74:63)
at emitThree (events.js:97:13)
at Object.emit (events.js:175:7)
at /homey-app/manager/flow.js:12:37
at /homey-app/helpers/client.js:1:1077
at Array.forEach (native)
at process.<anonymous> (/homey-app/helpers/client.js:1:1046)
at emitTwo (events.js:87:13)
at process.emit (events.js:172:7)

Exit code: 1
Exit signal: null

When I use normal flows the app doesn't crash so not sure that this is a real harmony problem but the app is crashing

Phuturist

Menno said:

Hmmm received an error working with bitflips:

Stack trace:

ReferenceError: device_data_id is not defined
at Object.module.exports.sendCommandToDevice (/drivers/hub/driver.js:332:15)
at Object.<anonymous> (/app.js:74:63)
at emitThree (events.js:97:13)
at Object.emit (events.js:175:7)
at /homey-app/manager/flow.js:12:37
at /homey-app/helpers/client.js:1:1077
at Array.forEach (native)
at process.<anonymous> (/homey-app/helpers/client.js:1:1046)
at emitTwo (events.js:87:13)
at process.emit (events.js:172:7)

Exit code: 1
Exit signal: null

When I use normal flows the app doesn't crash so not sure that this is a real harmony problem but the app is crashing

I got the same error sometime during the night (no activitity and Harmony Hub was not powered on). I did not re-add the Hub after installing v1.0.1 from GitHub. Is it needed to re-add the Hub again?

brinkie

Menno said:

Hmmm received an error working with bitflips:

Stack trace:

ReferenceError: device_data_id is not defined
at Object.module.exports.sendCommandToDevice (/drivers/hub/driver.js:332:15)
at Object.<anonymous> (/app.js:74:63)
at emitThree (events.js:97:13)
at Object.emit (events.js:175:7)
at /homey-app/manager/flow.js:12:37
at /homey-app/helpers/client.js:1:1077
at Array.forEach (native)
at process.<anonymous> (/homey-app/helpers/client.js:1:1046)
at emitTwo (events.js:87:13)
at process.emit (events.js:172:7)

Exit code: 1
Exit signal: null

When I use normal flows the app doesn't crash so not sure that this is a real harmony problem but the app is crashing

Was the hub online when is error occurred?

brinkie

Phuturist said:

Menno said:

Hmmm received an error working with bitflips:

Stack trace:

ReferenceError: device_data_id is not defined
at Object.module.exports.sendCommandToDevice (/drivers/hub/driver.js:332:15)
at Object.<anonymous> (/app.js:74:63)
at emitThree (events.js:97:13)
at Object.emit (events.js:175:7)
at /homey-app/manager/flow.js:12:37
at /homey-app/helpers/client.js:1:1077
at Array.forEach (native)
at process.<anonymous> (/homey-app/helpers/client.js:1:1046)
at emitTwo (events.js:87:13)
at process.emit (events.js:172:7)

Exit code: 1
Exit signal: null

When I use normal flows the app doesn't crash so not sure that this is a real harmony problem but the app is crashing

I got the same error sometime during the night (no activitity and Harmony Hub was not powered on). I did not re-add the Hub after installing v1.0.1 from GitHub. Is it needed to re-add the Hub again?

So your hub was turned off?

Phuturist

brinkie said:

Phuturist said:

Menno said:

Hmmm received an error working with bitflips:

Stack trace:

ReferenceError: device_data_id is not defined
at Object.module.exports.sendCommandToDevice (/drivers/hub/driver.js:332:15)
at Object.<anonymous> (/app.js:74:63)
at emitThree (events.js:97:13)
at Object.emit (events.js:175:7)
at /homey-app/manager/flow.js:12:37
at /homey-app/helpers/client.js:1:1077
at Array.forEach (native)
at process.<anonymous> (/homey-app/helpers/client.js:1:1046)
at emitTwo (events.js:87:13)
at process.emit (events.js:172:7)

Exit code: 1
Exit signal: null

When I use normal flows the app doesn't crash so not sure that this is a real harmony problem but the app is crashing

I got the same error sometime during the night (no activitity and Harmony Hub was not powered on). I did not re-add the Hub after installing v1.0.1 from GitHub. Is it needed to re-add the Hub again?

So your hub was turned off?

Can tell for sure, if you recieved a crash report between 0:00 and 07:00 it was off, otherwise it might have been on.

brinkie

Phuturist said:

brinkie said:

Phuturist said:

Menno said:

Hmmm received an error working with bitflips:

Stack trace:

ReferenceError: device_data_id is not defined
at Object.module.exports.sendCommandToDevice (/drivers/hub/driver.js:332:15)
at Object.<anonymous> (/app.js:74:63)
at emitThree (events.js:97:13)
at Object.emit (events.js:175:7)
at /homey-app/manager/flow.js:12:37
at /homey-app/helpers/client.js:1:1077
at Array.forEach (native)
at process.<anonymous> (/homey-app/helpers/client.js:1:1046)
at emitTwo (events.js:87:13)
at process.emit (events.js:172:7)

Exit code: 1
Exit signal: null

When I use normal flows the app doesn't crash so not sure that this is a real harmony problem but the app is crashing

I got the same error sometime during the night (no activitity and Harmony Hub was not powered on). I did not re-add the Hub after installing v1.0.1 from GitHub. Is it needed to re-add the Hub again?

So your hub was turned off?

Can tell for sure, if you recieved a crash report between 0:00 and 07:00 it was off, otherwise it might have been on.

I haven't actually. This is an interesting case though. I have read somewhere Hub's ID can change over power cycles, which could mean the app might be able to find the hub after it has been powered off. I have tried to test this, but a quick PTP and replug didn't result in a different Hub ID. I'd be interested to here some more test results from people actually unplugging their hub on a daily basis.

I'm going to do some more testing with this use case myself as well.