Wave Driver
Cloris Sopha
Hello, I use Sound Forge Pro 10.0, everything was fine until yesterday when my computer performed a windows update, now I get the message "the windows classic wave driver audio device stereo mix Conexant ISST audio is missing or in use by another application", anyone know how to resolve this, thanks in advance for your assistance.
@Rudy-Monroe Right Click on the speaker icon in the Windows Taskbar in the lower right corner then click on Sounds. The Windows Sound configuration window will open. Go to the Recording tab and look if your Stereo Mix device is listed there and if it is deactivated. Right click on it to acitvate it or to show deactivated devices in case it is missing.
If Stereo Mix isn't listed look in the Windows Device Manager -ways-to-open-device-manager-on-windows-10/ under Audio Devices if your Conexant ISST Audio device is listed there. If not, you probably need to reinstall your audio drivers.
Our electromechanical driver is an ideal device for harmonic and motion demonstrations. Its primary function is to provide variable frequency, variable-amplitude, and mechanical vibrations for the lab. These simple functions have many applications such as:
WARNING: This product can expose you to chemicals which are known to the State of California to cause cancer, birth defects, or other reproductive harm. For more information go to www.P65Warnings.ca.gov.
This newly redesigned Wave Driver offers improvements in driving force and amplitude as well as a built-in string guide so tiny parts don't get lost. It is ideal for vibrating waves in a string, driving Chladni plates to show the vibration modes, or to demonstrate resonance vibrations.
A coil inside a cylindrical magnet is driven by a sinusoidal signal which comes from the external function generator that is connected to the Wave Driver's banana jacks. The coil is attached to a diaphragm that the actuator rod is connected to.
Thanks but I was really stupid (too many of these things) and realized I had downloaded the wrong Z-wave driver. I deleted it and downloaded the correct one and then reinstalled it in the app and it now shows and is working so far (lock and unlock commands). Will test my automation tonight with it. Thanks again and hope you get it working as well.
I seem to recall reading that Custom DTH drivers still have priority over any Edge drivers. You can either 1) remove the existing DTH which will require you to delete the device; or 2) wait for ST to migrate the device from the DTH to Edge.
This is a simple modification of the official Z-Wave Switch driver, with a new profile to support in-app configuration of Leviton Z-Wave Plus dimmers (DZ6HD & DZ1KD). See the screenshot below for the available parameters.
I used your driver on some more Leviton switches and I definitely like the change you made removing the default values. The list makes it clear what values can be entered and what the default values are. I went back and updated all of my settings on Leviton switches. Again, I appreciate all your work.
I installed your driver a week or so ago, and all was going fine. Then, two days ago, the parameters of literally every Leviton switch in my house got changed. The most problematic change was to the maximum level (11%).
I also see you mention using this driver for DZPD3 plugs. I think the latest update uses more specific fingerprints to target only the DZ6HD & DZ1KD in-wall dimmers. Other than those this driver should behave just like the default as of the last time I updated my fork from the upstream repository. So you may not see a difference after switching, except being unable to uninstall this driver from your hub while in use.
I used the Simple Device Info Viewer to find the fingerprint (also called the deviceManufacturerCode), which tells the driver which type of devices should use the profile for custom preferences. The DZ6HD is 001D-3201-0001, but what is the DZPD3 fingerprint? Since it worked with the earlier driver, it should also start with 001D- and end with -0001.
If you are running zwave-js-ui yourself, I would recommend you read the release notes when you upgrade, in fact I think you have a responsibility to do so. The release notes for the release where the name change occurred describes all the breaking parts. -js/zwave-js-ui/releases/tag/v8.0.0
So the only way I was able to see the Open Web UI link was to actually start the add-on. Once I did that, I could enter in my Keys. When I entered in the path to my Zooz stick (using the by-id name), I received:
I hope everyone continue to stay safe and healthy
My guess Z-Wave driver you have mentioned from GitHub.com is unsigned. Any idea how to make it work?
Is it required a development license?
As well you mentioned Travis Z-Wave driver is it the same driver from Github.com of different?
Matrikon works on OPC server for Zigbee devices and looking for Beta Testers
Maybe worth a shot
Stay safe
Any idea what happened to the ZWaveDriver on github?
Edit: It looks to be available here: GitHub - syuan409/ZWaveDriver: The Z-Wave Driver Module for Ignition allows you to observe and control connected Z-Wave devices
This is a driver for the new Shelly Wave 1PM. It has an excellent price. Because of that it lacks some features like be able to run scenes on a switch press, but in most cases you just want that to toggle the switch anyway. Measures power, energy, amperage and voltage.
Should this be compatible with the Shelly Qubino Wave 1PM Relais? Or i that exactly what it's meant for? Last time i installed my Shelly Qubino Wave 1PM it reacted to Hubitats commands like switching on and of but when turned on, it would switch of after a second and then on again after 5 or so seconds. That cycle oon repeat. Might have something to to with the wiring in my 100 year old house. What do you think?
Hi @p.albright
Yes, that is the device.
Maybe you have some of the parameters set for the auto ON/OFF timers set. With this driver you can check if those values are zero (0) and change them if not.
Sadly, that's not the case. All the values are set to zero. The Manual says the blue and red rapid blinking means that shelly is "checking the power supply 230 V AC Frequency oder 24V DC Voltage". We have 60Hz 230V Power in germany. I bought the EU Shelly version in a german shop. that shouldn't be the problem right?! I'm stumped but also not an electrician.
As long as you have it connected per figure 1 in the manual it should work. Mine are and I am in the Netherlands. Unplug it for a minute or two (if you have not done so yet). If that does not help it may be faulty.
I have two plug drivers that sort of do this, and also a separate tool to query for the settings. The way the HE driver system is designed it would be impossible to create a single fully universal driver, but one could be created per device type, e.q. switch, dimmer, power meter, etc...
The device mostly will work with the generic zwave drivers included. The problems is always with the settings. There is no standard for that hence all the per model drivers. If they would tackle that is a simple way you could get far with standard drivers.
The settings can be scanned from the device if it supports the newer command classes and they have the data populated in the firmware. Here is an example of a driver that can do this: [RELEASE] Z-Wave Universal Device Scanner
That may work for devices that support configuration v3 and up as long as you know the first parameter and this is not always 1. I would love to have it all in generic devices, but I am seeing more variations than 10 years ago rather then less. So not holding my breath.
PS: Scan failed with a warning for the Shelly. It pulled the parameters, but not the names or descriptions. Without the Info option, it does seem to pull the names, but still a warning : "A range must have no more than 2147483647 elements but attempted 2147483648 elements"
I have a dream that one day, there will be a protocol that everyone is using, new devices are recognized, where ALL features are working without issues and no need of the goodwill of brave developers, I have a dream.
I think I will keep on dreaming for ever, LOL
@MrFarmer sorry to disappoint you the Shelly Wave devices have all the necessary data stored in the FW, if the data can't be retrieved is a problem of the controller.
Doing tests with other certified controllers all the data including the parameters (names, values etc) are correctly retrieved from the devices and presented properly in the controller....
They work with controllers that adhere to the same standard (specially now with the Z-Wave series 700 and 800), any controller that relies on their own integration to make the device work should not even be advertised as a Z-wave controller.
Are you responding here because of the ticket I opened with Shelly/Qubino about the issue with using this device at a greater distance from the Hubitat C8 hub? That should not have to to with this driver. Also main reason for the per device brand/type drivers is not about basic functionality. This is no problem on Hubitat typically. However, the parameter settings and options a (zwave) device has are far from standard and if you want to get the most out of a device special drivers are needed. The great thing about Hubitat is that you can create and add such a tailored driver fairly simple and not need to wait on Hubitat to update their code.
Actually, I was investigating another ticket and came across this discussion. Regarding the distance, I believe I know the ticket you are referring to. As mentioned, the controller manages the routing, as the device lacks sufficient memory for this purpose. Sometimes, the routing may be constructed in unconventional ways, which is beyond the device's control.
While parameters and certain settings are determined by developers, all this data is stored within the device itself (series 700 and 800). Controllers such as Z-Wave JS, Fibaro HC3, and homee that utilize series 700 or 800 Z-Wave chips can read and configure everything correctly.
From experience I can tell you that, We're able to test devices under development (far from being released or certified) with the mentioned controllers.