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
I am in the process of rewriting some parts to solve the pairing issues.
So in the mean time, please do continue this builds, @aloft! As we have seen with other parties and devices, real official access might be long off, even though talks are progressing, so this development is great - especially since the official way can still take quite some time before yielding any results.
♥
Maybe do this:
delete the device
restart the app
pair the device
restart the app
Did a hard reset again and still same error when opening a zone.
I am slowly approaching 'ready for app store' state.
Bugs solved:
- Pairing without setting would crash the app ; now it gives an error and aborts the process
- Pairing all devices at once would freeze the app; solved
- After pairing, restart of the app was needed to get update; solved
Bugs found:
- After pairing, you will still need to stop/restart the app, to get updates on the added devices over time. It won't crash, but it won't just update.
- After deleting a device, it will continue to be queried
- After initital pairing; insights won't log a temperature, first logging is when a temperature changes
Added:
- Action cards for setting individual thermostats
- Trigger card for temperature changes on thermostats
To do:
- Action for reset temperature for individual thermostat
Pending test verification:
- What happens if you change you Evohome password; will the app error correctly, or crash?
I've just release 0.3.6 which has a major rewrite of the pairing part, that -hopefully- solves your issues ( probably with a complete removal of the app ).
Please first remove the app within Homey, then install the new version.
Thanks for all your testing, it really helps! And it keeps me even more motivated to get this show on the road.
Win! i can open the zones at this moment.. Will do some more testing tommorow..
Many thanks!
error: target_temperature:invalid_type
Edit: Looks like that the Homey reboots after the error. After the reboot the Evohome App is gone.
This invalid_type error seems like a different error than the update error. I'll look into it. When you set the temperature via an action card, the device card can be clicked after the execution of the action card.
zones are opening and displaying temp
going to test set function
Features added:
- Cancel temperature via action card ; when a individual temperature is set, use cancel temperature to cancel and go back to the schedule (or quick action that is programmed)
Bugs solved:
- Major: Adding and deleting devices will not require restart of app to get into the flow
- Minor: Setting temperature via device card will not get 'invalid_type'
ToDo:
- Add status QuickAction as condition and trigger card
- Clean-up code; delete unused test-code, etc.
- Add speech support
Running Homey software version 0.8.36
Hopefully they will give the approval soon. Maybe @Stefan can assist, the number of installed Evohome apps might convince Honeywell to open the official API ;-)
just updated and app is still there
I am now working on triggers based on changing of the 'QuickAction' status; this will trigger (with a max 5 minutes delay, as we cannot query the Evohome server too much) when the status changes from outside Homey, e.g. via the Evohome app or via the Evohome console.
My assumption is that you don't want it triggered when the QuickAction is set from within Homey. But let me know your thoughts.
I hope to finalise the quickaction triggers in the next days, then i'll push a new version to the app store.
That is, for your official release from the app store.
It is now running as a test with actual temperature changes. So let's hope for dynamic weather the next hours.
I've also completed the quickaction triggers. I've also added some extra logging in the 'settings/logging' page, so that might help pinpointing if you see an issue.
If the logging works, I'll submit the new version to GitHub and the app store for approval.
One way or the other, the second update of a device will not trigger the insights logging (or even the 'measure temperature changed' part. Only the first change during a the application runtime will be noted, and logged.
I think I 'miswrite' some variables at the first update, making the trigger ineffective, but I need to figure out where. That might take some time.
Sorry for the delay! I hope the app is still useful in its current state. It will only get better ;-)