Javi

Hi @mbking, This was a design change, it was originally implemented to help users find grouped nodes in node picker dialogs. Grouped nodes are now expanded in the same list on the Home-Tab and Node/Status pickers have been updated. In addition there has been much user feedback that the Node's Dashboard display is too text heavy and they would like things to be simplified. With that said I see how it is useful in your example. The Node Dashboard screen is very similar to the first release and will be updated soon to address some layout and Query-Speed issues at that time I'll try add the grouped nodes in some capacity. Another way to do this is to have a Favorite Folder with a Display Node with the desired grouped nodes as items in the folder, this will allow the user to select the Display Status for each child. The App's database now has a table to add custom mapped names and icons for (#1) exact values and/or (#2) null/negative/zero/positive value mappings. This has not been implemented in the UI but will be at some point in the future. When implemented it will allow status values to have user defined mapped names and icons. This feature will put highest priority on user defined exact status value matches, secondary priority on user defined null/negative/zero/positive mappings, then current mapping priority. This will be implemented at the same time as the Node Dashboard rebuild (above) as this is the most logical place for status value edits. Note there is a bug fix for expanded nodes in 0.51.

Hi @patryk.szady, I believe some of the early Polisy firmware requires manual intervention for firmware upgrade. Are you familiar with ssh? If not are you on PC or MAC? https://forum.universal-devices.com/topic/32449-polisy-has-become-musical-when-rebooting-is-this-normal/?tab=comments#elControls_312789_menu

Please send me a PM with the exact changes and we'll make the corrections. For official views of Universal Devices please submit a ticket. Unofficially our Wiki has instructions for Locative.

iOS Beta (Open Testing) 0.4.9 Added Favorite Commands. Bug fixes. Add a Favorite Command by selecting "Command" as the Favorite Type, then select add ("+") next to the command header to add a command. Commands include support for commands with multiple parameters. Favorite Command Type supports multiple commands from multiple systems. Commands can be for any node and do not have to match the optional "Display Node" Known issues include : Command List shows raw numerical values as opposed to mapped names. Default variable values with prec may be saved incorrectly if not edited (i.e. app shows current value as default, if available, "0.033" may be saved as "33"). This can be corrected by manual typing of the prec value. Display nodes with toggle incorrectly override commands.

The instructions you have followed only pertain to Android. There are 2 apps in the Android app Store UD Mobile (Built by UD) and UDI Mobile (Built by a 3rd party developer). UDI Mobile is the app which works with the V2 occupancy node server. Results may vary with occupancy and UDI Mobile as it has not been updated in many years. Using Tasker is probably a better option on Android. If this is on iOS I think most users are using Locative (some can correct me here if that is wrong). We have geofencing on our list, however it may be a seperate app due to the extensive permissions needed. IMHO we should not burden most users of UD Mobile with these permissions or power consumption related to this type of tracking.

Thanks. Issues with both UD Mobile and Dyson Node Server found. The next version of UD Mobile will no longer stop synchronization for failed UTF8 encoding. Created pull request to fixed unsupported chars in Node Server https://github.com/exking/udi-dyson-poly/pull/4

Hi @jwagner010, We only have one crash reported on version 0.4.7. so this may be something on the local system or an install issue. I recently had a similar crash in development which was related to an installation compile problem. If this is the same a reinstall may fix the issue. Before reinstall please first reboot the device and the ISY then try sync again. If that does not work please backup you setup then uninstall the app, reinstall run sync. If everything syncs ok reinstall the backup and try sync again. I will provide additional instructions if the above does not resolve the issue.

T Hi @apostolakisl, This error is due to there already being one instance of this portal account entered into the app. The app supports multiple Portal accounts but each must have a unique user id. ISY Portal uses oAuth so this unique constraint is in place to prevent multiple authentication requests for the same portal account. There is no need to login to the Portal Account again to add the second ISY. See "Adding Another ISY (Existing Portal Users)" here https://wiki.universal-devices.com/index.php?title=UD_Mobile. Local Connection Settings can be found under Remote Connections in Advanced (Settings-Tab > Systems > Your-System > Advanced). Relationships between SSID and local connections can be set in Local Connection Settings. This is in case you have multiple ISYs are at different locations and would like to use local connections when at each location. See "Local Connections and Local VPN" at the same wiki link above.

