ISY994, portal

Certain devices (maybe 30% of mine) which used to work fine now say "Sorry it looks like universal devices is unavailable right now" when I try to turn them on/off by voice.  The rest work fine.

All devices work fine from App and Browser, Mini Keypads, etc.

I've tried uploading to Google several times, but no change.

Why?

Fixes?

Thanks

 

 

 

 

 

Edited September 28, 20232 yr by johnstonf

This problem didn't magically go away (as i hoped it would too LoL)...

I deleted it, uploaded spokens, then re-added and gave the spoken a new funny name "cookie"

It actually worked for a couple minutes, and now is back to "Sorry, Universal Devices is Unavailable right now"

WTF?

Other devices are working ok, but a few are stuck in this mode.

It seems like Google is preferring to talk to a non-existent (maybe OLD??) server for particular 'devices'.

 

 

 

 

Edited September 28, 20232 yr by johnstonf

17 minutes ago, johnstonf said:

It actually worked for a couple minutes, and now is back to "Sorry, Universal Devices is Unavailable right now"

There may be another way to get it working but I had to delete the UD service in Google Home and add it again to fix that problem.

44 minutes ago, mmb said:

There may be another way to get it working but I had to delete the UD service in Google Home and add it again to fix that problem.

Thanks... i just tried that, but didn't fix it...

@johnstonf I wonder if it's a result of the change posted by @bmercier in June.  No recent update to this so not sure if UDI was able to update things behind the scenes or of Google finally made a change that impacted users differently. Might be worth putting in a support ticket for a UDI Portal review.

https://www.universal-devices.com/my-tickets

 

I just tried to sumbit ticket... after 15 minutes work... submit, then...

OOPS page... like WTF?

See screenshot

@bmercierare you seeing this post?

 

58 minutes ago, Geddy said:

@johnstonf I wonder if it's a result of the change posted by @bmercier in June.  No recent update to this so not sure if UDI was able to update things behind the scenes or of Google finally made a change that impacted users differently. Might be worth putting in a support ticket for a UDI Portal review.

https://www.universal-devices.com/my-tickets

 

Google Home action has not changed and is still working.

39 minutes ago, johnstonf said:

@bmercierare you seeing this post?

 

I do, replied in the ticket.

My UUID is... (See attached)...

My device id:

53.1e.78

 

 

@bmercier

 

I have the same problem. Has been an issue for many months, if not years. An update would be much appreciated.

Here's a previous post I made about this issue without any resolution

 

Edited October 29, 20231 yr by beninsteon

On 10/28/2023 at 9:04 PM, beninsteon said:

@bmercier

 

I have the same problem. Has been an issue for many months, if not years. An update would be much appreciated.

Here's a previous post I made about this issue without any resolution

 

This can be 4 things:

1. GH does not understand you correctly and turns on/off something else that indeed does not respond.
2. The device in GH is orphaned (the device exists in GH, no longer exists on portal)
3. The device exists in both GH and Portal, but no longer exists on ISY
4. The device exists in both GH, Portal and ISY, but actually does not respond (
   • This could be a communication issue (Insteon/ZWave issue, node server issue
   • Or the device is dead.

Now, this happens when turning off lights in a room. First you have to figure out which GH device exactly does not respond. When you know which GH device does not respond, you need to figure out which of the above is the issue.

For case 1: Test from the GH app directly (Don't talk, use the buttons in the app).

For case 2: Delete the device from GH app, then ask GH: Hey Google, sync my devices. If the device reappears, it is indeed in Portal.

For case 3: Check your mapping in portal. Make sure the ISY address exactly matches the address you see in the admin console.

For case 4: Make sure you can control the device from the admin console.

Somehow (respectfully)  I don't think you're reading this properly...
-GH understands me!  (no problem)
-The command IS getting to Google (that's why it responds)
-It is GOOGLE that is saying it can't reach UDI
  (But ONLY for the devices in question!)
  (The message is TOTALLY different for all other cases and devices)
-The devices work PERFECTLY locally, and via UD-mobile remotely (NOT DEAD!!!)
-They worked FINE in the past... at some point Google is now linking these devices to a NON-EXISTENT server!
  (that's why it is saying it can't reach UD !!!)
-I see it in ISY portal and can control from "ISY Web Access"
-The Insteon Device ID's are Correct and DO match
  (In this particular case, I'm picking on 53.1E.78)
 

 

 

@johnstonf,

What's common between these devices? For instance, are they all dimmers or switches? What if you create a program that controls these devices and then call the program (using a differnet name). Does this work?

With kind regards,
Michel

I actually had this problem on Saturday out of nowhere -"can't reach UDI"

The usual fix of going into Google Home app and linking UD and authenticating fixed it for me.

Hi Michel,

Thanks for giving attention to this!

I created two programs, for on and off...
they both give the message "Sorry, i couldn't reach universal devices"

Recreated with good device, they work.

Now it gets more interesting... !!!
I then ADD the failing device to both...
(so each program is controlling 2 devices)

Now both programs WORK!

WTF?
 

 

Edited October 30, 20231 yr by johnstonf

9 minutes ago, johnstonf said:

Hi Michel,

Thanks for giving attention to this!

I created two programs, for on and off...
they both give the message "Sorry, i couldn't reach universal devices"

Recreated with good device, they work.

Now it gets more interesting... !!!
I then ADD the failing device to both...
(so each program is controlling 2 devices)

Now both programs WORK!

WTF?
 

 

Now i pulled the good device out of each program,
The programs STILL work !
(So if the failing devices are used to START the program, they fail)

Again... WTF?

 

 

Edited October 30, 20231 yr by johnstonf

Hi John,

Based on what you are saying, I think it's signal/noise related. i.e. ISY retries 3 times during which time GH times out.

The next experiment:

1. Open Event Viewer, change the Level to 3

2. Issue the commands again 

3. What do you see in the Event Viewer?

With kind regards,
Michel

Logic Question...  before going down this rabbit-hole...

If S/N bad, why is it 100% consistent!!??

That make no sense to me!

I would think I'd be having other problems and also inconsistencies too! No!?  I'm Rock solid other than this stupidity...

Respectfully, Fred

Hi Fred,

It's not a rabbit hole. Just trying to see what the event viewer shows.

With kind regards,
Michel

Ok,

Well, here's a link to the whole thing... but I don't think it ever gets anywhere close to communicating with my ISY...

Log is also attached.

Thanks, Fred

 

ISY-Events-Log.v5.0.16__Mon 2023.10.30 06.49.45 PM.txt

@johnstonf,

Are you controlling ZW_009?

With kind regards,
Michel

Not manually, no

@johnstonf,

So, those correspond to your commands to GH?

With kind regards,
Michel