MrBill

in case you don't have this: https://www.universal-devices.com/my-tickets/

press the "play" button to be able to set a scene on percentage. Be-aware this acts weird for complex scenes, however is useful for the typical "3-way switch" type of scene.

will never trigger Program Test1 to run at all. the only way the THEN and ELSE in that program will every run is if they are run by another program or manually run.

A state variable, not integer variable, must be used in this case.

Cloud gets the admin console (admin.jnlp) from a UD server (AWS). LAN downloads the file from the ISY itself. With a 994 the cloud option is faster because JAVA requires downloaded apps to be downloaded encrypted from an https source. The 994 can do that but it has a slow processor that might be kinda busy anyway so it takes longer than a modern web server to encrypt the file for transport, therefor the cloud option is faster for a 994. With the speed of eisy (or even polisy) there likely is no longer much difference in speed.

Other Insteon traffic is your issue. If other traffic happens during the link count the count will be inaccurate. known issue. "Other traffic" of course includes turning a device or scene on or off... but also can includes motion from Insteon motion sensors or any Insteon wireless traffic including heart beats and low battery. do link counts when no one else is home, stop programs using an false folder condition on the root folder, if you have motions avoid triggering them or cover them. there still could be heartbeat traffic from a battery device during the link count... if there is the count will be wrong. For this reason do more than one link count. the gist of the issue when doing a link count it is running down a list from top to bottom.... other traffic will make the process continue from the other traffic's position in the list of links.. in other words the pointer can jump forward in the list or back.

You may want to ask support, it could be a known or unknown bug. https://www.universal-devices.com/my-tickets/

The Home Assistant integration leaves a lot to be desired. (A Home Assistant "integration" is essentially like a node server but all the terminology is different.) That library seems to have a lot more functionally than the Home Assistant integration is making use of. The same guy developed both the library and the HA integration that I'm using, I'm surprised there is not more functionality in the integration. Hope it works out!

Not an expert, but I've had old devices and scene's get left behind in the Alexa App before. Phantom devices seem to get in the way. I would try deleting all Devices and Scenes using the Alexa app then tell here to "discover devices" again.

The PLM needs to be powered on before IoX starts. The PLM address is only read during startup. Shutdown Polisy and then make sure the PLM is powered up and ready to communicate before booting up Polisy.

I've recently started using NFC tags... they are wonderful. Not sure if you're in the Android or iOS camp, I use iOS. Using iOS you would need to use the Shortcuts app to create an automation for NFC tag, the action in the NFC tag needs to use IoX's REST API to do something... (such send the node a command). I'm currently using NFC tags with HA instead of ISY, I once knew now to build a REST call for the ISY in the iOS shortcuts app so i know it can be done. I don't see my notes on that anymore tho. It occurs to me the issue I had at first was with passing Basic Authentication but I ultimately figured that out. A tip I learned from a youtube video was to build the actual "action" first as a shortcut, get that working, and then set up the "automation" to just recognize the NFC chip and run the shortcut already created. Doing this makes sharing to another device easier, because the shortcut is shareable (although not as simple as it should be) and the automation is not shareable.

@Goose66 is the 3rd party Python library on github that's documented here not usable? Granted its not a local API, but sadly many are not.

tagging @Javi because this seems more like a UD mobile issue.

Addressing what @Morris Hansen was asking for: Coupled with the title of the thread "Make individual Flume values available" makes me believe he's not finding the 24 hour value. He further states: He should be able to do exactly that already.

I confess I'm not using this nodeserver, but the documentation says this is available now. https://github.com/UniversalDevicesInc-PG3/udi-poly-FlumeWater/blob/master/README.md#drivers-2

you're free to change the password, just log in via ssh and type passwd at a prompt and follow the prompt. You'll still be using the admin account tho, you can create other users also, but i'm not certain you need to unless you want to run something isolated. Probably not advisable. although things should be backward compatible you should probably let UD handle updates.

A running program also has a solid color icon. Currently running Then. Currently running Else. Not currently running, last time the Program ran it ran Then. Not currently running, last time the Program ran it ran Else. For many programs you won't actually see other than a flicker of the icon when it runs, Icons that stay solid are likely sitting in a wait. For the last two note that it means last time the program ran, which is not the same thing as the last time the If was evaluated. Other ways the program can be run include, but may not be limited to, manually running Then or Else from the admin console, or another program running Then or Else. Turn the SCENE on, not the device.

