TriLife

First of all Merry Christmas, belated Hannukah and happy holidays! I decided to move this thread from because it is seemed very specific to my case of migrating from OS12.x to 13.1 more than dealing with 5.5.0. Until this morning, I was operating just fine on OS12.x. @Michel Kohanim had told me that in order to upgrade to 5.5.0, I would need to flash the SSD with the new OS 13.1. I have 100+ sonoff/Tasmota devices and with @xKing's MQTT node server things were working quite well. Prior to that, I had started migrating from ISY994 on PG2 to IoP on PG3. I couldn't complete because the Zmatter dongle isn't ready. So I left Z-wave devices/programs on the ISY994 and migrated the rest to IoP 5.4.3 on PG3. I have a backup of ISY994/Zwave and a backup of PG2. Things were working a bit faster, all was good. Last week I received the mSATA-USB3 adapter, so today I flashed the SSD with 13.1. Judging from the uname -a, it even upgraded nicely. That's about where the good news stop! I never managed to ge back to the state of where I was with 12.x. It started with PG3 saying that the NS's were "unmanaged". Someone suggested that this was because PG2 still had the same NSs on there. I deleted them from PG2. No change. Then the same "unmanaged"messages started on PG2/ISY994. In the end, I deleted the Node servers from within Admin Console (in ISU and IoP) and waited until they disappeared from PG3 and PG2. Then I added the NS from scratch and reconfigured. Now ISY talks to PG2 and IoP talks to PG3. But none connect to the Tasmotas and neither does Google Assistant control them. In UD Mobile for the ISY994 connects, but MQTT doesn't show up. for IoP connects and MQTT shows, but doesn't do anything (theres news on that one further down). When I try to sync, at one point it tells me that 400+ items need to me removed... I canceled out! I remembered a couple of years ago, when I started installing MQTT, that I needed a mosquitto broker to be installed on Polisy. I did that, using @xKing's command: curl -s https://pkg.isy.io/script/setup_mosquitto.sh | sudo bash that worked. And then I followed the instructions in https://mosquitto.org/ to get the passwords to match. First question: the pwdfile is currently in /usr/home/admin/... the manual says that a good place for it is /usr/local/etc/mosquitto/... However, when I tried to follow the instructions again in that directory, it gave me something like "access denied"... Should I delete it from .../admin/... and try again in .../mosquitto/... provided it lets me? After I installed mosquitto changed the password file, I stopped the process (checking with pgreg mosquitto) and then I rebooted Polisy, to make sure it started on boot up. It did. BUT HERE IT GETS WEIRD: 1. I can no longer access PG2 (192.168.10.Y/dashboard), "refused to connect". 2. IoX Launcher 5.5.0 no longer shows IoP and it doesn't let me add it "invalid URL" is what I get. But withing PG3, it shows that IoP is connected and at 5.5.0. 3. UD Mobile now can't find IoP either... Here is the log file of MQTT from PG3. It still doesn't seem to want to connect to the broker... 2022-12-26 13:37:46,561 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2022-12-26 13:37:48,567 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.51 Starting... 2022-12-26 13:37:48,716 MainThread udi_interface.interface INFO interface:__init__: Initialization received from Polyglot V3 3.1.16 [ISY: 5.5.0, Slot: 1] 2022-12-26 13:37:48,718 MainThread udi_interface.interface INFO interface:__init__: Connect: Network Interface: {'addr': '192.168.10.248', 'netmask': '255.255.255.0', 'broadcast': '192.168.10.255'} 2022-12-26 13:37:48,720 Interface udi_interface.interface INFO interface:_startMqtt: Connecting to MQTT... localhost:1888 2022-12-26 13:37:48,723 MainThread udi_interface.interface WARNING interface:start: No node server version specified. Using deprecated server.json version 2022-12-26 13:37:48,723 MainThread udi_interface.interface WARNING interface:db_getNodeDrivers: mqctrl not found in database. 2022-12-26 13:37:48,724 MainThread udi_interface.interface WARNING interface:send: MQTT Send waiting on connection :: {'config': {'version': '0.0.10'}} 2022-12-26 13:37:48,767 MQTT udi_interface.interface INFO interface:_connect: MQTT Connected with result code 0 (Success) 2022-12-26 13:37:48,768 MQTT udi_interface.interface INFO interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:0d:b9:52:c7:30_1 - MID: 1 Result: 0 2022-12-26 13:37:48,774 MQTT udi_interface.interface INFO interface:_subscribe: MQTT Subscribed Succesfully for Message ID: 1 - QoS: (0,) 2022-12-26 13:37:51,729 MainThread udi_interface.interface INFO interface:addNode: Adding node MQTT Controller(mqctrl) [None] 2022-12-26 13:37:51,827 Thread-1 udi_interface ERROR mqtt-poly:parameter_handler: mqtt_user must be configured 2022-12-26 13:41:08,454 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: ofcbath not found in database. 2022-12-26 13:41:08,456 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: ofcsky not found in database. 2022-12-26 13:41:08,457 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: gymbath not found in database. 2022-12-26 13:41:08,459 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: gymsky not found in database. 2022-12-26 13:41:08,461 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: gymcloset not found in database. 2022-12-26 13:41:08,462 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: exthall not found in database. 2022-12-26 13:41:08,463 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: lincl not found in database. 2022-12-26 13:41:08,465 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: hallflr not found in database. 2022-12-26 13:41:08,466 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: ofccinta not found in database. 2022-12-26 13:41:08,467 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: gymcinta not found in database. 2022-12-26 13:41:08,469 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: emofc not found in database. 2022-12-26 13:41:08,471 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: hallcinta not found in database. 2022-12-26 13:41:08,472 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: itcl not found in database. 2022-12-26 13:41:08,473 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: pantry not found in database. 2022-12-26 13:41:08,475 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: kitisl not found in database. 2022-12-26 13:41:08,476 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: kitsky not found in database. 2022-12-26 13:41:08,477 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: socialbath not found in database. 2022-12-26 13:41:08,478 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: patisl not found in database. 2022-12-26 13:41:08,480 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: patsky not found in database. 2022-12-26 13:41:08,481 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: extsb not found in database. 2022-12-26 13:41:08,482 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: dintbl not found in database. 2022-12-26 13:41:08,485 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: dinsky not found in database. 2022-12-26 13:41:08,487 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: tersky not found in database. 2022-12-26 13:41:08,489 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: entstar not found in database. 2022-12-26 13:41:08,490 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: entry not found in database. 2022-12-26 13:41:08,492 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: living not found in database. 2022-12-26 13:41:08,493 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: livbar not found in database. 2022-12-26 13:41:08,495 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: livstar not found in database. 2022-12-26 13:41:08,497 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: waterroom not found in database. 2022-12-26 13:41:08,499 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: sbathcinta not found in database. 2022-12-26 13:41:08,500 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: extcact not found in database. 2022-12-26 13:41:08,502 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: extpantry not found in database. 2022-12-26 13:41:08,504 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: lvgcinta not found in database. 2022-12-26 13:41:08,505 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: emkitchen not found in database. 2022-12-26 13:41:08,507 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: mstsky not found in database. 2022-12-26 13:41:08,509 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: msttvsky not found in database. 2022-12-26 13:41:08,510 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: mstcl not found in database. 2022-12-26 13:41:08,512 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: mstbrsky not found in database. 2022-12-26 13:41:08,513 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: jacsky not found in database. 2022-12-26 13:41:08,515 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: extliving not found in database. 2022-12-26 13:41:08,517 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: lvgfloor not found in database. 2022-12-26 13:41:08,518 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: extmsteast not found in database. 2022-12-26 13:41:08,520 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: mstcinta not found in database. 2022-12-26 13:41:08,521 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: mstbrcinta not found in database. 2022-12-26 13:41:08,523 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: emfrontyd not found in database. 2022-12-26 13:41:08,525 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: emjac not found in database. 2022-12-26 13:41:08,526 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: svskit not found in database. 2022-12-26 13:41:08,528 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: svssky not found in database. 2022-12-26 13:41:08,529 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: svsbath not found in database. 2022-12-26 13:41:08,531 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: laundry not found in database. 2022-12-26 13:41:08,532 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: exteast not found in database. 2022-12-26 13:41:08,533 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: extsvs not found in database. 2022-12-26 13:41:08,535 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: svscinta not found in database. 2022-12-26 13:41:08,536 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: poolstor not found in database. 2022-12-26 13:41:08,538 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: empool not found in database. 2022-12-26 13:41:08,540 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: wsbath not found in database. 2022-12-26 13:41:08,541 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: wssky not found in database. 2022-12-26 13:41:08,543 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: parksky not found in database. 2022-12-26 13:41:08,544 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: extgym not found in database. 2022-12-26 13:41:08,546 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: parkbath not found in database. 2022-12-26 13:41:08,547 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: solar not found in database. 2022-12-26 13:41:08,549 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: emsouth not found in database. 2022-12-26 13:41:08,550 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: emnorth not found in database. 2022-12-26 13:41:08,552 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: elec not found in database. 2022-12-26 13:41:08,554 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: extgstpark not found in database. 2022-12-26 13:41:08,555 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: clrcinta not found in database. 2022-12-26 13:41:08,557 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: clrfan not found in database. 2022-12-26 13:41:08,558 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: clropen not found in database. 2022-12-26 13:41:08,561 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: clrclose not found in database. 2022-12-26 13:41:08,562 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: extbargdn not found in database. 2022-12-26 13:41:08,564 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: jacfloor not found in database. 2022-12-26 13:41:08,566 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: terrflrr not found in database. 2022-12-26 13:41:08,568 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: terrflrl not found in database. 2022-12-26 13:41:08,570 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: extzengdn not found in database. 2022-12-26 13:41:08,571 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: patfloor not found in database. 2022-12-26 13:41:08,573 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: clrtemp not found in database. 2022-12-26 13:41:08,575 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: cargate not found in database. 2022-12-26 13:41:08,577 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: sidegate not found in database. 2022-12-26 13:41:08,578 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: camgate not found in database. 2022-12-26 13:41:08,580 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: camhill not found in database. 2022-12-26 13:41:08,581 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: camlake not found in database. 2022-12-26 13:41:08,583 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: camdam not found in database. 2022-12-26 13:41:08,584 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: bedsidejr not found in database. 2022-12-26 13:41:08,586 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: bedsidehl not found in database. 2022-12-26 13:41:08,587 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: bluelamp not found in database. 2022-12-26 13:41:08,589 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: hometheater not found in database. 2022-12-26 13:41:08,590 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: orientes not found in database. 2022-12-26 13:41:08,592 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: gate not found in database. 2022-12-26 13:41:08,593 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: interior not found in database. 2022-12-26 13:41:08,595 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: exterior not found in database. 2022-12-26 13:41:08,596 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: guestsuite not found in database. 2022-12-26 13:41:08,598 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: cellar not found in database. 2022-12-26 13:41:08,600 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: workshop not found in database. 2022-12-26 13:41:08,601 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: parking not found in database. 2022-12-26 13:41:08,603 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: utility not found in database. 2022-12-26 13:41:08,604 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: pool not found in database. 2022-12-26 13:41:08,606 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: wall not found in database. 2022-12-26 13:41:08,607 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: cinta not found in database. 2022-12-26 13:41:08,609 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: floor not found in database. 2022-12-26 13:41:08,610 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: closet not found in database. 2022-12-26 13:41:08,612 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: sky not found in database. 2022-12-26 13:41:08,613 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: tech not found in database. 2022-12-26 13:41:08,615 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: floods not found in database. 2022-12-26 13:41:08,617 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: landscape not found in database. 2022-12-26 13:41:08,619 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: lamp not found in database. 2022-12-26 13:41:08,620 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: hanging not found in database. 2022-12-26 13:41:08,622 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: fan not found in database. 2022-12-26 13:41:08,624 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: social not found in database. 2022-12-26 13:41:08,625 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: mastersuite not found in database. 2022-12-26 13:41:08,627 Thread-4 udi_interface.interface WARNING interface:db_getNodeDrivers: emergency not found in database. 2022-12-26 13:41:13,394 Thread-3 udi_interface ERROR mqtt-poly:start: Error connecting to Poly MQTT broker [Errno 61] Connection refused 2022-12-26 14:38:21,217 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2022-12-26 14:38:23,631 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.51 Starting... 2022-12-26 14:38:23,768 MainThread udi_interface.interface INFO interface:__init__: Initialization received from Polyglot V3 3.1.16 [ISY: 5.5.0, Slot: 1] 2022-12-26 14:38:23,770 MainThread udi_interface.interface INFO interface:__init__: Connect: Network Interface: {'addr': '192.168.10.248', 'netmask': '255.255.255.0', 'broadcast': '192.168.10.255'} 2022-12-26 14:38:23,772 Interface udi_interface.interface INFO interface:_startMqtt: Connecting to MQTT... localhost:1888 2022-12-26 14:38:23,775 MainThread udi_interface.interface WARNING interface:start: No node server version specified. Using deprecated server.json version 2022-12-26 14:38:23,776 MainThread udi_interface.interface WARNING interface:db_getNodeDrivers: mqctrl not found in database. 2022-12-26 14:38:23,776 MainThread udi_interface.interface WARNING interface:send: MQTT Send waiting on connection :: {'config': {'version': '0.0.10'}} 2022-12-26 14:38:23,820 MQTT udi_interface.interface INFO interface:_connect: MQTT Connected with result code 0 (Success) 2022-12-26 14:38:23,822 MQTT udi_interface.interface INFO interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:0d:b9:52:c7:30_1 - MID: 1 Result: 0 2022-12-26 14:38:23,827 MQTT udi_interface.interface INFO interface:_subscribe: MQTT Subscribed Succesfully for Message ID: 1 - QoS: (0,) 2022-12-26 14:38:26,781 MainThread udi_interface.interface INFO interface:addNode: Adding node MQTT Controller(mqctrl) [None] 2022-12-26 14:38:32,755 Thread-3 udi_interface ERROR mqtt-poly:start: Error connecting to Poly MQTT broker [Errno 61] Connection refused 2022-12-26 15:37:33,577 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2022-12-26 15:37:37,924 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.51 Starting... 2022-12-26 15:37:38,381 MainThread udi_interface.interface INFO interface:__init__: Initialization received from Polyglot V3 3.1.16 [ISY: 5.5.0, Slot: 1] 2022-12-26 15:37:38,383 MainThread udi_interface.interface INFO interface:__init__: Connect: Network Interface: {'addr': '192.168.10.248', 'netmask': '255.255.255.0', 'broadcast': '192.168.10.255'} 2022-12-26 15:37:38,396 Interface udi_interface.interface INFO interface:_startMqtt: Connecting to MQTT... localhost:1888 2022-12-26 15:37:38,428 MainThread udi_interface.interface WARNING interface:start: No node server version specified. Using deprecated server.json version 2022-12-26 15:37:38,430 MainThread udi_interface.interface WARNING interface:db_getNodeDrivers: mqctrl not found in database. 2022-12-26 15:37:38,431 MainThread udi_interface.interface WARNING interface:send: MQTT Send waiting on connection :: {'config': {'version': '0.0.10'}} 2022-12-26 15:37:38,487 MQTT udi_interface.interface INFO interface:_connect: MQTT Connected with result code 0 (Success) 2022-12-26 15:37:38,489 MQTT udi_interface.interface INFO interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:0d:b9:52:c7:30_1 - MID: 1 Result: 0 2022-12-26 15:37:38,500 MQTT udi_interface.interface INFO interface:_subscribe: MQTT Subscribed Succesfully for Message ID: 1 - QoS: (0,) 2022-12-26 15:37:41,435 MainThread udi_interface.interface INFO interface:addNode: Adding node MQTT Controller(mqctrl) [None] 2022-12-26 15:37:47,676 Thread-3 udi_interface ERROR mqtt-poly:start: Error connecting to Poly MQTT broker [Errno 61] Connection refused 2022-12-26 16:08:43,160 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2022-12-26 16:08:49,272 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.51 Starting... 2022-12-26 16:08:49,799 MainThread udi_interface.interface INFO interface:__init__: Initialization received from Polyglot V3 3.1.16 [ISY: 5.5.0, Slot: 1] 2022-12-26 16:08:49,801 MainThread udi_interface.interface INFO interface:__init__: Connect: Network Interface: {'addr': '192.168.10.248', 'netmask': '255.255.255.0', 'broadcast': '192.168.10.255'} 2022-12-26 16:08:49,829 Interface udi_interface.interface INFO interface:_startMqtt: Connecting to MQTT... localhost:1888 2022-12-26 16:08:49,854 MainThread udi_interface.interface WARNING interface:start: No node server version specified. Using deprecated server.json version 2022-12-26 16:08:49,855 MainThread udi_interface.interface WARNING interface:db_getNodeDrivers: mqctrl not found in database. 2022-12-26 16:08:49,856 MainThread udi_interface.interface WARNING interface:send: MQTT Send waiting on connection :: {'config': {'version': '0.0.10'}} 2022-12-26 16:08:49,916 MQTT udi_interface.interface INFO interface:_connect: MQTT Connected with result code 0 (Success) 2022-12-26 16:08:49,917 MQTT udi_interface.interface INFO interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:0d:b9:52:c7:30_1 - MID: 1 Result: 0 2022-12-26 16:08:49,929 MQTT udi_interface.interface INFO interface:_subscribe: MQTT Subscribed Succesfully for Message ID: 1 - QoS: (0,) 2022-12-26 16:08:52,862 MainThread udi_interface.interface INFO interface:addNode: Adding node MQTT Controller(mqctrl) [None] 2022-12-26 16:08:59,417 Thread-3 udi_interface ERROR mqtt-poly:start: Error connecting to Poly MQTT broker [Errno 61] Connection refused Any help would be most welcome. It seems like I somehow really buggered up Polisy! Even if it tells me how to factory reset Polisy, and tells me how to install mosquitto properly. This has been a total disaster. I should have waited the extra couple of week and done a fresh start on eisy, keeping ISY/Polisy as a backup system... What a waste of a Boxing Day. Cheers

