›
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.

Homewizard

135678

Comments

  • jtebbensjtebbens Member
    Which version? And what error message..
  • marcelwolfmarcelwolf Member
    Version 0.0.9
    How can i see what the error is?
  • jtebbensjtebbens Member
    No red icon in the applist or run it as debug mode?
    On the other hand, just wait a little we are reordering the code a bit.
    Wait for a new version when have it ready.
  • marcelwolfmarcelwolf Member
    Yes. Red  icon but  it only says 'app crashed'
  • mbalik79mbalik79 Member
    I have the same problem, this is the error (latest version from git)

  • marcelwolfmarcelwolf Member
    found the error  :)


  • jtebbensjtebbens Member
    @marcelwolf yes we got track of that bug as well. Should be sorted in next release.
  • marcelwolfmarcelwolf Member
    When comes the next release?
  • jtebbensjtebbens Member
    Not sure. There is a total driver reconstruct underway. Instead of retyping all details for heatlink and energylink you can just click on a dropdown menu your homewizard. All seperate modules work but the whole bundle itself has issues. We were planning to release it last week but final testing held us back due those bugs we found. For example heatlink did not change the temperature. So yeah still work in progress but not finished. Hang in there. :) It will come.

  • ultimaultima Member
    HI there,  any chance to read out temperature/humiduty sensors (433/868), rain and wind ?  thx...
  • jeroenbos22jeroenbos22 Member
    edited December 2016
    @ultima We could do that but think its better to sell them and get temp sensors that are compatible with Homey. Love to have the core functionality of HW in the app but personally I think individual device data is something Homey should handle. Otherwise next question will be I want to switch KAKU stuff from my HW using Homey while you should just pair the KAKU to Homey directly. Long story short, not impossible but think its a little bit overdone.
  • jeroenbos22jeroenbos22 Member
    @ultima ;
    You could also use https://github.com/nlrb/com.weather-sensors. That works fine with most temp sensors
  • jtebbensjtebbens Member
    edited December 2016
    Hi everyone.

    We smashed some bugs and got a new version ready for testing (and when ok release it).
    Our own tests went fine but we lack a wattcher device to be sure. Please try for those that have it.

    One downside of this update, you have pair your homewizard again basically due to the code reconstruct and the dropdown selectbox support for heatlink, energylink and wattcher.

    This version will support:

    - Homewizard (scenes, presets)
    - Heatlink (adjusting the temp, use flows to modify)
    - Energylink (reading your energy cons/prod both current and daily, gas meter info as well).
    - Wattcher (information and trigger/flows)

    https://github.com/jeroenbos22/com.homewizard/tree/V0.09

    For those testing and experience issues/errors. Please sent us a PM with the get-status JSON so we can troubleshoot further.

    Thanks and enjoy!



  • mbalik79mbalik79 Member
    @jtebbens  Gonna try! Thanks...
  • marcelwolfmarcelwolf Member
    edited December 2016
    21:58 Problem solved. Deleted v.0.08 and installation wend fine.



    Crashes immediatly after installing.
    stack trace:
    TypeError: Cannot read property 'settings' of undefined
    at Object.module.exports.homewizard.call (/includes/homewizard.js:38:53)
    at getStatus (/drivers/heatlink/driver.js:132:16)
    at Object.module.exports.capabilities.measure_temperature.get (/drivers/heatlink/driver.js:84:7)
    at /homey-app/manager/drivers.js:189:13
    at Object.drivers.(anonymous function).ready (/homey-app/manager/drivers.js:131:9)
    at eventListeners.clientDriverMessage (/homey-app/manager/drivers.js:170:10)
    at /homey-app/manager/drivers.js:26:41
    at Object.Homey.ready (/homey-app/homey.js:1:1008)
    at /homey-app/manager/drivers.js:25:11
    at /homey-app/helpers/client.js:1:1077
    Exit code: 1
    Exit signal: null

  • jtebbensjtebbens Member
    marcelwolf said:
    21:58 Problem solved. Deleted v.0.08 and installation wend fine.



    Crashes immediatly after installing.
    stack trace:
    TypeError: Cannot read property 'settings' of undefined
    at Object.module.exports.homewizard.call (/includes/homewizard.js:38:53)
    at getStatus (/drivers/heatlink/driver.js:132:16)
    at Object.module.exports.capabilities.measure_temperature.get (/drivers/heatlink/driver.js:84:7)
    at /homey-app/manager/drivers.js:189:13
    at Object.drivers.(anonymous function).ready (/homey-app/manager/drivers.js:131:9)
    at eventListeners.clientDriverMessage (/homey-app/manager/drivers.js:170:10)
    at /homey-app/manager/drivers.js:26:41
    at Object.Homey.ready (/homey-app/homey.js:1:1008)
    at /homey-app/manager/drivers.js:25:11
    at /homey-app/helpers/client.js:1:1077
    Exit code: 1
    Exit signal: null

    @marcelwolf ;Yeah this is due to the old homewizard pairing. The new pair holds the settings differently so hence it will complain about it when loading. It should be a one time only due we keep the main settings for homewizard and the modules like energylink and heatlink tap into it.
  • mbalik79mbalik79 Member
    edited December 2016

    @jtebbens ;
    The morning starts with this ...(newest version from github installed)
  • jtebbensjtebbens Member
    Thanks @mbalik79 are you running it as athom project --run or athom project --install ?

  • mbalik79mbalik79 Member
    jtebbens said:
    Thanks @mbalik79 are you running it as athom project --run or athom project --install ?

    project --install

  • marcelwolfmarcelwolf Member
    My app didn't crash, yet :)
    However Wattcher still ain't working right. The dayusage is still empty.
    h

  • HarmStellingaHarmStellinga Member
    I did install it also, and my watermeter shows dagopbrengst 26 KWh
     :) , my watermeter is connected to port 1, its 26 liter.
    But it works fine, ill try to chance the name.
  • jeroenbos22jeroenbos22 Member
    edited December 2016
    Just updated the repo, added a lot of crash-prevention and some bugfixes
  • jtebbensjtebbens Member
    Hey @marcelwolf I took your getstatus sample but we see information in the card.
    Not sure where it goes wrong with Wattcher.


  • mbalik79mbalik79 Member
    Installed newest version from github @jeroenbos22 ;
    Will let you know if there are issues  ;)
  • jtebbensjtebbens Member
    edited December 2016
    Latest version (0.0.9) just have been uploaded to release. After approval it will show in the app store.

  • bockybocky Member
    @jtebbens and @jeroenbos22 Great work guys!
  • jeroenbos22jeroenbos22 Member
    edited December 2016
    Thanx @bocky ;, did u see the nee settingspage btw?
  • mbalik79mbalik79 Member
    Great work guys! Thanks for the good job
  • jtebbensjtebbens Member
    Latest version (0.0.9)  in store now!
  • bockybocky Member
    jeroenbos22 said:
    Thanx @bocky ;, did u see the nee settingspage btw?
    Yep! Very nice!
    Next step would be to reduce the number of API calls and globally do the get_status request en store this somewhere so all the other drivers can reuse the data from that.
Sign In or Register to comment.