apostolakisl

I currently have an elk zone that monitors the garage door state and I use UD mobile to turn my garage door icon green when open and red when closed, but like I said, I plan to add that the door is moving to the mix (gdo is pulling > some number of watts). The issue is that my car automatically triggers the gdo when I drive away and so does arming my alarm system. So if the car has already triggered it and then the alarm senses it isn't closed and triggers it, it ends up reversing. So the added info of not closed + moving will be programmatically set to tell the alarm system to skip activation of the gdo and wait, then notify if it isn't closed. I also intend on shutting power off to the gdo when the alarm is armed in night mode and when I'm out of town.

I have had various favorites disappear on ud mobile after various changes to eisy (not plugin migration) many times over the past few years. Fortunately I had ud Mobile backups to restore them.

I'm not sure what you mean exactly, but I just ordered some tuya wall warts that monitors wattage and of course switch on/off. Combined with a door closed contact my intention is to design a system that knows door closed, not closed, door moving, not moving to automate closure and then switch power off to gdo when certain conditions are met for added security.

@PGHBubba Fixed it. If the new version isn't showing up with an update button, just hit "reinstall".

I needed to enable, write some changes, then re-disable a number of nodes. There was a lot of useless busy work. right-click, hit enable . . . should be done. Instead you got a popup in the middle of the screen that you have to swipe your cursor way over to confirm you want to enable, then there is another popup announcing it is enabled that you have to click out of even further over. None of that is needed. Just right click, enable and be done with it. It is an easily reversed thing if you did it by accident and you don't need a popup confirming it because you get the red mark next to the node immediately. The java console is far better for this at present. I also then had to click on each node and swipe way over to the right menu to write changes. You should be able to do this also with just a single right click, write changes, like in Java. These were all devices I use for Christmas lights. Writing these changes now was only necessary because of the annoying messages every time you log in and then they hang out blocking the lower right of the screen. I don't think any of these messages are needed at all. The yellow dot next to the node is plenty.

Should all be fixed now.

I see that you posted a log earlier and am looking at it. it appears the port isn't blocked and the html editor is starting, but something with the migration from the old way of storing all the configuration values to the new way where it is shared with the eisy ui config page.

Maybe pm me your log. I currently have the most recent eisy firmware and installed http control locally from eisy developer plugins (not legacy ph3x) and it is all working. Ud mentioned that they were going to start blocking ports on eisy, perhaps they have with the latest firmware but for whatever reason a local install bypasses that. I assume you are running the latest version of http control. Exactly what happens when you open the html confirmation page? If it is port blocks, they said that they would then open ports for plugins after vetting it. So maybe I need to request that.

Just doing some house cleaning on my insteon network and was disappointed to not have the ability do multiple device writes after doing changes to multiple devices. I reverted to the java console. Is this feature there and I'm not finding it?

I suggest some windex and a micro-fiber cloth.

Just did a major revamp of the tuya smartlife plugin. It is now configurable from an html interface. No ssh needed at all. No setting custom values in the config file. It is all done with drop down menus, auto-discover, etc. From the plugins section, you just install it and then open the html page. The html page will populate the config file for you using the html gui. If you already have manually configured devices, no worries, they will be integrated automatically. If you are a first time use, you will still need to create a tuya developer acct and link your user acct to the developer acct and copy over your credentials from the developer acct to the plugin html interface. But after that, you can add new devices, remove devices, and replace devices from the html interface. They will show up in the config page of the plugin if you care to look. The nodes will appear and disappear in the eisy ui as you add/remove/replace them. I will be happy to add new device types to the plugin if you happen to buy something not currently supported.

After some futzing around, it appears the UDX version prior to 5.1.0 blocked package updates from eisy ui on polisy. I used ssh to manually update to udx 5.1.0. This version explicitly comments that it supports polisy updates but wants to leave freebsd at 14.3. After updating to udx 5.1.0 polisy automatically moved forward to update everything else. It takes a good long time to get through this, 37 minutes for me. Command to update udx sudo pkg upgrade udx after that succeeded, it moved onto the remaining packages. Probably because my first attempt from eisy ui failed and those updates were already pending. If you first manually did the udx upgrade, you might need to then go back to eisy ui and tell it to do the remaining updates.

Curiously, you didn't even need to change anything. When I first discovered that messing with node installs screws with programs, I, like you, initially thought you had to actually change something to get an update to put the program in queue to resave. But somehow, probably by accident, found that just hitting "update" with zero changes puts it in the queue to be resaved. Resaving resets everything. Restarting IoX also resets everything, but if you only have a few programs, it is a lot quicker to resave than waiting for a restart to finish.

Updated the plugin to now include native support of pentair globrite lights connected to intellicenter. Also updated intellichlor to be configurable from IoX on intellicenter pools that don't have intellichem automatically managing intellichlor. That is a lot of "intelli" to type.

You should be able to just restart iox. The nodes should have the exact same address as before so they should re-associate with the programs. If you only have a few programs, it is easier to just open the program (this works from java admin con, not sure about the eisy ui), click on any random line of the program, hit the "update" button at the bottom (don't actually change anything), which then tricks java into thinking the program has been updating and makes it available to resave. The act of saving it reloads all the lines of the programs and it should plug the wireless tag back in again.