Needs and wants for T-Day

List of items we still need before Transition Day for Edge devices, some of which we’re losing when the IDE is gone, some of which we don’t have with Edge devices, some of which we need to make the transition clean.

This list is about a) abilities needed for transition, b) features that we’re losing when the IDE is completely shut down or c) abilities that DTH+IDE had that Edge+App/CLI/API does not.

  • Ability to see Z-Wave device information in the app, CLI or API (fingerprint, clusters, security level). Currently only available in the IDE for DTH devices.
  • Ability to see Z-Wave routing information in the app, CLI or API. Currently only available in the IDE for DTH devices.
  • Ability to see ZigBee device information in the app, CLI or API (fingerprint, clusters, signal level). Currently only available in the IDE for DTH devices.
  • Ability to see ZigBee routing information in the app, CLI or API. Currently only available in the IDE.
  • Ability to transition Z-wave and ZigBee devices manually.
  • Ability to see and change ZigBee radio channel via app, CLI or API. Currently only available in the IDE.
  • Ability to reboot a hub via app, CLI or API. Currently only available in the IDE.
  • Ability to see hub event history via app, CLI or API. Currently only viewable in the IDE.
  • Ability for drivers to share informational data easier to a user (without requiring a custom capability.) Make it easier to share status of a device or details on the Information tab in the app.
  • Ability to see how much memory/storage is in use and available on a hub. Memory or CPU load per driver or device.
  • IDE DTH editor allowing edits of existing DTHs, so we can transition devices from DTH to Edge one-at-a-time.
  • Mechanism to help debug why some users are having so many issues with Zigbee devices going offline.
  • Smart Lighting app transition (IN PROCESS)
  • Notification when specific devices are being or have been automatically transitioned.
  • A menu driven system for choosing a driver during the discovery process rather than scanning everything. This would be similar to choosing the “brands” in the workflow. It is needed for LAN devices which don’t have fingerprints. Competing drivers will clash during discovery.

Post your requests and needs and I’ll add to the list above.

5 Likes

A menu driven system for choosing a driver during the discovery process rather than scanning everything. This would be similar to choosing the “brands” in the workflow. It is needed for LAN devices which don’t have fingerprints. Competing drivers will clash during discovery. This currently happens to my Hue driver and the ST bundled Hue DTH.

3 Likes

I would also say there needs to be a way for a LAN driver to disable being able to be changed to anything else. For instance, the virtual drivers can be changed to anything else, when they for sure won’t work.

2 Likes

Ability to do a Z-wave replace.

4 Likes

I can add it, but this is more about things needed for transition or that we’re losing when the IDE is completely shut down or things that DTH+IDE had that Edge+App/CLI/API does not.

We never had Z-wave replace before. We don’t have Z-wave replace in the current DTH environment, so its not something I’m immediately concerned about for the transition. :slight_smile:

Ahh, fair enough. I missed that nuance.

The only spot I could see swapping a v-driver would be to migrate to a different driver from the same developer. If I made a breaking change, I could offer a second driver that migrates devices. You would have to know the internals of both drivers though.

Would it make sense that LAN drivers offered a fingerprint string as well? Drivers could be told, only allow change to other drivers with a matching fingerprint.

Yes we did. We lost it in the Classic to ‘new’ transition. And it needs to come back.

1 Like

Is it needed for the DTH->Edge transition?

1 Like

Loaded question.

For feature parity for what exists today no.

For correct support of the ZWave spec and solving a lot of real world maintenance problems. Yes. Absolutely.

4 Likes

Sure we did. We had it for years, from at least 2014 up through 2019, although it was done at different ways at different times. It was covered in the official support documents at that time. I don’t know why it went away, it was very helpful. You’ll find lots of older threads in the forum discussing it.

And it’s still mentioned on the official support site, although it isn’t available anymore.

@nathancu

1 Like

I will rephrase my response from “we never had it before” to “we don’t have it now in the current DTH landscape”.

The goal of the post was to list the items that we’re going to lose on transition day or issues caused by moving from the current DTH environment to Edge.

1 Like

There might be some additional missing features in the following thread, although you may have already covered all those.

Life after the IDE: Questions and Answers

2 Likes