Jump to content

ST-Inventory 1.0.9 released.


bpwwer

Recommended Posts

Posted

I've released an update to ST-Inventory so that it should now work with PG3x on eisy.  

 

Note, I've only tested this update on PG3x 3.1.18 on eisy.  I have not tested it on PG3/Polisy, it should work there as well but if not, let me know.

Posted
45 minutes ago, bpwwer said:

I've released an update to ST-Inventory so that it should now work with PG3x on eisy.  

 

Note, I've only tested this update on PG3x 3.1.18 on eisy.  I have not tested it on PG3/Polisy, it should work there as well but if not, let me know.

On my eisy the ST-Inventory shows that I have 4 Insteon, but I don't have any Insteon. It looks it mixed up Insteon with Zwave as it shows 0 while I do have Zwave.

Posted

I installed it on the Polisy and I get FAILED that kind of flashes in the browser.  (pg3 3.1.16 which is latest for Polisy)

and I tried a couple slots and it never shows up at all in the IOP.  

 

023-01-11 23:03:23 info: NS: Starting Node Server
2023-01-11 23:03:23 info: POLY: Interface starting
2023-01-11 23:03:23 info: POLY: Getting config from environment
2023-01-11 23:03:23 info: POLY: MQTT client connected
2023-01-11 23:03:23 info: NS: MQTT Connection started
2023-01-11 23:03:24 info: POLY: MQTT client connected
2023-01-11 23:03:24 info: NS: MQTT Connection started
2023-01-11 23:03:26 info: POLY: MQTT client connected
2023-01-11 23:03:26 info: NS: MQTT Connection started
2023-01-11 23:03:27 info: POLY: MQTT client connected
2023-01-11 23:03:27 info: NS: MQTT Connection started
2023-01-11 23:03:28 info: POLY: MQTT client connected
2023-01-11 23:03:28 info: NS: MQTT Connection started
2023-01-11 23:03:29 info: POLY: MQTT client connected
2023-01-11 23:03:29 info: NS: MQTT Connection started
2023-01-11 23:03:30 info: POLY: MQTT client connected
2023-01-11 23:03:30 info: NS: MQTT Connection started
2023-01-11 23:03:31 info: POLY: MQTT client connected
2023-01-11 23:03:31 info: NS: MQTT Connection started
2023-01-11 23:03:32 info: POLY: MQTT client connected
2023-01-11 23:03:32 info: NS: MQTT Connection started
2023-01-11 23:03:34 info: POLY: MQTT client connected
2023-01-11 23:03:34 info: NS: MQTT Connection started
2023-01-11 23:03:35 info: POLY: MQTT client connected
2023-01-11 23:03:35 info: NS: MQTT Connection started
2023-01-11 23:03:36 info: POLY: MQTT client connected
Posted
18 hours ago, asbril said:

On my eisy the ST-Inventory shows that I have 4 Insteon, but I don't have any Insteon. It looks it mixed up Insteon with Zwave as it shows 0 while I do have Zwave.

I just checked. Still the same on eisy,  4 Insteon nodes while have none and while I have 4 Zwave nodes. However it is correct on Polisy. BUT there seems to be a general issue with PG3 on Polisy which is that my node servers  do not update with restart, even though the update message disappears after a restart..... and then comes back after a day or so.

So, as on Polisy PG3 I am still on 1.0.8  I could possibly have the same reverse Insteon-Zwave if & when it updates to 1.0.9

Posted
10 minutes ago, asbril said:

I just checked. Still the same on eisy,  4 Insteon nodes while have none and while I have 4 Zwave nodes. However it is correct on Polisy. BUT there seems to be a general issue with PG3 on Polisy which is that my node servers  do not update with restart, even though the update message disappears after a restart..... and then comes back after a day or so.

So, as on Polisy PG3 I am still on 1.0.8  I could possibly have the same reverse Insteon-Zwave if & when it updates to 1.0.9

Nothing has actually changed in ST-Inventory.  1.0.8 and 1.0.9 are the same as far as the code goes.   The difference is in the interface module used to interface to PG3(x) so 1.0.8 is using an older version of the interface module and 1.0.9 is forcing it to use the latest interface module.

Showing the nodes as insteon vs. zwave is likely because how zwave node are represented with the zMatter board is different from how they are represented with the older boards.  ST-Inventory is probably checking to see if they match the old representation and when they don't, assumes the nodes are Insteon.

I have not looked at updating ST-Inventory to recognize the new z-wave representation, yet.  I'm just trying to get the node server to work.

 

  • Like 1
Posted
16 minutes ago, bpwwer said:

Nothing has actually changed in ST-Inventory.  1.0.8 and 1.0.9 are the same as far as the code goes.   The difference is in the interface module used to interface to PG3(x) so 1.0.8 is using an older version of the interface module and 1.0.9 is forcing it to use the latest interface module.

Showing the nodes as insteon vs. zwave is likely because how zwave node are represented with the zMatter board is different from how they are represented with the older boards.  ST-Inventory is probably checking to see if they match the old representation and when they don't, assumes the nodes are Insteon.

I have not looked at updating ST-Inventory to recognize the new z-wave representation, yet.  I'm just trying to get the node server to work.

 

Am I the only one having issues with updating node servers on Polisy with Zooz ? It is not a big deal for me as most likely I will soon try migration to eisy with ZMatter and then send my Polisy to the Smithsonian :-) 

Posted

I've updated the interface module and it now should work with both PG3x and PG3.  New installs will pick up the latest, if you already have it installed and it's not work, a re-install should pick up the new interface module.

Posted

UPDATE-  Latest version seems to be working.  Only thing is the update speed.  I cleared the log and it was a good 5-10 minutes before it updated in the ISY.

Do I adjust the short or long poll?

But the good news is it seems to be working.

This developers other node servers seem to be working except LinkTap which is still on PG2.  I sent you a PM about that.

Posted
5 minutes ago, asbril said:

1.0.10 still shows Insteon for ZWave devices.

I just checked and mine is correct. As I said in my previous post it took 5 to 10 minutes for numbers to update. Also you can try restarting the note server and the admin console. 

Posted

Version 1.0.11 fixes the z-wave discovery.  And because I could, I made it do a discovery on startup so you don't have wait for the poll event for it to populate.

Just a note, installation takes longer than I would expect and discovery takes 10 - 12 seconds so it can seem like a long wait on first installation before it sends everything to the IoX device.

  • Like 2
Guest
This topic is now closed to further replies.

×
×
  • Create New...