Skip to content
  • MySensors
  • OpenHardware.io
  • Categories
  • Recent
  • Tags
  • Popular
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo
  1. Home
  2. Hardware
  3. Gateway-less sensors

Gateway-less sensors

Scheduled Pinned Locked Moved Hardware
4 Posts 3 Posters 1.8k Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • T Offline
    T Offline
    tigra
    wrote on last edited by
    #1

    Congrats on a great project here!

    My understanding that nRF24L01 was chosen because of the low cost. Was CC1101 ever considered?
    It's just a dime more but from what I recon it can be configured to run in the native z-wave band of 908.42MHz
    If done this would allow the use of sensors without need for gateway which opens the project to more controllers and apps like SmartThings.
    Assuming that hardware is up to it, the radio chip abstraction layer can be created so the same code can be compiled for one of two methods with just a directive.

    Anyway, it would be interesting to hear the thoughts.

    T 1 Reply Last reply
    0
    • T tigra

      Congrats on a great project here!

      My understanding that nRF24L01 was chosen because of the low cost. Was CC1101 ever considered?
      It's just a dime more but from what I recon it can be configured to run in the native z-wave band of 908.42MHz
      If done this would allow the use of sensors without need for gateway which opens the project to more controllers and apps like SmartThings.
      Assuming that hardware is up to it, the radio chip abstraction layer can be created so the same code can be compiled for one of two methods with just a directive.

      Anyway, it would be interesting to hear the thoughts.

      T Offline
      T Offline
      ToSa
      Code Contributor
      wrote on last edited by
      #2

      Independent from z-wave I like the idea to abstract the RF hardware layer - similar to a device driver that is picked at build time. The interface should be relatively simple (init / send / check if received / receive).

      1 Reply Last reply
      1
      • hekH Online
        hekH Online
        hek
        Admin
        wrote on last edited by
        #3

        z-wave if a closed protocol. We cannot communicate with other z-wave stuff even if we run at the same frequency.
        Also the "z-wave" frequency differs for different regions where 908.42MHz is the US one.

        1 Reply Last reply
        0
        • T Offline
          T Offline
          tigra
          wrote on last edited by
          #4

          @hek: Is it technical "cannot" or legal "cannot"?
          From technical angle it's not walk in the park but it's been done (google z-force and open-zwave).

          1 Reply Last reply
          0
          Reply
          • Reply as topic
          Log in to reply
          • Oldest to Newest
          • Newest to Oldest
          • Most Votes


          13

          Online

          11.7k

          Users

          11.2k

          Topics

          113.0k

          Posts


          Copyright 2019 TBD   |   Forum Guidelines   |   Privacy Policy   |   Terms of Service
          • Login

          • Don't have an account? Register

          • Login or register to search.
          • First post
            Last post
          0
          • MySensors
          • OpenHardware.io
          • Categories
          • Recent
          • Tags
          • Popular