Zach Underwood

After a trip to Ikea they had simple voting system near the exits of the store. That got us to think so we made a box that we would place at the exit of session to allow guests to rate the session. We simply ask if the user “loved it” , “was neutral about it” or “hated it”

For the hardware we use esp8266 nodemcu running esphome much like the speaker lights. The vote boxes connects to the staff wifi and will report the votes using mqtt to node red. We count a love it as +1, neutral as 0 and hated as -1 to give us a final vote.

esphome:
  name: ballroomavote
  platform: ESP8266
  board: nodemcuv2

wifi:
  ssid: 'x'
  password: 'x'
  manual_ip:
   static_ip: x.x.x.x
   gateway: x.x.x.x
   subnet: 255.255.255.0
# Enable logging
logger:
ota:
  password: 'x'
sensor:
  - platform: wifi_signal
    name: "balllroomAvote WiFi Signal Sensor"
    update_interval: 60s
switch:
  - platform: gpio
    pin: D2
    name: "vote LED"
    id: voteled

binary_sensor:
  - platform: gpio
    pin:
      number: D3
      mode: INPUT_PULLUP
    name: "pos  Button"
    filters:
      - delayed_on: 10ms
    on_press:
      then:
        - switch.toggle: voteled
        - delay: 2ms
        - switch.toggle: voteled
        - mqtt.publish:
             topic: vote/A
             payload: "pos"


  - platform: gpio
    pin:
      number: D6
      mode: INPUT_PULLUP
    name: "natural  Button"
    filters:
      - delayed_on: 10ms
    on_press:
      then:
        - switch.toggle: voteled
        - delay: 2ms
        - switch.toggle: voteled
        - mqtt.publish:
             topic: vote/A
             payload: "natural"


  - platform: gpio
    pin:
      number: D5
      mode: INPUT_PULLUP
    name: "neg  Button"
    filters:
      - delayed_on: 10ms
    on_press:
      then:
        - switch.toggle: voteled
        - delay: 2ms
        - switch.toggle: voteled
        - mqtt.publish:
             topic: vote/A
             payload: "neg"

mqtt:
  broker: x.x.x.x
  keepalive: 15s
  username: x.x.x.x
  password: x.x.x.x

We use the speaker lights to give speaker a heads up about what the automation is doing with the recording.

For the hardware we used an esp8266 nodemcu board connected to the LED traffic light style board. Here is an example of the type of LED board that we used:
https://www.amazon.com/Oak-Pine-Traffic-Display-Creative-Arduino/dp/B07R4YR2QJ

For the software we are using ESPhome and speaker lights assembly connect to the staff wifi. Over the wifi they will connect to the MQTT server to listen for commands. We powered the speaker light using USB.

Below is what it looks like before it was placed into a case.

Here is the esphome config file that we use.

esphome:
  name: ballrooma_speaker_light
  platform: ESP8266
  board: nodemcuv2

wifi:
  ssid: 'xxx'
  password: 'x'
  manual_ip:
   static_ip: x.x.x.x
   gateway: x.x.x.x
   subnet: 255.255.255.0
# Enable logging
logger:
ota:
  password: 'x'
switch:
  - platform: gpio
    pin: D2
    name: "Red LED"
    state_topic: light/a/
    command_topic: light/a/red
  - platform: gpio
    pin: D2
    name: "Red Flash LED"

    id: Red_pin
  - platform: template
    name: "Red Flash LED"
    optimistic: yes
    id: redtemp
    state_topic: light/a/
    command_topic: light/a/redflash
    turn_on_action:
    - while:
       condition:
        lambda: 'return true;'
       then:
       - switch.turn_on: Red_pin
       - delay: 500ms 
       - switch.turn_off: Red_pin
       - delay: 500ms
    turn_off_action:
    - switch.turn_off: Red_pin



  - platform: gpio
    pin: D1
    name: "Yellow LED"

    id: yellow_pin
  - platform: template
    name: "Yellow LED"
    optimistic: yes
    id: yellowtemp
    state_topic: light/a/
    command_topic: light/a/yellow
    turn_on_action:
    - while:
       condition:
        lambda: 'return true;'
       then:
       - switch.turn_on: yellow_pin
       - delay: 500ms 
       - switch.turn_off: yellow_pin
       - delay: 500ms
    turn_off_action:
    - switch.turn_off: yellow_pin


  - platform: gpio
    pin: D3
    name: "Green LED"
    state_topic: light/a/
    command_topic: light/a/green
    
mqtt:
  broker: x.x.x.x
  keepalive: 15s
  username: x
  password: x

In case you missed it, I have done an overview of everything we do for SELF here

For the SouthEast Linux Fest we take over the event space of the Sheraton Charlotte Airport Hotel to host our 3 day event. I have been helping with SELF for the past 5-6 years and in those years we would get to the hotel on the Thursday morning before the event and have all day to setup the network. We go live with the network Friday 8 am as that is the start of the event. With the permission of the hotel staff we turn off and power down the hotel’s wifi system in the event spaces were we will be setting up our own wifi. Doing this helps with reducing RF interference.

The logistics of getting there.

I live about a hour away from the hotel that we host SELF at as a result I really do not want to make two trips each way. I am fortunate to have a Yukon and large trailer so I am able to load everything in one trip. I have found those large Husky tool chests very nice. This was gearing up to SELF 2019.

Internet connection

Over the years we had a few different forms of internet connection all around a coax connection from the local cable company. When I first started to help we started with 100×5 internet connection. Next we did 3 bonded 100×5 connections to gain more upload speed for videos. We progressed to what we currently use, a 940×35 coax connection. I wish we could have fiber but can’t afford it. We are trying to get a local Wireless ISP to get us a connection. If that happens then we should be able to get a 500×500 connection. We also run a full dual stack ipv4/ipv6 network.

