"Device Not Found" using DTA commands

[MNB]

Ultrajones, I'm having issue with the latest Caller ID Plug-in. As per your latest posting I deleted all of the UltraCID virtual devices, re-created my events.

But.. within the UltraCID plugin I can see the caller's ID and phone number (within the logs) and the new VD are displaying the caller name and phone number correctly (see figure 1)

The problem is when I ask via an event to speak the caller's name using "$$DTA:UltraCID3-Name: Is calling command" (figure 2), I get "Device Not Found" instead of the caller name, has something changed in the DTA command or am I missing something else? Mike

I was able to run some of my other DTA, DTS commands and they all worked as expected along with other spoken text so both DTA command and TTS work for other instances but it seem that $$DTA:UltraCID3-Name: is not being recognized.

[MNB]

Can any other UltraCID3 user confirm that "$$DTA:UltraCID3-Name:" is not being recognized and is being announced as "Device Not Found". In the absence of any recommendation(s) I ended up using the "Last Caller Name" VD, by using "DSR:XXXX" command instead of the "$$DTA:UltraCID3-Name:", which seems to work. Mike

[ewkearns]

I believe, with the latest version, the address should be "UltraCID3-Name1," but I haven't tried it....

PS
I think you may need to delete your old devices and use the new ones, created under the new version....

See here:

https://forums.homeseer.com/showthread.php?t=195298

[MNB]

I believe, with the latest version, the address should be "UltraCID3-Name1," but I haven't tried it....

PS
I think you may need to delete your old devices and use the new ones, created under the new version....

See here:

https://forums.homeseer.com/showthread.php?t=195298

Gene, many thanxs for the comeback. I tried your recommendation and "lo and behold" it worked.. thanxs I will change my events and random PI to reflect. where did you find that detail? I had looked at Ultrajones updated posting and did see the instructions for deleting old devices and using the new ones but did see any new documentation reflecting the name change. Mike

[ewkearns]

Gene, many thanxs for the comeback. I tried your recommendation and "lo and behold" it worked.. thanxs I will change my events and random PI to reflect. where did you find that detail? I had looked at Ultrajones updated posting and did see the instructions for deleting old devices and using the new ones but did see any new documentation reflecting the name change. Mike

The only documentation I have been able to locate (other than the link I included above) is dated 12/21/2014.

[MNB]

Gene, how did figure out the latest version, being = "UltraCID3-Name1" ? Mike

[ewkearns]

Gene, how did figure out the latest version, being = "UltraCID3-Name1" ? Mike

Originally, I missed the information in the link I sent, too. Things were broken and upon inspection, I discovered I had two sets of devices, one with addresses like UltraCID-[name]: and one with addresses like UltraCID-[name]1:

It then became apparent which was the old and which was the new, since we now had line 1 and line 2 to choose from. You will have to edit anything that uses the old addressing scheme.

Another issue you might encounter is that there is a typo on page 13 of the manual. If you want to use the ring count, it is $$DVA:UltraCID3-Ring, instead of $$DTA:UltraCID3-Ring.... of course that would now be: $$DVA:UltraCID3-Ring[line number].

[MNB]

Originally, I missed the information in the link I sent, too. Things were broken and upon inspection, I discovered I had two sets of devices, one with addresses like UltraCID-[name]: and one with addresses like UltraCID-[name]1:

It then became apparent which was the old and which was the new, since we now had line 1 and line 2 to choose from. You will have to edit anything that uses the old addressing scheme.

Another issue you might encounter is that there is a typo on page 13 of the manual. If you want to use the ring count, it is $$DVA:UltraCID3-Ring, instead of $$DTA:UltraCID3-Ring.... of course that would now be: $$DVA:UltraCID3-Ring[line number].

Thanxs Gene, for the comeback. Interestingly all of my new devices are named "UltraCID3 Plugin" (under rooms) and only when I look within the "Advance" tab of a device do I see "UltraCID3-Name1" under the Technology Address field, the same with the ring device ect.. Mike

[ewkearns]

Try this:

Under "Category" choose "Check All" and under "Room" check everything resembling "UltraCID3 Plugin."

That may show up some "hidden" info......

[S-F]

What a nightmare. Does any have any ideas how many events I have that are impacted by this? Ugh. There goes Friday night.

[MNB]

What a nightmare. Does any have any ideas how many events I have that are impacted by this? Ugh. There goes Friday night.

Colin, I would have thought most of your work was to cut/Paste within random PI for phone conversations, unless you've been something else? Mike

[Ultrajones]

I am sorry, I didn't take into account anyone that had more then 1 or 2 HomeSeer events. I decided to rename the devices of the original modem in an effort to keep a consistent naming standard between devices. There also really isn't a good way for me to communicate these changes other than making a post here within this forum.

Regards,
Ultrajones

[Ultrajones]

Originally, I missed the information in the link I sent, too. Things were broken and upon inspection, I discovered I had two sets of devices, one with addresses like UltraCID-[name]: and one with addresses like UltraCID-[name]1:

It then became apparent which was the old and which was the new, since we now had line 1 and line 2 to choose from. You will have to edit anything that uses the old addressing scheme.

Another issue you might encounter is that there is a typo on page 13 of the manual. If you want to use the ring count, it is $$DVA:UltraCID3-Ring, instead of $$DTA:UltraCID3-Ring.... of course that would now be: $$DVA:UltraCID3-Ring[line number].

If this is occurring, then the code to readdress the existing devices is not working.

[MNB]

I am sorry, I didn't take into account anyone that had more then 1 or 2 HomeSeer events. I decided to rename the devices of the original modem in an effort to keep a consistent naming standard between devices. There also really isn't a good way for me to communicate these changes other than making a post here within this forum.

Regards,
Ultrajones

Ultrajones, firstly thanxs for the comeback. I would have expected that any changes/communique would fit nicely in your update thread https://forums.homeseer.com/showthread.php?t=195298. If you would be so kind and explain with the new UltraCID3 does the new device names change or is "UltraCID3-XXX1" under the Technology Address field reflect the new naming schema? As I made mention below I found that one can either use DTS[device ID] or DTA[device name] so I learnt another HS3 nugget Mike

[dzee]

UltraCID3 Won't Speak CallerID

I, too, am having no luck getting UltraCID to speak the caller ID and number. I have removed my old UltraCID3-Name and UltraCID3-Nmbr devices (and others from the old UltraCID)

I see the new Name1 and Nmbr1 devices, and have updated my events to speak: "Caller is $$DTA:UltraCID3-Name1:, $$DTA:UltraCID3-Nmbr1:", but nothing is spoken. The data in the variables is updating, and I can see log entries identifying the incoming call (see attached).

If I manually trigger the event, then I hear the correct text, including the values in UltraCID3-Name1 and UltraCID3-Nmbr1, so the problem appears to be the trigger not firing, not any problem with the data variables or devices. I've tried various event trigger parameters including Any Caller, Any Line, but the event won't fire. If I select Line1, specifically it will fire, so the problem is narrowed down to "Any Line" not causing a trigger to fire.

Is there a way to get the old UltraCID3 back?