Bs Tweaker Msi 5
Jon Followell
I have the group numbers for both Eaton devices via the links below, but I am new to home automation and need some more specific instructions on creating the association between these two devices once I have the tweaker installed.
My tale:
Last night, looking at z-wave details, thought I'd 'fix' a slow connection.
Wound up excluding a switch and re-included using app swap-no problem.
Alas, I forgot that it was associated with a door contact sensor.
So, today, there's the 6-second delay, discussed recently, symptomatic of no hub z-wave radio comms, and just device to device communication.
Using your tweaker device, and in part the basic z-wave tool, I was able to determine which devices were associated and then, un-associated them.
I have another association, in the basement, that I'm going to see if I can live without.
Hopefully, I don't have another one or two still lurking.
It's not worth the hassle, especially with the delay.
Thanks.
I have not added association stuff to the scanner tool yet. I want to eventually incorporate everything form the "tweaker" tool into the scanner. For now, here is the old tweaker tool which can set and remove associations: [BETA] ZWave Tweaker port from ST
Yes, I discovered that.
I just removed three associated with a door contact with the tweaker.
There's always some red stuff with Java in the message in logs, so I made sure they were removed with the basic tool.
Basic tool is decimal, while tweaker is hex, and hex is what you need.
Now to search out a couple more associations in the basement.
Yeah battery devices are especially fun. I do have in my line of ideas to have the scanner support battery devices properly as well, where it will wait for it to wake up then send the commands. Lots of ideas, not enough time and motiviation.
On the latest, when I scan assoc groups, it's only giving me info for group 1 (lifeline). 10 times the same. I know there's an association based on the basic tool, but would like to see it as well in tweaker.
got it: had to print assoc scan.
Sometimes in that tweaker app you have to press the cleanup button, refresh the page, set your association groups in the settings again, save, then scan. Also, are you setting the groups to scan in the settings then saving?
Typically group 1 (lifeline) will get ALL reports sent to it. So if you have the hub in any other groups it would get duplicated messages, which could cause issues or just logging spam depending on the driver. Should only need the hub in group 1.
Sort of unrelated, but this happens to me even without loop tweaker in 10.0.20 (97) in both Wavelab Pro and Elements on macOS. Loop markers are completely ignored. Works fine in 9.5 Tried reformatting my hard drive and doing fresh install of 10.0.20 (97), same problem. (and 9.5 still works fine)
I recently bought WaveLab Pro 10 for the Mac and have not been able to use it since I only have problems with loops and the Loop Tweaker. Version 10.0.30 is already installed. The bugs only seem to exist on the Mac version! I made 2 videos, which you can download here:
But: If I stop the loop and start it again, the old area will be looped again before I have moved the right marker. The cursor simply goes through the marker and loops at the point where the marker was previously.
Video 2 (Steinberg has already reproduced these two bugs, so a fix can be expected for this):
Q: Where is the portable version?
A: When installing the tweaker, choose the Portable type of install, as shown on the image below.
The portable version will be extracted to the selected folder.
Multi-page scrolling is only triggered inside the area where program icons are displayed (the area between the task view button and the system try). Instead, make multi-page scrolling available on the complete taskbar. That way users can benefit from both features. You can minimize/restore programs and you can scroll pages if you move the mouse on the start button (or search field/search button/task view button/system tray).
Is it possible, please, to add a secondary checkbox for volume control over taskbar in order to choose to work over the empty space of taskbar (c)?
In this way, using a+b+c will split the taskbar space more evenly between both commands.
Thank you