I think I may have a hint on what is wrong here: When I first started working with the MQTT server, I had to install a mosquitto broker ( I'm guessing that when I upgraded the OS to 13.1, all that got wiped out! and I need to start from scratch. Now, in this thread, @xKing talks about installing the broker on an RPi. When I try the same commands on polisy: sudo: apt-get: command not found [admin@polisy ~]$ sudo apt-get install mosquitto sudo: apt-get: command not found Can someone help me translate this into Polisy-Linux, please? Thanks

Thanks Bob; I did get rid of the "unmanaged"stuff. But Nothing seems to be working anymore. Admin console shows all of my sonoff switches, but won't control them, Google says it cannot reach Unversal devices. When try to do a sync with UD Mobile, it gives me a warning that 400+ items no longer exist etc. Major screw-up here. Also, the Node server configuration pages now show MacIDs instead of user names (the MQTT in particular should show my MQTT userid/password, no?) I think the best is to reset Polisy and all of the PGs and try for a restore from my ISY994 to my ISY994 and from PG2 to PG2. I think I'll wait to get the eisy delivered, with hopefully ZMatter migration, before I touch PG3 again. Too much of a PITA. Can you please tell me how to reset the PGs? Do I need to reset Polisy too? Thanks

The bad news is, I just tried to undo this whole shebang and revert to PG2, using ISY994 and look what I get?! The same "unmanaged"NS. Seems like the bug got introduced passing from OS12.x to 13.1...

Thanks; Until yesterday, I had PG2 running with ISY994 to still handle my Z-Wave devices and PG3 running IoP for all the non-Zwave sensored programs/devices. Both had mostly the same node servers and all was well. I now upgraded the OS to 13.1 so I could install the Zmatter dongle. And I seem to be having oodles of problems: The "unmanaged" NS in PG3 ZWave not transferring at all Since MQTT NS isn't loading, none of my lights can be controlled Every time I do a change (like deleting NS in PG3), Admin Console goes through 3 "updates" which take about 15 minutes each and nothing seems to change... AND, as I just mentioned, I screenshot PG2 data and deleted it, but after 40 mins, I still get the "unmanaged" NS, and no way to delete them. I did restart PG3 and rebooted Polisy, BTW. No dice If there is no way to delete, How do I REBOOT PG3, so I can start from scratch?

I was using an 18V power supply from within my alarm cabinet to power the Polisy Pro. With the new ZMatter board, I have to move the Polisy outside of that cabinet and to a location with better reception. I have no idea where I put the original supply. What power requirements does this box have? Voltage, amperage, connector ID/OD? Thanks.

I was able to log on, and transfer my PG2 data to PG3, or almost. Please look at the screenshot below. The three node servers that I transferred have "no data available", are "unmanaged". No way to manage them or otherwise modify them. I I tried to reinstall them, but they are would be going to a different slot. and I haven't found a way to delete them either, so I can reinstall them... Thanks for your help.

That was the ticket! Thanks @Techman

Greetings; Just updated my OI to 13 on my Polisy Pro. Did a first upgrade packages, which seemt to have worked fine. Now, when I launch IoX (5.4.5), I get an error stating that IoP is on 5.5.0, but admin console is lower version... Where can I find the new admin console, please? Thanks!

Thanks Geddy, Most helpful insights again. Yes, I'm using Upgrade packages now, trying to get PG3 to upgrade to 3.1.16... Since the house is mostly up and running now, I think it behooves me to wait a few days until the ZMatter dongle Firmware issue is resolved and then I'll migrate Z-Wave and retire the ISY994... Thanks again for your help!

mostly SOLVED! These are the steps I took to fix MOST of the problem: 1- From within PG3, I picked the second option of restoring PG2 into PG3 2- From withing IoP, I restored ISY994i 3- Rebooted PG3 and Admin Console and everything came on line 4- Added ELK, Sonos, WeatherLink and WOL, which all came on line once I exited and reentered Admin Console. I now have the ISY994 running on PG2, with only the programs that include Z-Wave sensors enabled. IoP is running on Polisy. QUESTION: Can I add the ISY994i to PG3 instead, or better to just wait for Zmatter dongle? Remaining issues: 1- I cannot seem to be able to upgrade PG3 to 6.1.16. It's stuck at 6.0.63 2- Google Home turns individual Tasmota MQTT switches on or off without a hitch. If, however I ask it to turn on a room with several switches (like Kitchen or Office), it executes (seemingly slower) and then tells me that it cannot reach Universal Devices... 3- It still refuses to open the Wine Cellar for my wife Heather!!! ( I think that once the the ZMatter dongle firmware is available and installed, I'll disconnect UD from Google Home, reset my Google Home account, reconnect and set it up again and readd my wife to it. This is a simple but tedious job and I don't want to repeat it needlessly. Thanks again for everyone's help. BTW, UD did reach out to me via suppor@...

Thanks @Geddy, that explains the odd behaviour. Correct. My bad I've been running Polisy nicely for about 2 years, with PG2. It was sitting in the closet from purchase until the house was ready until then. I ran quite well except for one major crash, which required @Michel Kohanim remote intervention (something about mongo db crashing) and vanishing passwords. I have the Z-wave 500 board and am running on 5.3.0 (one of you told me that I would not need to upgrade to 5.3.4 as suggested in the migration document you refer to above , since it only fixes a unit conversion bug). There was chatter about not being able to use the upgrade button with the pre-order units in some of the chats. I must have confused them. Finally, I just checked, in the Admin Console of the ISY, that Upgrade button obviously isn't available. Hence SSH... This is the pdf, I was following: I understand. I meant to say that once I had PG3 up and running, ISY994 wasn't responding anymore... before going to bed last night and stopping the trouble shooting, I had to disable PG3 via SSH and powrup 994 in order to control my lights again (UD Mobile works, but Google Voice controls are sketchy: individual lights work, programs don't). Started to follow this manual, with the hopes that it will straighten out the problem. However, already in step 3: 3. Backup your 994's Z-Wave dongle (Admin Console | Z-Wave | Utilities | Backup | Full) there is a discrepancy. I only get the choice of (Admin Console| Z-Wave|Backup). Additionally, after the backup it says "Backup successfully completed", but it doesn't tell me where. It is not in Downloads. The File|Backup ISY command does ask me where I want to back it up... Strange. I'm currently at 3.0.63, Tried to follow the steps in the link, it stays at 3.0.63... Good idea. I will resend and add my current findings. Thanks again for all the insight, Geddy. Seems like I'm stuck for now, until UD gets back to me.

