Javi

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.

Hi @nitenshinarmor, you have valid points and most of our previous firmware updates did not require the user to download firmware. If you are upgrading the 4.x branch of ISY994 firmware the update is done automatically from the Admin Console. The same is now true for 5.x upgrades on Polisy. Migrating to 5.x from 4.x requires manual intervention and may require a Z-Wave hardware update, so an automatic update is not available. For users who want features of 5.x without the purchase of Polisy there is the option of a manual firmware update.

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

I've only had it for about 2.5 years, but it is in the main entry and living room, so with the family being home for the last two years due to covid it is being triggered all day long. The only insteon motion sensor which I have not replaced is in the laundry, maybe triggered 5- 20 times a day, and I'm lucky if it lasts a year. I also still have a few remaining Insteon Open close sensors with the same horrible battery life but have replaced most with low cost Z-Wave sensors with great battery life. With regards to setting the parameters: Does the main node have a "Set Parameters" command? Are parameter edits available by right clicking the node > Z-Wave > Set-Configuration-Parameter?

Assuming you can access your ISY from the same remote remote url. If your certificate is invalid you would have had to override the browser security warning, or may show as insecure in the address bar. Please refer to the UD Mobile wiki regarding Trusted CA Certificates. You will need to purchase one or configure your mobile device at the global level to trust your self signed certificate. Instructions for the former is linked in the wiki, instructions for the latter is complicated, so it is beyond the scope of support. Also be aware that opening ports on your router carries is a greater security risk. Even more risky if your CERT is not valid.

The "Requests timed out" error is a connection error. So, the app cannot connect to the url provided. Certificate issues will have a security or handshake error. You should be able to access the ISY994 basic control from a browser using the same address. If you cannot access ISY from a browser UD Mobile will also not be able to access ISY.

I have gradually moved most motion/water/door sensors from Insteon to Z-Wave over the past few years and only have one wired Z-Wave switch. I have not yet had to replace a battery in a Z-Wave device, all the insteon sensors need battery replacements at least once a year. Anyway, this one has worked well for over 2 years without any issues and mounts easily in corners: https://www.amazon.com/gp/product/B01MQXXG0I/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1

Hi @AZCRUM, Have you already purchased a CA CERT? What is the error message when pressing "Test remote connection" button at the bottom of Remote Connection settings in the App's system settings?

Apple has a way of persisting settings even on new devices which are not cloned but linked to the users apple id. I had a weeks long battle with Accessibility settings and even bought a new device. I did not copy the image and only signed into my account but the issue persisted. Ultimately I had to contact apple developer support as Voice Over access was needed for app development. An Apple engineer had to walk me through a "hidden" accessibility setting (difficult to access accessibility setting ha!). The engineer said the setting should only be linked to one device and should not transfer, alas it did transfer to a new device and changing the setting on one device transferred to all my other devices. Changing the hidden setting felt like a Konami code, it required the user to twist 2 fingers and then swipe up immediately. ......did you try up, up, down, down, left, right, left, right....?

Check PG2 frontend for an update also, then reboot. When disconnecting from WiFi or Mobile-Data an error may be shown as the subscription connection is lost. The subscription connection should be reestablished within a few seconds. Are you having multiple disconnects?

Fixed in firmware:

Hi All, Thank you, issue has been replicated. We are looking into the issue now. Issue: https://github.com/UniversalDevicesInc/UD-Mobile-iOS/issues/55

I believe the missing protocol was fixed. So the original version should work...

Thanks @DennisC. That is great news and reduces some of my fears of WiFi trigger implementation.

Thanks @dbwarner5 and @larryllix. I'll leave this for @Michel Kohanim as not related to UD Mobile.

I'll see what we can do with network change triggers, likely after the default geofencing has been implemented. That's great, the default geofence implementation should work in your case. I assume you are not using the WiFi method used by @JimboAutomates, my Samsung devices had mixed results compared to Pixel devices with regards to WiFi disconnects during long durations of screen off.

Can you verify the time of last change value on UD Mobile differs from that in the AC?

Hi @dbwarner5, This time is published by the ISY as a string and not modified by UD Mobile. You may notice there are two formats as the REST and Subscription strings differ. The times should match the last run time in the Admin Console. Sometimes messages via email, or email to carrier to sms, can be delayed or arrive out of order. In my personal use I add a timestamp the message, although it is not needed as much now with Push Over. When I was using the email to sms for my messages some would arrived 12-18 hours late. Also be sure you are on the latest firmware as I recall the time being an issue in previous firmware versions.

I've used a similar tasker profile in the past as my results were also better with WiFi than geofencing. I feel that the basic iOS geofencing is superior to the basic Android geofencing, especially when we consider multiple manufacturers (i.e. Samsung) implementing their own battery saving features. However when adding the required permissions, changing settings, and adjusting polls with Tasker I feel Android has the advantage. I am very hesitant to implement the WiFi method as I foresee too many support issues. If you know what your doing tasker works fine, if you don't the same implementation on UD Mobile will not work either. The main issue being WiFi will disconnect a few times a day event if the device is in the same location, some of this is mitigated by disabling battery saving features. There was a time a few years ago I swore I'd been hacked or haunted as the lamp in my office would turn on/off at random times day and night as I had left a Tasker profile active on a development device. The cell tower density of rural, suburban, or urban environments along with type of transportation have a role in success rates. Living in an urban area most of my errands and previous employers where within 3 miles, so the basic geofencing implementations failed frequently when driving, but worked well when walking. If I had Google maps, or any other gps app, running while driving geofencing worked better. However I have no reason to use Navigation driving to locations within my community. Finally, trying to add family members into the mix, some who frequently have a dead phone, children who have restricted use times, and some who frequently left the device at home, it became too much. I say this as, much like @MrBill, I found another way to ensure security is being monitored. In my case we walk more than drive and parking in not attached to the home, so we just need to monitor the doors and motion sensors. With that said we do plan on implementing the basic geofencing methods by Apple and Google in UD Mobile. If the basic geofencing methods do not work for a user, it may be better to find another solution to monitor location.