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

When Athom/Homey will make avaiable the source code to manage 433 frequency devices ???

JorgeCastroJorgeCastro Member
in Archive
Hello
Before: When I suscribed to Homey's campaign I was under the belief that the company suscribed a sharing/collaborative approach of the information so supporters were able to develop new apps and take advanage of Homey's capabilities and manage all possible devices..and this was a very appealing approach and concept

Now: It has been a while since Homey was launched and I still have no information from Athom that will allow me to develop an App to control most of my radio frecuency devices. Specifically I have been asking for info to calibrate Homey radio frequency signal to 433.42 MHz which is the ones my devices use. Homey aready do it with Somfy devices that operate with that frequency, so the question is why that code is not made available to the developers so they can incorporate it to their Apps and therefore make a better product for all customers. Without being able to adjust the frequency the range of the signal is so poor that is worthless

Future: Can please someone at Athom let me know if this information is planned to be released anytime in the near future?. Has the company policy changed and now this code is not shared?..Will it cost money now?? can the company provide an alternative solution to build my app for these devices or control them through Homey or should I unplugged Homey and forget?

I hope this reaches someone at Athom that can provide me an answer. Keeping in mind that without the support of the company todevelopers to build functionality for devices, this product is no different from other solutions in the market

Thanks in advance

Comments

  • jjtbsomhorstjjtbsomhorst Member
    have you seen https://developers.athom.com/ ? As you can see 433 and the other things are not specified yet but the NFC tag can be reacted on. Next to that you can already create applications using the platform (which is just nodejs ). So you statement 'supporters were able to develop new apps and take advantage of..' is partially already reality. 

    I don't think that the 433 and other mhz devices will become opensource but that Athom will add hooks on which we can react using the various managers.
  • JorgeCastroJorgeCastro Member
    Thanks for your reply, but specifically around 433 there is nothing available on the site or time line for it...not code, no hooks..nothing.
    I was searching for a clear position on this from someone at Athom so I know if I will ever be able to use my RF devices with Homey or need to search for alternative solutions
  • jjtbsomhorstjjtbsomhorst Member
    JorgeCastro said:
    Thanks for your reply, but specifically around 433 there is nothing available on the site or time line for it...not code, no hooks..nothing.
    I was searching for a clear position on this from someone at Athom so I know if I will ever be able to use my RF devices with Homey or need to search for alternative solutions
    What do you mean by "use my rf devices with homey". Are you talking about custom devices or just things like Klik aan klik uit or something else. Because lots of devices already are supported ( see apps.athom.com)
  • JorgeCastroJorgeCastro Member
    I am not talking about custom devices but established commercial brands (i.e: Jung) that operate under 433.42 MHz radio frequency signal 

    And nothing eiher in the App store...or I would no tbe putting this post

    Regards
  • casedacaseda Member
    edited June 2016
    On github there is already a mockup of a 433 MHz app creater (made by athom), it is still in development, but it's gotten pretty far. 
    Which should make the apps for like Jung almost automatic. 
    Just some patience  <3
  • jjtbsomhorstjjtbsomhorst Member
    my guess is that indeed we have to wait until the 'generator' app will be ready. If that is done they should be able to make 433 mhz apps very fast since the basics, I think, is all the same only the protocols differ sometimes. 
  • JorgeCastroJorgeCastro Member
    Thanks Caseda..I will check that mockup on github and if it does what you say it would be a real good step

  • AndyWildeAndyWilde Member
    I have an app for lightwaveRF that is using 433,  the git for this is also posted,  The most difficult part is the protocol.

    It certainly is possible to do this with the current released code thats avaliable
  • NattelipNattelip Member
    edited June 2016
    caseda said:
    On github there is already a mockup of a 433 MHz app creater (made by athom), it is still in development, but it's gotten pretty far. 
    Which should make the apps for like Jung almost automatic. 
    Just some patience  3
    what a nonsense : if you dont know to what specifications you have to translate the jung signal specifications to homey understandble variables you have no use of the app creator : garbage in garbage out, you have to feed the app generator jung signal variables and that is not possible because the code all the jeelab transmitters on raspberry and arduino
    is other specified as homey signal variables. And knw where is speciafied how to interptret the Signal('''433"), no where is a code found how to chnage normal 433 frequnexy to somfy frequency.

    I dont understand the appgerator, an app is easily made , ther are a lot of third party apps already but not in the 433 or 868 section because it isnt specified. yes there are examples on github but that are the easy ones.

  • JorgeCastroJorgeCastro Member
    Andy/Caseda
    I have checked the mock up and the  lightwaveRF and if I am not mistaken they both lack the main functionality needed to create an app for many devices, which is to set the Homey RF frequency signal to 433.42 MHz which is the one the devices use (without being able to set the frequency to this specific signal the oerational range is nothing)
    Please correct me if wrong
  • NattelipNattelip Member
    edited June 2016
    indeed the normal frequency of 433 is 433,92 , somfy als uses 433.42 or something but not 433.92, so the interface now for 433 is very simple and cant do what the somfy app can so the signal variables are not completely known yet by 3th party app builders. I found the x10 tranlation with the help of @AndyWilde if he hadnt give me some essential info to know i still would be wondering what the Homey 433 signal was about. But i have now spend a few weekends searching for the right translation for oregon en visonic sensors but no succes yet.

  • casedacaseda Member
    edited June 2016
    What a hammering...
    Like i said.. It is still in development.!
    And the "difficulty" of 433 is the main reason why there is no specification (yet) by the athom people and are they building an APP creator.
    The BIG positive about doing it this way:
    It can read raw 433 MHZ signals, this should include all sub ranges...
    And all the apps created, will work all the same, big plus when working with flows.!

    There are about 35! different 433MHz brands around, if you want to add them all, man what a work if it can be done with just a few clicks when the APP creator is done.
    Especially because they would be pretty much all the same..

    Is it that hard to believe a little bit more in the athom people?
    First the z-wave way they are doing was crap (but is going to be the most future proof and stable way of handeling Z-Wave ever)
    and now with the 433 MHz...
  • JorgeCastroJorgeCastro Member
    Caseda
    I want to have faith..but it is taking a little bit longer than expected to get Homey useful with my devices
    Anyway, I am going to follow your advice and follow closely the App creator to see if it finally (and in the short term) incorporates the functionality we need

    Thanks!!
  • jordenjorden Member
    Developer documentation for 433 & 868 within a few weeks, said by Emile yesterday on the developer slack channel.
This discussion has been closed.