Schwie's Pad

A bit of an M$-centric post, but this issue has bugged me on a few occasions: if you use Outlook’s Quick Steps to archive messages in your inbox to a Public Folder continue reading. In the past when I have attempted to create a new Quick Steps button that links to a Public Folder location, I have found the Public Folder I’m interested in unavailable for selection. To make the Public Folder of interest available to make a new Quick Steps button, we have to coax Outlook by adding the Public Folder to the recently used folder list. The steps below help us to make the Quick Steps button; steps 1 and 2 involve archiving a message which helps to add the Public Folder to the recently used folder list and steps 3 through 5 help create the new Quick Steps button:

1. In Outlook, move to the Home->Move pane, click the “Move” button, and choose “Other Folder…”
2. Navigate to the Public Folder where you would like to archive a message, select the folder, and choose “OK”.
3. In Outlook, move to the Home->Quick Steps pane, click the down arrow on the right hand side of the pane, select “New Quick Step”, and then select “Move to Folder”.
4. Replace the text “Move to Folder” with the name of your Public Folder.
5. Next to the “Move to folder” checkbox, click the “Choose folder” contextual menu and choose your Public Folder from the list of recently used folders.

That’s all! I feel like M$ could eliminate this issue by allowing us to select a Public Folder that is not part of our recent folders list, but I’m more of an Apple user.

Thanks to DJBenson, who posted the instructions below:

Log in to https://home.nest.com with your credentials then browse to https://home.nest.com/session in the same tab, you will see a JSON object of your session. Look for the string enclosed in the quotes after “access_token” and copy that to the clipboard (copy the full string between the two quotes).

It looks something like this:

