Javi

It's been a while for Amazon App Store updates. Updated version 0.110. https://www.amazon.com/Universal-Devices-UD-Mobile/dp/B08SKT5NM8/ref=sr_1_8?keywords=Universal+Devices&qid=1637251777&s=mobile-apps&sr=1-8

Android Alpha 0.110 (Closed Testing) Added not null Status Mappings. Fixed existing Status Mappings not showing mapped values. Node Dashboard now honors Status Mappings. Updated wiki with Not Null mapping values.

Hi @FuegoMCS, I recommend upgrading firmware first. Please backup before starting the process and take notes of password reset and program adjustments.

Standard Hex Codes. I would like to offer a predefined set for the globals, but it is lower on the priority list. I noticed I forgot to remove Global test color values for Null and Zero for existing database upgrades, but this will be removed in the next update, only alpha testers affected. The same color code appearance varies too much on Android depending on screen type for light and dark modes so, as before, I ultimately decided to not set default values. I'll try to add "Not null and not equal to" comparison in the next update, probably as the lowest comparison priority so greater/less than values can be caught first. I was hesitant to add this in the beginning as I anticipated too many support issues as not equal could catch multiple unrelated states. I'll have to think about this one, currently there is no value in the NLS for color. This would require additional work during synchronization to insert new and preserve existing user defined values. I'll try to add mappings for existing values in the next update. A few other issues which should be fixed soon: Lock error on back top bar back button press shows lock. Node Dashboard does not reflect color.

Adding a color picker is on the list, I'll also try to add a saved colors table at some point to avoid the copy/paste for user defined hex codes. Adding 'not equal to' should not be an issue. Comparisons were limited to prevent user created loops and complex logic which could dramatically reduce the speed of the already complex home/favorites queries. Do you think "not equal to" should include NULL values?

Android Alpha 0.109 (Closed Testing) Note: Sync will be required to change mapped Icons/values for folders and Scenes. Added Customizations and Edit Locks. Colors can be changed based on Status values at the Global, Individual and Favorites level. Status mappings available at the individual level. App can now lock all Top menu edit, Admin Tab and Settings Tab access. Customizations: https://wiki.universal-devices.com/index.php?title=UD_Mobile#Customizations.28Currently_Android_Only.29 Edit Locks: https://wiki.universal-devices.com/index.php?title=UD_Mobile#Edit_Locks_.28Currently_Android_Only.29

Android Alpha 0.107 (Closed Testing) Note: Favorites shortcuts will have to be recreated as the old shortcuts will be unavailable. This was needed to prevent subscription from closing if it was not closed with the new subscription enhancements. ISY Subscription improvements. Subscriptions will now remain active during app pauses and screen rotations for up to one minute (default). Subscription duration can be changed in Advanced settings. Added Dynamic Shortcuts to prevent subscription close with Static Shortcuts. Removed Static Shortcuts and Widget please use Dynamic Shortcuts going forward. Created user preferences table. Rebuilt Systems Activity and Network Picker screens. Systems Activity will now use newer fragment pickers. Improved onboarding in Systems Activity. Please give feedback on Subscription duration if you think the default of one minute should be changed. Set to -1 to not close the subscription until device low memory warning.

Hi @GJ Software Products, The numbers you are seeing are unique address numbers which will not change. Most users rename the node after creation, you can prefix the name with a new number if your goal is to have a sorted list of nodes.

@tazman, You could try hard coding the webSocketUrl in housepanel.js. change line 495 from: wsSocket = new WebSocket(webSocketUrl); to: wsSocket = new WebSocket("192.168.0.24:8080"); This is right below the console message: console.log("Creating webSocket for: ", webSocketUrl); which is showing the incorrect port. If it works you will have a reproducible fix if someone wants to correct the error.

Some file managers do not allow install or require a setting to allow install of non store apks. But based on your screen grab I do not think it is an issue with Polisy. This was just to verify that the Polisy's websocket is working. Looking at Console it looks as if HP is injecting an incorrect port as both 1380 and 3080 are listed and it does not match the HP log of 8080. I searched his source and found both hard-coded and default 3080 port values but am unsure how HP is pulling 1380 although it may just be misrepresented in the log.

Added java source, apk build, and installation instructions for Sample Dev App to GitHub. https://github.com/UniversalDevicesInc/UDWebSocketExample-Android

@tazman, Below the lines quoted above are console.log error messages. Can you open the the Chrome dev tools (google console.log) to see if an error is presented. Basically this is opening dev tools, clicking Console tab, then reload. For process of elimination we have an Android dev app for Websocket logs, if you have an Android device it will log output for a WS connection, this will eliminate server side issue.

