-
Posts
49 -
Joined
-
Last visited
Everything posted by bwade913
-
The installation instructions for the Yolink NS are brief and just say to "Enter both UAID and SecretKey under configuration". Well, I spent a lot of time trying to make this work in the Node Server Configuration window in the Admin Console, when what I really wanted was the Configuration page in Polyglot. I did look for it there too, but didn't think to scroll down past the first "Save" button. Oh well. It might be helpful for other noobs if the install were more explicit about where the configuration change is. I have the Yolink NS working now with leak sensors, motion sensors, and switches. So far everything has worked perfectly and the range has lived up to expectations.
-
Thanks to TFay for putting this together. It works great with my RX-V683. I'm going to add some information for those (like me) who haven't used Network Resources before: 1. You need to have Network Resources enabled. It's included with ISY Portal subscriptions or you can purchase it separately. 2. The zip files provided here can be imported at the admin console tab, Configuration-->Networking-->Network Resources 3. Each resulting Network Resource needs to be edited to change the IP address to the address of your Yamaha AVR. 4. Programs can be written to execute these NR commands using the Network Resource category. 5. When the OP talks about there being a lot of network resource requirements, he's not talking about it bogging down your network.
-
Thanks again Javi. It took me a while to get my head around this reading the several posts, but it is pretty simple now that I see it. The shortcut requires just two actions. 1. A URL action populated with a url which can be found in the connectivity, IFTTT/Webhooks section of ISY Portal. Just click on the icon between the red x and the event name that you have created. Copy and paste the url into the URL action. 2. A "Get contents of URL" action. Set Method to POST. Set Request Body to JSON. I still think a direct interface to UD Mobile in Shortcuts (like other apps have) would make this sort of thing much more user friendly.
-
Thanks Javi. I did see that and will take a look. But it's another case of using a third app in the middle, so it's not clear it would be an improvement over my current Roomie Remote solution. I have very little experience with IFTTT, but I remember it having very slow response when I tried it a few years ago. The thing about having UD Mobile support in Shortcuts is that you could configure a new voice command in seconds.
-
Sorry if this has been covered before, but I wasn't able to find any previous mention. Are there any plans for UD Mobile to provide an interface to Siri Shortcuts as other apps have done? For example, I can create a shortcut "Start Coffee" to run a Roomie Remote activity "Start Coffee", that in turn sends a command to my ISY to turn on my coffee machine. It would be nice if I could cut out the middle man and send a command to UD Remote to turn on a device/scene. It would save me the trouble of creating the RR activity. and likely run faster. I've been migrating away from Alexa to Siri for voice activation, because Siri shortcuts are very easy to configure and modify, and they can be run by talking to my Apple watch. Shortcuts are also supported on M1 macs, so there's that as well.
-
I got a quick response from Michel and was advised to use a new micro SD card, and that did solve my problem. I was able to install v5.3.4 and restore my configuration from a backup.
-
Yes, FW/UI are both v5.3.2. Thanks, I'll open a ticket.
-
Thanks Geddy. The boot sequence looks normal. No error light, and the transmit, receive and memory lights flicker as usual until the boot is complete. Do you know of anyway to edit a file on the ISY? I feel like if I can get that file to exist again, I'll be back in business. If not, I'll go ahead and open the ticket.
-
I've just recovered from a networking issue that had the ISY portal down, and prevented me from using https in general. I resolved that and the system is working quite well now, except I am unable to create a backup. It's failing with: Could not retrieve file /CONF/DISCLAIM.UDI Error log: Wed 2023/01/11 01:41:34 PM System -170001 [UDSockets] RSub:42 error:6 I'm able to telnet into the ISY and the LS command shows /CONF/DISCLAIM.UDI to be a zero size file, the only zero size file in that directory. Is there a way to touch that file to resurrect it? A forum search shows that someone else encountered a problem with this file and there was talk of the micro SD card being bad. I don't have any other indication of file system problems. I have an ISY 994i running version 5.3.2. The networking problem I had cleared up when I changed the reserved IP address for the ISY on a Google mesh network. There's no indication that any other device was using that IP address, but the change in IP address definitely cleared my problem. TIA for any help.
-
I'm timing from the triggering event, not the push notification which is also delayed in my case. The limitation I found is described like this, 'The Nest Polyglot polls the Nest API every 30 seconds due to Nest anti-flooding mechanisms that temporarily disable queries to the API. So if anything is updated outside of ISY it could take up to 30 seconds to be reflected in the ISY interface." https://github.com/Einstein42/nest-polyglot
-
Just following up on this in case anyone is looking for the same solution. I have the Nest2 node server running on a Raspberry pi and it works but isn't much faster than the Stringify solution. During the install I came across some documentation (I forget where) that said there can be up to a 30 sec delay due to a Nest limitation and that's pretty much what I'm seeing. Still happy to find out about Polyglot and get it running. I use Simple control and Sonos too and am installing their node servers.
-
I found the documentation and see that I can run it on my OSX machine. I'll give it a try. I'm a recently retired applications engineer looking for a hobby.
-
I did not as I wasn't aware of Polyglot. I'll look into it. What sort of response time might I see with my Nest-->ISY application?
-
Thanks for the tip on Stringify. I was looking for something for something with less latency than IFTTT and this is pretty good. My responses have mostly been under 20 sec with the longest at about 40 sec. I am using Nest camera events to turn on outdoor lights and the five minute turnaround from IFTTT wasn't cutting it. It took a while to get my head around the Stringify app but it's pretty straightforward once you get there. BTW, another advantage is that Stringify supports Nest's "camera saw someone" feature whereas IFTTT only supports motion detection.