The Ortur laser is completely open air, providing no assistance or infrastructure to vent the fumes away. I decided to work on a vacuum table for the laser as the second component to fume management alongside the enclosure. The vacuum table also has some other added benefits when working with thinner materials like paper that may warp up while being cut.
Hold pieces down and prevent them from moving under the pressure of the air assist
Pull away smoke and soot from the machine and exhaust it elsewhere
I was updating my boxes as usual when I encountered an error when trying to run updates on my unifi controller. This lives on a slightly older box (I tried upgrading it at one point and not all the dependencies were supported yet on the newer version), and I ran into an error when running the apt commands. One of the keys was expired for a component needed by the controller. So lets figure out how to update that key so we can update the box once more.
While working on making my macro pad trigger Home Assistant automations, I found the API would be the easiest way to integrate the systems. Here’s some of my experimenting with the API and how to call it from Linux curl and PowerShell Invoke-WebRequest
Using the Linux curl command is pretty straight forward.
Apparently windows has a build of the official Unix curl and tar commands, but my PowerShell prompts all had curl as an alias to Invoke-WebRequest. I did find that if i call curl.exe, it would run the official curl command.
Do be careful when copying and pasting between shells, I found that copying out of the PowerShell prompt and back in would yield an invalid token. This was also encountered in the WSL terminal as well.
The API is pretty straight forward after a little bit of trying things out. The documentation covers the capability but doesn’t have as many examples as I would have liked otherwise.
I was able to get WLED going on a light strip but I do have a lack of ideas on how to make use of it. I finally decided to go with the tried and true movie lighting. So my goal is to setup automations so that when my Roku begins playing something, the WLED strip dims and sets to a specific color (we’ll go with red), and when I pause or stop playing, it will turn to max brightness white light. This will give lower lighting while watching and brighter lights if something is paused (and I have to go get something). I’m still not entirely sure if I will end up making use of this in the end, but it will give me some ideas on what I can do and how to do it.
Adjust lighting when Roku plays some media
If light is on, dim when playing
If light is on, brighten and go to white when paused or stopped
Change to solid colors and a specific color
When the Roku goes to Idle, turn the light strip off
The Roku integration has a number of different statuses, however we’ll be focusing on 3 of them:
For our automations, we’ll be looking for changes in status in the following ways:
any status to playing
any status to idle
playing to any status
The plan is to create an automation for each one of these status changes. And each of those automations will perform the actions we have listed in the goals. To do this, we’ll be making use of the Roku and WLED integrations as well as the WLED webui for creating presets.
Setting everything up starts on the WLED webui side of things. This is where presets can be added to the device and various settings can be changed on the fly. We will be adding two presets for our set of automations (bright white and dim red). I did this on a desktop, so with the webui all the way open, it was on the far right side. I first set the LED strip to the settings I wanted the preset to use, then I clicked to add a new preset. Doing this twice got me the two presets.
Do make sure to note the presets numbers since this will be used to call up the presets when used in the automations later on.
Those presets can be called by the HASS automation to set things a bit more specifically than the HASS service will allow. The presets allow setting the solid color to use which I didn’t see as an option using the home assistant WLED service.
Dim when Playing
The first automation in our set of 3 is to dim the lights when the Roku starts playing some content.
The trigger for dimming the lights uses a state change from any state to ‘playing’. Since we don’t care about the original state, we leave the ‘from’ field blank, essentially acting as a wildcard, and we set the ‘to’ field to ‘playing’. This trigger will work when going from paused to playing, from an app to playing, etc.
The condition here is that the LED strip is already on. If the LED strip is off, we do not want to turn it on and start manipulating it.
It may seem a bit strange that we’re turning on the light as the action here when we already know its on, but it was the most straight forward way I could find to set the brightness on the light strip.
After turning the lights on, we want to set the lights to a solid color and call the preset to our dim red preset. I realize this could all be performed using the preset, but this is in part a relic of my experimenting with the automations. This can probably be simplified into the preset to handle the brightness, effect, and color.
The final (and only really necessary) action is to call a service with one argument to the light strip. The argument is the preset number that was created in the webui of WLED.
Turn Bright when Paused
The second automation in this grouping is to turn the lights up when pausing the video.
The trigger for turning up the lights when the media is paused is similar to the others. This time we want the state to change from playing to anything else. Due to this, we’re just using the ‘from’ field.
We only want to adjust the lights when they’re on, if we turn them off then we don’t want to be manipulating them.
The action for this automation is simple enough, we just need to set the light strip to the preset. This is a service call with one argument to the light strip.
Turn off When Idle
The final automation for this setup is to turn the lights off when the Roku goes idle. The idle state is when they Roku goes to the screensaver. In this automation, we’re not going to use the condition that the light strip is on, since if it is on or off, turning it off will have the exact same effect.
The trigger for turning off the lights when the Roku goes idle is similar to the others. This time we want the state to change from anything to idle. Due to this, we’re just using the ‘to’ field.
The action is simple to setup, we just want to turn off the light strip.
Testing and Changes to Plans
I went to play and pause the Roku far more times than I expected. Using the testing is how I found my sun condition of before sunrise and after sunset was causing problems. It took a few tries to figure out the right status settings for the automation. Below is the failed Sun condition that I tried to use.
Since this condition did not work, I decided to create a different condition, that the WLED strip is on already before manipulating it. Since the goal Sun condition was to manipulate the lights only at night, I decided that using the lights on/off status would be a good compromise and fit the same goal. I can just say ‘well if the lights are on already, then start manipulating them’.
This was a fun project to get some automation experience with WLED. I didn’t have the light strip setup with my TV as I hadn’t yet decided how I was going to use it, I just wanted to know what I could do. This does however work pretty well. This also gave me some other knowledge on the automations, triggers, and actions.
I encountered a problem recently on the Joplin desktop app where it couldn’t synchronize due to a file lock being stuck in NextCloud. It uses a file in the jopline data directories to determine sync status and lock status on files being edited, and this file was stuck locked in NextCloud with no way to delete it. I performed some searching, finding some blog posts on the subject and found this on how to solve it. I’ll be going through the manual solution to this problem and updating the process with my experience.
While the Ortur Laser Master 2 that I picked up is advertised as a laser engraver and not a laser cutter, it can do lightweight cutting and I was intent and optimizing that capability. After performing some research, I found that air assist would be a great modification to aid in this endeavor.
The air assist system was built with 1 main goal in mind, to make cutting with the laser more efficient. This will also reduce sooting and scorching by putting out fires while cutting.
The Ortur laser is completely open air, providing no assistance or infrastructure to vent the fumes away. I decided to work on an enclosure for these reasons. The enclosure has 2 main goals, to contain excess laser light from the room and to contain fumes from the laser so they can be exhausted. The exhaust could be a fan in the back of the box or using a vacuum table underneath the laser. In my case, I’ll be building a vacuum table to hold materials and exhaust fumes.
One thing needed with every CNC driven machine is good software to control it and generate the gcode. There are two main options for the Ortur Laser Master 2. These are LaserGRBL and LightBurn. The Ortur uses LaserGRBL as the main control software out of the box while LightBurn is a commercial offering that costs $40. This article will be going through the LightBurn setup while I went through LaserGRBL in the past.
One thing needed with every CNC driven machine is good software to control it and generate the gcode. There are two main options for the Ortur Laser Master 2. These are LaserGRBL and LightBurn. The Ortur uses LaserGRBL as the main control software out of the box while LightBurn is a commercial offering that costs $40. This article will be going through the LaserGRBL setup while I’ll be doing one in the future going through the LightBurn setup.