sjenkins

By setting config parameter to 0 - no scenes or 1 - use scenes you can then get the scene button parameters to work. Mine look like this in the device. Use the scene button to trigger the scene or program.

Not exactly what you are asking but I use folders to do something with similar functionality.

thanks to @Chris Jahn & @btreinders ! Chris you are right the first statement was the winner. 1. ssh into eisy 2. sudo mv /var/isy/FILES/CONF/ENABLED.D2D ~ 3. reboot now 4. through admin search for and disable the appropriate programs 5. reboot from admin. 6. sigh with relief Thanks to all !!

Yes still crashing on 1.1.22 within seconds of moving to iPhone app screen or another app.

it may not be known but this issue is NOT resolved. I have done multiple updates and reboots. The very odd thing is that it is not happening on every reboot but at least 50% I do not reboot often but have been having some issues ota updating a particular zooz switch (one works the other won't update with a socket error; different issue or related??.) Am I alone in this or are others experiencing the disabled program issue on reboot?

Getting that often too. I get the message when on the iPhone I switch to another app or the Home Screen. Swipe up or over. I have been hitting the report to developer option most times but haven’t been putting in my email most times. Quick query: does that help you a lot ?

First time in my 10yrs I lost all my init values on a reboot. Any other reports of this? Very inconvenient when you lose your ALWAYS_ON variable! ****Update - must have lost an init file as back-up failed part way through at var init. As soon as I edited the init values I was able to do a back-up. Again first time corruption of a file on EISY (only had it once on my 994 when the memory card failed)

Since the last 3x update I have also been getting just my YoLink server failing then restarting a number of times per day. Does not seem to be internet though as I also have a monitor on that. Anyone else?

Interesting as yours have a few minutes between the offline & online. Mine (which only happen on my 994, not POLISY or EISY), go offline then online in the same minute. The time delay should solve mine but yours have significant time between and even a number of offlines in a row.

So I have an eisy, polis, & a 994. Over the last two days have gotten about 10 off/on notices but only from the 994. Just letting you know if it helps for debugging. Might need a longer timeout.

Just want to echo both points made by @Bumbershoot& @MrBill. I rely on my automation & am away regularly. I also do think this small company would do well to focus on up to date systems (free) with paid options for older (revenue). It actually may speed up the path to stabilization which is a main reason I am with UD for 12yrs. Not my choice to make for them but we get to voice an opinion. Also, none of this is to be critical to anything UD is doing, just encouragement.

@Javi Thank you so much for the clarifications and of course the great work on the app. I do think a node server will not be necessary as you can make a status variable which collates the individual family members statuses. I have repurposed my notifications arriving/leaving from the Occupancy and made status state variables for each family member with associated programs. Mind numbing programming but not difficult. I do have one bug report. Which kept happening & now I cannot replicate so ignore until someone else comes up with it too. When I started adding my first geofence & changed the name, enabled it & saved a command ; this ended up with 4 geofences with names(1,2,3,4). Again now that I am established I cannot seem to replicate so just keep it in mind if another sees it. thanks again, you are really developing an all inclusive app.

Have 1.0.22 IOS w/ Geofencing. Started playing with it, read the wiki, and just want to make a few statements I think are true, might save you multiple questions later. Just to be clear, @Javi can you verify? This is a parallel system to the Occupancy Node server the Portal provides. The Idea being that it would replace it (not augment it) Saying above the Geofences in Occupancy are NOT meant to sync to UD Mobile. We could delete Occupancy and the Node that comes with it, as well as stop using the additional app, Locative in my case. With the command we would need to simulate the status node (if we want that, or could just do direct commands as I see) as no 'status' node is going to be recreated. This looks like a great idea and initiative (you don't need to verify this.

I think I calculate 9hrs until you succumbed & updated. I can relate

As others here I required an extra reboot on both my Polisy & Eisy to make PG3 come up. Did not need to ssh & run update script. most node servers started in their own which is great except backup/restore and openweather . They both required a restart to get going. I’ll try to remember to cross post there nothing new on zwave devices so far.

Sorry Dennis, didn’t read up the screen. I actually had the same issue with YoLink as you & worked with Bob on it day before last. I was describing the other NS issue which resolved the way I described.

I had this not being able to write with a few of mine. One resolved after “a while” the others might have but I did sync with man’s without replace they made it through the gauntlet. Interesting is the one which resolved itself also completed interview. I actually went backwards in this update for my “completed interview” score but all my z-wave are working pretty fast. Just not all features yet. Thanks @Chris Jahnkeep slogging, bit by bit we are getting there!

Have you tried stopping & restarting the node server. There is a bug currently they are working on where the node server shows running but is not. Happens for me in a number of servers usually indicated in the admin where the server node does not indicate running.

I have the power failure alarm device if you are looking for another tester.

I appreciate that UD is giving us one more knob to tryout as we all figure these devices out.

I will PM you my main pg3x log @bpwwer also asked for it right after a pg3x reboot. Also, I checked in the EISY folder log files and they end at the point of upgrade. Nothing after.

No log available ; I understand not the same thing. Last log file for the NS ends at point of upgrade.

No log available for the YoLink on its own. PM'ing you a copy of my general log. At the bottom will be a restart of the YoLink server.

Sorry I didn’t state that. Yes a few complete power downs and pg3x restart along with the ns cycling. only this ns; all others, about 10, came back and even started up with eisy boot post update. enjoy your w/e we will survive just fine.

It actually sets a delay between commands as opposed to truly speed. The release notes say it may be useful for older devices or those struggling to be interviewed properly. I am thinking of trying it on a device or two which are not completing interview. I would likely try to move it back to default after that though as all my devices are talking ok outside of interview.