mbking

@jjc, How do you go back to a previous version of PG3?

@garybixler, I'm seeing errors as well after updating. Actually, all node servers are showing the same string of errors. I sent that information to bpwwer to have him look at it.

RainMachine updated to 3.1.5. Thanks! Sent from my iPhone using Tapatalk

@glarsen, I updated to PG3 version 3.0.45 today, but I still can't get my RainMachine node server to update to 3.1.4. I have two other node servers that updated as expected after installing this new version of PG3.

@Michel Kohanim, I have examples of #3 as well. For me, the variable update times are only wrong when a program sets the value and it's always 6 hours behind the actual time which happens to be the same as my time zone offset. The times are correct when, for example, the init value is applied to the value at reboot.

@Javi, I was turning Wifi off while I was in the app, so I was probably seeing those disconnects. When I walked far enough away from my house to lose Wifi naturally, opening the app worked fine without error. Sorry for the false alarm. Seems to be OK now. All software is up to date. Thanks for the details. UD Mobile is a great app. I'm looking forward to some of the other updates coming.

@Javi, The firmware update seems to fix my problem of being able to connect when off of wifi, but I'm still getting error messages, I think the same ones as before. Seems odd. I'll keep testing.

@vbphil, I don't know of a sudo command to check for UEFI, but in the release notes for IoP 5.4.0, Michel said something about needing UEFI to activate TPM Security. Before I did the 6 Button press procedure, my TPM Security setting was grayed out. After the procedure, my TPM Security setting was activated. I assume that's because UEFI was installed. My left most LED was blinking after this install. The UDX 2.6 update Michel put out yesterday fixed my blinking LED. The TPM setting is under the Configuration/System tab of IoP. Hope this helps.

@Javi, I get the following error message when trying to use UD Mobile away from my WiFi. I believe this problem started after updating to IoP 5.4.0. I've applied the new UDX updates to take care of blinking lights on Polisy and I'm able to use UD Mobile without issue when connected to my WiFI. My ISY Portal account is active and seems to be OK. Any thoughts?

My Polisy, front panel, left most LED is flashing like others have reported after the update. But, operationally, everything seems to be working OK.

I updated using ssh and rebooted Polisy after the update completed. Some PG3 node servers were not reporting properly after this reboot, but started working again after a PG3 restart. No issues with UD Mobile after the update. Sent from my iPhone using Tapatalk

@MrBill, I noticed that some of the developers were staying with V2 of PyISY, so I thought I would do the same for now to limit the number of changes required. I appreciate the link you included because all the Change Log links I found online did not work. Your link has a Change Log link that spells out the specific code changes needed. That will make the change easier. I think I will install 2.1.4 and hold off on V3 for now. I'll see how it goes. Thanks again for that link. That gave me a lot more info I needed.

Several years ago when I ran Polyglot on a Raspberry Pi, I wrote a simple program to collect and send to my ISY-994I the Pi CPU temperature and the cabinet temperature where my equipment was located. I installed PyISY and took my first stab at Python programming. The PyISY version is 1.1.0, and that still works fine with my ISY-994I. However, when I change the Python code to point to my IoP, I get PyISY errors. I assume I need to upgrade PyISY to work with IoP, but what version should that be and what is the best method for doing that upgrade. I'd like to avoid rewriting the program for now until I have more time to dedicate to it. What version of PyISY should I use? Also, what is the best pip command to accomplish the upgrade. I know enough to be dangerous, so I could easily pick the wrong options. There are a lot of them and a lot of opinions out there as to which ones to use. Any insight would be appreciated. Mark P.S. I did backup my Raspberry Pi SD card just in case.

@JTsao, Your program will work fine with the Hue Emulator. Once the Hue Emulator has set your light to 10% and the ISY recognizes the change, your program will run. My issue is a timing issue. In PG2, the ISY recognized turning on or off a light using the Hue Emulator as a control action which is very fast. With PG3 and ISY on Polisy, the control action does not trigger when I turn off a light from my Harmony remote. Jimbo does not believe there's been any change in the Hue Emulator to cause that. He's surprised that it worked in PG2. It could be the ISY code or some of the PG3 base code. So for me, I have to come up with a better way to handle my logic because the status update is slower than the control trigger. Your example will work fine. I've had really good luck with the Hue Emulator and would recommend it.

