Javi

The Idle-True, Idle-False, Running-Then and Running-Else status for the IF condition is only evaluated when IF is run. Disabling a program will cause IF condition to not be evaluated unless manually triggered. So, when a Program is disabled it will show the status of the last evaluation. A work around would be to use a State or Integer Variable, State if used to trigger a program, Integer if only needed for status. Then Set the Variable as the status node, Finally add the value mappings to have human readable status values displayed on UD Mobile.

That does make more sense, maybe @bpwwer can chime in regarding this parameter. I know there are some changed in PG3 regarding status but I'm not up to date with the exact changes.

I see how it could be confusing. Maybe better words would be "running" and "stopped". If a NS does not crash, or does not stop itself, then it should remain "connected" (running) until stopped by the user.

See download link for ISY Launcher to launch the Admin Console https://wiki.universal-devices.com/index.php?title=Main_Page#Quick_Start_Guides

Exclude can be done from from any zwave controller, does not have to be the same controller which included the device.

The best option is to restore your backup If you have a one. If you do not search "excluded <lock name>" on Google and there should be a few videos/instructions.

If you search the form preferably with google ( site:forum.universal-devices.com Yale ) you will find many users with issues communicating with Yale locks. I recall a post (although I could not find it with a quick search) that stated the only way the lock would work reliably was with the ISY within a few feet. The same users stated communication would not work through a repeater, possibly due to the security level. There are other users with posts having issues similar to yours when batteries are not close to 100%. Other locks work much better, although some require the device to be very close to the ISY during initial inclusion. I assume there is an issue with this manufacturer, if locks from other manufactures function correctly at a much greater distance. I have a couple of Schlage locks about equal distance from the ISY, some 20-30 feet through 70+ year old 1.5" plaster walls and backer board. For context to the extent of signal degradation in the home, it is almost impossible to get WiFi outside of the home, 20-30 feet from the access point. One lock is hard wired to my whole home 12v system, with voltage transformer the other is using batteries. The wired unit rarely reports an unknown status, the battery unit more often especially when batteries are low, although both will report correct status on query.

The only time it should be overwritten is if the step value is not null during synchronization. So, if the value was initially empty then the value you set should remain. It is possible that a firmware update or Node Server update (Node Servers only) adds/changes this value.

Hi Dennis, I made some adjustments to the position calculation in 0.133, please try changing the step value to "1" again. If this does not work I may need to run a remote diagnostic to find the cause. Android 0.133 Added value rounding for editor range scroll position.

Have you tried what @apostolakisl suggested? To eliminate the possibility the commands are coming from a source outside of ISY or PLM, disconnect the internet ethernet cable. ISY and PLM will still function but completely remove the possibility of outside interference.

Thanks @DennisC. The precision appears to be the same if the values are incremented by a whole number even if a decimal value of zero is shown. To help me find the root cause of the app not scrolling can you verify if the AC initializes the setpoint command to the current temperature or to another number such as zero?

If not using polyglot, and you are not having any issues with the app, then the errors can be disregard as it relates to the Node Server slot 1. If you would like to remove the error I can ask you for some additional information. Correcting the error will have no changes to a system not using polyglot, and may be corrected automatically when/ if you start using polyglot in the future.

Connected Status in the picture is the connection status between the Node Server and Polyglot. States are connected, disconnected, and unmanaged. The status may show connected for a Node Server as long as the connection between Polyglot and the Node Server is not terminated. The Node Server may be able to communicate with Polyglot and show connected even when the Node Server is not "working". An example would be a Node Server is started and communicating with Polyglot but still needs credentials for the service it supports.

The first error indicates a parsing error for the National Language Support (NLS) file. What Node Server is installed in slot 1?

Yes it is either a picker or raw input. I assumed your request was for a list of values, was I mistaken? What is the Status (current temperature) decimal precision (i.e. 0.5 or 0.1 or none)? Normally the picker should automatically scroll to the current set point, so there may be another issue. This could be a few things including the Command (setpoint) is NOT hard coded to be initialized (mapped) to the Status value (current temperature), or the app could not match the current temperature in the list. The latter is likely the issue if the Status (current temperature) has a higher precision than the list of step values. If the Status (current temperature) precision matches the precision you entered into the Step editor then the issue is likely a missing initialization (mapped) in the Node Definition. I'll try to round the Status (current temperature) to the precision of Commands (setpoint) in a future update. That should allow the app to scroll to the close to the current Status (current temperature).

