Tag Archives: update

fixed : replacement HUE lamp not working properly in Google Home group

Posted on by
Reply

Question :

I had a Philips HUE lamp that went rogue after 4 years of working without any problems, so I had to replace it with a new one. Installation was easy (as always) : it was immediately recognised by my HUE Bridge and there is no problem when I use it with the HUE.app (I am not using the HUE(Bluetooth).app since I have an HUE Bridge). Even the HUE Remote that controls to the group of lights that the old HUE lamp is in, immediately integrated the replacement HUE lamp.

But when I want to control my HUE lights from my Google Home devices and apps, all lights are still controlled properly, but not the newly replaced HUE lamp… I can’t control it from Google Home… What is wrong ?

Answer :

After connecting the new Philips HUE lamp to the HUE Bridge and the HUE.app, you need to also reconnect it to Google Home manually… Philips HUE doesn’t automatically update in Google Home (or the other way around)… To get things working in Google Home, do this :

  • make sure that the new HUE lamp is working properly with the HUE.app and all HUE Remotes as intended
  • then, make sure the group of lights that the new/repaced HUE lamp is in is turned on (so all lights of the group should be burning)
  • now, open the GoogleHome.app on your iPhone (or iPad)
  • when the “Home” page opens, click on the “Settings” button (the one with the sprocket/gear-icon)
  • in the “Home settings” page that opens, scroll down to the bottom and click on “Works with Google”
  • in the “Add Devices” page that opens, you will see a “Linked” chapter and a “Add new” chapter below ; since you already have your HUE lights set up in Google Home previously, you can click on “Philips HUE” in the “Linked” chapter
  • in the small popup menu that opens, click on “Check for new devices”
  • when the auth.meethue.com online login page opens, login to your Philips HUE account using your eMail address and your password
  • in the “Grant permission” webpage that opens, scroll down to the bottom and click on the blue “Grant permission” button
  • now the “Add Devices” page in the Googlehome.app opens, and at the bottom a message saying “Philips HUE is linked” will show
  • then, the “Choose device” page will automatically open where you see all your HUE lights and devices that are currently not connected to Google Home, so select the HUE lamp’s icon tile that you have replaced and click “Next”
  • in the “Connect Home” page that opens, drag&drop the HUE lamp’s icon tile onto the correct HOME icon tile (usually the HOME location that you have setup in Google Home) [ note that you can only connect the lamp to one home ] then click “Next”
  • in the “Connect Groups” page that opens, drag&drop the HUE lamp’s icon tile onto each and every GROUP icon tile (of lights and devices) you want the HUE lamp to be in, one after the other
  • when done, click “Next” and the GoogleHome.app will update
  • when done, back in the “Home” page, scroll down to the proper group and test what happens when you turn the group of lights off and back on
  • if everything works properly, you’re done
  • if you run into a problem (now or maybe later on), try this :
  • turn on all HUE lights
  • turn off all running GoogleHome.apps on all devices you have and unplug all Google Home speakers, Google Home displays and Nest Hubs
  • after at least 30 seconds, plug all Google Home speakers/displays and Nest Hubs back in and wait for them to restart
  • now, test if the group of HUE lights that includes the replaced HUE lamp works as intended when using one of the restarted Google Home speakers/displays or Nest Hubs (if it works on one Google Home device, it will work on all the one that have been restarted)
  • also test if the group of HUE lights that includes the replaced HUE lamp works as intended when using the GoogleHome.app on your iPhone (or iPad)
  • now, everything should work as intended (in the very unlikely event that it does not, redo all of the above)

that’s it !

enjoy πŸ˜‰

Advertisement

fixed : LandRover navigation update gone wrong, navigation maps gone

Posted on by
Reply

Question :

I tried upgrading the HERE maps on the navigation system in my LandRover Discovery Sport P300e using a USB-stick as per the directions given by HERE and LandRover, but after 3 attempts that failed for no clear reason, when I retried yet another time, the update crashed while it was about halfway and now… there is no map left in the system to use for the navigation… nothing… the navigation is completely blind…

What can I do to solve this ?

Answer :