@JTsao, I primarily use the Hue Emulator to turn lights on or off using my Harmony remotes. It's more convenient than pulling out the phone to do it. In my office, I use motion to turn on my desk light as I walk into the room and keep it on while I'm in the room. When I leave the room, I turn off the light using my remote and need a way for the motion sensor to be ignored while I leave. This is where the "Switched Off" action works great. The motion sensor is deactivated for about 15 seconds when it sees the desk light "switched off". Using the status is too slow. Switch Off used to work with PG2, but doesn't with PG3. Not sure what is different. It's not a big deal, just was nice to have. I don't know of any other way to use the Hue Emulator. It just emulates the Phillips Hue lights so the Harmony remote will recognize it as such even if the light is really another type of light in the ISY. I'm not aware of any other functions that are available with the node server.

@bpwwer, If I copy all the contents of the PG3 folder on Polisy to a remote machine, my Mac, before updating PG3, can I copy that folder content back to Polisy to revert back to a working copy of PG3 and my node servers assuming a new update causes issues? Recognizing this is Alpha software, it would be nice to be able to revert back easily to a working version until any issues with an update get resolved. I've moved all my node servers to PG3 except one and they are working quite well and this gives me the opportunity to participate in testing, etc.. But the update from 3.0.39 to 3.0.40 was a wake up call that this is Alpha software and updates can go wrong. All that said, kudos to getting it fixed so quickly! Mark

Yes, the 994i saw it as a Control event. I used it to disable a motion sensor for a few seconds to allow me to exit the room after turning off a light with the harmony remote. There are other ways to handle it, so I don't view this as a must have. I was just surprised it worked differently with Polisy ISY and PG3.

@Jimbo, In the PG2 version of the Hue Emulator, the Switched On/Off condition was recognized in programs when the device was switched on or off by my Harmony remotes. That's not the case in PG3 and it's a nice feature to have. I don't know if that's due to a change in the node server or some other component, but I wanted to bring it up in case it's a bug or something that can be added back. I verified that Polisy ISY does recognize the switched on/off from other devices. Mark

@Jimbo, 3.0.5 fixed the labeling issue on my end. Thanks

To update a node server in PG3, you stop and then restart the node server. I haven’t tried it yet, but that’s the process I see listed in one of the installation screens. Sent from my iPhone using Tapatalk

@Jimbo, I tried loading the Profile in the node server on PG3 and that did not correct the labeling in the Admin Console. Do you have anything else I can try? I noticed in the ISY a place to load a profile for node servers, but I'll need the actual file.

@Jimbo, That didn't work. I tried restarting the node server and rebooting Polisy ISY. No change.

@Jimbo, I installed Hue Emulator on PG3 and all seems OK except for one issue. In the Admin Console, the field and button names are not resolved to the preferred text. They say things like [NLS-10:CMD-SET_LISTEN_NAME], etc. The emulation seems to be fine and I've been able start the process of linking my Harmony remotes. I tried rebooting Polisy ISY, but that didn't fix it. Neither did restarting Polisy. I did decide to start from scratch since I was in a different slot and wasn't sure how that might impact things. Adding things back in is going smoothly.

When moving over to PG3, I will be in a different slot. Didn't think about that when I started a manual transfer to Polisy ISY and PG3. The Hue Emulation will include the same Insteon devices and scenes with the same spoken name as I have now. I have 4 hubs. Should I delete the Hue device from the remotes and start over or can I leave them as is and maybe re-pair them to the hue bridge emulator. Not sure of the mechanics involved here. If started over is the best thing, I'm good with that. Just trying to save some steps if I can.

@Jimbo, Did the latest update to PG3 (yesterday) fix the issue you reference here? I was about to move the devices that are controlled through this node server to Polisy ISY and install the node server to PG3. Glad I read this first. By the way, I have the ELK node server installed on PG3 and running on Polisy ISY. No problems at this time. I'd like to put a vote in for getting the ability to send text to the keypads. I noticed it's on your issues list to be added at some time. Mark