{“2fa_state”:”none”,”access_token”:”REDACTED”…

In your Homebridge config.json, remove the email and password fields and create a new parameter called “access_token” like such:

{
"platform": "Nest",
"access_token": "***REDACTED***,
"options": [
"HomeAway.AsOccupancySensor",
"Protect.MotionSensor.Disable"
]
},

Thanks, Tina! My first pair of toasty slippers in a few years. These badboys are model RN 88276 and have an upper lining and sock lining consisting of 100% wool. So far I can say they are very warm and seem size 12’s seem to run a bit small on my feet (I wear size 12’s in street shoes and size 11.5 in soccer shoes). Curious to see how they compress and fit over time.

My 2001 Volkswagen New Beetle GLS had recurring OBD2 trouble codes, P0171 and P1582, coming up over the summer. Reading other threads, I popped the hood and found a short piece (~1 foot) of disintegrated hose on the left hand side of the engine block (American passenger side). I pulled off the hose clamps and what little cloth like tubing remained and replaced the tubing with black silicone tubing purchased from an eBay auction with these specifications:

The new tubing fits like a glove and the listing is still available: https://www.ebay.com/itm/161551221275.

I’ve had this hose installed for almost 4 months with exposure to hot (90 degrees Fahrenheit) and cool conditions (10 degrees Fahrenheit) and my 2001 New Beetle GLS is purring like a pussy cat again. Even better, the trouble codes have stopped.

I love my Lumma light grips. Each light/laser packs a 750 mAh battery, which work wonderfully all winter. I’ve had my Big Dummy fall sideways and smash the the Lumma light grip into concrete and except for a few scratches, they seem unfazed.

The buttons have been a little finicky, but they work. Also, the USB port cover has broken off a couple of my grips. This isn’t so bad, but it allows rain to go right inside the grips and soak the PCB. Sadly, I let this happen to a couple of my grips. After this happens, I attempted to turn the lights on and they don’t seem to want to illuminate, or they might after the first soaking and from that point forward, they only sporadically light up.

This weekend, I pulled out my two bad light grips that are exhibiting the behavior described above. Accessing the PCB is really easy, two Phillips machine screws come out and the grip housing separates. After you unplug the battery from the PCB, the board slides right out – be careful to not let the laser lens and LED gaskets to get away.

Using my 50X magnifier (thanks Frank!), I looked at the pin connections for the button and where they attach to the board. Sadly, I don’t have pictures showing a closeup of the damage, but I found that solder points between the pads and the S2 button had cracked and separated. No problem, just a little heat from my solder gun and silver solder and I’m back in business! I fixed two light grips and a third is exhibiting different behavior that I haven’t figured out how to fix yet (the third one stays illuminated and only extinguishes the red LED when either of the buttons is pressed – yeah, pretty messed up). Still, I’m tickled silly to have two other grips back in service!

Comcast emailed me about changing settings – they are no longer allowing outbound email and port 25.

My aging Loftek Nexus 543 security camera has been jamming outbound messages on port 25 for years. There are no updates for its firmware, so I logged on thinking it might be in trouble of not supporting the present. Lo and behold, its sending test messages with Comcast while configured with these settings:

We have Comcast for internet-only service. Earlier this year, we successfully removed all TV plans and charges by exchanging messages with a Comcast representative in the support area of their website:

https://forums.xfinity.com/t5/Stream-TV-App/STREAM-BETA-APP-ON-SAMSUNG-75-INCH-TV-IS-NOT-IN-FULL-SCREEN/m-p/3205833/highlight/true#M21342
– strike up a conversation with a Comcast Employee by sending a private message as described in the link above and state that you’d like to drop tv service and go with internet-only
– the Comcast Employee you connect with will walk you through options you request and help activate your new plan

Or, you may be able to do the same by logging into your account through Comcast’s website to directly manage your plan – you can opt out of television and phone plans and choose an internet-only plan:

https://www.xfinity.com/learn/offers?lob=internet
– sign in to your account
– click above link again if you weren’t already signed in
– click “View all offers”
– click “Filter”, uncheck “tv”, and check “internet”, click “Done”
– choose the internet bandwidth best for you

If you add a term to your agreement, you generally get better rates for the term duration, after which rates go back up and you may need to repeat the instructions above to improve your rates again. Good luck to you.

January 2018, I was corresponding with LIVALL over my failed LIVALL BH81H bicycle helmet. I really liked the helmet while it worked, but first its heart rate sensor failed and then the entire helmet stopped working. Remembering the BH81H’s good days, I quickly accepted LIVALL Support’s offer to purchase a new BH61S for $35, including shipping. The BH61S is essentially a BH81H, without the heart rate sensor and a bit of a different profile, but nearly identical in operation, even down to the front-mounted buttons.

I received the BH61S in February 2018 and it came with another BlingJet 100 that I left in the box, because I found little use for the first BlingJet 100 I received with my BH81H. After opening the package, I noticed the helmet was even lighter than the BH81H, so I weighed it in at 308 grams, nice! The BH61S had nearly identical construction to the BH81H , down to the straps and padding. Also identical to BH81H is the comfort, these helmets are barely noticeable compared to the comfort of a non-smart helmet.

The pairing setup for the BH61S is identical to the BH81H, just power on the helmet with the center round button and hold it down until a female voice announces over the helmet speakers “Pairing”. The pairing was quick and painless with my iPhone 6s+. I used the helmet for the ride to work the next day, which was near 0 and found that the helmet held its charge until I got to work, about a 1.5 hour ride due to the snowy conditions. The helmet continued to charge and operate like a champ until the spring, when it got pretty wet riding home one day. I tried to towel it off as soon as I got home, but it was a soaker of a rain and the helmet didn’t respond to button presses. I let it sit by the dehumidifier for a day and the helmet started working again – woohoo! Over the 1.5 years since I started using this helmet, I found that it is very sensitive to rain – don’t get it wet.

The helmet continued to work fine through the winter of 2019, which included a snowfall in the Twin Cities that bested the previous record by nearly 50% – yikes! All through this time weather, the BH61S worked, with wetter days requiring use of the dehumidifier mentioned above. In the spring of 2019, two issues developed with the helmet. The left speaker started to cut out. In September 2019, the left speaker stopped working and the center button has also started to fail, button presses only sporadically turn the helmet on or off.

Other notes: the audio quality from the speakers lacks bass and the microphone leaves plenty to be desired. While riding and making phone calls technically works, the quality of the BH61S’ microphone may drive your telephone call recipients crazy. I have to pretty much ride at less than 5 miles per hour for people to hear me on the helmet microphone.

Since buying into LIVALL helmets, Sena (motorcycle helmet company) has developed their X1 and R1 helmets, the latter includes a model with a front-facing camera, and other companies are offering smart helmets too, including Coros and Cosmo Connected. Still, the BH61S has been enough of a winner that I’m willing to triple down with LIVALL and pursue their latest helmets, the BH51M or BH51M Neo Range, whichever I can get my hands on for less. More on this in a future review, which will most likely note how much more the BH51M-series weigh and what that means to comfort over an hour plus commute.

** Update 11-7-2019 ** The helmet has officially died again. I heard rattling inside the plastic enclosure on the front of the helmet. Taking apart showed that R22 and R23 were literally blown off the board that is now a bit black in that area. If you have info on what the resistance should be for each of these resistors, please let me know! I haven’t found the board design files anywhere on the internet (yet).

We have a couple high capacity drives attached to a Mac mini running macOS Server on High Sierra. Family Macs use Time Machine to back up to these drives. At some point, my wife’s password on her Mac (running Mojave) changed from what was on the mini and Time Machine began to error out. Some foreshadowing: she uses the same username on the mini and her Mac.

After her password on the mini changed, her Time Machine backups displayed the following error messages:

“There was a problem connecting to the server”
“Time Machine can’t connect to the backup disk”
“OSstatus error 65”

Basic troubleshooting called on me to make a manual connection using Finder (command K) from her Mac to the mini – mounting the drive was successful, so I went back to Time Machine and tried from there, but the same errors above barfed out. Frustrating.

From Terminal on my wife’s Mac, I pasted in the following line:

log show --predicate 'subsystem == "com.apple.TimeMachine"' --info | grep 'upd: (' | cut -c 1-19,140-999

I pasted output from the command into Google and came across this post on Apple’s site:

https://discussions.apple.com/thread/7898878

Yes, Satrop’s issue and fix is it! The username on my wife’s Mac is identical to the username on the mini and somehow this disturbs things if the password changes. To get around this issue, I decided to use the following workaround, which is essentially changing the credentials on her Mac for how it mounts the mini. From her Mac I had to:

1. Disable Time Machine by System Preferences->Time Machine->Select Disk…->(click the disk you’re trying to mount)->Remove Disk.

2. In Keychain.app, remove all instances of the saved password to your NAS, in my case the mini. I searched for “mini” and “10.0.1.125” and deleted those instances.

3. From Finder, mount the mini’s disk (Command K) using my own credentials, which obviously differ from hers.

4. After the disk mounts, go back to System Preferences->Time Machine->Select Disk…->(select the mounted disk – I used AFP to mount the disk, so when I hovered over it I could see its address had the AFP protocol).

5. Success! When you quit Time Machine preferences, it should automatically start a new backup (or continue an existing one).

I have posted on installing and removing Homebridge platforms and accessories, which are useful for installing a web user interface for Homebridge. I’ve had good luck installing this web user interface from Terminal.app:

sudo npm install -g –unsafe-perm homebridge-config-ui-x

By installing this package, you’ll be able to install and uninstall packages and accessories and updated Homebridge’s config.json file with a graphical user interface. Be sure to open port 8080 or whatever port your prefer from the outside so you can gain remote access. Also be sure to change the default username and password if you do this 🙂