There are several reasons why this problem might have occurred. Your LandRover will probably show a warning message advising you to go to a LandRover garage and get this fixed, but you can also give it a try yourself first, just make sure you include all of these additional instructions in your next attempt :

  • start off by using a USB-stick with no previous navigation files on it – if you do not have a brand new USB-stick of 32GB at hand, you can also try using the current one : no need to format it, just open it in the Finder (on macOS), then inside the folder named “HereV1”, select all files (press the CMD-A key combo) drag them to the Bin and empty the Bin
  • goto the landrover.here.com website, login using your account name and pasword, goto “Maps & Services”, click the “Get Latest Update” button of the map you want to install and in the next page that opens, start by downloading and installing the latest version of the MapDownloader-app before you proceed to downloading the desired map itself ; just finish making the USB-installer as usual
  • now, before you enter your P300e hybrid LandRover to start the update, make sure to unplug the electrical charger cable before you start your car (so the engine will stay running during the entire update process that may take up to 30 or even 45 minutes to complete – if your electrical charger would be plugged in, your engine won’t start and your car will definitely go into sleep mode before the navigation update is finished ; if you like you can take a drive during the map update, just remember you are not able to see any maps on your screen during the update – you might be able to use navigation though Apple CarPlay in the mean time – and you have to keep the engine running until the update is complete, so you cannot leave the car until done)
  • when starting the navigation update in your car, wait with plugging in the USB-installer until the car’s system asks you to do so and make sure you use a different USB-port than you did before

…then proceed as per the onscreen instructions and sit back and relax

…if you do so, the update process may appear to be a little slow, but it will succeed in about 30 minutes. (and if it doesn’t just try again – and if it still fails after a few attempts, the problem is not ‘just an upgrade’ so you will still have to contact a LandRover garage to get it fixed)

That’s it !

enjoy πŸ˜‰

fixed : switch Hue light bulb to different Room in GoogleHome.app

Posted on by
1

Question :

I have installed a new Philips Hue light bulb and for some reason it ended up in the wrong Room in the GoogleHome.app

How can I move it to the right Room ?

Answer :

To move a Hue light bulb (of any other light bulb or connected device) to another Room in the GoogleHome.app, do this :

  • open the GoogleHome.app on your iPhone
  • click on Settings (the circular button with a sprocket/gear on it)
  • now the “Home Settings” page opens, click on “Rooms and groups”
  • now the “Rooms and groups” page opens, find the group that the light bulb that you want to move is still in and click on it
  • in the “Room settings” page that opens, click on the name of the light bulb you want to move
  • in the page that opens (called by the name of the specific light bulb), click on “Room”
  • in the “Choose room” page that opens, click on the name of the room you want the light bulb to move to, so it will be highlighted with a the checkmark and a blue color
  • then click “SAVE” (top right)
  • now the light bulb will have moved from the old room to the new Room
    • if it wasn’t moved, repeat the above

That’s it !

enjoy πŸ˜‰

Note : if you have trouble updating the new settings from the GoogleHome.app to your Google Nest Hub (or any other Google Home controlling device), try this.

fixed : Rooms not updating on Google Nest Hub

Posted on by
1

Question :

I have a bunch of Philips Hue light bulbs and one of a group of three had to be replaced. I have installed a new one and connected it to the Philips Hue Bridge using the Hue.app on my iPhone. And that works properly. But it turned out that in the GoogleHome.app the new one was not in the same group as the other two. I figured out how to fix that, so it’s now working properly when using the GoogleHome.app also.

However, when I am trying to control the Hue lights from my Google Nest Hub, the new Hue light bulb is still in a separate room… I looked for an option to sync the settings of the Rooms on the Google Nest Hub and it’s settings, in the GoogleHome.app and in the Hue.app, but there is none… I’ve also looked this problem up online, and the only solution given is to completely reinstall the Hue light bulb (and if that doesn’t work ‘just’ completely reinstalling multiple or even all Hue light bulbs…)

Isn’t there any easier solution ?

Answer :

Yes there is. And it is extremely simple : after you have made sure that the settings are the way you want them to on the GoogleHome.app, just unplug the Google Nest Hub from power, wait about 30 seconds and reconnect the power… now the Google Nest Hub will restart and fetch the updated settings from the cloud… so, everything is synced.

That’s it !

enjoy πŸ˜‰

Note : if anyone reading this also wants to know how to move a Hue light bulb from one room to another in the GoogleHome.app, read this post.