Due to a design flaw found during a security audit PGC was shutdown until further notice. So, any PGC Node Servers will have the last status reported to ISY until ISY is restarted.

Android 0.132 (Beta) Fixed default values for Node Def Accept Buttons. Fixed database reentry for Node Def Accepts query Accepts Param and Mapped name creation. Joined Node Def Accepts Mapped name tables into Node Def Accepts Query. Added Accepts Command Name and Parameter Name to Parameter Picker/EditText. Added increment and decrement buttons for Accepts param raw input. Fixed default values during edit of commands with multiple parameters. Added Editor Range editor. iOS 0.7.2 (Beta) Fixed Editor Range Step values for undefined Steps. Added Value request in Node Dashboard when application becomes active. @DennisC I think a found a solution to change Step from within the app, although it will need to be tested for your case. In Android 0.132 (should be live in the today) I've added an Editor-Range editing screen which allows the step value to be changed. There is still a 200 Step limit so the Step value may require a value greater than or equal to "1" if the min/max or subset values are greater than 100. To edit the param select the edit button at the top of the dialog for the raw entry.

I suspect an automation is running somewhere like @MrBill suggests. Do you or have you ever set up a geofence, IFTTT, Alexa, or Google Assistant automation?

Base on the symptoms of the values earlier in this thread I would say the Editor does not define a step value. I will ask about that in our next meeting, as I could be either the editor needs to be updated in firmware or that is just the way it is reported. The increment/decrement buttons next to the edit text box may be the best solution today. I have been thinking of adding custom editors for individual commands, this would allow users to set limits/steps/uoms/ect for an individual variable. In UD Mobile variables are implemented like any other node, so the same implementation could be used to add custom editors values for other nodes.

Thanks @DennisC, Understood regarding the error, it may have been a temporary internet issue. If it persists please open a ticket as the error shows ioP is not updating Portal with status. Entering raw values should only be for commands which have more than 200 possible values, all others should show a list. This number may need to be changed after the recent updates. If your thermostat has values 0 - 120 with a step of .5 I think it would be good to change this value to something like 250. However if the step values are not defined or defined as .1 this would be 1200 possible values, so changing to 250 will not have any impact. The app creates this list when the button/status is clicked and may have to iterate over all values for Human readable replacements. I've set the 200 limit to balance speed, and so the user does not have to scroll over hundreds or thousands of values. In the AC are the values stepped by 0.5 or 0.1 or something else? I don't think 1500 values would cause too much of a noticeable delay, but would be many values to scroll through. Looking at the AC for similar commands it looks like there is an increment and decrement button next to and edit text box. I'll try to add the same in UD Mobile for values over 200 (or wherever we land on that number).

Great, IoP was likely still trying to establish a connection if it was soon after the update. Android Version 0.131 Should now be live with the steps fixed, please let me know if it resolves the the value issues.

We recently had a similar issue with IoP (versions 5.4.0 it should be fixed in 5.4.0_2) so this error is still fresh in my mind. The error, posted below, does not affect local connections but will affect UD Mobile or AC through ISY Portal. This error is only thrown by ISY portal when there is a subscription connection issue with ISY. If a reboot does not resolve the issue please open a ticket so Michel or Benoit can take a look. For reference, the full subscription error, see <info> tag: responses: <?xml version=\"1.0\" encoding=\"UTF-8\"?><s:Envelope xmlns:s=\"http://www.w3.org/2003/05/soap-envelope\"><s:Body><UDIDefaultResponse><status>404</status><info>Error contacting sub.server: ETIMEDOUT</info></UDIDefaultResponse></s:Body></s:Envelope> or: "Server error"

The hard part is accurate voice recognition, speaker, and wake word. Google is, in my opinion, the best out of all I've tested. I built a project over 5 years ago which uses the downloaded voice models on android. So it would work on intranet without access to internet. I still use it for most of my voice actions as it is quicker than the Google Home and has chaining commands.

I believe that is a portal error, ISY portal is not connected to ISY (subserver). If this is IoP verify you are on the latest version, a previous version had issues with Portal connections.

Thanks @DennisC, I think I found the issue, Editor Range values without a defined step has step defaulted to 1. This will be changed to the minimum possible when undefined. I'll try to push an update by the end of the day.