simplextech

logs is created if/when the NS starts... which it isn't. Looks like your system is messed up or needs updating. Update the system and try again. If it continues to fail open a ticket.

Look at the NodeServer log. It's in ISY-Inventory/logs/debug.log See if the errors are the same as before. If they are then for some reason it's not installing the modules on your Polisy. Manually run the install.sh file. /var/polyglot/nodeservers/ISY-Inventory sudo -u polyglot ./install.sh Post any errors from that. If there's no errors then try to start the nodeserver from the UI

Yup no worries. Delete from Polyglot as you did. Then check and delete the files from the Polisy. Then try the install from scratch.

How did you remove the files? Did you change to the directory and delete the files? Or did you delete the entire directory? It looks like the .git information is still present meaning you deleted the files but not all of them. Delete the top level directory to delete everything. cd /var/polyglot/nodeservers sudo rm -rf ISY-Inventory If you did remove the entire directory then something else is wrong...... It makes no sense for it to install/work for me on Polisy but not for you doing the same things.

I just deleted from Polyglot and removed the files from Polisy and installed from the store. It installed and started without any errors/problems. I'm pretty sure a removal of the files and then a fresh install will resolve this.

Did you install from the "store" or manually? It looks like the install script was not executed. You will need to delete the NodeServer and I'd recommend deleting it from the Polisy as well. Login to the Polisy as the admin user and delete the entire directory of the nodeserver in /var/polyglot/nodeservers After it's deleted then try the install from the store. Also is your Polisy up to date on updates?

Anything in your logs? Polyglot Logs and NodeServer logs? When you go to the configuration page do you see the instructions box? If not then the nodeserver is not running. It needs to be started and if it won't start then something else is wrong. What's your Polyglot version?

As mentioned by @DennisC if you don't see the parameters already named then the nodeserver did not install correctly. Are you installing this on Polisy or rPi? This does NOT work in Polyglot Cloud.

In the Polyglot Web UI. Did you configure the nodeserver with the IP of your ISY, Username and Password for access? Once configured. Restart the nodeserver. There's nothing else to "add" or touch from the Admin Console.

Only 100? nothing... Number of packages to be upgraded: 291 Most of them are FreeBSD system packages and dependencies.

Here's the link to the official Z-Wave Product DB. https://products.z-wavealliance.org/ Here's the link to the GE/Enbrighten receptacle: https://products.z-wavealliance.org/products/3892?selectedFrequencyId=2 All devices will have a Conformance statement that goes over the z-wave characteristics.

No, not normal.

Me neither! I had the same problem of trying to figure out how much of things I had and there wasn't anything... so... this was born. The total is below: total_nodes_count = node_count + scene_count + folder_count

Everyone wants documentation Total Nodes: z-wave, insteon, nodeserver nodes, and now device folders Scenes: well...scenes Programs: programs and folders Individual counts for nodeserver nodes, z-wave, insteon devices, state variables, integer variables

Yes they are included in the program count.

This is not for program folders. This is for device/node folders.

wrong site. That's a data analytics / streaming system. This is the link for Keen Smart Home Vents: https://keenhome.io/ I don't have Keen Vents however a quick glance they appear to be ZigBee and require their own "Smart Bridge" or can interface with Iris (defunct/dead) or SmartThings. The best option would be UDI or an integrator to partner with Keen and integrate the Keen Smart Bridge via a NodeServer. Going the direct Zigbee route with a NodeServer just for these vents would be very costly.

As expected... the saga of the Admin Console and profile changes. I hate making profile changes after a NS is released.

The 0.0.9 is correct but it's weird that your display doesn't show the folder value. You could uninstall it and re-install and see.

Odd. I checked and the latest version is showing on GitHub. Seems like it wasn't updated. Did you update it from Polyglot in the "store" section?

Interesting.... gimme a minute...

Still looks like the Admin Console isn't displaying the Folders. I see the box is now created but there's no value. In the previous screenshot of the log I see the folders count which is good. However at the bottom I don't see an entry for updating GV7 which is the folders. Could be Admin Console or not... Restart the NodeServer and then restart the Admin Console and let me know if the Folders shows up with the correct number.

The "folders" count is missing in the screen. Hit the Update Profile button and then restart the admin console. It should show up. If not then you'll have to delete the NodeServer from Polyglot and add it again. Doing profile updates it painful.

Myself if I had normal/standard HVAC I'd opt for a Venstar Wifi thermostat. Unless you already have a good/solid Z-Wave mesh you will have problems with just a Z-Wave thermostat. The Venstar provides remote access/monitoring/control capabilities and the API is local for integration so you don't have any outside "cloud" dependencies if you choose to integrate it. Alas I don't have normal HVAC and I'm stuck with baseboard heating so I have limited options.

It seems I need to update the total count to include the scenes. It's actually odd that it's not in the total as the total is a count of all elements in the "/rest/nodes" return value. I'll look into that. I'll have to see about adding "folders" into the count as well. [Version Update]: Updated version of ISY-Inventory has been pushed. Includes Scenes and Folders to the total count. New Status element for folder count was added. Because of the profile change run the Update Profile from the nodeserver and restart the admin console.