gschoffstall

A program acts to turn on a set of lights. It has IF commands to check if a motion sensor is on, a remote switch has been pressed, or if an X10 command has been issued. I need to make the program time sensitive to make the lights come on dim within a time range, but leave the rest of the functionality alone. Can this be done within the same program? If not, how? Thanks.

@Geddy Painful as it was, the result is: There was a reboot, a delete and reinstall of the plugin, and several presses of the Hue button, in no particular order. I've learned a LOT. Thank You, Thank You, Thank You!

You've been great. Thanks for your input. I have started a ticket.

AAARRRRG. I have restarted the Admin console and nothing has changed. I deleted what I had entered. I closed the Admin console and went back to the store and reloaded the plugin over top of where it was (slot 1). I restarted the Admin console and, again, nothing had changed. Here's what reloading accomplished: Selecting Node Servers and Hue, This is what I get: Selecting Configure gets me this: And Selecting [01] to [20] gets me this: Sorry, I am so confused. Thanks for any suggestions. Nothing was added to my network display after the Hue plugin was loaded, even though it appeared to have loaded successfully - Both times it was tried. The only thing that has changed is that Hue was added to the Node Server list. And Query does nothing.

@ Geddy. thanks for bearing with me. I have one more question. I have configured the node for slot 1 (Since I have nothing else). Is there a "How to" on configuring the lights that are already found by the Hue Hub in the EISY Admin Console? In the console, I went to node servers > Configure and made Hue Network 1. To add lights as nodes, it looks like it wants the light's node address. Just where is that? When the hub finds them it doesn't share that information and I can't find it in the Philips mobil app.

@Geddy YAY!!! That was indeed the issue. I signed up for the free trial. There was never a need for me to have portal access because I always did everything locally. Does the fact that it could not see the portal mean I need to pay for portal access for this plugin to continue to work? Sigh.....

And Ping gives me the same Axios 404 error.

@Geddy I will try all the above. Just curious, I bought the EISY direct from UD. Their portal doesn't show the EISY, just the Isy994's. And my EISY doesn't show up in my devices. How do I register it so they see it. And where do I start a ticket if not their portal?

@Geddy I have tried several times to restart and clear the Java cache after an attempt at getting the plugin. It never helped, but I'll give it another whirl just for effect. Thanks.

@Geddy, here's what I get: I generally tried to get to the plugins by going to Admin Console>Node Servers>Launch Polyglot V3 (PG3). That gives me the certificate error like what you show above. Going past that with Advanced, I log in. Usually without closing the console. I then pick Plugins Store and scroll to Hue. The above screen shot is what I get when trying to actually get it loaded. I also just tried by using your direct polyglot link and closing the admin console. Same difference. You said something about registering the EISY with the portal. I did try your maneuver "Switch Portal Profile". It didn't help. Thanks.

Gentlemen, When attempting to get the plugin for Philips Hue via PG3x, first the link presents with a certificate issue. Next, after going there anyway and selecting HUE, it errors with failure message 404 and not loading. It references Github. Whats up? Is there a work around, or am I doing something wrong.......again?

OK, I got past the login and picked the Hue plugin. When attempting to load it, I got: Axios Error. Request failed with status code 404 in a big red error box.

Michel, I click the link, get to the PG3 page, attempt to log in. Poof it hates me. How do I log in? Do I create a new account? It doesn't like my UD user or forum name. Thanks.

Yes, I am figuring that out now, but it's too late. I already upgraded to EISY from my ISY994Ir because then I could use their optional additional Zigbee/Zmatter dongle to control Zigbee smart lights. Only after trying to figure out the "how to's" did I uncover the truth of compatibility... or lack thereof. I would like to make something of my investment, but it looks like the dongle will never do what the implications of advertisement alluded to. I still want to control Philips Hue lights, and if I have to do it through a Hue Hub, then so be it. But that still means an adventure with very little knowledge- EISY-wise, Zigbee-wise, programming-wise, etc. I need the "How to integrate Philips Hue to EISY for Dummies" manual. Pointed suggestions are mildly helpful, but I really need to know what I need to know to get started. I don't have Java or Python programming experience, and don't know if it's necessary. I don't know how to configure a node server, as has been suggested. Sooo, there I am. Guess I jumped in the deep end without a life jacket. But thanks for trying to help.

Thank you Michel. I appreciate it.

