October 21Oct 21 Moved wireless sensors to plugins in eisy-ui. The controller shows up but the sensors themself's do not show up under the controller.
Thursday at 01:58 PM5 days Author Have tried many things to get this plugin to shows it nodes. Reinstalled, hard reboot of eisy and others. have latest Beta updates installed. Nothing worked so far.In reading the read-me for this pluging by JimBoca it stated the following after the tag manger node shows up, "The Tag Manager node created in the ISY has a "Monitor Tags" option, which by default is disabled in case you have multiple ISY's. It should only be enabled on the ISY that is on the same LAN as the Tag Manager. When this option is enabled, the nodeserver updates all the Tag URL's so any updates are pushed to the REST server. "This option is not showing up in the wirelesstag controler options after a new install in eisy-ie. Has anyone been able to get this node server to work with the new Eisy-ei?I can get the wireless tags working in Home-asst and send the data to eisy-ie using variables for the programs needing it but holding off for now.
Thursday at 03:24 PM5 days This issue was previously reported in this linkPerhaps it's time to tag @Jimbo.Automates
Friday at 12:25 PM4 days Author Solution Well finally fixed the problem and have the nodes for the wirelesstags workingFirst after installing or migrating your plugin, ignore this in the node list Wireless TagControllerNow go look at the top of your node list for some thing like this ( no idea were this name came from) Node Name Type#5B02630EC28c Wireless Tags ManagerIf you click on this node you will get the correct panel on the right. In this panel go to monitor tags and set value to true.Nodes will appear under the #5B202630C28No idea why two different node names show up for the wirelessplug in, the one labeled wireless tagsController does nothing.Found this by pure chance, looking at the top of the node list and wonder what this strange node name was.
Friday at 01:26 PM4 days After migrating, it appears you also have to either resave any program referencing a tag, or restart iox.
Friday at 06:35 PM4 days 3 hours ago, EricBarish said:Well finally fixed the problem and have the nodes for the wirelesstags workingFirst after installing or migrating your plugin, ignore this in the node listWireless TagControllerNow go look at the top of your node list for some thing like this ( no idea were this name came from)Node Name Type#5B02630EC28c Wireless Tags ManagerIf you click on this node you will get the correct panel on the right. In this panel go to monitor tags and set value to true.Nodes will appear under the #5B202630C28No idea why two different node names show up for the wirelessplug in, the one labeled wireless tagsController does nothing.Found this by pure chance, looking at the top of the node list and wonder what this strange node name was.After updating eisy.ui to the recent ver 1.4.6, I found a new entry for my WirelessTags plugin, that included the Monitor Tags button. Enabling that allowed the plugin to find and display my tags and their status. Additionally, the update allowed my Zibgee service to once again find and access my Hue bulbs. Nice!Now, to update all of my Wireless Tag programs to eliminate the "Not Loaded" status.
Saturday at 02:05 PM3 days 19 hours ago, wrj0 said:After updating eisy.ui to the recent ver 1.4.6, I found a new entry for my WirelessTags plugin, that included the Monitor Tags button. Enabling that allowed the plugin to find and display my tags and their status. Additionally, the update allowed my Zibgee service to once again find and access my Hue bulbs. Nice!Now, to update all of my Wireless Tag programs to eliminate the "Not Loaded" status.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.
Saturday at 04:30 PM3 days Yep, thanks. Nodes did indeed have the same address as before. And just changing a character in the Comment section, updating and saving, restored the programs into operation without the "Not Loaded" status. All good now.
Saturday at 05:24 PM3 days 49 minutes ago, wrj0 said:Yep, thanks. Nodes did indeed have the same address as before. And just changing a character in the Comment section, updating and saving, restored the programs into operation without the "Not Loaded" status. All good now.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.
Create an account or sign in to comment