Have reinstalled it, stopped and started it several times. Running V1.08  Log shows: 

2023-01-03 15:05:05 info: NS: Starting Node Server

2023-01-03 15:05:05 info: POLY: Interface starting

2023-01-03 15:05:05 info: POLY: Getting config from environment

2023-01-03 15:05:06 error: POLY: MQTT Error: Connection refused: Identifier rejected

Mine is disconnected after the update, tried deleting, re-installing, and re-configuring, log shows this:

2023-01-03 19:51:49 info: NS: Starting Node Server
2023-01-03 19:51:49 info: POLY: Interface starting
2023-01-03 19:51:49 info: POLY: Getting config from environment
 

14 hours ago, jkosharek said:

Mine is disconnected after the update, tried deleting, re-installing, and re-configuring, log shows this:

2023-01-03 19:51:49 info: NS: Starting Node Server
2023-01-03 19:51:49 info: POLY: Interface starting
2023-01-03 19:51:49 info: POLY: Getting config from environment
 

simplextech,  any input on ST-Inventory not working with EISY 5.5.2?

I can confirm I even deleted mine in IOX 5.5.3 (new today) and pg3 3.1.16 (polisy version) and it shows all zeros now.

Was working before 5.5.2 and if you had it running and did not delete it, it would show old cached values.

But once you delete and reinstall you get zeros.

Tried in multiple slots.

I did the same this morning after the update to IoX 5.5.3 and get similar results, mine creates the NS connections in IoX but doesn't even create the node device it's self and the Node shows disconnected in PG3x. 

Try a different slot. I’ve had issues with a couple of note servers not really deleting
 

Also the procedure I’m running now for notes servers is to stop it first, restart PG3, and quit the admin console.  Then I reinstall the node server. Then I start up the admin console and it should be up at the top.  
 

But even with this procedure I get all zeros   
 

jeff

I am running PG3x v3.1.18 which fixed NS not correctly being added to IoX (KASA NS was one it fixed) but ST-Inventory is still an issue. I have a ticket open with UDI support and will update the thread once resolved. 

3.1.18 is only for the eisy so I can’t even go past 3.1.16

Interesting because I started this thread, but it is working for me now on5.5.2. I dont remember what I did to get it going again. 

 

Apparently the developer is washing their hands of support and UDI support is looking in to it.