apostolakisl

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.

It would be really nice if you could have alternating lines of slightly darker/lighter so you can follow across the page more easily. Or maybe very faint lined pages, like an excel spreadsheet, but not quite so obvious.

After migrating, it appears you also have to either resave any program referencing a tag, or restart iox.

Just updated the plugin to now be configurable from a nice html interface. No plugging in all kinds of parameters and values into the plugin config page. Also added xml to parsing.

Why do have an x for my plugin data files? Currently, I only have locally installed plugins using the new eisy plugin section, do local plugins not get backed up? I am only using the plugin section at this point for plugins I have created, I have not yet started migrating my purchased plugins over. Also, would a restore put all the plugins into their slots plus configuration files, or just configuration files?

What is happening with the various backups? PG3x plugins have their own backup section. I don't see any backup section under the Eisy-UI plugin section. Backing up the entire Eisy UI shows me this. Where exactly do the EisyUI plugins get backed up? It looks like not here based on the red x. And by data files, do you mean just the configuration or the entire plugins. Where do local plugins in my development section fall? If I need to restore the entire eisy, will it put all my plugins back into the correct slots with all the configurations? And what exactly is getting backed up in the old developer section when I do a backup? For some reason levolor is listed as a local install here, but it also shows up in the new eisy plugin section, which is where it is currently running from. Perhaps I did a local install here and then started using the new (beta at the time) plugin section.

We have an official thread for this plugin. HTTP_Control basically can be used as a structure to build custom plugins. If you have some device that is a one-off or otherwise no one wants to make a plugin for it, and it accepts get/post/put/delete requests and responds with plain text or json responses, then you can use http control to create IoX nodes. It is similar to network resources but adds the fact that it creates nodes so sending requests can be done directly from scenes and then the bigger thing is that responses go into nodes and again can be used directly in scenes. Of course you can still use programs to control it. The biggest advantage over network resources is that responses are accepted and usable. The simple example is a thermometer that you make into a thermostat. You can send a request from a node and get a response that then goes into a node. Within the plugin configuration you set certain values to be "on" or "off" allowing for the node to turn scenes on or off, or in the case of a thermostat, perhaps a heater or cooler. You might say above 38 is "on" below 35 is "off" for a fridge., Between 35 and 38 are left alone as hysteresis zone,.

We have an official thread here for questions comments regarding Unifi Control. The plugin integrates Ubiquiti UniFi Network with IoX. Provides monitoring and control of Traffic Routes, selected network clients, switch ports, PoE ports, and user-created firewall policies. Supports Traffic Route enable/disable, client online and blocked status with Block/Unblock control, switch-port link and speed monitoring, PoE status/power with On/Off/Cycle control, and firewall policy enable/disable.

@aca2b2 Are you using intellicenter or are you directly linked to the Pentair Color Sync Controller? I am testing with a direct connection as I don't have intellicenter. If you turn the lights on/off or whatever from IoX, it should update immediately. If you change it from the app or some other means, you need to wait for the polling interval, which defaults to 30 seconds. EDIT: I see from your other post you are using intellicenter and Globrite lights. I suspect the issue is that the plugin is designed and tested to work with Color Sync controller, both through Intellicenter and via direct link to Color Sync. The API is probably using the same commands as Color Sync commands, but not reporting back using the same format as Color Sync. I'm sure I can work it out and add that, but it would require you giving me your Intellicenter username and password.

This is a plugin to link your Mammotion lawn mower to IoX. This is off of the public API. It can do most all of the important stuff, but doesn't have everything. That is because the public api doesn't expose everything. While people have reverse engineered it, Mammotion warns you that if they detect your account hacking in to the non-public stuff, they can cut you off, and apparently have actually done that to some people, so public it is. Plus my first feeble attempts to break in failed and I figured it was just a bad idea anyway. The Mammotion plugin also detects pool robots, but the public api supports basically nothing for them except online/offline. Not sure what good it would do to have IoX control it because you can't control a pool robot when being under water cuts it off from wifi. It might be nice though if it reported state of charge, so you could know if it was done charging. Maybe someday. If Mammotion exposes more features to the public API, I'll likely add them.

This is the official thread for any questions or issues with IoX logger. IoX logger is a plugin that lets your Eisy (or probably Polisy) host an html interface that lets you choose any node on your IoX and log it at various intervals of your choosing or log on change. It has a rudimentary graphing function built in and you can download a csv file for fancy analysis in Excel or similar. The interface looks like this: To access you go to your IoX LAN address port 8765. Setting it up requires that you give it API access in the configuration page of the plugin. Don't forget to enable API Access when installing it and be sure to hit the save button to the right of that, not at the bottom.

@Javi What is the logic of doing away with a purpose built app for phones? Seems like every other company out there tries desperately to get you to install their app rather than use the web interface.