fixed : where can I get OS version 8.4.4 for AppleTV 3 ?

Posted on by
Reply

Question :

I was having a problem on my WiFi network so I had to reconfigure my AppleTV 3 from 2012. While doing so, I also wanted to do an update for the AppleTV-version of iOS. When I tried to do so, the AppleTV said I had version 7.6.2 installed and there were no automatic updates available. To be completely sure, I looked up my AppleTV 3 in the MacTracker.app and found that the Maximum OS listed there is version 8.4.4, so I searched online to see what info I could find on a 8.4.4 update.

I found that the 8.4.3 update was released around April 2020, and that it could be installed over USB using a Mac with iTunes on it… but on the Apple website Software update 7.6.2 is still listed as the latest release… https://support.apple.com/en-us/HT202157

What is going on ?

Answer :

There is no problem… at least, there is no problem regarding the updates, the only problem is in the naming…

It’s just that the AppleTVs initially ran on iOS, just like the iPhones and iPads… (correction : the original AppleTV ran MacOSX) …but as the products drifted apart, the versions of iOS needed for various iDevices did too …so Apple finally split the old iOS up in iOS for iPhone, iPadOS for iPad and tvOS for AppleTV.

For the iPads this wasn’t really confusing as iOS 12 was succeeded by iPadOS 13. But for AppleTV the naming became extremely confusing : tvOS 9.0 was introduced almost simultaneously with and only for the 4th generation AppleTV (now called AppleTV HD) in autumn 2015, but the previous versions of AppleTV kept running versions of iOS, just anonymously :

  • Apple TV 1.0 = “Front Row” release = MacOSX “Tiger” 10.4.7tv (for Intel) = build 8N5722 = 20070321 iTV release
  • Apple TV 1.1 = “YouTube” release = 20070720 iTV release
  • Apple TV 2.0 = “Take Two” release = 20080115 iTV release
  • Apple TV 2.0.1 = “Genre” release = 20080328 iTV release
  • Apple TV 2.0.2 = “Network” release = 20080414 iTV release
  • Apple TV 2.1 = “MobileMe” release = 20080709 iTV release
  • Apple TV 2.2 = “HD” release = 20081002 iTV release
  • Apple TV 2.3 = “AirTunes” release = 20081119 iTV release
  • Apple TV 2.3.1 = “No Hax” release = 20090225 iTV release
  • Apple TV 2.4 = “Gesture” release = 20090624 iTV release
  • Apple TV 3.0 = “Genius” release = 20091029 iTV release
  • Apple TV 3.0.1 = “Reprise” release = 20091107 iTV release
  • Apple TV 3.0.2 = “Finale” release = 20100211 iTV release
  • TV release 4.0 = Apple TV 4.0 = iOS 4.1tv = build 8M89 = 20100901 aTV release
  • TV update 4.1 = Apple TV 4.1 = iOS 4.2tv = build 8C150 = 20101122 aTV release
  • TV update 4.1.1 = Apple TV 4.1.1 = iOS 4.2.1tv = build 8C154 = 20101214 aTV release
  • TV update 4.2 = Apple TV 4.2 = iOS 4.3tv = build 8F191m = 20110309 aTV release
  • TV update 4.2.1 = Apple TV 4.2.1 = iOS 4.3tv2 = build 8F202 = 20110322 aTV release
  • TV update 4.2.2 = Apple TV 4.2.2 = iOS 4.3tv3 = build 8F305 = 20110511 aTV release
  • TV update 4.3 = Apple TV 4.3 = iOS 4.3tv4 = build 8F455 = 20110801 aTV release
  • TV update 4.4 = Apple TV 4.4 = iOS 5.0tv = build 9A334v = 20111012 aTV release
  • TV update 4.4.1 = Apple TV 4.4.1 = iOS 5.0tv2 = build 9A335a = 20111017 aTV release
  • TV update 4.4.2 = Apple TV 4.4.2 = iOS 5.0tv3 = build 9A336a = 20111024 aTV release
  • TV update 4.4.3 = Apple TV 4.4.3 = iOS 5.0.1tv = build 9A405l = 20111117 aTV release
  • TV update 4.4.4 = Apple TV 4.4.4 = iOS 5.0.1tv2 = build 9A406a = 20111215 aTV release
  • TV update 5.0 = Apple TV 5.0 = iOS 5.1tv = build 9B179b = 20120307 aTV release
  • TV update 5.0.1 = Apple TV 5.0.1 = iOS 5.1.1tv = build 9B206f = 20120510 aTV release
  • TV update 5.0.2 = Apple TV 5.0.2 = iOS 5.1.1tv2 = build 9B830 = 20120605 aTV release
  • TV update 5.1 = Apple TV 5.1 = iOS 6.0tv = build 10A406E = 20120924 aTV release
  • TV update 5.1.1 = Apple TV 5.1.1 = iOS 6.0.1tv = build 10B831 = 20121129 aTV release
  • TV update 5.2 = Apple TV 5.2 = iOS 6.1tv = build 10B143 = 20130128 aTV release
  • TV update 5.2.1 = Apple TV 5.2.1 = iOS 6.1.3tv = build 10B329a = 20130319 aTV release
  • TV update 5.3 = Apple TV 5.3 = iOS 6.1.4tv = build 10B809 = 20130713 aTV release
  • TV update 6.0 = Apple TV 6.0 = iOS 7.0.2tv = build 11A502 = 20130723 aTV release
  • TV update 6.0.1 = Apple TV 6.0.1 = iOS 7.0.39tv = build 11B511d = 20131024 aTV release
  • TV update 6.0.2a = Apple TV 6.0.2 = iOS 7.0.4tv = build 11B554a = 20131114 aTV release
  • TV update 6.0.2b = Apple TV 6.0.2 = iOS 7.0.5tv = build 11B601 = 20140130 aTV release
  • TV update 6.0.2c = Apple TV 6.0.2 = iOS 7.0.6tv = build 11B651 = 20140221 aTV release
  • TV update 6.1 = Apple TV 6.1 = iOS 7.1tv = build 11D169b = 20140310 aTV release
  • TV update 6.1.1 = Apple TV 6.1.1 = iOS 7.1.1tv = build 11D201c = 20140422 aTV release
  • TV update 6.2 = Apple TV 6.2 = iOS 7.1.2tv = build 11D257c = 20140630 aTV release
  • TV update 6.2.1 = Apple TV 6.2.1 = iOS 7.1.2tv2 = build 11D258 = 20140717a aTV release
  • TV update 7.0 = Apple TV 7.0 = iOS 8.0tv = build 12A365c = 20140717b aTV release
  • TV update 7.0.1 = Apple TV 7.0.1 = iOS 8.1tv = build 12B4410a = 20141020 aTV release
  • TV update 7.0.2 = Apple TV 7.0.2 = iOS 8.1.1tv = build 12B435 = 20141117 aTV release
  • TV update 7.0.3 = Apple TV 7.0.3 = iOS 8.1.3tv = build 12B466 = 20150127 aTV release
  • TV update 7.1 = Apple TV 7.1 = iOS 8.2tv = build 12D508 = 20150309 aTV release
  • TV update 7.2 = Apple TV 7.2 = iOS 8.3tv = build 12F69 = 2015048 aTV release
  • tvOS 9.0 = build 13T396 = 20151029 ATV4 release
    • tvOS 9.0.1 = build 13T402 = 20151109 ATV4 release
    • tvOS 9.1 = build 13U85 = 20151208 ATV4 release
  • tvOS 9.1.1 = build 13U717 = 20160125 ATV4 release
  • TV update 7.2.1 = Apple TV 7.2.1 = iOS 8.4.1tv = build 12H523 = 20160125 aTV release
  • tvOS 9.2 = build 13Y234 = 20160321 ATV4 release
    • tvOS 9.2.1 = build 13Y772 = 20160516 ATV4 release
    • tvOS 9.2.2 = build 13Y825 = 20160718 ATV4 release
  • tvOS 10.0 = build 14T330 = 20160813 ATV4 release
    • tvOS 10.0.1 = build 14U71 = 20161024 ATV4 release
  • tvOS 10.1 = build 14U593 = 20161212 ATV4 release
  • TV update 7.2.2 = Apple TV 7.2.2 = iOS 8.4.2tv = build 12H606 = 20161212 aTV release
  • tvOS 10.2 = build 14W265 = 20170327 ATV4 release
    • tvOS 10.2.1 = build 14W585a = 20170515 ATV4 release
    • tvOS 10.2.2 = build 14W756 = 20170719 ATV4 release
  • tvOS 11.0 = build 15J381 = 20170919 ATV4 release
    • tvOS 11.1
    • tvOS 11.2
    • tvOS 11.2.1
    • tvOS 11.2.5
    • tvOS 11.2.6
    • tvOS 11.3
    • tvOS 11.4
    • tvOS 11.4.1
  • tvOS 12.0 = build 16J364 = 20180917 ATV4 release
    • tvOS 12.0.1
    • tvOS 12.1
    • tvOS 12.1.1
    • tvOS 12.1.2
    • tvOS 12.2
    • tvOS 12.2.1
  • tvOS 12.3 = build 16M153 = 20190513 ATV4 release
  • TV update 7.3 = Apple TV 7.3 = iOS 8.4.2tv = build 12H847 = 20190513 aTV release
  • tvOS 12.4 = build 16M568 = 20190722 ATV4 release
  • TV update 7.3.1 = Apple TV 7.3.1 = iOS 8.4.2tv2 = build 12H864 = 20190722 aTV release
    • tvOS 12.4.1
  • tvOS 13.0 = build 17J586 = 20190924 ATV4 release
  • TV update 7.4 = Apple TV 7.4 = iOS 8.4.3tv = build 12H876 = 20190924 aTV release
    • tvOS 13.2
    • tvOS 13.3
  • tvOS 13.4 = build 17L256 = 20200324 ATV4 release
  • TV update 7.5 = Apple TV 7.5 = iOS 8.4.4tv = build 12H885 = 20200324 aTV release
    • tvOS 13.4.5
    • tvOS 13.4.6
    • tvOS 13.4.8
  • tvOS 14.0 = build 18J386 = 20200916 ATV4 release
  • TV update 7.6 = Apple TV 7.6 (8130) = iOS 8.4.5tv = build 12H903 = 20200916 aTV release
    • tvOS 14.0.1
    • tvOS 14.0.2
    • tvOS 14.2 = build 18K57 = 20201105 ATV4 release
  • tvOS 14.3 = build 18K561 = 20201214 ATV4 release
  • TV update 7.6.2 = Apple TV 7.6.2 (8144) = iOS 8.4.6tv = build 12H914 = 20201214 aTV release
    • tvOS 14.4 = build 18K802 = 20210126 ATV4 release
    • tvOS 14.5

