Javi

Android Alpha Testing 0.54 Added Node Dashboard edit mode. Node Dashboard status objects and buttons objects now allow for sequence change and can be hidden. Many bug fixes.

Hi @asbril, I'll investigate the error bytes not being decoded (optional). Was this on today's release 0.1.4 or a previous version? <edit> Fixed 62758ed </edit>

I've had our Public Works trucks (trash, recycling, ect) break our overhead internet lines in the alley a few times over the years. I call Centurylink and they tell me there lines are fine and that I need a new modem. When I finally convince them my eyesight is great and the line is physically broken they will come by and fix within a week. During the repair the line it is zip tied to a higher cable to prevent Public Works from breaking the line. Unfortunately the higher cable is property of Xcel Energy, eventually Xcel will come through and cut the zip tie, and the cycle continues.....Not to mention CenturyLink deciding the route the cable through a large evergreen during the last repair, so now everytime it snows I have to get a large pole and shake the branches above the cable to prevent it from breaking. Anyway, I'll see what we can do about resending messages that are missed when we are at that point. I think the Node Server approach may be needed for these situations as data persistence is needed in the event of power failure or restart.

We are looking into push notifications for the UD Mobile apps, however it will be some time after our initial goals have been achieved. This would also require server side so notification triggers may, at least initially, require that the ISY is connected to the Portal. Being that connectivity is required, i'm not sure if it would help if a notification fails due to loss of portal/internet connection. Personally, all my network/home-automation equipment is on a battery backup and I use @Jimbo's Notification Node Server with Pushover and it has been more reliable/configurable than email/text notifications. Some routers, such as Nest Wifi, will notify the user when the router is offline which is also a great way to know if you will be missing notifications. A final note would be to add a timestamp to all notifications. When your mobile devices loses network connection, the device may be flooded with notifications when it is reconnected to a network. I have noticed that after regaining connection notifications may not be in the order they were sent.

Hi @smacbride, Yes, all Z-Wave devices are Nodes. So, they should have the same controls available in the Admin Console.

Hi @smacbride, If the RGBW controllers are Nodes in the ISY then the app should be able to control them. If you encounter Nodes which can not be controlled please report it to us so we can find the error. There are a few know Node Servers with errors in the configuration files which may prevent the app from controlling them. We have created pull request to fix Node Servers with known configuration errors, however some are still awaiting the authors approval.

Hi @Riggins, It appears you login tokens to the portal have become invalid for some reason. Please go to Settings>ISY Portal Accounts then select your portal account. Now click the logout button (x on top right). Now add the portal account again, this will also require that you link your portal account to all your ISYs in Settings>Systems. I'll change the button to say logout in the future to avoid confusion and allow logout without removal of the account from the App. Please let me know if this resolves the issue.

Hi All, We are opening a few dozen additional alpha testing slots. App still requires a few security upgrades and onboarding features before open testing. To be added to our Apple Test Flight group please send me a PM. Include the email used with Apple, ISY firmware version(s), iOS version(s), and let us know if your ISY is connected to the ISY Portal . This group does not require ISY Portal subscriptions. App will work on local connections (Advanced->Local Connections), remote connections with ISY Portal or a trusted CERT.

Currently in alpha testing. App has all node/node-server controls and status values, it still needs a couple of bug fixes, favorites, and a few security upgrades for Portal connections before open testing. We will open to a few dozen additional alpha testers in about a week.

The comment was regarding starting off without wires using the Sompy WireFree motors and batteries, then pulling/hiding wires later. The JST connectors on the 12v motors are Micro JST 2.0, I did not measure them but my guess would be between 24-30 gauge. When/if you decided to run power, a 12v CCTV regulated and fused power supply will come in handy for other equipment also (CCTV cameras, door locks, sirens, ISY, routers, switches, and modems). Then connect the regulated power supply to battery backup and all your equipment is still functional during power outages.

