Controlling a power outlet
590 views
Skip to first unread message
Audio Ape Remotes
May 12, 2017, 12:40:34 PM5/12/17
to QLab
Looking to be able to turn off and on a 110 power outlet wirelessly.
I see some new wifi outlets for home automation, wondering if those can be tapped into.
Perhaps a plug and play OSC type of outlet?
Would be used in QLab 4 for say, wirelessly turning off and on a lamp onstage.
Johannes Halvorsen
May 12, 2017, 1:39:09 PM5/12/17
to QLab
The simplest solution would be to buy a cheap dmx dimmer and an ArtNet dongle...
Audio Ape Remotes
May 12, 2017, 3:21:14 PM5/12/17
to QLab
Thanks I was looking for a very compact solution as I am a traveling one man show.
Found these interesting for transmitting DMX. It looks like you can have multiple receivers and one transmitter.
Their claim to 8 universes I am guessing means 8 different receivers correct?
Yeah the DMX dimmer is simple enough, finding the right product that's small and reliable to talk to it seems more challenging.
Most Artnet dongles I found were very bulky. Maybe I am missing something...
Jeremy Lee
May 12, 2017, 6:54:12 PM5/12/17
to ql...@googlegroups.com
Couldn't you set up an Arduino or Pi as a MIDI controlled relay to flip the switch? Or something like this:
--
Contact support anytime: sup...@figure53.com
Follow Figure 53 on Twitter: http://twitter.com/Figure53
---
You received this message because you are subscribed to the Google Groups "QLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qlab+uns...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/1717bb55-93bb-4dad-8693-e2edeb220e9e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Johannes Halvorsen
May 13, 2017, 2:25:51 AM5/13/17
to QLab
If you are on a budget and like to tinker tjere are of course something like this: http://m.ebay.com/itm/351973014580
Should be possible to get that to work if you can figure out the command protocol.
Scott Nelson
Jun 20, 2019, 4:23:43 PM6/20/19
to QLab
Hi Charles!
I would get a transmitter, Nano chip, and antenna from Wireless solutions, and a DMX switch like this: https://smile.amazon.com/Channel-Decoder-Controller-Converter-Protective/dp/B0111QOZXE/ref=sr_1_9?crid=NY7CH78PHOPP&keywords=dmx+relay+switch&qid=1561061859&s=gateway&sprefix=dmx+relay%2Caps%2C202&sr=8-9
You could solder the nano chip inside the DMX switch case, add the antenna to it and a power supply, and you'd have everything you need in one little box.
Alexander (Mailing List) Taylor
Jun 24, 2019, 8:15:04 AM6/24/19
to ql...@googlegroups.com
I have three of these I use, you can send UDP commands to turn each outlet (or the whole group) on and off. Not DMX, but very useful to me.
Alexander
Follow Figure 53 on Twitter: https://twitter.com/Figure53
User Group Code of Conduct: https://figure53.com/help/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups "QLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qlab+uns...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/95284359-ad58-4ad1-a606-7fa7fec313de%40googlegroups.com.
Erik Rietman
Jun 26, 2019, 3:35:49 AM6/26/19
to QLab
I’ve build one based on a Wemos D1 (Arduino formfactor board) in combination with some relays attached who can switch the power outlets. Qlab can send an OSC command over the network to remotely trigger the relays. Very easy to build. If you’re interested I can lookup the code for you.
Adam Earle
Jun 27, 2019, 10:38:12 PM6/27/19
to QLab
I've also used a Wemos to use MQTT to control things wirelessly. Similarly simple to do with QLab and applescript. Those things are insanely cheap.
Michael James Mette
Jun 27, 2019, 10:52:30 PM6/27/19
to QLab
I recently used this board (https://www.amazon.com/gp/product/B00R6DGSAK/ref=ppx_yo_dt_b_asin_title_o04_s00?ie=UTF8&psc=1) to turn on and off a fog machine. It works via DMX and has 3 relays.
peace,
mjm
Jonathan Pearce
Jul 4, 2019, 6:24:46 AM7/4/19
to QLab
Worth adding that while controlling a lamp should be fine, people should consider the safety implications of anything they are remote controlling - as most methods discussed here are not sufficiently robust for anything that would cause trouble if it powered up in error.
Rob Ram
Jul 21, 2019, 6:39:33 AM7/21/19
to QLab
im not sure if i hit send earlier or post reply, sorry to bug you.
im really curious about the setup and commands..
after spending quite a few hours on it.. i have come to the conclusion that i have no idea what i am doing . i can't seem to control the box if i change it's IP address in anyway via web browser.. in fact any change makes the web browser interface fail..even if i type in the newly assigned address (FOR EXAMPLE: changing the default 192.168.1.100 to 192.168.1.194, or the port from 80 to 9009 etc) in the address bar.
any command like pset 1 1 in RAW UDP does absolutely nothing .. even when assigning the address in the qlab settings page.
i wanted to attach screenshots
On Monday, June 24, 2019 at 5:15:04 AM UTC-7, Alexander (Mailing List) Taylor wrote:
I have three of these I use, you can send UDP commands to turn each outlet (or the whole group) on and off. Not DMX, but very useful to me.
Alexander
On Jun 20, 2019, at 4:23 PM, Scott Nelson <sc...@scottandmuriel.com> wrote:
Hi Charles!
I would get a transmitter, Nano chip, and antenna from Wireless solutions, and a DMX switch like this: https://smile.amazon.com/Channel-Decoder-Controller-Converter-Protective/dp/B0111QOZXE/ref=sr_1_9?crid=NY7CH78PHOPP&keywords=dmx+relay+switch&qid=1561061859&s=gateway&sprefix=dmx+relay%2Caps%2C202&sr=8-9
You could solder the nano chip inside the DMX switch case, add the antenna to it and a power supply, and you'd have everything you need in one little box.--
Contact support anytime: sup...@figure53.com
Follow Figure 53 on Twitter: https://twitter.com/Figure53
User Group Code of Conduct: https://figure53.com/help/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups "QLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ql...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/95284359-ad58-4ad1-a606-7fa7fec313de%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Adam Earle
Jul 21, 2019, 2:36:55 PM7/21/19
to QLab
Rob -
First thought - it looks like you have a port discrepancy. In QLab you have port set to 80, but in the device setting it looks like http is set 9009.
Second: In your device settings panel for Source IP it says to leave as 0.0.0.0 to disable. Since it doesn't have that warning for DNS, I wonder if not having a DNS set is tripping you up? I'm completely unfamiliar with this product, so I'm not sure that would cause an error.
Erik Rietman
Jul 21, 2019, 3:19:54 PM7/21/19
to QLab
I’m not familiar with your product but just a quick thought. Your subnet mask is set to 255.255.0.0. Mostly it is 255.255.255.0. Could that do the trick?
Graham Coates
Jul 21, 2019, 4:19:14 PM7/21/19
to 'Rich Walsh' via QLab
I can chime in on this.
I believe this is the solution - as long as you know what the commands you need to send to the netbooter are.
Based on your screen shots, the address on your netbooter device is 192.168.1.194. You have this set incorrectly in QLab. You need to change the port number to 23 as well.. Like this:
Settings -> OSC -> Patch 2 -> Name: nb 2port. IP address: 192.168.1.194 Port: 23.
The Cue that you have setup in your screenshot is perfect. As long as that command is correct.
On your Computer. Make sure your IP address starts with 192.168.xxx.xxx where xxx is anything between 1 and 254. ***Note that if your computer and netbooter are connected to a router, then changing your IP address will likely disconnect you from the internet. If it still doesn’t work after you’ve made those above changes, then write back with screenshots of your routers LAN configuration page and your network preferences on your computer. I can help you set that up too!
Long explanation:
Networking is stupidly complicated. Colour coded for topic! =)
An IP address of 0.0.0.0 means ALL addresses. Never put this number in any field on your device unless you know what it means! There will never be a reason for a consumer to use this number as an IP address, subnet mask, router address, or DNS IP address. In the case of your netbooter, the 0.0.0.0 allows ANY device on your network to send commands to it.
Subnetting: If you have an IP address that looks like this: 10.0.0.25, with a subnet of 255.255.0.0 then you have room for like 65000 computers on your network. You’d never have need of this on a wee non-enterprise network…. That said, it WILL work. You might just have 5 or 6 devices on your network which could hold 65000.
That said, it’d work exactly the same way as if you’d set the subnet to 255.255.255.0. This subnet has room for 254 devices. Same deal. Just fewer numbers.
As long as the last number or two in the subnet mask is a zero then you should be good. (The first two numbers need to be 255)
Choose one. 255.255.0.0 OR 255.255.255.0. It’s very unlikely that your compy is using something different.
Not having a DNS number in the field will very likely stop your computer or device from talking to the internet at large. Your netbooter doesn’t need to talk to the internet. If you’re not connected to the internet with your device at all, then there’s no need to have that number in there. Leave it blank.
If you’re connecting your computer and any device DIRECTLY into one another… (no router)
You do not need to have an address in the router or gateway field. BTW the words Router and Gateway are synonymous.
If your devices ARE connected to a router and need to communicate with one another, then you have to have an address in the router field. If your gateway is just a dumb d-link, netgear, or consumer grade device, the address is VERY LIKELY going to be 192.168.0.1, 192.168.1.1, or 10.0.0.1. If you had a subnet of 255.255.255.0 then your computer / device can have an address where the last number is anything from 1 - 254. Most of the time, it’s 192.168.0.1, 192.168.1.1 or 10.0.0.1.
Port numbers are like doorways for network traffic to travel through. You can only have one IP for any device with one network port. Two for two ports, three for three etc.
If you have one IP address on your device, a Port is a way to send specific types of traffic to services in your computer or device. An interesting side note: QLab could be considered a service and listens for traffic on port 53000. Your netbooter has three services available to send info to. So you have to send to port 9009, 23, or 25.
Since you’re not sending HTML traffic, I wouldn’t use that. Use port 23 - telnet. Port 25 is for diagnostic stuff. Not for consumers typically.
That's the long and drawn out reasoning behind networking. If you’re interested, I can elaborate. If I’ve made a typo, somewhere pile up on me and tell me that I should learn to network better!
On Jul 21, 2019, at 12:19 PM, Erik Rietman <er...@kirentis.nl> wrote:
I’m not familiar with your product but just a quick thought. Your subnet mask is set to 255.255.0.0. Mostly it is 255.255.255.0. Could that do the trick?
--
De inhoud van dit bericht is alleen bestemd voor de geadresseerde en kan
vertrouwelijke of persoonlijke informatie bevatten. Als u dit bericht
onbedoeld heeft ontvangen verzoeken wij u het te vernietigen en de afzender
te informeren. Het is niet toegestaan om een bericht dat niet voor u
bestemd is te vermenigvuldigen dan wel te verspreiden. Aan dit bericht
inclusief de bijlagen kunnen geen rechten ontleend worden, tenzij
schriftelijk anders wordt overeengekomen. De Leercompany aanvaardt geen
enkele aansprakelijkheid voor schade en/of kosten die voortvloeien uit
onvolledige en/of foutieve informatie in e-mailberichten.
--
Contact support anytime: sup...@figure53.com
Follow Figure 53 on Twitter: https://twitter.com/Figure53
User Group Code of Conduct: https://figure53.com/help/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups "QLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qlab+uns...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/b3e085ff-cf1c-4cc0-ab86-0643d627139c%40googlegroups.com.
Rob Ram
Jul 21, 2019, 4:50:39 PM7/21/19
to QLab
Thanks to everyone that chimed in i appreciate the help.
apologies to all though.. the config screenshot was an example of how when i change the default settings even the web panel loses control..
i have attached the default reset settings..
192.168.1.100 for the port i used 80 those or the defaults and the only way the web interface works.. if i make any changes both qlab and the web interface don't do anything.. like it loses communication
this is the products guide
To unsubscribe from this group and stop receiving emails from it, send an email to ql...@googlegroups.com.
Graham Coates
Jul 21, 2019, 6:38:11 PM7/21/19
to 'Rich Walsh' via QLab
Right. The web interface runs on port 80. If you change it, you have to specify the new port in order to access the device.
So if your IP address is 192.168.1.100…. In order to gain access to it, you now need to add the port number to the address. 192.168.1.100:9009
Here’s the thing though.
I just had a perusal of the technical manual on that device and didn’t see that it’s capable of accepting raw UDP messages without authenticating. QLab can’t do that.
If so they might be pulling some magic out of their hats by implementing an apple script or something.
Have you see this device work before? Or have you heard of anyone using it?
-Graham
To unsubscribe from this group and stop receiving emails from it, send an email to qlab+uns...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/346b660a-869d-47bc-a4dc-089aa9652185%40googlegroups.com.
<Screen Shot 2019-07-21 at 1.39.12 PM.png>
Robert Ramirez
Jul 21, 2019, 7:11:33 PM7/21/19
to ql...@googlegroups.com
Some one earlier in this thread said they use 3.
Alex I believe
You received this message because you are subscribed to a topic in the Google Groups "QLab" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/qlab/9aKppxYxiwY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to qlab+uns...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/5D6ACA23-5BFC-4676-910E-D08097B52DC6%40gmail.com.
Alexander (Mailing List) Taylor
Jul 22, 2019, 8:12:15 AM7/22/19
to ql...@googlegroups.com
On my setup, I ended up using script cues. It may have been an earlier version of QLab that didn't support doing this via network cues, I can't remember. Anyway...
Script cue:
do shell script "echo \"gpset 1\" | nc -c 10.10.10.100 23"
Replace the IP address with the one you set on the netbooter.
Change to gpset 0 to turn off the group. You can use the other documented commands if you want to do one port at a time too.
Alexander
To unsubscribe from this group and stop receiving emails from it, send an email to qlab+uns...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/598b1263-4413-4688-b787-52ab00715647%40googlegroups.com.
<Screen Shot 2019-07-21 at 3.38.04 AM.png><Screen Shot 2019-07-21 at 3.38.23 AM.png><Screen Shot 2019-07-20 at 5.05.39 PM.png>
Robert Ramirez
Jul 22, 2019, 3:49:24 PM7/22/19
to ql...@googlegroups.com
Alexander..
Thank you! youre a genius.. totally worked
You received this message because you are subscribed to a topic in the Google Groups "QLab" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/qlab/9aKppxYxiwY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to qlab+uns...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/EF924FE5-9B50-48FE-9538-051E61D80462%40orcsd.org.
please note my email has changed, update your address books.
Alexander (Mailing List) Taylor
Jul 22, 2019, 11:45:06 PM7/22/19
to ql...@googlegroups.com
The UDP commands are independent of the web interface. Defaults are port 80 for the web (standard HTTP), and port 23 for telnet/UDP (also standard for telnet). You can require authentication for the UDP/telnet commands or not - I left mine off since my subnet
is isolated from the rest of our institution's network. You could write a command to insert the authentication credentials along with the commands to the netbooter too, but I haven't done that. Here are some screenshots of my setup. I can provide more details
if needed.
devAudioRackOn
deviceControl.theaterMainRack.powerOn
00:00.000 00:00.000
00:00.000
do shell script "echo \"gpset 1\" | nc -c 10.10.190.5 23"
devAudioRackOff
deviceControl.theaterMainRack.powerOff
00:00.000 00:00.000
00:00.000
do shell script "echo \"gpset 0\" | nc -c 10.10.190.5 23"
To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/CAMikEpauNCaUC2q_m7qjmvSVJXEgw-qOLebYU15aqhqjC3KWhQ%40mail.gmail.com.
Rich Walsh
Jul 23, 2019, 4:58:28 AM7/23/19
to ql...@googlegroups.com
I think it's worth pointing out that without the -u flag nc will be sending TCP not UDP, so these shell commands aren't sending UDP. It's not clear from the manual that the device actually supports UDP; telnet is usually TCP. I wouldn't be surprised if you could not control this device with raw UDP strings from Network Cues.
(Port 25 is the standard SMTP port of course, for sending email. There's a typo in the manual in the header for the section about SNMP, which is something altogether different used for network monitoring.)
Rich
On 22 Jul 2019, at 13:20, Alexander (Mailing List) Taylor <ataylo...@orcsd.org> wrote:
The UDP commands are independent of the web interface. Defaults are port 80 for the web (standard HTTP), and port 23 for telnet/UDP (also standard for telnet). You can require authentication for the UDP/telnet commands or not - I left mine off since my subnet is isolated from the rest of our institution's network. You could write a command to insert the authentication credentials along with the commands to the netbooter too, but I haven't done that. Here are some screenshots of my setup. I can provide more details if needed.
devAudioRackOn deviceControl.theaterMainRack.powerOn 00:00.000 00:00.000 00:00.000do shell script "echo \"gpset 1\" | nc -c 10.10.190.5 23"
devAudioRackOff deviceControl.theaterMainRack.powerOff 00:00.000 00:00.000 00:00.000do shell script "echo \"gpset 0\" | nc -c 10.10.190.5 23"
<PastedGraphic-1.tiff>
<PastedGraphic-2.tiff>
Reply all
Reply to author
Forward
0 new messages