Layer 1 the cabling

Over the years we run own network cabling both cat6 and fiber. We are able to leave the cabling in the ceiling year to year allowing to reuse and built up over time the cabling that we have in place. In 2019 we expand into a new part of the hotel so we needed to extend the network to new wing. This wing was connected to the our current wing with a 5 foot in diameter underground pipe that carried services between the two different parts of the hotel. In this tunnel we were able to run a 800 feet of fiber which allowed us to use 10gbit networking between our switches.

We deploy temporary cabling to run between the end devices and the switches. Those temporary cable runs are mostly made of cable trunks where we will group 2-8 ethernet cables together as a single run. We did this because we found that we were running multiple cables to the same location. Right now we have 67 cable runs which total over 7,000 feet of ethernet. Below you can see how we labeled each trunk cable. The 24 the cable ID and the 64ft is how long it is. All of the cable’s info is saved in a spreadsheet with the ID number as the reference point. Each port is then labeled started with A. So you get something like port 24A. Both ends of the cables are labeled like this.

Switching

Right now we use 5 Dell Powerconnect 5524 POE switches that we got from ebay for between $100-150 each. We use the 10gbit ports as trunk ports between switches. Currently the switches are setup by hand using the built in GUI and CLI, we are hopping to change that soon. Also in the future we are looking at some Brocade switch to get more 10gbit ports and some 40gbit ports.

Routing

At this time we only do inner-vlan routing on our PFsense firewall. The PFsense box has 4x 1gbit interfaces that get lagged together and linked to the switches. When we get more 10gbit ports we will be moving to 10gbit LAN link. The PFsense also has another 1gbit interface that we use as our uplink to the coax modem.

WIFI

Right now we use 20 Unifi APs bulk of them the AC-pro model but we also use nano-HD, AC-HD, AC-lite, AC mesh. All APs are powered from the POE switches and backhauled using ethernet. We host the Unifi controller onsite. We run 3 SSID at SELF, staff, public fast(5ghz only) and public slow(2.4ghz only). We use social engineering with the names, to encourage users to connect to the 5ghz only network.

Servers

We run all services that are needed for the event onsite.

Lan party area

We host a lan party area at the Linux fest. In this area we offer tables with power and wired network drops. We host a few game servers onsite for games that support Linux well. Since the guest wireless and wired lan party network are open guests are allowed to run there own game servers if they wish. We built a power monitoring rig to allow us to track power usage to make sure that we are not about trip a breaker. From the hotel’s connection we get 2x 20amp breakers, we take one lead to each breaker. Inside of the gray box we have Shelly EM and two CT clamp. The CT clamp will give us, in real time, the number of amps running to each breaker. Each breaker will connect to one of the quad set of outlets.

Note that we did put outlet covers on after this picture was taken

NOC setup

For our NOC setup we have a shared space in the admin/command room. This is where we place the server and have all of the cables run back to. In the picture you can see the cabling coming down from the ceiling. For SELF 2021 we will be moving the server into a closet to reduce the noise and heat of the NOC area.

This is to serve as introduction to the network and automation of the SouthEast Linux Fest and documentation of said setup. This will link to more details posts of each component. This is written as of October 2020 and will be updated over time.

The SouthEast Linux Fest (SELF) is an 3 day event that is held in Charlotte, NC each summer and pull together around 800 attendees and speakers. We have over 70 sessions in 5 tracks talking all about Linux and open source. SELF started in 2009 and held in person each year with the exception of 2020 due to Covid-19. We are hopping that we can back in person for Summer 2021. My role with SELF is to lead the team that handles all onsite tech needs around the network, servers, wifi, and video recording.

Here is a list and overview of the services that we offer for the event

Recording the talks
We record the speaking session will try to have the sessions uploaded to Youtube with in one hour of the end of the session.
Here is example video from a session that I gave in 2019  https://youtu.be/eFNsEpwpRek 

For SELF 2021 we will be uploading not only to Youtube but to the Internet Archive and Peertube as well.

OBS setup
Being an Linux/open source event we try to use open source where ever we can. We use Open Broadcast Studio for all of the video recording. For SELF 2021 we will partnering with the folks at http://www.asknoahshow.com/ live stream each sessions allow with uploading the video post session. 

Speaker Lights
Since the recording of sessions is all automatic we needed a way to let the speaker know about the timing info. We built 3 led stop light style indictors that give the speaker a heads up.

More details about it here

People counting
We placed a camera over each doorway leading to a session room, this camera would be pointing straight down as people walked into each room. We connect the cameras to some software that count the people entering the session.

Vote boxes
We placed a box at the exit of each session room with 3 buttons: loved the talk, neutral or hated the talk.

More details about it here

Displays
At the hotel were we are hosted, they have built in TV displays outside of each room that are used for digital signage. SELF 2021 we will be repurposing the displays for our use.

 
Network
We bring in our own internet connection to the hotel and use none of the hotel’s house wiring. We roll out 2k feet of fiber and 7k feet of copper to support the network. We install 8 servers and 20 APs to give wifi services to our lan party area, staff, vendors and all guests. 

More details about the networking here

Monitoring

We monitor all facets of the network, wifi, and automation. We also have a public display where we will show some of the stats, such as how many wifi users, the total number of votes logged for the presentations, how many attendees have entered presentations, etc.

Automation
The heart of our automation system is Node-Red, we use it to automate all of the above with the exception of the network. I hope to change that one day.