Is stopped PG3 via SSH, turned the power to the ISY994i back on and everything is working again for now. When UD comes back on line and I can get a ticket issued and responded, we'll continue this saga. Very disappointing, I must say. I'm sure there's a good explanation to this. Thanks for all of your efforts to get this resolved. I'm going to bed!

This was the first time I went into SSH, following the Wiki pdf. I have one of the original pre-ordered Polisys. Unfortunately, I have no way of getting a hold of UD at this point. Their portal is down and when I write to support@... although they answer, I don't get their mail. I would see it in my ticket queue, but, I can't log on. Hopefully @Michel Kohanim will see this post and either fix the portal or send me a response from outside the ticket management system. Cheers;

In the meantime, onto the ELK NS. It shows connected in PG3 and I can see the different areas and sensors within NODES. However the ELK NS doesn't show up in the Admin Console 2022-12-10 20:38:47,137 Thread-63 udi_interface WARNING Controller:handler_poll: waiting for sync and node initialization to complete 2022-12-10 20:39:18,591 Thread-64 udi_interface WARNING Controller:handler_poll: waiting for sync and node initialization to complete 2022-12-10 20:39:48,838 Thread-65 udi_interface WARNING Controller:handler_poll: waiting for sync and node initialization to complete 2022-12-10 20:40:17,232 Thread-66 udi_interface WARNING Controller:handler_poll: waiting for sync and node initialization to complete 2022-12-10 20:40:19,526 Thread-67 udi_interface WARNING Controller:handler_poll: waiting for sync and node initialization to complete 2022-12-10 20:40:50,707 Thread-68 udi_interface WARNING Controller:handler_poll: waiting for sync and node initialization to complete 2022-12-10 20:41:22,802 Thread-69 udi_interface WARNING Controller:handler_poll: waiting for sync and node initialization to complete 2022-12-10 20:41:53,271 Thread-70 udi_interface WARNING Controller:handler_poll: waiting for sync and node initialization to complete 2022-12-10 20:42:06,650 Thread-71 udi_interface ERROR Controller:discover: ELK Controller: discover currently does nothing 2022-12-10 20:42:23,961 Thread-72 udi_interface WARNING Controller:handler_poll: waiting for sync and node initialization to complete 2022-12-10 20:42:55,019 Thread-73 udi_interface WARNING Controller:handler_poll: waiting for sync and node initialization to complete 2022-12-10 20:43:26,503 Thread-74 udi_interface WARNING Controller:handler_poll: waiting for sync and node initialization to complete 2022-12-10 20:43:57,636 Thread-75 udi_interface WARNING Controller:handler_poll: waiting for sync and node initialization to complete 2022-12-10 20:44:20,246 Thread-76 udi_interface WARNING Controller:handler_poll: waiting for sync and node initialization to complete 2022-12-10 20:44:31,042 Thread-77 udi_interface WARNING Controller:handler_poll: waiting for sync and node initialization to complete 2022-12-10 20:45:00,125 Thread-78 udi_interface WARNING Controller:handler_poll: waiting for sync and node initialization to complete 2022-12-10 20:45:30,726 Thread-79 udi_interface WARNING Controller:handler_poll: waiting for sync and node initialization to complete Here's the log file for ELK