As you can see from the list above, there is no TV update 8.x yet… the version you’ve been reading about online is the “based on iOS 8.4.4”-version, which actually is TV update 7.5

So, if your 3rd generation AppleTV lists it’s OS version as 7.6.2 you already have the latest OS-version available (…at the time of writing this post : mid March 2021)

That’s it !

enjoy πŸ˜‰

FYI : it’s good to know that there’s a slight hardware difference between the 2012 version and the 2013 version of the 3rd generation AppleTV :

  • A1427 = AppleTV3,1 = 3rd generation AppleTV (2012)
  • A1469 = AppleTV3,2 = 3rd generation AppleTV (2013)

NOTE : the procedure you are mentioning of upgrading or altering the version of the AppleTV OS by connecting the AppleTV to your Mac by USB-cable is a “jailbrake”, which Apple considers “illegal”…

fixed : CanoScan 5600F driver for macOS Big_Sur

Posted on by
4

Question :

I have a Canon CanoScan 5600F scanner that worked great with my previous Mac, but now I have upgraded to a new Mac running macOS 11.0 Big_Sur.

I’ve looked on the Canon website and searched the internet, but there is no macOS 11.0 Big_Sur compatible driver available for this scanner.

Is there any way to use this CanoScan 5600F scanner in macOS 11.0 Big_Sur ?

 

