Skip to main content

is wireless the wave of the future

As I sit in my room coiling 20+ cables that didn't quite make it into the new setup. I keep thinking of all the people who try to convince me that wireless is the way to go.

Its not that I totally do not believe everything should be wired, but I've seen so many issues with wireless technology.

Here's a brief breakdown of cables i have. Power cables, 1/4 in, TRS, XLR, midi, USB, firewire, DVI, component, VGA, RCA audio, CAT5, SPDIF, etc. Right, so lets make all this wireless. How much bandwidth can you put into the air and not get conflicts in frequencies. I believe the air is polluted enough. I can't even get a good large file transfer with 802.11g without my neighbour accidentally disconnecting me. Speed rules doesn't it and everyone wants broadband which you can't get at this point with wireless.

Contrary to what my wife thinks, I dont really like cable messes. Sure, I'd like to clean it all up. I actually like the idea of multi purpose hub based fiber cable that does all protocols including power.

Yup, how about fibre channel hook up every home and have personal junction/firewall boxes to each household. Each rooms has a couple of fibre sockets that provide energy through high powered lasers. Maybe by then 30% of the earth population will already be living in space due to taxation reasons, i.e. no tax or tax benefits in space.

Back to the point. wireless at present should be used for wifi surfing, mobile phones and television remote controls.

Troubleshooting isn't really easier too. Give me a cable anyday.


Anonymous said…
Stealing bandwidth from your neighbours is fast becoming common in the housing estates here
Melven said…
maybe i ought to walk over to my neighbour's house and tell him to add a password to his internet router.

SSID is currently linksys with no password :P

the other neighbours learnt their lesson and now on WPA encryption.

Popular posts from this blog

Multiple Broadlink RM mini 3 integration using MQTT

Broadlink now has quite a lot of integration options almost out of the box. If you enable Broadlink IHC, you can directly link it to Alexa by giving the device a unique name.

There is a homebridge plug in for homekit integration but I haven't tried or tested this.

I wanted to put the device in domoticz so I can have more control over what can trigger my broadlink. I decided to use broadlink-mqtt for this, which is a fairly easy method to trigger from any source.

Setup Instructions for broadlink-mqtt

1. git clone

2. vi /home/pi/broadlink-mqtt/mqtt.conf

3. Update the mqtt.conf file with the device type set as multiple_lookup

device_type = 'multiple_lookup'
mqtt_multiple_subprefix_format = '{type}_{mac_nic}/'
4. Start the python script and check that it started and detected all the RM devices.
Check the log file to see what the IP / MAC addresses are. DEBUG Connected to RM2 Broadlink device at …

Fibaro HCL Virtual Device Slider

How to setup Fibaro home center lite (HCL) slider for virtual devices.

As the Fibaro HCL does not support LUA. The question was how to update the number value of the slider to send to the HTTP string. Thanks to this site which is a really good reference

The 2 use cases here are;

Sonos HTTP API Volume

To allow for volume control for all Sonos devices, add a virtual device with the IP address for SONOS HTTP API and specify the default port to 5005. Create Slider and put the following text into the string.

GET /volume/_sliderValue_ HTTP/1.10x0D0x0A0x0D0x0A

Domotiz Virtual Devices

GET /json.htm?type=command&param=switchlight&idx=XX&switchcmd=Set%20Level&level=_sliderValue_ HTTP/1.10x0D0x0A0x0D0x0A

Replace XX with the device ID.

Restart Fibaro HCL when it stops working automatically

It seems that the Fibaro HCL seems to hang every now and then. Instead of trying to restart it regularly, which doesn't really work, as it's almost impossible to predict when this will happen.

This method checks that the HCL is actually running and in the event it stops working, trigger a script that will restart it.

1. Get a non Fibaro controlled power plug and scripts to control it.

I used a wifi smart plug, TP-link HS100 and downloaded the scripts from

2. Create a bash script to restart the Fibaro, e.g.



$scripts/ -t $ip_addr -c off
sleep 10
$scripts/ -t $ip_addr -c on

3. Create a test global variable in the Fibaro HCL

Go to the variables panel and create a test variable, e.g. Test

4. Add a cron entry to test that the Fibaro API is still working and restart if it's not.

The cron script is scheduled ev…