Does HP have PORT field? I took a quick look at the source (hpserver.js lines 8119 and 8399) and it does not appear the PORT is injected. ISY uses port 80 Polisy uses 8080 for local connections. If there is not a port field try adding the IP address with the port i.e. 192.168.1.20:8080 where "192.168.1.20" is the IP of Polisy and ":8080" is the port. If that does not work you may be able to hard code this somewhere below. hpserver.js Line starting 8119 // if user provides hub access info, use it // for ISY hubs we know the endpoint as /rest so use it if ( body.hubType==="ISY" ) { body.userAccess = body.clientId + ":" + body.clientSecret; body.userEndpt = hub["hubHost"] + "/rest"; hub["userAccess"] = body.userAccess; hub["userEndpt"] = body.userEndpt; } hpserver.js Line staring 8399 var hubhost = hub["hubEndpt"]; if ( hubhost.startsWith("https://") ) { wshost = "wss://" + hubhost.substr(8); } else if ( hubhost.startsWith("http://") ) { wshost = "ws://" + hubhost.substr(7); } } // set up socket for ISY hub if one is there if ( wshost ) { var wsclient = new webSocketClient(); var buff = Buffer.from(hub["hubAccess"]); var base64 = buff.toString('base64'); var origin = "com.universal-devices.websockets.isy"; var header = {"Authorization": "Basic " + base64, "Sec-WebSocket-Protocol": "ISYSUB", "Sec-WebSocket-Version": "13", "Origin": "com.universal-devices.websockets.isy"}; wshost = wshost + "/subscribe";

Hi @tazman, The Polisy does accept both old and new SOAP bodies. The client code for the UD Mobile apps is still using the original SOAP requests and is working. I ran a test with web sockets (ws://192.168.1.160:8080/rest/subscribe) and it works on both ISY and Polisy. Is the port missing? If your running on the same box it may need localhost.

It is a little confusing as only the prefixed abbreviation is different. "UDI Mobile" a 3rd party Android app for Geofencing. This is the reference in the Occupancy V2 instructions. "UD Mobile" In house Android and iOS app for Control and Configuration of ISY which currently does not have geofence implemented.

iOS Beta (Open Testing) 0.5.4 Added Polyglot Cloud functions including Delete, Start, Stop, and Set Parameters. Added Polyglot Cloud Store for PGC Add function. https://wiki.universal-devices.com/index.php?title=UD_Mobile#Polyglot_Cloud

Prior to about a month ago it only took a few hours for beta builds, however the last few versions have taken almost 48 hrs.

Hi @DaveStLou, The app was ignoring the optional selections of parameters for command with multiple parameters, we also fixed a few issues which should make this less confusing in the Command Parameters Dialog. Android 0.102: Fixed optional parameter commands for commands with multiple optional parameters. Accepts Parameter value is now reset after UOM Selection for Accepts Parameters with multiple UOMs. Removed CANCEL button from Command Parameters dialog.

Hi @DaveStLou, This is the first time I have seen a command with that many options and it does look confusing given that there is only one option for the On parameter with the "index" UOM. This is the intended behavior for ACCEPTS-CMDs which are not OPTIONAL and have multiple CMD-PARAMs. Please send me an email with a copy of the backup and I'll see if this should be an OPTIONAL (menu to the right of button) selection not honored by the app (i.e. "On" should be a command by itself with the option of selecting the exact parameters). Also to avoid confusion I think the button "UPDATE" on the first screen should be changed to "SEND" and the button "CANCEL" should be removed as there is a back button (I think this is how it was done on iOS) Some additional information if you want to geek out. I'll add this to our wiki soon for documentation. Brief definitions: ACCEPTS-CMD: A command the device accepts (such as on) CMD-PARAM: A parameter which adds a value to the ACCEPTS-CMD (such as "on" percentage). There may be multiple parameters for a command (i.e. Z-Wave Set-Configuration has both the number and value). Each of these parameters needs a VALUE. Default VALUE can be defined to matched to a current status (such as current "on" percentage VALUE), if VALUE can not be matched the app uses the lowest possible value. VALUE: A numerical value for the CMD-PARAM (i.e "on" percentage value). Sometimes this is mapped and shows human readable values (i.e. "off" for zero). UOM: Unit of measurement. Some examples include percentage/binary/index. Note UOM "index" is usually predefined values such as a thermostat mode (heat/cool/off). Some devices accept multiple UOMs for a CMD-PARAM such as percentage (0-100) and byte (0-255). Multiple UOM is usually just a calculation difference, i.e. UOM percent set to "50" and byte (0-255) set to 128 will both produce the same outcome. Changing the UOM will affect the accepted VALUEs OPTIONAL: The ACCEPTS-CMD can be sent by itself (such as "on") or with CMD-PARAM(s) (such as "on" to percentage. Not all ACCEPTS-CMD have OPTIONAL CMD-PARAMS. The app will show Commands which have an OPTIONAL as a button and a menu next to the button. In the image above: The title "On" at the top is the ACCEPTS-CMD Blue highlighted is the CMD-PARAM Green highlighted is the VALUE of the CMD-PARAM Red highlighted is the UOM. For most devices this is not selectable as there is only one defined UOM.

Thanks. PM sent.

Hi @CalPolyME, Thanks. Does issue persist after synchronization?

Hi @CalPolyME, This class was rebuilt 0.98 and has issues in beta builds 0.98-0.100, so it could be related. This was done fix dropped queries for large/multiple systems and prepare for enhancements. 0.101 was pushed to beta yesterday and is still awaiting Google's review, but should be live soon. Please let us know if the issue persist after update.

Hi @SteveT, It was a design change. Allowing users to specify the number of columns for each favorites folder is on our list.

Hi @CalPolyME, Currently not possible. Disable of Admin/Settings/Edits is on our list.

Hi @Envirogreen, As mentioned above the app will work with both of these item as Node Servers. Alternatively you could add programs/variables/network-Resources using the apps Favorite Command Type to control these devices. See command type instructions and example here: https://wiki.universal-devices.com/index.php?title=UD_Mobile#Favorite_Custom_Toggle