Answer :

Yes, there is :

  • goto Canon’s US website : https://www.usa.canon.com
  • choose Support > Scanners > Film & Negative Scanner > CanoScan 5600F
  • or use this link : https://www.usa.canon.com/internet/portal/us/home/support/details/scanners/film-negative-scanner/canoscan-5600f/canoscan-5600f?subtab=downloads-drivers
  • there, choose the “Drivers & Downloads” tab
  • then, choose “macOS Mojave v10.14” as your operating system and “English” as your language
  • then, choose the “Drivers” tab
  • now, you will see 2 drivers listed :
    • > 5600F Scanner Driver Ver.14.11.5h (Mac) : msd_-mac_cs5600f-14_11_5h-ea8_2.dmg
      • > ICA Driver Ver.4.1.4a (Mac) : misd-mac-ijscanner2-4_1_4-ea21_3.dmg
  • download both of them
    • note that despite the fact that both are versions from 2018, these will still work with macOS 11.0 Big_Sur
  • goto your downloads folder
  • first, double-click on the file named msd_-mac_cs5600f-14_11_5h-ea8_2.dmg
  • this will mount the ScanGear_CanoScan 5600F_141105.pkg
  • again, click on that and version 14.11 of the ScanGear driver installer will open
  • now, follow the on-screen directions and the latest ScanGear driver will be installed
  • then, double-click on the file named misd-mac-ijscanner2-4_1_4-ea21_3.dmg
  • this will mount the Canon IJScanner2_040104.pkg
  • again, click on that and version 4.1.4 the IJScanner2 driver installer will open
  • now, follow the on-screen directions and the latest IJScanner2 driver will be installed
  • when done, goto System Preferences > Printers & Scanners
  • if the CanoScan 5600F is already listed on the left, click it
  • if not, click the +sign (plus-sign) to add the scanner first
  • when done, click the CanoScan 5600F in the list on the left
  • when the scanner details open on the right, click on the “Open Scanner”-button
  • now, the built-in macOS scanner-app will open and it will immediately do a preview scan of whatever is in the scanner