Gentlemen, I'm really eager to learn so I don't have to bug you guys. Here's the issue- I've been an electronic tech for 28 years, a hydraulic field service tech for another 18. I've dealt with A&B PLC's and a lot of different devices. But the ISY and EISY are all different. It's like there's this box of unknowns that runs other unknowns using various software and firmware structures that may or may not want to work with each other. I can learn code and structure, but I have to know what code and how the structure is put together. I can load programs if I know where to load them and the syntax. I'll have to look at a lot of the video files and help instructions before I can even navigate the technical jargon that is being spoken. I'm sorry to be a pain in the butt, but most of what is coming at me is at a much higher level than I can digest without the foundation that you guys already have. Thanks for all your good intentions.

Just took a peek at the link. What's a Polyglot? Code, hardware, something inside an EISY? See my point? I have to start somewhere to form a foundation. Thanks for coddling me.

I will try to digest all the information with this caviat: I have very little troubleshooting experience and no programming experience in the base languages they use. I mostly can get the ISY or EISY to communicate with the modules and controllers. But once the system is running, and I mean for years untouched, it's like learning code again. For me, and forgive me, it's like trying to translate pidgeon English to something I can work with. I can navigate the if, then, else framework when everything is working, but getting it working is a real challenge.

You need to use the hue nodeserver or network resources to connect your eisy to your hue hub I'm new, so humor me. I bought into the EISY program because they used the magic word "Zigbee" and wrongly assumed compatibility with Zigbee based Philips Hue systems. Silly me. I even jumped on the Zigbee/Zmatter add-on for that reason. Assuming I bought some Hue bulbs and a hub, and IF I were to try integrating my EISY system with them, please explain nodeserver or network resources in terms of how to connect and/or program it that my tiny mind can fathom. Is there a "how to" somewhere that I can digest to get me on my way?

Is there an easy way to integrate Hue LED lights without the need for a Hue Hub yet? If not, what's the hard way, or the work around? If I have to use a Hue Hub, how does that connect to an EISY system. I'm kind of new at this and don't want to take a wrong turn before I even start. Thanks for any help you can offer.

Seriously, there has GOT to be something wrong with my 4 key!! Yes, everyone, I have an ISY994Ir. There, it came out right. 😉

Thanks for all your kind replies. I bought the new EISY because the recovery of my ISY994Ir was in doubt - mostly because of my missteps in troubleshooting. And the fact that UD doesn't really want to deal with the older devices any longer. Then there was the attraction of Zwave. From some posts, it seems that path may be a little shaky yet. But I did get the Zwave module in case it proves better than Insteon for range. That said, I may just run the 994Ir until it really dies, keeping the firmware up to date (which may be a moot point if they decide that's the end anyway). When it does, you've given me the tools to migrate. Is there an issue with going back to the ISY99Ir if I wanted to set up the EISY to make sure the new hardware works properly? To answer apostolakisl, my 994Ir is hardwired to my router and I talk to it over wifi. I bought the IR version, but never used the IR. Thanks for asking.

I just got my new EISY and I just recovered, thanks guys, operation on my ISY99Ir. I wanted to move slowly in swinging over to the EISY. Is that even possible, or do I have to rip the bandaid off and start over? I have a good ISY994Ir backup, but I wanted to learn more before committing fully. I did go for the Zigby/Zwave module, but as yet have no compatable hardware for it. Thanks for any suggestions.

The epilog: My thanks to everyone that came to my rescue: Techman, Geddy, IndyMike. You pushed a LOT of helpful information my way. I am ashamed that I let a little green led on the original power pack snooker me. What a rabbit hole that sent me down. Should have known better is an understatement. But I digress. With the hardware working, I restored a working file and everything seems to be working as well as it ever did. I am so grateful.Please forgive my fat fingers. There was never an ISY99Ir in the mix, always an ISY994Ir, and it's Java, not Jave. But you get the picture. Thanks everyone.

Yay!! I looked at my router, found the IP, plugged it in when finder didn't, and viola. It connected. I have no clue why all the information remains in the ISY after a "Factory Reset", but there it is, programs and scenes. Thanks guys. I really wasn't looking forward to the $300 plus investment I thought I was staring at. I am still checking things out, but it looks as though everything is intact. I may have to delete and relink some devices, but that's minor. For all the trouble, it looks like "Geddy" nailed the power supply failure right out of the gate. Thanks, Geddy.