johnnyt

I'd like several of my 'Favorite' tiles (or whatever they're called) to show a second sub-node (or whatever they're called) instead of the primary one. For example I have smart switches that show, in this order, Total Energy, Current Power, Current Voltage, and Current Current. I added the tile to my favorites and it shows the first number (Total Energy) but I want "Current Power" to show. See screenshot below. Of course, I'm referring to the favorites screen (back from this one.) This actually wasn't a problem when I was using 994i. Only after I moved to IoP 5.6.0. Sorry if this is explained somewhere already. I looked around, including wiki, and didn't find it.

Thanks. Found the setting you're talking about inside the "Wake Up" node, which I had buried in a "Not Used" folder along with all but the nodes I use in my programs. Hopefully this fixes two issues I'm having. I have one of the two sensors that works for a short period but then shows the green arrow indicating need to update (and "Write Change" doesn't work). I was able to write changes this morning but I'll have to wait and see if the fix is permanent. I also have not been able to "Update Neighbors" when I move the sensor back from the "bench" to it's ultimate destination,. In part, I think, because I had to run between where my AC is running and that ultimate destination.

I upgraded the device firmware to ver 1.30 and they now work. I was at original v1.10. It looks like in the new world order I need to start command to queue it up, then wake the sensor up, the command is sent and the device is immediately put back to sleep. On 994i I had at least 30 secs of awake time to do a couple of things. It appears though I can queue several commands and they are all sent. No good for when I need to view multiple parameters - have to press wake up for each one, which is a bit of pain. These are my only battery zwave devices - is this behavior for all zwave battery devices? Is there a way to change this in IoX to delay the return to sleep? (looked but didn't see one). There's no setting in ZSE44 but I don't think it's the one putting itself back to sleep.

oh yes, that makes sense. Now I need to figure out if I have to migrate to PG3x on Polisy in order to be able to restore one of those backups on an eisy. I was holding off on that because I think there are still some growing pains with PG3x on Polisy and no new features I need yet... unless recovering a dead Polisy on an eisy is one of those features that is...

but that was there all along, even when there was a "Migrate to ZMatter Z-Wave" button and a clear distinction made that a migration backup was different than a regular backup. Hopefully it's all in one backup now and the wiki page hasn't been updated yet. I'd rather not have to do two backups every time. I just haven't read or seen anything about that.

If my Polisy was to suffer a catastrophic failure I'd like to be able to recover using an eisy. I was looking up the migration steps at https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Preparing_for_Migration_from_Eisy_/_Polisy and don't see where the "Migrate to ZMatter Z-Wave" option is in my AC today. I do remember seeing that option in the past (before I migrated off my 994i to IoP). Did it go away in 5.6.0? There's a warning further down that "A migration backup is different than a regular backup" Here's what I see when I go to the Configuration tab: Does this mean one would only need to restore a regular backup, even with a different Zmatter dongle?

I migrated 994i to IoP (IoX 5.6.0) this past weekend and my two Zooz ZSE44 temperature/humidity sensors won't wake up long enough for me to do anything with them. The are put (or put themselves) back to sleep a microsecond after being awakened. Mon 05/01/2023 05:14:45 PM : [ZY104_199 ] ST 100 (uom=51 prec=0) Mon 05/01/2023 05:14:45 PM : [ZY104_199 ] DON 100 (uom=78 prec=0) Mon 05/01/2023 05:14:45 PM : [ZY104_199 ] ST 0 (uom=51 prec=0) Mon 05/01/2023 05:14:45 PM : [ZY104_199 ] DOF 0 (uom=78 prec=0) They're stuck waiting to write updates. I've tried multiple times to right-click and "Write Changes" to no avail. Multiple Interview attempts also fail, as do "Update Neighbors". I can't view or change any parameters either, of course. Each time clicking the button 4 times to wake it up, of course, and seeing the LED flash but immediately stop flashing. When I used these with 994i the flashing would keep going while it was awake. I was able to exclude / include them and did that several times for each one in case something about the process was flaky but there were no noticeable hiccups or differences. I've tried with "all" and with "no" security. Same result. It does seem to add all the nodes but then something happens and they stop listening and won't let anything wake them up. Anyone see this?

yes that worked. in addition to deleting the *udi* files in temp folder per the wiki, I also cleared Java cache for what that's worth. udi_launcher.state wouldn't delete until I restarted machine. It was allegedly 'in use' even though IoX Finder wasn't running.

I migrated to IoP 4 days ago after upgrading Java and ever since IoX Finder does not remember the IoP link I added. I've added it many times and it's not working. Strangely it does remember 994i link, which is now offline. Both my 994i and Polisy are on their own VLAN subnet so I always need to add the IoX IP address but it's always remembered them until now. This morning I tried the launcher on a PC that is still at previous Java version and it remembered my IoP (and 994i), so I think there's something about the latest Java version that's at least part of the problem. @SHM you may want to check the Java version on the different machines you're using to see if that's the problem in your case too. It's strange that it remembers the now missing 994i but not IoP. The latter was on the list before I migrated to it. Since I did "Upgrade Package" to 5.6.0 from 5.5.9 before migrating, it could also be 5.6.0 related - or combination of the two.

I do have the zmatter board in it and it's been there for a couple of months, although it and CPU were mostly idling until I migrated to IoP a couple of days ago. Before that it was only running 4 node servers. I went through my e-junk drawer and found a 2.5A PS with same polarity (+ on the inside) so I'm using that now.

Mine is one of the first ones made, which came with a 1A power supply

Interesting. Although I've been using Polisy (one of the first ones out) for PG3 for a while now without problem, I just moved to IoP 2 days ago and had a spontaneous reboot last night. Of course it could be unrelated but maybe adding the zmatter board and the new processing demands of IoP is taxing the PS. Does anyone know what size the connector into Polis is?

good point. I wanted UD mobile to make things available remotely so never went there. Thanks.

Interesting. I just used the default inclusion on 994i. I think it was S0. I didn't/don't really feel I personally need high security, and question why it should it be needed. It usually adds processing overhead as the trade off and, other than for maybe door locks, which I don't have, I don't see including things with high security as a requirement. None of my neighbors have or care about taking over my lights or HVAC, which is what I use the ZEN17s for. (If I'm missing something on this front, let me know.) I know you're just saying what worked in the end but I'm just saying that it's an issue if the fix is what level of security I used when I included it... I did upgrade firmware to 1.20 before adding to 994i so that's not the issue.

@joembz and @ISY4Me, I just migrated from 994i to IoP 5.6.0 - starting the process that it is late 2 days ago. One of the issues I'm seeing is that, although all my ZEN17 nodes were there on 994i, I lost both sensors and can't seem to get them back using methods other than excluding and reincluding them at this point. I'm saving that as the last resort. Aside from the pain of firing up a laptop to bring my AC close to each device it will break multiple programs that will need to be fixed afterwards. So far UD support suggested power cycling the ZEN17 (after checking that the parameters were ok - they were) but that didn't fix the problem. I've done lots of "Update with Interview", "Update Neighbors", and "Heal Network", as well as querying other device nodes in case that would help but no joy. UD Smart add would certainly make getting close the three ZEN17s I have in use however my portal license didn't move over to IoP despite my following the instructions, so I can't use UD mobile until that gets fixed. I presume UD smart add implies exclude/include process but please correct me if it can do some magic without that. I haven't used UD Mobile for anything but the occasional viewing of some device states, and in an attempt to set up an eisy, which didn't work at all (probably because I have my untrusted IoT devices - where UD mobile runs - are on a separate VLAN/subnet as my HA (ISY) stuff, with both separate from my trusted devices) FWIW, my parameters 2/3 are 10 (dry contact), and params 10/11 are at 0 to decouple sensors and relays. More to come on this.

Am hoping to move from 994i to IoP this weekend. I don't believe any of my zwave devices linked with any security (or should I say they are linked with S0 if I understand correctly). What happens during migration? I'm guessing I end up with all/only S0 security on all my devices and that I would need to exclude/include every device (and fix every programs that points to it) if I wanted to link them with more than S0 security. It's in that context that I ask how important is Zwave security?. I don't have any close neighbors with any zwave devices, assuming that would be part of the calculation. any info would be appreciated.

Consider trying this (at your own risk, of course): Take two backups. With one of the backups, open it using 7z and look for file "NTCLIST.CFG " in the MAIL subfolder. If it's there, delete it and restore that modified backup to see if it fixes the problem. If it causes problems rather than fix them, you will have the other untouched backup to restore. I recently saw my backup shrink without justification and, worried about my upcoming migration to IoP, I looked for file differences between the smaller and last larger backups. I found the smaller one did not have "NTCLIST.CFG ", which was a comparatively large xml file full of my custom notifications. Despite it not being there, all my custom notifications were still there, and a restore of the file on a blank (test) eisy (minus NODES and SCENES because I did not want it to take over my devices) showed the notifications where still there. I asked UDI support about this and they told me the file is "a cached version of some of the information stored in the custom notifications. It may disappear at times but can always be recreated when needed". They may not suggest doing something that requires you to mess with the backup so maybe that's why they didn't offer you a fix. Or maybe it's completely unrelated, but, if it goes as it did for me, you at least won't be any worse off. And if you are worse off, you have the untouched backup to restore. Be warned that ISY backups don't save web server files if you use the built web server for logging as I do. (If you don't know what I'm talking about, it won't be a problem) Hope this helps.

@dwengrovitz Was this fixed in 5.6.0? I don't see it mentioned explicitly in the release notes but was it maybe included under "Minor bug fixes"?

Is there a way - in PG3 - to migrate the node servers I have linked to my 994i to IoP, or do I have to reinstall each one again and configure them from scratch (what I ended up doing in the past during some testing)? Both are using the same PG3 3.1.20 instance on the same Polisy, and both have an active portal license. If this is done automagically during migration from 994i to IoP, that's what I'm really looking for right now. Even if this is the case, knowing how to do this outside the context of a h/w migration would be good to know as I will eventually want to also use some of the NS on IoP on an eisy. Not having to re-install/reconfigure them one at a time would be a time saver. (Any required NS license purchases for new h/w would be done, of course.) Apologies if this is posted somewhere. I looked but didn't find the info.

Thanks for the helpful info @bpwwer. It appears to me that there are more problems (growing pains) with eisy and PG3x than with Polisy and PG3 - at least from the posts I've read. Given PG3x will run on Polisy, this reinforces my thinking to migrate my 994i to Polisy rather than to eisy. For sure I will eventually use eisy and PG3x, but because I have a large system (I won't repeat details here), it's highly valuable to me to be able to reduce the "surface area" for problems and extra work before I migrate. If I can punt something down the road without losing much, count me in.

Thanks for the helpful answer, @Geddy So it's certainly less critical to know what's in PG3x so if there's no one or nothing that can list what's new in PG3x I guess I'll just wait and find out 1-2 features at a time.

Saying that PG3 is deprecated does not answer whether PG3x can be run on Polisy. PG2 is deprecated on Polisy and that didn't prevent PG3 from running on it.

Is Polisy going to be able to move to PG3x?

Hi, Can someone provide (or point me to) a list of the major features and benefits (current and planned) of PG3x compared to PG3? The eisy user guide only tells you how to install it, and the announcement/release notes for PG3x only mention the following: make node servers (and PG3x) more secure Add setClientState API framework to support remote access to PG3x And I don't know if #2 is new or just catching up to PG3. The rest look like fixes or minor enhancements to me. I'm trying to decide if I migrate 994i to Polisy or eisy, and it's my understanding that Polisy will be stuck at PG3. Because I have a Polisy, I'd like to make use of it and if there's nothing I need in PG3x over the next 1-2 yrs I would be fine to stick with PG3. If my understanding is wrong and PG3x will be coming to Polisy, great. I'd still like to know what PG3x will offer over PG3. Any info would be appreciated.

starting yesterday I've been receiving a flood of UD Mobile notifications about ISY going offline and online. I think it's because my ISY is overloaded and can't respond fast enough. Hopefully when I migrate off 994 that will help but I would like to suggest a longer delay in being notified that ISY is offline. Also, I tried to turn off notifications in app but it kept turning itself back on. I had to disable notifications in iPhone settings.