But are your if statements written with “is” and “is not”, because if your not careful you can end up with neither home or away being true.

As we've all spelled out they are a different beast, and they can cause unpredictability. I've never used them in nested form, which I assume works correctly. The problem I have is turning off programs I didn't mean to turn off, or didn't get conditions to where they should be before the folder cut off execution. It's a different level of planning because they work differently that everything else you're used to. That said, I do have a few simple instance's were folder conditions work reliably for example I have different kitchen lighting programs for day and night. One folder condition is If $sDark is 0, the other is if $sDark in not 0. In that case one folder or the other will always be true, even if $sDark somehow has a weird value like 42 (it happaned once). Had I used '$sDark is 0' or '$sDark is 1' a weird value like 42 would mean neither worked. AND that said, in OP's example folders for Guest, Owner, Home and Away I can see problems, because when switching between you have to take every condition into account. For example if A guest doesn't have any ability to control the widgit, then one must make sure the widgit is the correct mode before switching to guest mode, because if you're disabling widgit control it might stay on (or off) for the entire guest mode duration.

Correct. Unlike disabled programs tho, a false folder condition stops ALL execution, including when a program is run by another program (or manually). Another note, when a folder becomes false any program below it in the hierarchy will stop instantly, it will not finish (for short programs with no "wait" this isn't an issue).

You absolutely CAN trigger the "then" branch from the Echo device with a blank "if": https://wiki.universal-devices.com/index.php?title=ISY_Portal_Amazon_Echo_Integration_V3#Programs

Did Finder find the eisy or did you need to manually add it in the Finder window? If you needed to add it did you include a port number? 8080 for http, or 8443 for https. http://192.168.1.222:8080/desc https:/192.168.1.222:8443/desc of course your IP address will be different. ISY994 didn't need a port number, eisy does.

I figured we were reading it differently but thought i should contrast in case the PLM is indigo based.. because he may loose his links if he restores PLM in this case. May be recoverable from indigo, but i know nothing about Indigo other than it's Mac OS only..

a PLM connected to Indigo, correct? In that case the ISY wouldn't have the links table, and i don't know that it can be read from a PLM to a new controller. I think Restore Modem in that case would clear the PLM because that's writing new links to the PLM, and there are none in the ISY. @DennisC read your comments differently than I did, I'm not sure what his thought was...

The Schlage Encode Plus (BE499) has now been installed. To answer the specific question "can Homekit/Home app and Schlage Home app co-exist?" the answer is Yes. However there are some serious shortcomings, that frankly I blame more on Apple than I do Schlage. Basically, Users can be created either in (Apple) Home or Schlage Home. Users must be managed from whichever app created them, not interchangeable. Once the User/home key/guest code is created in (Apple) Home the lock can be unlocked very quickly and awesomely in using an iPhone or Apple Watch. The home app can be configured to send notifications that will show locked/unlocked status, and if by another user the notification will include that users name. Other than the notification, there appears to be no other way in (Apple) Home to see the history of the lock. (specifically for example: there is no way to see who unlocked the door or when UNLESS the push notification from the Home app is still around in iOS Notifications.) A lot of the (Apple) Home app notifications are pretty generic too, for example "Front Door was locked" "Front Door was unlocked" with no information about the source (By Contrast, the Schlage Home app notifications include words like "Locked by Thumbturn" vs "Locked by 1-touch Locking" which tells you if the person locking was inside (staying) or outside (leaving) when they locked the door. In the Schlage Home App Users can be created with code only access (no HomeKey). The Schlage users can be scheduled (Apple users and guests can not be scheduled), and there is a slide switch to turn notifications for these users on/off by user. Viewing History in the Schlage Home app shows every lock and unlock, but if an Apple device was used it simply shows "Unlocked by Apple Home Key" but not whose home key. I take this to mean that Apple won't let that detailed information be known. I've experimented with one of the Home Assistant integrations installed via HACS, the information supplied is basic, locked/unlocked state (with user name if it's a code Created via Schlage Home) and Battery state. Haven't had time to look at a few others i find at github, I'll report back if any of them turn out to be better. I had more expectation based on what's been built into the pyschlage library linked at the top of the thread. @Goose66 @hart2hart @lilyoyo1