is @Michel Kohanim aware of the log-on page being down?

Thanks for that important piece of information. In the meantime, I was able to get UD Mobile to connect to PG3. Progress. However, neither Mobile nor the Admin Console are giving me the status of my MQTT/Tasmota switches anymore... At least I can turn off the lights now (no mechanical switches in this house)

Thanks, some progress: Google still says that it cannot reach Universal Devices, but after 30 secs or so lights sequentially respond... The Home App still says it cant talk to UD though.

Hmmm... do I understand you correctly that in order for Google Home to communicate with my Polisy, the UD infrastructure needs to be up and running? Was I mistakenly thinking that Google would communicate directly with my Polisy?

I did a complete SSH upgrade following the Wiki document just a few hours ago. BTW, PG2 has a Polisy Update Button, but that option doesn't exist in PG3 anymore...

In the meantime, I tried to "reconnect to Universal Devices" From within the Google Home App. I get a "Could not reach Universal Devices". Definitely up a creek. And PG2 doesn't seem to be working together with PG3. In order to undo this mess, I think I have to completely delete or at least stop PG3, restart PG2 and turn on ISY994. Not really a smooth migration, is it? Especially when UD is unreachable...

yup. real bummer

I did... No answer. But that sometimes happens. They do answer, but it doesn't get to my email. It only shows in the ticket managments system. But since I can't log onto the ticket management system, I'm kinda up a creek...