Hi @Tango, An ISY from 2017 with the first gen 300 series board is compatible with firmware 5.0.16c. For context my production ISY from 2012 with added first gen 300 series board had been running 5.0.16 for the past year, although I have recently upgraded to the 500 series Z-Wave module to run the latest firmware. Some new Z-Wave devices require a new hardware controller for full functionality, but most are backward compatible. Our new and more powerful Polisy hardware will soon be available as an ISY replacement, so if all of your current Z-Wave devices are functioning with the 300 series board there is no reason to upgrade hardware at this time, only firmware update is needed to use UD Mobile. The ISY994 hardware has been around for about 10 years and is still very capable and has outlasted many competitors. When you decide to upgrade your Home Automation hardware we hope you consider our Polisy controller, if our product history is any indication it will be around for many years with both hardware and software upgrade support. Notes: Z-Wave module was in stock yesterday, but now appears to be out of stock, please check back at a later date.

Hi @Tango, First thanks for trying UD Mobile. UD Mobile is still in development and does not yet have all features of our Desktop Admin Console, but we hope to have most of the same features available in the future. Our firmware upgrades have no monetary cost. There are hardware dependencies for some Z-Wave firmware versions, for which we sell an upgrade module. UD Mobile will work with both the older 300 series (firmware 5.0.16) and newer 500 series (latest firmware) Z-Wave modules. The SSL Certificate (or SSL Portal) requirement is only for remote connections and is due to Apple's and Google's push for security. Some third party developers can offer options to bypass SSL with exceptions from Apple/Google. However because we control firmware and the ISY is updatable we do not qualify for these exceptions (see link below for Apple's exception requirements). If we bypass this without the proper exemptions from Apple/Google it may lead to removal from their app stores. For more information on local and remote connections, including all remote options, please see the following link. https://wiki.universal-devices.com/index.php?title=UD_Mobile

iOS Beta (Open Testing) 0.4.1 - 0.4.2 Note: 0.4.1 should be live sometime today or tomorrow, however there are a few issues which were discovered in internal testing after app was submitted to App Store. These issue have been fixed in 0.4.2 which will be submitted after review of 0.4.1 is completed. 0.4.1 Favorites are now a tiled grid. Favorites should now be much faster on initial load, on a good connection load times should be about 2 seconds local and 5-7 remote. Added custom favorites database observer (speed improvements), crated new favorites, node, and nodeStatus object builders from cursor. Added new favorites folder move-to-folder picker and Edit-type picker. 0.4.2 Fixed Favorites tile width on screen rotation, fixes both width and number of items per row. Fixed Favorites move-to-folder and edit-type dialog image clicks. Fixed release notes for 0.4.1 showing as duplicate 0.4.0.

Thanks. Hiding nodes has been implemented in Android, coming to iOS. Still need to add automatic hiding with (~) prefix during synchronization. We'll look into getting hepatic feedback on iOS.

Android Beta (Open Testing) 0.94 Polyglot cloud is now functional. Install from PGC NodeServer Store. Start, stop, delete, and upgrade-config for PGC nodeServers. Real-Time-Log non-functional. Added icons.

Also on our list

Added window folder with additional windows and coverings. Added mail icons into objects folder.

Hi @keith mcelhinney, Thank you. Below are some of my thoughts and our road map. Icon-value and color-value have been tried with unfavorable (subjective) results, so some of my comments are intended as objective criticism. My comments and questions are not intended to discourage, but to encourage more ideas that consider issues caused or foreseen with some (previous) implementations. Also, if you are on iOS some of these requests may be addressed when Grid-View and Favorite-Types are implemented (currently only on Android). #4 Import is on our list although it has lower priority than some basic controls which still need implementation. Please let us know the exact icons you would like to have, and we can try to add them soon. If they are available here https://fonts.google.com/icons?selected=Material+Icons it is more likely they can be added. #3 Currently any device which has a status, supports “on” command, and supports “off” commands will have a toggle indicator. Clicking on the icon will toggle the device. Whole toggle cells are on the roadmap as a Favorite-Type which has been implemented in Android, coming to iOS. #2 On our road map. #1 This one is the most difficult. So, let’s look at both color and icon scenarios. As a reference UD Mobile is based on Go2ISY which allowed color, icon, names (#2), and icon import (#4). So, my comments below are from much trial and error with results which were unfavorable or confusing (subjective). Comments and ideas from others are welcome. #Color The app supports light and dark modes for both platforms, however the screen type has a large effect on how colors are displayed. There are 3 icon-press-types (toggle-type); no-toggle, on-off toggle, and command. In addition to the toggle type we also have a no-status type (i.e. app-startup does not have node status). So essentially there should be 4 color types; no-status value during app startup (gray?), on (amber?), off (black?), and non-toggle (blue?). Now we have a few issues; should the color black be white in dark mode? Which leads to the next issue, some screen types (when the app is in dark mode) white, amber, and gray all appear to be the same color. Not to mention node status values which do not conform to on/off as a status (i.e. thermostats, security panels, tesla, etc.), this would require the user (or more unlikely us) to develop rules on when a device is “on” or “off”. The only method found to combat the color similarity issue in dark mode was to encircle all icons with a colored circle, which dramatically decreases the size of the desired icon. However, encircle caused confusion of on/off state, toggle-type, and non-filled icons were difficult to distinguish color. So use the circle fill to show status….start over at #Color. To solve this problem the app uses the same color for all icons and then adds an indicator (top left) for toggle-type (or favorite type (Android)) and on/off indication. Allowing the user to choose the accent color is on our road map. #Dynamic icons This can be related to #2 as custom icons for values has a direct relation to custom name for value. Go2ISY had comparison rules for “>”, “<”, “no-status”, and “=” values for icons, icon color, and custom names so it is possible. However, it was much work for the user and the user would eventually hit the same issues described in #Color. With that said, I think value-based icons can (and should be) implemented. However only by relying on #2 to change the icon and complete omission of comparison value-based rules. Value based rules could still be implemented via ISY program and then using #2 to map the icon based on program status. This would also indirectly allow users to change icon colors when #4 (import) is implemented.

Android Alpha 0.93 Fixed Program Editor crash with invalid UOM. Fixed Favorites Folder crash when no status node specified. Unfinished items in this release: Added Polyglot Cloud NodeServer Store (installs not functional). Added details for installed Cloud NodeServers (start/stop/delete and additional information not functional).

Thanks, found a missing check for folders without a status node. I'll push an Alpha fix in the next few hours.

Android Alpha 0.92 - 0.89 Sync required! This release has mapped human readable data for program If/then/else data with limited exceptions which are listed below. Editing, adding, and adjusting programs is not yet implemented. To view program data open a program to its dashboard (values/commands screen) then click the program icon at the top of the screen. Sync required to obtain Node Definition Command Sends (<nodeDef><cmd><sends>) objects, and Link Definitions objects for use in Program mapping. Without sync many values will be raw non-human-readable values. Please report if data is not mapped or is not correct except in cases listed below and only after synchronization. Program Mapping will be raw for the following Items: #1) Scene Consequent (then/else) mapping for commands which are not available in UD Mobile (i.e. Scene Thermostat commands) #2) Wake on Lan Consequent (then/else) values as UD Mobile does not yet parse WOL. #3) Notify Consequent (then/else) value as UD Mobile does not yet parse Emails/Notifications, Settings/Groups, or Customizations. #4) All Modules except for Networking/Network-Resources are not mapped as Node Servers are now the preferred plugins. #5) X10 Condition (if) and Consequent values are raw unmapped values.

Is this the zwave version ZRTSI? The point was that a work around found by others with non-ISY zwave controllers was to set ON to 50% which triggered the MY command, the status is not important and will never be know by any of the wireless RTS controllers. If @jwagner010 is not using the zwave version I wonder if setting a basic node with a value would work (Left-Click node, Z-Wave, Add/Refresh Basic Node). A quick search and an Amazon review appears to confirm what I remember "50% level command is working" (https://www.amazon.com/gp/customer-reviews/R1PHGHIOB9FAH9/ref=cm_cr_arp_d_rvw_ttl?ie=UTF8&ASIN=B00HSOMH0M)

Which is why I suggested a rest command with the 50% parameter to test. I have encountered nodes will accept undefined commands and some that report an undefined status back to the ISY. Some examples are rest commands to Insteon binary switches which will accept and report back On-Level (not defined), and rest command sto the Hue Bridge Node Server will accept on (DON) with 0-256 values even though on (DON) parameters are not defined (only Brightness is defined). So this leads me to believe the ISY will try to send a command/parameter even when not defined. If this works then it may be possible to create a workaround, the workaround process would differ dependent on how the node is defined in the Zwave definition. If the definition allows on (DON) and a param (0 or 100) a program variable could be used to set the param to 50, If no params are defined a network resource could be used...

iTach w/ Network-Resources along w/ a few programs. Allows my KPLs to control Somfy in every room with on, off and fade up/down presses. Looked at the Somfy (?) node server a while back but it needs some improvements for full control. Most of this was done before the ZRTSI was released.....Did you try the 50% command?

I use the URTSI II for ISY integration which has full control (up,down, stop, jog-up, jog-down) and do not own the ZRTSI. However I do recall reading somewhere that this device acts as a dimmer and will send the STOP/MY command if set to 50% (could have also been 25% or similar 255 variation). Has anyone tried sending a REST command with a 50% param. I'm sure the nodeDef does not support this param but I have seen other devices respond to commands which are not defined. /rest/nodes/<address>/cmd/DON/50

Thanks. We found a firmware issue with REST requests for programs, let us know if its not corrected within the next couple of versions.

@mbking, Are you running the most recent build for Polisy?