This is the forum archive of Homey. For more information about Homey, visit the Official Homey website.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
Comments
https://forum.athom.com/discussion/comment/33333/#Comment_33333
Tried it with a single device ther's no problem. Is this a known bug or am I missing something?
But for my Yamaha receiver and LG tv it does not allow commands.
After a few tries i got an invalid_card error and found this info at the app settings:
Stack trace:
TypeError: Cannot read property 'sortBy' of undefined
at Object.<anonymous> (/app.js:271:57)
at emitTwo (events.js:87:13)
at Object.emit (events.js:172:7)
at /homey-app/manager/flow.js:1:417
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)
at internal/child_process.js:696:12
Exit code: 1
Exit signal: null
Maybe it's better to get an extra card that says "Stop Activity".
That looks like an app or phone problem
I will further investigate it.
When i look ait the app in settings it displays a red triangle and when i hover over it i see a lot of errors.
Is this app not supported anymore or do i something wrong?
What do you mean with 'when i try to add it to a room'?
Her it states, follow the instructions, i waited 10 minutes but nothing happens.
When i press NEXT the popup closes and nothing has been added.
When i look in the settings menu there is a red triangle with the harmony app:
Stack trace:
Error: listen EADDRINUSE :::61991
at Object.exports._errnoException (util.js:907:11)
at exports._exceptionWithHostPort (util.js:930:20)
at Server._listen2 (net.js:1250:14)
at listen (net.js:1286:10)
at Server.listen (net.js:1382:5)
at ResponseCollector.start (/node_modules/harmonyhubjs-discover/lib/responseCollector.js:33:5)
at Explorer.start (/node_modules/harmonyhubjs-discover/lib/explorer.js:75:25)
at startHubDiscovery (/drivers/hub/driver.js:70:18)
at EventEmitter.<anonymous> (/drivers/hub/driver.js:8:9)
at emitTwo (events.js:87:13)
Exit code: 1
Exit signal: null
If so, try rebooting the hub just before you try to connect it to Homey. There is an issue with to much connections to the hub causing the requests to be dropped. If you have other devices connecting to the hub as well you could try to limit this traffic while you connect it to Homey as well.
I've picked up development where I left off, so you can expect an update for the dropped connections issue before the end of the year.
For now I wish you all a merry Xmas!
That is great news, both for you and for us!
Hope to see the Harmony Hub state available as a trigger in flows again. You removed it, as it lagged the system. Works in Domoticz, though.
Thanks for all your effort!
Great to hear you're back!
Hope you can find a solution for the device commands not showing up, really missing that right now
needed to reinstall all devices (kinda obvious) otherwise it wouldn't trigger on app level -> scene changed.
on deletion of my hubs (in the new app) it crashed the app:
But after re-inclusion it worked good on triggers for changing scenes.
After trying to include my second hub (which i had offline at the moment) i got another crash of invalid_driver:
and afterwards keeps crashing the app trying to include the second hub, even after deleting the app, and reinstalling it, as soon as it sees 2 hubs in the network it will crash the app with this error.
will test more tomorrow awesome job until now
TypeError: Cannot read property 'client' of undefined
at Object.module.exports.autocompleteDevice (/drivers/hub/driver.js:232:43)
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:1:417
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