Irecommend to use the plugin xsaitekpanels found on these forums and ignore the Logitech drivers.
The only useful software from Logitech is the test utility that allows you to check if the radio panel is working properly, independently from x-plane
You will also need at least a 2A usb hub, the radio panrl is quiet power hungry. Once xsaitek panels are installed it should temporarily light up when starting xplane than go off. It requires aviation bus to be powered b4 it cones on, you will alfo need to move a knob or push a button to get it to light up.
Thank you for your reply. By the xsaitekpanels I sense that you are not referring to the Logitech / Saitek Flight Instrument Panel Support Addon, costing $39, and available in the X-Plane.org website. In the description of this item there is a sentence at the bottom as follows: "Note that this plugin is compatible with the "XSaitekPanels" plugin available at X-Plane.org." This seems to indicate a different item and the one you mean, and costing possibly less, but, using the website search function, I cannot find it in X-Plane.org. Monty
Installation instructions are part of the manual - please visit the links provided to download, read and use. Support via the comments section in the link too. The first download is informational, the second download is the plugin. Enjoy, and thank you @sparker!!!
I have a Logitech throttle quadrant along with Logitech Switch and Multi panels. I'm perfectly happy with Logitech's drivers and would like to keep using them instead of using spad to control them. However, spad interferes with the logitech drivers and using the panels. In addition to causing issues with the panels, it has constant popup warnings about using the logitech drivers.
The purpose of SPAD is to replace the Logitech drivers (as well as provide a heck of a lot of features that Logitech doesn't provide). My feeling: delete the Logitech drivers. You have so many more options with SPAD.
hi guys... sorry I'm writing on an old thread. I just got a MultiPanel (autopilot panel) from Logitech and I'm trying to use it with FS2020 and default aircrafts (like the Cessna 172) and using Spad.Next ... I have tried many of the 2020+ online profiles for the device but I cannot get them to work properly.. specially the Altitude Hold part of the panel. I can get the VS to hold, but it seems like the altitude hold is not being read/synched between the aircraft and the panel. For example, I have 3000ft showing on the aircraft and when I try selecting an altitude on the panel (which is shown 5100 for example) and turn the knob, the numbers on the panel start jumping around and don't set.
On another note regarding this thread, I did eventually switch to using Spad to control my panels and deleting the logitech drivers. Even have a profile at -emb-110-bandeirante-spad-next-profile-for-logitech-saitek-switch-panel for the NextGen EMB-110.
I am running the Hubitat module with the Harmony Hub drivers. Presently I am able to use the Harmony remote home automation buttons to control a dimmer. I am doing this with a Hub variable that is connected to a virtual dimmer... and the virtual dimmer is mirrored to my light.
However, the one case that I use that the cracks (not breaks) the process is in the morning. I have a routine set up that when I wake up it slowly brightens the room. At the end of this process my virtual dimmer (and light) is on and set to 100. The harmony driver has the values set as off and 0. I can fix this by pushing (on the remote) the approriate button and the the rocker button. this will sync the remote and the virtual dimmer/light to all having the same value.
Last night my Home Control buttons were working. This morning they were not working. This occurred on both of my harmony hubs. I checked to logs and when i push one of the buttons on the remote I get the following error messages:
Please explain the process you followed to enable the use of the Harmony Remote Home Control Buttons with Hubitat. Specifically, I am curious if you were using the SmartThings Virtual Button 'hack' that was originally used to get these working with Hubitat. Since the ST 'hack' relied on the old SmartThings/Harmony Hub Groovy integration, it would not surprise me if this Groovy integration has finally been shut down by Samsung.
Personally, I simply use the Harmony Hub remote's Home Control buttons with my Philips Hue and Lutron Caseta lighting systems, as these integrations with Harmony are still functional. Both of these work very nicely with the Home Control buttons without any need for Hubitat in the middle.
Probably not the new you wants to hear, unfortunately. Even if Samsung has not shut down the Harmony Hub legacy Groovy integration, they will soon. Logitech actually recently released an upgraded Harmony Hub mobile phone app that is supposed to support the "new" SmartThings platform. This has come as a surprise to everyone. I am not sure if this new integration might afford a new opportunity to use the SmartThings virtual device 'hack' once again, or not...
I do not have Philips Hue or Lutron Caseta (trying not to create complexity of an ever growing number of hubs). All of my lights are connected to smartthings or hubitat while I am in the process of moving them all over to hubitat. Until this the only thing that I was going to have left on Smartthings was a samsung washer (which the functionality does not demand to have it connected).
I might try homebridge connection to harmony... but that would create more dependency on homekit (which except for the MYq I was looking to get rid of). Would be nice if homebridge would send its accessories to hubitat.
It looks like Smartthings changed something in their third party security/login process. The screens during the login were very different and it exposed all of my smartthings device to Harmony without asking what to expose.
You can now do all of your harmony/smartthings integrations straight from the harmony app on your phone. It used to be that to login into smartthings from harmony you had to use the pc/mac app and plug your harmony hub into the pc/mac. Now you can do that login directly from the phone app!!!!!!
I have multiple harmony hubs and ran into a slight issue that I was able to resolve. Which ever hub I last re-login to smartthings from was the only hub that would work. I noticed that there was a option to remove two factor authentication option during login. Once I had selected that (and re-login with both hubs) they both were able to operate smoothly.
I have gotten my harmony hubs integrated with hubitat using your driver. I have just recently overcome the new issues with the upgraded smartthings 3rd party app security upgrade (impacts harmony working with smartthings on the home control buttons).
Not sure how to move forward on this. What I am trying to do is sync the button level between hubitat and harmony when I use a hubitat rule to control the device vice pushing the button on the remote.
@user4652 - I have just updated the Logitech Harmony Hub Parent driver in my GitHub repo. The manual push and hold commands are now properly supported on the parent device page. Please give it a test and let me know if this has resolved the issue you reported. Also - please be aware, if you're a long-time user of this code, that a few months ago I made a breaking change to the Parent Device driver. The driver now uses Hubitat's built-in Generic Component Switch child driver instead of my old custom one.
With HUBIthings I think I can solve my problem (not elegantly). HUBithings allows me to share the virtual hub in Smartthings that the harmony button is tied to. So I can change the value of the dimmer through HUBIthings.... Then I THINK (not sure yet) that when I push the button Harmony will then update the value from Smartthings... so sure be able to make my two dimmers (Hubitat controlling the physical device... and Harmony button) equal each other when they are out of sync.
After installing Intel Wireless Bluetooth for Windows 10 and Windows 11 version 22.220.1.1, both my Logitech Bluetooth devices (MX Keys and MX Anywhere) stopped functioning. I rolled back the driver to version 22.170.0.2 and both devices were functioning. Just to make sure, I repeated these installing and rolling back procedures and the same results occurred.
Thank you for the information in this case since this is a laptop we recommend using the manufacture's drivers to ensure compatibility, you can find them here ( -1690-1675-1650-Wi-Fi-Controller-Driver_XWCCG_WIN_3.1222.7103_A32_02.EXE) the ones you were installing are what we call generic drivers, we offer these drivers to all computer manufacturer, and they usually modify them to ensure compatibility with your system.
However, I don't see why this driver has anything to do my Bluetooth problems. Since I have rolled back the Intel Bluetooth driver to version 22.170.0.2 and both my MX Keys and MX Anywhere work, this apparently is my solution.
Thank you for the update. It is very likely that Windows updates already provided the latest recommended driver for your pc that is why you got the error, so I would be a good idea to only use the drivers provided by the manufacturer in your case. Are there any other questions that I can help with?
Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.
3a8082e126