Javi

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.

If you need an alternate method: Use a State variable for Alexa, set the on and off values, percentage is calculated automatically. Then have a program monitor the State variable and set the "on" value to the same state variable Variable Test - [ID 0084][Parent 000F] If $State_6 is not -1 Then Set 'Devices / Basement / Basement Computer Room Lights' On '$State_6 %' Else - No Actions - (To add one, press 'Action') You may want to set the variable init value to -1 to avoid the light being changed on reboot.

Hi @DennisC, The number input fix should now be live in alpha/beta builds. If I understand correctly the control previously had a scrollable list of values, then changed to a raw numerical input (edit text) after an app update. Are these assumption correct? If my assumptions are correct, what is the device type (i.e.Node Server, Z-Wave, etc.)? Does synchronization correct the issue? I ask as changes made in the last few months, beside yesterday's update, should not have changed this behavior. If this is a Node Server it is possible the range of accepted values changed. If the range of accepted values is greater than 200 the app will show raw input (edit text) instead of a scrollable list of values. The current range limit of 200 values may need to be changed to a greater number after Yesterday's update as it may cause nodes, such as thermostats, with steps of 0.5 to hit the range limit after the first 100 whole numbers.

Hi @DennisC, Thanks for the report. I'll push 0.130 as soon as 0.129 is finished with review to fix the editor input. Did the list of predefined values turn into an edit text on the latest version or a previous version? The picker should be shown if there are equal to or less than 200 pickable values, it will show the edit dialog if there are more. This value was increased from around 150 to 200 in January. However the most recent version will now count step values. If the step value is less than 1 all steps will now count toward the 200 limit. If this is not the case then I may need to look at the nodes editor file. Android 0.130 0.130 Fixed decimal and negative number input of editor range raw entry dialog. Fixed populating of existing computed value for editor range raw entry dialog.

iOS Beta 0.6.9 (live) Added alexa configuration for ISY Portal. Add/edit/view individual Alexa Spoken configuration from a Node's Dashboard by clicking the voice icon at the top. Add/edit/view all spokens from Admin Tab. Legacy Elk Module configurations (non-Node Server) is implemented but not tested. UD Mobile does not support the Legacy Elk Module so these types can only be accessed from the Admin Tab iOS Beta 0.7.0 (in review) Fixed missing Alexa AV parameter. Updated Systems Settings UI. Bug Fixes. iOS Beta 0.7.1 (submitted) Fixed Editor Range Picker creation for Step, Precision, and Decimal min/max values. Removed the raw suffix from raw UOM, sync required. Renamed variable Init command to Initial Startup Value, sync required. Android 0.128 (live) Fixed Alexa AV Type value change. Bug Fixes. Android 0.129 (in review) Fixed Editor Range Picker creation for Step, Precision, and Decimal min/max values. Removed the raw suffix from raw UOM, sync required. Renamed variable Init command to Initial Startup Value, sync required.

Hi @BamBamF16, Please first check with the node server developer to see if they can add a hint for the node(s) in question. If that is not an option you can try the "Device Hint Editor" from "Connectivity" in the "Select Tool..." drop down on ISY portal. Be sure to select the "Help" button for detailed information.

Hi @BamBamF16, What type of device? Currently the Alexa Configuration uses Hints for device types, some devices do not conform to a mapped device type. Some nodeServers that do conform may be missing a device type hint.

Thanks @brians. I've added your requests to the the issue tracker.

Hi @brians, Thanks for the feedback! My main use cases are integration with Flume for broken drip lines which go unnoticed until I see plants in distress and having remote access from ISY Portal and UD Mobile. This was my first Node Server so I'm sure there will be other issues once the watering season has started. The multiple statations issue should be reported to OpenSprinkler as that appears to be a firmware issue. I'll try to replicate and report and update the Node Server known issues so users can know they must add a delay in programs.

Hi @MrBill, I purchased a few of these after testing one a few years ago, although they do not appear to be available now. https://www.amazon.com/gp/product/B07BK65MLH/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1 If the Unit of Measurement (UOM) is changed from 1-byte to 1-byte-unsigned it should allow for 0-255. https://hpccsystems.com/training/documentation/ecl-language-reference/html/INTEGER.html%23Integer_Value_Ranges