Skip to main content

Just when you think its safe to use Vista

Well, as I dropped my occupation as a consultant for microsoft stuff, I might as well complain a bit about my own pangs for using Vista.

I've been using Vista for quite a while now on various desktops and laptops, and its failed me several times and somehow always saved itself after some re-install or patch or issue. To be honest, I really started to like to use Vista, its stable, simple and effective minus the initial setbacks.

Initially it couldn't burn ISOs. Actually it couldn't burn anything at all, everytime you put in a CD it asks if you want to format it. Even non blank CDRs. You need to google and dig out some special software, The best I've seen is ISOrecorder. That of course worked after a re-install with a later build.

After the CD burning drama, it couldn't recognise all my devices, so I had a pile of peripherals lying in a corner of a room. Even after device drivers were created for some devices, I've already moved on to the 64 bit version of Vista and the whole driver saga continues. I still can't use my Sony Net MD with 64bit Vista. I'm probably going to try to VM the software and drivers. I actually solved the driver issues by buying a mac, at least all my peripherals are usable now.

Still Vista is great for corporations because it is cheap, easy to manage and control. Its stable, lets the laptop sleep properly and lets you surf the net and check emails. The enterprise version or business versions are good enough.

I have even moved to Windows 2008 64 bit for workstation and was very pleased with the results. Since then, I've downgraded back to Vista Ultimate for media center as the Hauppage HVR-1100 WinTV does not work with Windows 2008. But there was one thing I've done different from just fighting vista. Next to my Vista desktop is my Mac Book Pro!


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…