Yup, when I do that, it tells me that I already migrated 93 commands. Yet Google Assistant tells me that it cannot connect to Universal devices. And, I lied, its not 5-8 seconds to log onto Polyglot, its more like 90-150 seconds.

Greetings; So, I was following the Wiki 994i to Polisy.pdf nicely. The ISY was showing up, I started configuring the three NS I have. Then, all of a sudden things came to a screeching halt, or to a crawl. Say I click on details of the MQTT NS, it shows up after about 5-8 secs of only the Polisy SW versions. I click configure. nothing for 5-8 secs. Then some fields show up. Then 5-8 later the config help shows up... I go back to the Dashboard and click the ELK NS. for about 8-10 secs it goes backt to MQTT NS. Then slowly things appear. When I go to the admin console, turning things on or off also takes 5-8 seconds. Oh, then, when I reboot Polyglot 3, it flashes to the my.isy.io screen, asking me to sign in. Same happens after the reboot. I go to my-IP:3000 and after a long while I get the user/password screen. when I enter the combo, I get flashed to my.isy.io again and back to the my-IP:3000. After a lot of thinking, it says it cannot find the ISY.... I tried soft resets and power cycles. No dice. Polisy is on 5.4.4. FIGURED THIS ONE OUT: Oh, and in my.isy.io i get the attached information, "pending approval by owner"... Even if I purchased the full year's license on top of the 30 day trial as suggested in the above Wiki... And to boot, UD's ticket system seems down, doesn't let me sign in. the buttons are missing. Please HEEEELP!