NOTE : you might run into a small problem every once in a while ; when the automatic scanning preview starts, you might get an error saying “Scanner reported an error – Cannot communicate with scanner for these reasons: – Scanner is turned off. – USB cable is disconnected. Please check and try again.” If so, just flip the scanner’s ON/OFF-switch in OFF-position manually and then back into ON-posistie. That should help in making the scanner preview work again.

enjoy πŸ˜‰

 

fixed : Canon scanner error -21345 on M1 Mac

Posted on by
4

Question :

I have have just upgraded to a new MacBook Air M1 2020 (with an Apple M1 processor) running macOS 11.0 Big_Sur. Now, I am trying to get my Canon PIXMA MG3250 All-in-one printer-scanner to work with it… but even though I can get the printer function to work, when I want it to scan I get an error…

Installing the Canon MG3250 through System Preferecens > Printers & Scanners > Add Printer was really simple as it was immediately seen through Bonjour. After installing, the MG3250’s icon is listed on the left, and when I click it, the window opens where I can choose either the “Print” or the “Scan” tab. After choosing the later, I get the “Open scanner”-button, and when I click that, the built-in macOS scanner-app opens the “Scanner” window… which gives this error : “Failed to open a connection to the device (-121345)” each time I try. I just can’t get it to work.

What is wrong ?

Answer :

When you get this error in this setup, you will probably have gotten an error saying “IJScanner3” also. Do this to fix it :

  • goto the Canon UK website : https://www.canon.co.uk
  • there, browse to the PIXMA MG3250’s Driver Support-page or go there directly using this link : https://www.canon.co.uk/support/consumer_products/products/fax__multifunctionals/inkjet/pixma_mg_series/pixma_mg3250.html?type=drivers&language=en&os=macos%2010.15%20(catalina)
    • Yes, that’s right, even though you are running macOS 11.0 Big_Sur and Canon tells you there is no driver for such an advanced OS, the macOS 10.15 Catalina driver still works
  • when you see the ICA Driver Ver. 4.0.0a (Mac) version listed, click the blue download button to download
  • in your downloads folder, you will now find a file called miss-mac-ijscanner3-4_0_0-ea19_2.dmg
  • click that file and it will mount an installer called Canon IJScanner3_040000.pkg
  • click that file and the 2020-version of the scanner driver will be installed
  • when done, make sure the System Preferences are closed
  • then open System Preferences > Printers & Scanners > MG3250 again and click the “Open Scanner”-button
  • now, the built-in scanner-app will open the Scanner-window again, but hits time without the error… so you are good to go !

That’s it !

enjoy πŸ˜‰