¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

Toolbox (Latest Version Bug)


 

Just a heads up.? I was having strange issues with the latest Toolbox on my machine and rolled back to the previous version.? Thought maybe, it was something with the install.? Nope, I had issues with it on one of my techs computers today as well.??

Using network device tree and connected to a shade power supply.? click on a shade and F2, change the ID and it changes all IDs for shades with the same ID.? Go to use the shade functions to set limits and it controls both shades. So there is a bug that causes interacting between devices.? So I rolled back to the previous version and the issue went away.

On my machine, it was debugger stopping after triggering a single digital signal.


 

Hi John

I have the same problem trying to change some duplicate ID's on a new job

Anyone seen or had a fix for this?


 

Hi Stujrob

?

i have the same problem,

after I ask crestron support, do change the ID one by one device?

the result was successful?but it takes a lot of time


 

yes i think also this is a bug of the latest version of the toolbox, maybe it's better to use the previous version first if it works fine


 

Previous versions of Toolbox had the "Clear ID" option not greyed out, I don't know why Crestron greyed it out a few versions ago, I rolled back my Toolbox to version 3.03.252.00 on a 2nd laptop I had onsite with me and cleared each device before changing it. This speeds up the process quite a bit. I have seen this type of thing happen off and on for years, mostly with lighting devices, and made it a habit of clearing before changing a Cresent ID. I sent a request to True Blue to un-grayout the clear button about 3 weeks ago.

Mark Dodson
Programmer - AVSOURCE
markd@... |
704.313.8331


 
Edited

This issue was identified back in late August and being tracked under BR 7307.
If you have a support case it can be added to BR 7307 for tracking and follow-up.
I've also added this groups.io thread to BR 7307 for follow-up when fix is released.

In the meantime, rolling back Toolbox or using the SETCRESNETIDBYPPN cmd in Text Console are both viable workarounds.

Toolbox - Network Device Tree View - Changing CNET ID on 1 Device Affects All Devices With Same ID

During installation CNET devices all initially report at their default CNET IDs (ex. HZ-KPCN @ 1C).
NDTV is used to adjust CNET ID on devices to ensure they're unique and match the program.
TB 3.12.1 NDTV uses SETCRESNETIDBYPPN <NEW CNET ID> <TSID> cmd to only affects the one device w/ spec'd TSID.
TB 3.12.2 NDTV uses SENDCNETPKT <OLD CNET ID>FD<NEW CNET ID>, causing all devices with same CNET ID to change.
Customers must roll back Toolbox to correctly set unique CNET IDs using NDTV.


 

?
?
?
Toolbox - Release 3.12.3 (Version 3.1230.0051) (3-6-2023)
Resolved issue with setting Cresnet IDs in Network Device Tree
?