1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

AtmoOrb Device

Introduction

AtmoOrb is a Philipe Hue like device which you can send color information over WiFi, it uses a simple network protocol and transmits it data over UDP multicast.

It offers much better performance over Hue with on average 1ms color changes depending on WiFi quality and can be controlled without the need of a bridge or additional IP configuration / pairing.

More information on how to build the AtmoOrb device can be found in the Hardware chapter.

Setup

The settings options in your Hyperion configuration file are as follows:

Code:
....
"output"  : "239.15.18.2",  <-- Your Orb multicast group IP address, should match that of your Orb
"transitiontime"  : 0,      <-- not used / required but may allow for future delay configuration
"useOrbSmoothing"  : true,  <-- use Orbs own (external) smoothing algorithm when true
"skipSmoothingDiff"  : 0,   <-- minimal color (0-255) difference to override smoothing so that if current and previously received colors are higher than set dif we override smoothing (only used when useOrbSmoothing = true)
"port"  : 49692,           <-- Default multicast port, should match that of your Orb
"numLeds"  : 24,           <-- Number of leds per Orb, should match that of your Orb
"orbIds"  : "1",           <-- Comma separated list of all your Orbs, in example we only use a single id (1)
....
Generally you would only need to change the OrbIds and keep the rest default, here's a sample configuration using a Orb with ID 1:



The skipSmoothingDiff setting allows for faster transitions when the minimal color difference is defined (0-255), for instance if you go from full white to black it can clear smoothing right away for instant color change however this is only used when external Orbs smoothing is enabled (useOrbSmoothing = true).

It's recommended to set useOrbSmoothing to true in Hyperion 1.02 or higher, the amount of smoothing can be set in your Orb sketch at Particle build (see hardware chapter with link to guide).

Graphical configuration is possible with HyperCon.

Multi zone configuration

In the LEDs area of your Hyperion configuration file the index is used as follows:

Code:
Index 0 = Orb ID 1
Index 1 = Orb ID 2
..and so forth
So you can define several Orb IDs in the orbIds setting from earlier and in the LEDs area you can define which scan area it utilizes, here's an example of 2 Orbs (ID 1 and 2) with different scan areas:

Code:
.....
"output"  : "239.15.18.2",  <-- Your Orb multicast group IP address, should match that of your Orb
"transitiontime"  : 0,      <-- not used / required but may allow for future delay configuration
"useOrbSmoothing"  : true,  <-- use Orbs own (external) smoothing algorithm when true
"skipSmoothingDiff"  : 0,   <-- minimal color (0-255) difference to override smoothing so that if current and previously received colors are higher than set dif we override smoothing (only used when useOrbSmoothing = true)
"port"  : 49692,           <-- Default multicast port, should match that of your Orb
"numLeds"  : 24,           <-- Number of leds per Orb, should match that of your Orb
"orbIds"  : "1,2",           <-- Comma separated list of all your Orbs, in example we only use a single id (1)
.....
   "leds" :
   [
    {
  "index" : 0,
  "hscan" : { "minimum" : 0.0000, "maximum" : 0.5000 },
  "vscan" : { "minimum" : 0.0000, "maximum" : 0.5000 }
  },
     {
  "index" : 1,
  "hscan" : { "minimum" : 0.5000, "maximum" : 1.0000 },
  "vscan" : { "minimum" : 0.5000, "maximum" : 1.0000 }
  }
   ],
You can have Orbs with the same ID so this only required for multiple Orb setups where you need different scan areas.

Hardware

It consists of a Particle Photon (Arduino-ish with WiFi) and Neopixel led ring which you can optionally extend with additional WS2812 LEDs using its data out, for complete build instructions you can check out this tutorial:

http://forum.team-mediaportal.com/t...e-photon-with-neopixel-tutorial-added.131901/

You can skip the AtmoLight setup part there as Hyperion will be controlling it in this case

This page has been seen 2,682 times.