@carealtor if you have to pull wires, with limited space, I would go with the 12v motors. It will be much easier to pull/hide a single 18 gauge wire. I installed 8 motors on our main floor about 7 years ago with wires pulled through the attic. About 2 years ago I did a small basement remodel and added egress windows. During the remodel we pulled wires for 7 basement windows. During the basement Sompy install I did a write up as I had to relearn the Sompy install/setup process and figured it would be helpful in a few years when I get to the last section of the house. Below is a link to the write up if interested. I still need to do a write up on hardwiring the z-wave door locks with the same power supply. https://voiceforiot.wordpress.com/2019/02/24/adding-motorized-blinds/

Hi @CandC, Glad the issue was fixed. Do you know which Node Server you have in slot #3?

Hi @apostolakisl, Thanks for posting the node xml. I think I see the problem, The app is only adding <group flag = "132"... not <group flag = "4". This was done to exclude the ISY scene, but I'll change this to only exclude if flag="12" instead. Please let me know if version 0.51 fixes the issue, should be available later today or early tomorrow.

Hi @CandC, Please try to resync the app, do you receive any errors? If no errors are presented please open a Ticket and ask for Javier and we can diagnose the issue. The app uses the Insteon Node Server files from the editor, opposed to hard coded values in the Web UI, so if a sync does not fix the issue we will have to check the files on the ISY.

Hi @apostolakisl, Have you been able to access these scenes before, or has this always been the case? If this has always been the case, your files may have an issue created by a bug in an older firmware version, assuming no errors were presented during sync. In rest/nodes can you check if the missing scenes have a parent tag containing a parent address. If they do can you search for the parent address, is this folder defined? If the parent address is not defined can you add the scenes to a new folder, at least temporarily, in the Admin console? This should remove the link to the non-existent parent.

Hi @auger66, Thank you. A there is no option for a selected ISY, they are all combined into a single interface. That said you can achieve something similar by adding a favorites folder. iOS is in testing, but we do not have a release timeline.

Hi @only1miller, Do you also have the Hue Node server? If so please be sure it is updated as the OP had an older version causing the error.

Hi @ddurrant, Is the issue with the UD Mobile App?

Hi @dbuss, To keep the app as fast as possible the initial status for Programs, State Variables, and Integer Variables is not requested when the app is opened. This can be changed in Systems>Your-System-Name>Advanced. Status population speed may be affected on low-end/older Android devices or if you have many items in the additional request category.

HI @diggler, Thanks for finding the issue, I'll try to catch this in the next release for a better error message.

Does this happen on the local network also (setting>system>name>advance)? If it doesn't, or if unable to connect to the local network please logout of the portal account (setting>ISY Portal Accounts>Name> Delete). Then go back to you system and add login (setting>systems>name). If that doesn't work we can schedule a remote session to diagnose.

Was UD Mobile synchronized after the reboot? Is the problem only affecting this node or is it affecting all nodes?

Thanks. There is a firmware bug for firmware less than 5.3.2 which can cause issues with the app. Please let me know if reboot fixes the issue.

Hi @diggler, The error appears to show an invalid device address (C 63 EC 1). Please post an image of this same screen with the header showing the device address (top left), and let us know your ISY firmware version. This image does not need to show the error. I want to check if the app has a valid address or if the address is being changed when sending the command. If this started after a sync, please reboot the ISY then resync. Thanks

Hi @bikerbobhain, The icon-toggle functions similar to a button on a keypad link. Currently the home/favorite list icon-toggle needs a status (on/off, running/stopped) to execute a command. There is no way for the app to know which command you would like to toggle if the command is not based on a status. In my opinion we should keep programs and nodes appearing similar. This will avoid confusion and keep the home/favorite lists clean without too many buttons/switches/toggles. I understand this will not accommodate all situations, however many programs can be slightly changed to make it work by adjusting the IF statement. At some point we will also add the ability to name the commands, so when viewing the node/program dashboard a user could change the run-then/else to display on/off. The exception to this is network resources which has a static radio button, which executes a single command, as network resources have no status. On our to-do list we have a feature to allow a single, non-status related, command for all nodes. This would be similar to the network resources static radio button and allow the user to select a single command to execute when pressed (i.e run-if, run-then, run-else, stop). Even when this feature is ready you would need 2 favorites (run-then and run-else) to accomplish the same.