Select Page

Don’t Buy WeMo Smart Plugs

So I bought a 3 pack of the WeMo Smart Plugs in the hopes of yelling “Alex turn Bedroom Light Off” before bedtime. Instead of buying a Clapper, of which I’ve never seen in real life. 

Which was probably a better idea seeing as the WeMo Smart Plugs are notorious for disconnecting from Wifi or having general issues connecting with HomeKit.

There are tons of community posts about this issue on the WeMo community forums.

All the issues on the WeMo Community Forums

Unfortunately you can’t view the posts unless you register an account. Good luck, as their registration page is also broken.

WeMo Community Forums Registration Broken

I had bought the WeMo Smart Plugs based on The Wire Cutters Best Smart Switch review, of which WeMo is number one.

If you read the Disqus comments, you’ll see that’s not really the case. Most of the comments talk about how the WeMo is unreliable.

Oh and you’ll notice that sometimes after the WeMo is registered as a device in the mobile app. It’s unsecured Wifi is still active and you can still connect to it.

Anyone interested in the wemo mini please be aware that there is currently a security issue with the latest iteration of hardware. When using the latest version the setup network stays active after the device is setup. It may go away at first but will turn back on after the device loses power or loses connection to your router.
Belkin has told me they had a similar issue with their previous hardware last year and was able to fix it with a firmware update, but there is currently no fix for the current version.
Early replies from their technical support claimed that the setup network is “inactive” after setup, and that although it may broadcast the network no one can perform any actions with the device over this network after setup.
This is not true. The setup network can be connected to and the device can be operated by anyone connected to the setup network.
If you currently have the device, as of Feb 22nd 2019, there is currently no solution but to unplug your devices.
Please see details on the issue in their support form.
https://disq.us/url?url=https%3A%2F%2Fcommunity.wemo.com%2Ft5%2FWEMO-Hardware%2FWifi-Setup-network-broadcasting-constantly%2Fm-p%2F51663%2Fhighlight%2Ftrue%23M19326%3AZZvw-24FQM8kz7xZwJQf-Dtokcc&cuid=1030491

For now I’m going to do some research but would love to know what others are using and having success with!

Booster for WooCommerce Showing Hidden Item Meta

If you have the Booster for WooCommerce plugin enabled and have used their order items table, specifically “[wcj_order_items_table]”

You might see item meta that should be hidden. I’ve created a GitHub Gist that you can place into wp-content/plugins

Adding OVH Monitoring IP’s to Windows 2012 Server Firewall

If you login to the OVH control panel and notice that the monitoring is showing Red instead of Green, this is due to their monitoring servers not being able to connect to your VPS. You simply need to add their IP’s for monitoring that they provide in the control panel to your Windows 2012 VPS firewall.

The following command will add a new rule called “OVH Monitoring” and allow the remote IP’s specified in the OVH Control Panel.

 

OVH Public Cloud CentOS 7 Change Hostname

If you’ve tried to change the hostname on your OVH public cloud instance running CentOS 7, you may have had issues with it persisting after reboot.

Took me way to long to find this solution, but someone had already spent way too much time figuring it out.

This GitHub Gist explains it all https://gist.github.com/zmjwong/77ee37deb1749c2582eb

Basically you need to edit /etc/cloud/cloud.cfg and add “preserve_hostname: true” and then set your hostname using hostnamectl.

hostnamectl –transient set-hostname your.new.hostname
hostnamectl –static set-hostname your.new.hostname

Hope that helps and thank zmjwong!

CrashPlan Update 4.8 and Linux Headless Issues

An update to CrashPlan was rolled out at version 4.8 but no download files were available on their site for Windows. So if you’ve been trying to manage your Linux headless install and its failing, this might be why.

Here’s the release notes.

https://support.code42.com/Release_Notes/Code42_Platform/Code42_Public_Cloud_Version_5.4

I don’t know how to kick off updates to CrashPlan on Windows manually, due to this update being pushed out by CrashPlan cloud.

Update 09/30/2016 @ 2:40PM

Was able to direct connect via port 4243 headless without issues.

Update 09/30/2016 @ 10:00AM

Tried accessing a Linux server running 4.8.0 with a Windows client running 4.8.0 with no luck. Essentially what you would call headless, this was over an SSH tunnel. Will try direct.

Update 09/30/2016 @ 9:15AM

Got a reply from CrashPlan on twitter.