Jump to content
View in the app

A better way to browse. Learn more.
Universal Devices Forum

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

MQTT (for Sonoff) on PG2 AND PG3, not working after upgrading to OS 13.1 (trying to migrate to IoP)

TriLife
in Polisy

Featured Replies

Posted

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

There are a number of things that went badly here.

First, this probably isn't obvious but when you re-flash the SSD, you're are basically factory resetting the Polisy.  Before doing this you should make a IoX backup and a PG3 (and PG2 if it's being used) backup. 

You don't say what you had backed up and what you restored (if anything).  The first step after flashing the SSD should have been to restore the IoX and then restore PG3 (and PG2).  In theory, that should have brought everything back to the state it was before the re-flash.  Your description above doesn't provide any details on what steps you took here (maybe that's in the other thread?)  But based on the fact that PG3 was showing unmanaged, it sounds like you didn't restore PG3 from a backup.

Both PG2 and PG3 run internal MQTT brokers. I believe that PG2 actually runs it's internal broker on the standard MQTT port so installing Mosquitto would probably conflict with it unless you specifically started it using a different port. If Mosquitto was started before PG2, it would block PG2 and nothing in PG2 would work right.  Which is that looks like is happening based on the log information.

Now this also assumes that the image you flashed doesn't already have Mosquitto configured. For the eisy, we've started moving to using Mosquitto for the PG3 broker instead of the internal broker. The image may have that already enabled to prepare for the migration to PG3x.

I don't really know how @xKing's node server expects for MQTT broker configuration so I'm mostly just guessing that it may be conflicting.

    • Like 1
    • Author
    2 minutes ago, bpwwer said:

    There are a number of things that went badly here.

    First, this probably isn't obvious but when you re-flash the SSD, you're are basically factory resetting the Polisy.  Before doing this you should make a IoX backup and a PG3 (and PG2 if it's being used) backup. 

    You don't say what you had backed up and what you restored (if anything).  The first step after flashing the SSD should have been to restore the IoX and then restore PG3 (and PG2).  In theory, that should have brought everything back to the state it was before the re-flash.  Your description above doesn't provide any details on what steps you took here (maybe that's in the other thread?)  But based on the fact that PG3 was showing unmanaged, it sounds like you didn't restore PG3 from a backup.

    Both PG2 and PG3 run internal MQTT brokers. I believe that PG2 actually runs it's internal broker on the standard MQTT port so installing Mosquitto would probably conflict with it unless you specifically started it using a different port. If Mosquitto was started before PG2, it would block PG2 and nothing in PG2 would work right.  Which is that looks like is happening based on the log information.

    Now this also assumes that the image you flashed doesn't already have Mosquitto configured. For the eisy, we've started moving to using Mosquitto for the PG3 broker instead of the internal broker. The image may have that already enabled to prepare for the migration to PG3x.

    I don't really know how @xKing's node server expects for MQTT broker configuration so I'm mostly just guessing that it may be conflicting.

    Hi Bob;

    In 12x I had a mosquitto broker installed and running and it worked well.

    Before I started migration to IoP, I made backups of ISY994 from within Admin Console and also a backup of PG2.

    I then installed PG3 (yes, it runs on 12.2!) and did a partial migration to IoP, since the Z-wave dongle for Polisy wasn't (and apparently still isn't) functional. I left the Z-Wave programs on the ISY994 and move the rest to IoP, adding the ELK NS in the process. All this worked very well and I could notice a difference in speed in the response to Google voice commands.

    I vaguely recall spending time getting the mosquitto broker up and running with @xKingand @Michel Kohanim a few years back. PG2 didn't have an MQTT broker then as I recall.

    So, I would like to get back to where I was. I have ISY994 backups and PG2 backups from before 13.1.

    How do I go about it? If PG2 and PG3 have MQTT brokers built in, how do I configure them? all of my Tasmotas are on port 1884. (PG2 Config has an area to set ports and users etc, but I didn't find this on PG3)...

    Thansk again Bob, Cheers

     

    • Author

    oddly now, mosquitto seems to be running in two separate processes: 

    [admin@polisy ~]$ pgrep mosquitto
1169
1174
[admin@polisy ~]$

    "confusion" doesn't begin to describe my state right now

    • Author
    30 minutes ago, bpwwer said:

    You don't say what you had backed up and what you restored (if anything).  The first step after flashing the SSD should have been to restore the IoX and then restore PG3 (and PG2).  In theory, that should have brought everything back to the state it was before the re-flash.  Your description above doesn't provide any details on what steps you took here (maybe that's in the other thread?)  But based on the fact that PG3 was showing unmanaged, it sounds like you didn't restore PG3 from a backup.

    Yes, I did try to restore both PG2 and PG3 from the PG2 backup prior to beginning the migration. I didn't make a PG3 backup, because (maybe erroneously) I thought this was going to be a temporary affair, due to the lack of Z-Wave and that I would end up using the ISY994/PG2 backups as my base for the final step of migration. To tell you the truth though, I do not recall, if i restored ISY or PGx first...

    • Author
    34 minutes ago, bpwwer said:

    First, this probably isn't obvious but when you re-flash the SSD, you're are basically factory resetting the Polisy.  Before doing this you should make a IoX backup and a PG3 (and PG2 if it's being used) backup.

    Indeed, if that had been obvious, I would have bought another SSD and flashed it, in order to keep the 12.2 as a working backup. Live and learn! I even asked someone in the know about getting as spare SSD and was told "shouldn't be necessary". 

    • Author
    5 hours ago, bpwwer said:

    There are a number of things that went badly here.

    First, this probably isn't obvious but when you re-flash the SSD, you're are basically factory resetting the Polisy.  Before doing this you should make a IoX backup and a PG3 (and PG2 if it's being used) backup. 

    You don't say what you had backed up and what you restored (if anything).  The first step after flashing the SSD should have been to restore the IoX and then restore PG3 (and PG2).  In theory, that should have brought everything back to the state it was before the re-flash.  Your description above doesn't provide any details on what steps you took here (maybe that's in the other thread?)  But based on the fact that PG3 was showing unmanaged, it sounds like you didn't restore PG3 from a backup.

    Both PG2 and PG3 run internal MQTT brokers. I believe that PG2 actually runs it's internal broker on the standard MQTT port so installing Mosquitto would probably conflict with it unless you specifically started it using a different port. If Mosquitto was started before PG2, it would block PG2 and nothing in PG2 would work right.  Which is that looks like is happening based on the log information.

    Now this also assumes that the image you flashed doesn't already have Mosquitto configured. For the eisy, we've started moving to using Mosquitto for the PG3 broker instead of the internal broker. The image may have that already enabled to prepare for the migration to PG3x.

    I don't really know how @xKing's node server expects for MQTT broker configuration so I'm mostly just guessing that it may be conflicting.

    Hello Bob;

    So, I decided to reflash the SSD to get a clean slate.

    Both PG3 and PG2 showed up. I upgraded the packages. PG2 connected to the ISY994 and I restored PG2. The MQTT NS connected, but it is still refusing to connect to the MQTT broker:  

    2022-12-27 06:19:46,387 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Z4 Social
2022-12-27 06:19:46,389 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Z4 Social(social)
2022-12-27 06:19:46,390 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Z4 Master Suite
2022-12-27 06:19:46,392 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Z4 Master Suite(mastersuite)
2022-12-27 06:19:46,393 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Z4 Emergency
2022-12-27 06:19:46,394 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Z4 Emergency(emergency)
2022-12-27 06:19:46,395 Node Server polyinterface      INFO     mqtt-poly:start: Done adding nodes, connecting to MQTT broker...
2022-12-27 06:19:46,400 Node Server polyinterface      ERROR    mqtt-poly:start: Error connecting to Poly MQTT broker [Errno 61] Connection refused

    I'm reluctant to install the mosquitto broker, since you're telling me that PG2 and PG3 have their own brokers...

    all of my Tasmotas are operating on port 1884. Yet the Polyglot setting (PG2) is 1883

    image.thumb.png.5a813907a5fd22e9b87bbbd689bd2666.png

    Could that be the problem?

    Note that when I was getting ready to migrate from 12x, I took a screenshot of that same polyglot and it also has 1883 as the port (and all the tasmotas 1884)...

     

    Any help would be welcome at this point.

     

    cheers.

    • Author

    Ok, making progress;

    In 

    @gzahar explains what needs to be done with the mosquitto.conf file.

    I'm not very familiar with the sed command at all, and could use some help, confirming that I understood this correctly: 

    #!/bin/sh

PREFIX=/usr/local/etc/mosquitto
PASSWORD=`openssl rand -base64 8`
echo "Your Mosquitto user is: mqttuser"
echo "Your Mosquitto password is: ${PASSWORD}"

    PREFIX sets the path for legibility

    PASSWORD is generated randomly (I'll set this later as shown below)

    and the pair is echoed on the screen. 

    sed -i .bak -e 's/^port 1883/port 1884/' -e 's/^#allow_anonymous true$/allow_anonymous false/' -e 's/^#password_file$/password_file \/usr\/local\/etc\/mosquitto\/pwfile/' ${PREFIX}/mosquitto.conf

    I understand that the -e wants to replace:

    port 1883 --> port 1884 (except the new mosquitto.conf replaces this with "listener" default is 1883, I'll use 1884)

    #allow_anonymouse true --> allow_anonymous false (understood)

    #password_file --> password_file /usr/local/etc/mosquitto/pwfile (understood)

    inside the mosquitto.conf file (understood) 

    cp /dev/null ${PREFIX}/pwfile

    No idea what this means. Can you please explain 

    mosquitto_passwd -b ${PREFIX}/pwfile mqttuser ${PASSWORD}

    here we're adding the new user and password to the pwfile
      

    sysrc mosquitto_enable=YES

    not really sure what this is. Can you please explain?

      

    service mosquitto start

    this is fairly clear.

    The one remaining thing is that mosquitto needs to start by itself after a reboot. Will it do that, or do we need to add a line somewhere?

    I will save the current file as .old and modify .conf as explained above. Let's see what gives. Stay tuned

    Cheers

     

     

    • Author

    RATS!

    Ok, I executed the steps above. And rebooted Polisy to make sure. 

    sudo service mosquitto status

    confirmed that mosquitto is running on pid 1130. Oddly, 

    [admin@polisy ~]$ pgrep mosquitto
1130
1135

    pgrep shows two processes running. Not quite sure why.

     

    AAANNNDD: PG2 is not responding anymore and IoP disappeared from the IoX Launcher.

    So, it is confirmed that launching mosquitto crashes Polyglot somehow.

    Except, I didn't download mosquitto this time, it is already on the system. I just executed the steps I had done in June 2020. It must be said that mosquitto is now a very different rev.

    Could the fact that there are 2 processes running be the problem? How do I make sure only one runs?

    So, any help to solve this mystery would be welcome

    I can provide a bit of clarity on the commands above and for the most part they look correct. 

    cp /dev/null ${PREFIX}/pwfile

    This is simply making sure the pwfile is empty.  It is overwriting whatever was in pwfile with nothing (/dev/null) 

    sysrc mosquitto_enable=YES

    This is enabling the mosquitto service so that it starts up automatically whenever the Polisy is rebooted.

    You see two process id's when you grep for mosquitto because one is the mosquitto process and the other is the grep process itself. So that is normal.

    Even though both PG2 and PG3 have internal MQTT brokers, they aren't usable for anything other than PG2 and PG3 communication with node servers.  They're not general purpose MQTT brokers.  Running Mosquitto in addition should be fine as long as the port is different and 1884 is not used by either PG2 or PG3 and should be fine.

    The Mosquitto settings look correct and shouldn't effect either PG2 or PG3.  And it definitely shouldn't have any effect on IoX showing up in the finder.

    If you upgraded packages, that may be the issue now.  There have been issues with the latest updates, I'm not sure of the current status and if all the issues are resolved or not.   I'd suggest doing another upgrade and see if that helps the finder pick up the IoX.

    I'm also concerned that by upgrading packages you may have now removed PG2. I believe @Michel Kohanimhas removed PG2 packages now and if that's the case, then you're going to have to start over and get migrated to PG3 before upgrading any packages.  I.E.

    re-flash

    install mosquitto per above

    restore PG2 from backup

    migrate what's on PG2 to PG3 and make sure things are working.

    Then upgrade packages to get the latest IoX and PG3 installed.

    • Like 1
    • Author
    58 minutes ago, bpwwer said:

    I can provide a bit of clarity on the commands above and for the most part they look correct. 

    cp /dev/null ${PREFIX}/pwfile

    This is simply making sure the pwfile is empty.  It is overwriting whatever was in pwfile with nothing (/dev/null) 

    sysrc mosquitto_enable=YES

    This is enabling the mosquitto service so that it starts up automatically whenever the Polisy is rebooted.

    You see two process id's when you grep for mosquitto because one is the mosquitto process and the other is the grep process itself. So that is normal.

    Even though both PG2 and PG3 have internal MQTT brokers, they aren't usable for anything other than PG2 and PG3 communication with node servers.  They're not general purpose MQTT brokers.  Running Mosquitto in addition should be fine as long as the port is different and 1884 is not used by either PG2 or PG3 and should be fine.

    The Mosquitto settings look correct and shouldn't effect either PG2 or PG3.  And it definitely shouldn't have any effect on IoX showing up in the finder.

    If you upgraded packages, that may be the issue now.  There have been issues with the latest updates, I'm not sure of the current status and if all the issues are resolved or not.   I'd suggest doing another upgrade and see if that helps the finder pick up the IoX.

    I'm also concerned that by upgrading packages you may have now removed PG2. I believe @Michel Kohanimhas removed PG2 packages now and if that's the case, then you're going to have to start over and get migrated to PG3 before upgrading any packages.  I.E.

    re-flash

    install mosquitto per above

    restore PG2 from backup

    migrate what's on PG2 to PG3 and make sure things are working.

    Then upgrade packages to get the latest IoX and PG3 installed.

    Thanks Bob;

    Before I do another re-flash, I'd like to share a couple of log files.

    Here is the one from PG3's MQTT node server, at: 

    2022-12-27 13:32:22,569 Thread-6   udi_interface      WARNING  mqtt-poly:_on_disconnect: Poly MQTT disconnected, trying to re-connect
2022-12-27 13:34:22,593 Thread-6   udi_interface      WARNING  mqtt-poly:_on_disconnect: Poly MQTT disconnected, trying to re-connect
2022-12-27 13:36:22,634 Thread-6   udi_interface      WARNING  mqtt-poly:_on_disconnect: Poly MQTT disconnected, trying to re-connect
2022-12-27 13:40:14,562 MainThread udi_interface      INFO     polylogger:set_basic_config: set_basic_config: enable=True level=30
2022-12-27 13:40:16,750 MainThread udi_interface      INFO     __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.51 Starting...
2022-12-27 13:40:16,889 MainThread udi_interface.interface INFO     interface:__init__: Initialization received from Polyglot V3 3.1.16  [ISY: 5.5.0, Slot: 1]
2022-12-27 13:40:16,890 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-27 13:40:16,892 Interface  udi_interface.interface INFO     interface:_startMqtt: Connecting to MQTT... localhost:1888 <---- NOTE PORT 1888?
2022-12-27 13:40:16,895 MainThread udi_interface.interface WARNING  interface:start: No node server version specified. Using deprecated server.json version
2022-12-27 13:40:16,896 MainThread udi_interface.interface WARNING  interface:db_getNodeDrivers: mqctrl not found in database.  <----- what is mqctrl?
2022-12-27 13:40:16,897 MainThread udi_interface.interface WARNING  interface:send: MQTT Send waiting on connection :: {'config': {'version': '0.0.10'}}
2022-12-27 13:40:16,945 MQTT       udi_interface.interface INFO     interface:_connect: MQTT Connected with result code 0 (Success)
2022-12-27 13:40:16,946 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-27 13:40:16,953 MQTT       udi_interface.interface INFO     interface:_subscribe: MQTT Subscribed Succesfully for Message ID: 1 - QoS: (0,)
2022-12-27 13:40:19,918 MainThread udi_interface.interface INFO     interface:addNode: Adding node MQTT Controller(mqctrl) [None]
2022-12-27 13:40:25,791 Thread-3   udi_interface      ERROR    mqtt-poly:start: Error connecting to Poly MQTT broker [Errno 61] Connection refused  <----this would be normal since the broker isn't running right now

    Note comment on line 8 (why port 1888?). I thought PG3 operated on 1883...

    Note comment on line 10 (what is mqctrl?

    Also line 11 says a deprecated json version is being used

    But it seems to connect succesfully until last line: But we didn't start the broker...

     

    Now PG2: 

    2022-12-27 13:37:07,696 Thread-1   polyinterface      WARNING  mqtt-poly:_on_disconnect: Poly MQTT disconnected, trying to re-connect
2022-12-27 13:38:13,032 MQTT       polyinterface      DEBUG    polyinterface:_message: Received stop from Polyglot... Shutting Down.
2022-12-27 13:38:13,033 MQTT       polyinterface      INFO     polyinterface:stop: Disconnecting from MQTT... localhost:1884
2022-12-27 13:39:27,292 MainThread polyinterface      INFO     polylogger:set_basic_config: set_basic_config: enable=True level=30
2022-12-27 13:39:28,346 MainThread polyinterface      INFO     polyinterface:init_interface: Received Config from STDIN.
2022-12-27 13:39:28,347 MainThread polyinterface      INFO     __init__:<module>: UDI Polyglot v2 Interface 2.1.0 Starting...
2022-12-27 13:39:28,602 MainThread polyinterface      DEBUG    polyinterface:get_network_interface: gws: {'default': {2: ('192.168.10.1', 'igb0')}, 2: [('192.168.10.1', 'igb0', True)]}
2022-12-27 13:39:28,603 MainThread polyinterface      DEBUG    polyinterface:get_network_interface: gw: default=('192.168.10.1', 'igb0')
2022-12-27 13:39:28,604 MainThread polyinterface      DEBUG    polyinterface:get_network_interface: ifad: igb0=[{'addr': '192.168.10.248', 'netmask': '255.255.255.0', 'broadcast': '192.168.10.255'}]
2022-12-27 13:39:28,605 MainThread polyinterface      INFO     polyinterface:__init__: Connect: Network Interface: {'addr': '192.168.10.248', 'netmask': '255.255.255.0', 'broadcast': '192.168.10.255'}
2022-12-27 13:39:28,607 Interface  polyinterface      INFO     polyinterface:_startMqtt: Connecting to MQTT... localhost:1883
2022-12-27 13:39:28,678 MQTT       polyinterface      INFO     polyinterface:_connect: MQTT Connected with result code 0 (Success)
2022-12-27 13:39:28,680 MQTT       polyinterface      INFO     polyinterface:_connect: MQTT Subscribing to topic: udi/polyglot/ns/1 -  MID: 1 Result: 0
2022-12-27 13:39:28,682 MQTT       polyinterface      INFO     polyinterface:_connect: MQTT Subscribing to topic: udi/polyglot/connections/polyglot -  MID: 2 Result: 0
2022-12-27 13:39:28,683 MQTT       polyinterface      INFO     polyinterface:_connect: Sent Connected message to Polyglot
2022-12-27 13:39:28,692 MQTT       polyinterface      INFO     polyinterface:_subscribe: MQTT Subscribed Succesfully for Message ID: 1 - QoS: (0,)
2022-12-27 13:39:28,746 MQTT       polyinterface      INFO     polyinterface:_subscribe: MQTT Subscribed Succesfully for Message ID: 2 - QoS: (0,)
2022-12-27 13:39:29,219 Node Server polyinterface      INFO     mqtt-poly:start: Started MQTT controller
2022-12-27 13:39:30,977 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Office Bath
2022-12-27 13:39:30,979 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Office Bath(ofcbath)
2022-12-27 13:39:30,981 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Office Sky
2022-12-27 13:39:30,983 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Office Sky(ofcsky)
2022-12-27 13:39:30,985 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Gym Bath
2022-12-27 13:39:30,986 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Gym Bath(gymbath)
2022-12-27 13:39:30,989 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Gym Sky
2022-12-27 13:39:30,990 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Gym Sky(gymsky)
2022-12-27 13:39:30,993 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Gym Closet
2022-12-27 13:39:30,995 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Gym Closet(gymcloset)
2022-12-27 13:39:30,997 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Exterior Hallway
2022-12-27 13:39:30,999 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Exterior Hallway(exthall)
2022-12-27 13:39:31,001 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Linen Closet
2022-12-27 13:39:31,002 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Linen Closet(lincl)
2022-12-27 13:39:31,005 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Hallway Floor
2022-12-27 13:39:31,006 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Hallway Floor(hallflr)
2022-12-27 13:39:31,008 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Office Cinta
2022-12-27 13:39:31,009 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Office Cinta(ofccinta)
2022-12-27 13:39:31,011 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Gym Cinta
2022-12-27 13:39:31,012 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Gym Cinta(gymcinta)
2022-12-27 13:39:31,014 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Emergency Office
2022-12-27 13:39:31,015 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Emergency Office(emofc)
2022-12-27 13:39:31,016 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Hallway Cinta
2022-12-27 13:39:31,017 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Hallway Cinta(hallcinta)
2022-12-27 13:39:31,019 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch IT Closet
2022-12-27 13:39:31,020 Node Server polyinterface      INFO     polyinterface:addNode: Adding node IT Closet(itcl)
2022-12-27 13:39:31,022 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Pantry
2022-12-27 13:39:31,024 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Pantry(pantry)
2022-12-27 13:39:31,026 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Kitchen Island
2022-12-27 13:39:31,027 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Kitchen Island(kitisl)
2022-12-27 13:39:31,029 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Kitchen Sky
2022-12-27 13:39:31,031 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Kitchen Sky(kitsky)
2022-12-27 13:39:31,033 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Social Bath
2022-12-27 13:39:31,034 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Social Bath(socialbath)
2022-12-27 13:39:31,043 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Patio Island
2022-12-27 13:39:31,045 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Patio Island(patisl)
2022-12-27 13:39:31,047 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Patio Sky
2022-12-27 13:39:31,049 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Patio Sky(patsky)
2022-12-27 13:39:31,052 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Exterior Social Bath
2022-12-27 13:39:31,053 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Exterior Social Bath(extsb)
2022-12-27 13:39:31,063 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Dining Table
2022-12-27 13:39:31,065 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Dining Table(dintbl)
2022-12-27 13:39:31,067 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Dining Sky
2022-12-27 13:39:31,071 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Dining Sky(dinsky)
2022-12-27 13:39:31,074 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Terrace Sky
2022-12-27 13:39:31,076 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Terrace Sky(tersky)
2022-12-27 13:39:31,078 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Entry Starlight
2022-12-27 13:39:31,079 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Entry Starlight(entstar)
2022-12-27 13:39:31,081 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Entry
2022-12-27 13:39:31,083 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Entry(entry)
2022-12-27 13:39:31,085 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Living
2022-12-27 13:39:31,087 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Living(living)
2022-12-27 13:39:31,089 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Living Bar
2022-12-27 13:39:31,090 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Living Bar(livbar)
2022-12-27 13:39:31,092 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Living Starlight
2022-12-27 13:39:31,094 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Living Starlight(livstar)
2022-12-27 13:39:31,096 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Water Room
2022-12-27 13:39:31,098 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Water Room(waterroom)
2022-12-27 13:39:31,100 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Social Bath Cinta
2022-12-27 13:39:31,101 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Social Bath Cinta(sbathcinta)
2022-12-27 13:39:31,104 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Exterior Cactus Garden
2022-12-27 13:39:31,106 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Exterior Cactus Garden(extcact)
2022-12-27 13:39:31,108 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Exterior Pantry
2022-12-27 13:39:31,109 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Exterior Pantry(extpantry)
2022-12-27 13:39:31,112 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Living Cinta
2022-12-27 13:39:31,113 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Living Cinta(lvgcinta)
2022-12-27 13:39:31,116 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Emergency Kitchen
2022-12-27 13:39:31,117 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Emergency Kitchen(emkitchen)
2022-12-27 13:39:31,120 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Master Sky
2022-12-27 13:39:31,121 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Master Sky(mstsky)
2022-12-27 13:39:31,123 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Master TV Sky
2022-12-27 13:39:31,125 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Master TV Sky(msttvsky)
2022-12-27 13:39:31,127 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Master Closet
2022-12-27 13:39:31,129 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Master Closet(mstcl)
2022-12-27 13:39:31,131 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Master Bath Sky
2022-12-27 13:39:31,132 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Master Bath Sky(mstbrsky)
2022-12-27 13:39:31,134 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Jacuzzi Sky
2022-12-27 13:39:31,136 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Jacuzzi Sky(jacsky)
2022-12-27 13:39:31,138 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Exterior Living
2022-12-27 13:39:31,140 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Exterior Living(extliving)
2022-12-27 13:39:31,142 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Living Floor
2022-12-27 13:39:31,143 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Living Floor(lvgfloor)
2022-12-27 13:39:31,145 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Exterior Master East
2022-12-27 13:39:31,147 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Exterior Master East(extmsteast)
2022-12-27 13:39:31,149 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Master Cinta
2022-12-27 13:39:31,151 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Master Cinta(mstcinta)
2022-12-27 13:39:31,153 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Master Bath Cinta
2022-12-27 13:39:31,155 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Master Bath Cinta(mstbrcinta)
2022-12-27 13:39:31,156 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Emergency Front Yard
2022-12-27 13:39:31,158 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Emergency Front Yard(emfrontyd)
2022-12-27 13:39:31,160 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Emergency Jacuzzi
2022-12-27 13:39:31,161 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Emergency Jacuzzi(emjac)
2022-12-27 13:39:31,163 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Service Kitchen
2022-12-27 13:39:31,165 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Service Kitchen(svskit)
2022-12-27 13:39:31,172 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Service Sky
2022-12-27 13:39:31,175 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Service Sky(svssky)
2022-12-27 13:39:31,177 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Service Bath
2022-12-27 13:39:31,181 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Service Bath(svsbath)
2022-12-27 13:39:31,184 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Laundry
2022-12-27 13:39:31,186 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Laundry(laundry)
2022-12-27 13:39:31,188 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Exterior Service East
2022-12-27 13:39:31,190 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Exterior Service East(exteast)
2022-12-27 13:39:31,192 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Exterior Service
2022-12-27 13:39:31,194 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Exterior Service(extsvs)
2022-12-27 13:39:31,196 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Service Cinta
2022-12-27 13:39:31,198 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Service Cinta(svscinta)
2022-12-27 13:39:31,200 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Pool Storage
2022-12-27 13:39:31,201 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Pool Storage(poolstor)
2022-12-27 13:39:31,204 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Emergency Pool
2022-12-27 13:39:31,205 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Emergency Pool(empool)
2022-12-27 13:39:31,207 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Workshop Bath
2022-12-27 13:39:31,209 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Workshop Bath(wsbath)
2022-12-27 13:39:31,211 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Workshop Sky
2022-12-27 13:39:31,215 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Workshop Sky(wssky)
2022-12-27 13:39:31,218 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Parking
2022-12-27 13:39:31,219 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Parking(parksky)
2022-12-27 13:39:31,232 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Exterior Gym
2022-12-27 13:39:31,233 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Exterior Gym(extgym)
2022-12-27 13:39:31,235 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Parking Bath
2022-12-27 13:39:31,237 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Parking Bath(parkbath)
2022-12-27 13:39:31,240 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Solar
2022-12-27 13:39:31,241 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Solar(solar)
2022-12-27 13:39:31,249 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Emergency Parking South
2022-12-27 13:39:31,251 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Emergency Parking South(emsouth)
2022-12-27 13:39:31,275 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Emergency Parking North
2022-12-27 13:39:31,276 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Emergency Parking North(emnorth)
2022-12-27 13:39:31,278 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Electrical Room
2022-12-27 13:39:31,280 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Electrical Room(elec)
2022-12-27 13:39:31,282 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Exterior Guest Parking
2022-12-27 13:39:31,283 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Exterior Guest Parking(extgstpark)
2022-12-27 13:39:31,287 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Cellar Light
2022-12-27 13:39:31,289 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Cellar Light(clrcinta)
2022-12-27 13:39:31,292 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Cellar Fan
2022-12-27 13:39:31,293 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Cellar Fan(clrfan)
2022-12-27 13:39:31,296 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Open Cellar
2022-12-27 13:39:31,298 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Open Cellar(clropen)
2022-12-27 13:39:31,301 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Close Cellar
2022-12-27 13:39:31,303 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Close Cellar(clrclose)
2022-12-27 13:39:31,305 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Exterior Bar Garden
2022-12-27 13:39:31,307 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Exterior Bar Garden(extbargdn)
2022-12-27 13:39:31,310 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Jacuzzi Floor
2022-12-27 13:39:31,311 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Jacuzzi Floor(jacfloor)
2022-12-27 13:39:31,313 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Terrace Floor Right
2022-12-27 13:39:31,315 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Terrace Floor Right(terrflrr)
2022-12-27 13:39:31,317 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Terrace Floor Left
2022-12-27 13:39:31,319 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Terrace Floor Left(terrflrl)
2022-12-27 13:39:31,321 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Exterior Zen Garden
2022-12-27 13:39:31,322 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Exterior Zen Garden(extzengdn)
2022-12-27 13:39:31,325 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Patio Floor
2022-12-27 13:39:31,327 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Patio Floor(patfloor)
2022-12-27 13:39:31,329 Node Server polyinterface      INFO     mqtt-poly:start: Adding TempHumid Cellar Temp
2022-12-27 13:39:31,331 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Cellar Temp(clrtemp)
2022-12-27 13:39:31,333 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Car Gate
2022-12-27 13:39:31,335 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Car Gate(cargate)
2022-12-27 13:39:31,337 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Side Gate
2022-12-27 13:39:31,338 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Side Gate(sidegate)
2022-12-27 13:39:31,341 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Camera Gate
2022-12-27 13:39:31,343 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Camera Gate(camgate)
2022-12-27 13:39:31,345 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Camera Hill
2022-12-27 13:39:31,346 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Camera Hill(camhill)
2022-12-27 13:39:31,348 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Camera Lake
2022-12-27 13:39:31,350 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Camera Lake(camlake)
2022-12-27 13:39:31,352 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Camera Dam
2022-12-27 13:39:31,354 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Camera Dam(camdam)
2022-12-27 13:39:31,356 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Bedside JR
2022-12-27 13:39:31,358 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Bedside JR(bedsidejr)
2022-12-27 13:39:31,360 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Bedside Heather
2022-12-27 13:39:31,361 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Bedside Heather(bedsidehl)
2022-12-27 13:39:31,364 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Blue Desk Lamp
2022-12-27 13:39:31,365 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Blue Desk Lamp(bluelamp)
2022-12-27 13:39:31,367 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Home Theater
2022-12-27 13:39:31,369 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Home Theater(hometheater)
2022-12-27 13:39:31,371 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Z1 Orientes
2022-12-27 13:39:31,372 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Z1 Orientes(orientes)
2022-12-27 13:39:31,414 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Z1 Gate
2022-12-27 13:39:31,416 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Z1 Gate(gate)
2022-12-27 13:39:31,418 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Z2 Interior
2022-12-27 13:39:31,420 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Z2 Interior(interior)
2022-12-27 13:39:31,421 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Z2 Exterior
2022-12-27 13:39:31,423 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Z2 Exterior(exterior)
2022-12-27 13:39:31,425 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Z2 Guest Suite
2022-12-27 13:39:31,426 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Z2 Guest Suite(guestsuite)
2022-12-27 13:39:31,428 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Z2 Cellar
2022-12-27 13:39:31,429 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Z2 Cellar(cellar)
2022-12-27 13:39:31,431 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Z2 WorkShop
2022-
12-27 13:39:31,433 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Z2 WorkShop(workshop)
2022-12-27 13:39:31,435 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Z2 Parking
2022-12-27 13:39:31,436 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Z2 Parking(parking)
2022-12-27 13:39:31,438 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Z2 Utility
2022-12-27 13:39:31,439 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Z2 Utility(utility)
2022-12-27 13:39:31,441 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Z2 Pool
2022-12-27 13:39:31,442 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Z2 Pool(pool)
2022-12-27 13:39:31,444 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Z3 Wall
2022-12-27 13:39:31,446 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Z3 Wall(wall)
2022-12-27 13:39:31,447 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Z3 Cinta
2022-12-27 13:39:31,449 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Z3 Cinta(cinta)
2022-12-27 13:39:31,451 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Z3 Floor
2022-12-27 13:39:31,452 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Z3 Floor(floor)
2022-12-27 13:39:31,455 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Z3 Closet
2022-12-27 13:39:31,456 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Z3 Closet(closet)
2022-12-27 13:39:31,458 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Z3 Sky
2022-12-27 13:39:31,461 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Z3 Sky(sky)
2022-12-27 13:39:31,463 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Z3 Tech
2022-12-27 13:39:31,465 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Z3 Tech(tech)
2022-12-27 13:39:31,467 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Z3 Floods
2022-12-27 13:39:31,468 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Z3 Floods(floods)
2022-12-27 13:39:31,470 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Z3 Landscape
2022-12-27 13:39:31,471 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Z3 Landscape(landscape)
2022-12-27 13:39:31,473 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Z3 Lamp
2022-12-27 13:39:31,475 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Z3 Lamp(lamp)
2022-12-27 13:39:31,477 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Z3 Hanging
2022-12-27 13:39:31,478 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Z3 Hanging(hanging)
2022-12-27 13:39:31,480 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Z3 Fan
2022-12-27 13:39:31,481 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Z3 Fan(fan)
2022-12-27 13:39:31,483 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Z4 Social
2022-12-27 13:39:31,484 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Z4 Social(social)
2022-12-27 13:39:31,486 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Z4 Master Suite
2022-12-27 13:39:31,487 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Z4 Master Suite(mastersuite)
2022-12-27 13:39:31,489 Node Server polyinterface      INFO     mqtt-poly:start: Adding switch Z4 Emergency
2022-12-27 13:39:31,491 Node Server polyinterface      INFO     polyinterface:addNode: Adding node Z4 Emergency(emergency)
2022-12-27 13:39:31,492 Node Server polyinterface      INFO     mqtt-poly:start: Done adding nodes, connecting to MQTT broker...
2022-12-27 13:39:31,500 Node Server polyinterface      ERROR    mqtt-poly:start: Error connecting to Poly MQTT broker [Errno 61] Connection refused

    it works on 1883 alright and seems to connect. (at the beginning you see me shutting down after I change from 1884 to 1883)

    I get the same [Errno61] as in PG3, again because the broker isn't running

    1 hour ago, bpwwer said:

    If you upgraded packages, that may be the issue now.  There have been issues with the latest updates, I'm not sure of the current status and if all the issues are resolved or not.   I'd suggest doing another upgrade and see if that helps the finder pick up the IoX.

    I think you are right. This has something to do with upgraded packages.

    I just asked @Michel Kohanim for a 12.2 version, which I can reflash. He doesn't have one... so we're stuck trying to get this to work. With so many moving parts, this is not going to be fun.

    I'll re-flash with 13.1 and won't upgrade. Let's see, if we can get it to work on PG2 first. I won't even touch IoP as a first pass.

    BTW, on 12.2 i was able to restore PG2 onto PG3. This no longer works!

    38 minutes ago, TriLife said:

    Note comment on line 8 (why port 1888?). I thought PG3 operated on 1883...

    Note comment on line 10 (what is mqctrl?

    Also line 11 says a deprecated json version is being used

    But it seems to connect succesfully until last line: But we didn't start the broker...

     

    PG3 uses 1888, PG2 uses 1883.  Different ports so they don't conflict with each other.

    mqctrl is a node name (or address). It is a node created by the node server.  The log entry is just saying that when the node server started, it PG3 didn't find an existing node called mqctrl in it's database.  This will always be the case when a node server first starts, none of it's nodes will be in the PG3 database.

    It's a warning mostly to the node server developer.  We used to get the node server version from a file but now expect the node server to handle it internally.  This node server is still getting the node server version from the file.

    Yes, the node server started correctly but then was unable to connect to a broker.  It has nothing to do with the internal broker that PG3 is running.  There needs to be another generic broker running somewhere that the node server can connect to.

    I'm not familiar with the mqtt-poly nod server so I'm mostly guessing that it needs a generic broker running.  I know it won't work with the PG3 internal broker since that has authentication requirements that the node server won't know.

    I'm not sure about the PG2 internal broker and it's relationship with the mqtt-poly node server.

     

    48 minutes ago, TriLife said:

    BTW, on 12.2 i was able to restore PG2 onto PG3. This no longer works!

    The OS doesn't make difference but the version of PG3 might.  The ability to restore PG2 backups on PG3 was somewhat supported with the initial PG3 production versions but because of the licensing requirements for PG3 node servers, it's probably not going to work for current PG3 production versions. 

    • Thanks 1
    • Author

    Look at this beauty! this is the stream of data of mosquitto broker accepting my Tasmota switches!!! 

    [admin@polisy /usr/local/etc/mosquitto]$ sudo service mosquitto start
Starting mosquitto.
1672169950: The 'port' option is now deprecated and will be removed in a future version. Please use 'listener' instead.
1672169950: mosquitto version 2.0.13 starting
1672169950: Config loaded from /usr/local/etc/mosquitto/mosquitto.conf.
1672169950: Opening ipv6 listen socket on port 1884.
1672169950: Opening ipv4 listen socket on port 1884.
1672169950: mosquitto version 2.0.13 running
[admin@polisy /usr/local/etc/mosquitto]$ 1672169950: New connection from 192.168.10.101:51626 on port 1884.
1672169950: New client connected from 192.168.10.101:51626 as DVES_925B39 (p2, c1, k30, u'Orientes').
1672169950: New connection from 192.168.10.83:54157 on port 1884.
1672169950: New client connected from 192.168.10.83:54157 as DVES_4BC9DB (p2, c1, k30, u'Orientes').
1672169951: New connection from 192.168.10.17:62094 on port 1884.
1672169951: New client connected from 192.168.10.17:62094 as DVES_5AC5B4 (p2, c1, k30, u'Orientes').
1672169959: New connection from 192.168.10.92:54723 on port 1884.
1672169959: New client connected from 192.168.10.92:54723 as DVES_4BC9FA (p2, c1, k30, u'Orientes').
1672169961: New connection from 192.168.10.23:59287 on port 1884.
1672169961: New client connected from 192.168.10.23:59287 as DVES_953E73 (p2, c1, k30, u'Orientes').
1672169965: New connection from 192.168.10.122:59118 on port 1884.
1672169965: New client connected from 192.168.10.122:59118 as DVES_8E1BEE (p2, c1, k30, u'Orientes').
1672169967: New connection from 192.168.10.143:52155 on port 1884.
1672169967: New client connected from 192.168.10.143:52155 as DVES_1F4DC5 (p2, c1, k30, u'Orientes').
1672169968: New connection from 192.168.10.121:49273 on port 1884.
1672169968: New client connected from 192.168.10.121:49273 as DVES_A192B6 (p2, c1, k30, u'Orientes').

    Following your recommended steps of:

    re-flash, configure mosquito.conf restore ISY and PG2 (and NO upgrade packages) we're up and running!

    Google Voice is not yet communicating with Universal Devices, but that is likely because I need to renew that connection. And I still have both ISY and IoP on the ISY Portal...

    Not daring to open PG3 right now!

    At least I have my house back!

    Thanks soooo much for leading me through this @bpwwer and @Michel Kohanim.

    I am interested when you figure out how to get this working in PG3 how to install fresh. I have no experience with mqtt however it sounds interesting to play around with. There is pretty much no instructions how to get it working.

    • Author

    Ok, I couldn't resist.

    PG3 is now also running and Google Voice is back!

    PG3: 3.1.15, Frontend: 3.1.15, IoP: 5.4.5

    PG2: 2.2.13, Frontend: 2.2.9-5, ISY: 5.3.0

     

    Here are the next steps, for which I'm going to need help. Important, given that PG2 is about to disappear.

    ISY994 has the built-in Zwave dongle and is handling my 20+ motion sensors (Aeotec multisensor 6). I also have an ELK alarm system, which I was able to migrate to the ELK Node Server on PG3.

    I understand from @Michel Kohanim that the Zmatter dongle for Polisy/eisy (I removed it from Polisy to elimitate vaiables) is not yet ready for migrating Z-wave...

    Seems like I will need ISY994 for the foreseeable future to handle my Zwave devices.

    1- What is the safest iterative path to move ISY994 from PG2 to PG3 and then disable PG2, so we can make sure this setup will continue working? Especially with eisy, which will no longer have PG2?

    2- Also, as seen above, all of my versions are a bit dated, but are stable. Is there a less painful way than reflashing the SSD to try out more current versions?

    Cheers! 

    • Author
    3 minutes ago, brians said:

    I am interested when you figure out how to get this working in PG3 how to install fresh. I have no experience with mqtt however it sounds interesting to play around with. There is pretty much no instructions how to get it working.

    I will put together a how-to guide. I owe this forum at least that much!

    • Like 1
    • Author
    6 minutes ago, brians said:

    I am interested when you figure out how to get this working in PG3 how to install fresh. I have no experience with mqtt however it sounds interesting to play around with. There is pretty much no instructions how to get it working.

    I just ordered a couple of 32GB mSATA SSDs, so we can try a cold start. It'll take a couple of weeks to get here.

    41 minutes ago, TriLife said:

    1- What is the safest iterative path to move ISY994 from PG2 to PG3 and then disable PG2, so we can make sure this setup will continue working? Especially with eisy, which will no longer have PG2?

    I believe a number of people have documented what they did to migrate from PG2 to PG3.  At this point, most PG3 versions of the node servers have continued to get updated while the PG2 versions have not, I'd recommend just deleting the PG2 version and installing the PG3 version.   You can try the PG3 re-install option but then you run the risk of the PG2 version causing issues later.

    When you configure PG3 with the ISY994 it should show all the PG2 node servers as unmanages (because PG2 is currently managing them). 

    One-by-one.

    1. document the configuration in PG2 (screen shot of config page, cut-n-paste values, write them down, whatever).  Then delete the node server from PG2. 

    2. Within a few minutes, PG3 should then show that slot as empty.  Install the PG3 version to the same slot and then using the configuration info you saved above, re-configure it.

    49 minutes ago, TriLife said:

    2- Also, as seen above, all of my versions are a bit dated, but are stable. Is there a less painful way than reflashing the SSD to try out more current versions?

    Your PG3 version is only one minor version out of date.  3.1.15 is stable and should be fine for now.  When you're no longer using PG2, you should be able to an 'update packages' to update to the latest versions.  No re-flashing necessary.   I believe the only thing missing with IoP 5.4.5 is the ZMatter board support so you'll have to update the packages before you want to migrate your z-wave anyway.  The main thing to finish is the getting PG2 migrated to PG3 before upgrading.

    • Like 1
    • Author

    Thanks Bob;

    Is there a way to back up create an image of the whole SSD? Just in case I manage to bungle it like yesterday?

    Cheers

    51 minutes ago, TriLife said:

    Is there a way to back up create an image of the whole SSD?

    See if this is what you're looking for. Haven't ever tried it and not sure if it's of value, but might be worth trying out.

     

    • Like 1
    • Author

    Good morning;

    Slightly off topic, but as I'm getting ready to move ISY from PG2 to PG3, I want to synchronize usernames...

    image.png.151d65a8891c1fb37ee706493d0bb7ce.png

    I'm getting this! My current username is 6 letters long. this one is 8...

    It's the same 8 letter username that I have in IoP...

    The log doesn't show anything.

    While we're at it, why aren't my ACTUAL user names listed? It sure would make life easier...

    image.png.b73ac7d919a26129200010e2b68eb2e4.png

    Cheers

     

    • Author
    22 hours ago, bpwwer said:

    2. Within a few minutes, PG3 should then show that slot as empty.  Install the PG3 version to the same slot and then using the configuration info you saved above, re-configure it.

    Hello Bob;

    As you said, in PG3 the two node servers on ISY were showing as " unmanaged" .

    So, I recorded the details and deleted first the DavisWeather node from PG2, leaving MQTT in place. after about half an hour, it still showed unmanaged. So I went ahead and deleted MQTT from PG2 as well.

    When I say "delete", I mean deleted from PG2, not from within ISY!

    It's been more than an hour now. they both still show as "unmanaged" on PG3...

    I rebooted Polisy and ISY. No change. I also changed the credentials for ISY inside PG2 just now, just to make sure it is no longer connected to ISY. No dice.

    Cheers.

    Edited by TriLife

    • Author
    25 minutes ago, TriLife said:

    Hello Bob;

    As you said, in PG3 the two node servers on ISY were showing as " unmanaged" .

    So, I recorded the details and deleted first the DavisWeather node from PG2, leaving MQTT in place. after about half an hour, it still showed unmanaged. So I went ahead and deleted MQTT from PG2 as well.

    When I say "delete", I mean deleted from PG2, not from within ISY!

    It's been more than an hour now. they both still show as "unmanaged" on PG3...

    I rebooted Polisy and ISY. No change. I also changed the credentials for ISY inside PG2 just now, just to make sure it is no longer connected to ISY. No dice.

    Cheers.

    The fix to this was restoring PG2 into PG3... I'm up and running now on PG3 only with IoP and ISY, with the minor detail of:

    4 hours ago, TriLife said:

    I'm getting this! My current username is 6 letters long. this one is 8...

    It's the same 8 letter username that I have in IoP.

    No big deal, but then again, I'm anal!

    As I mentioned earlier, I ordered a brand new 32GB SSD. Should get it next week. Once I have it, I'll try to document the following to help get users with an old OS and MQTT devices to migrate to PG3:

    Pre-1: back  up everything!

    1- Flash OS13.1

    2- Edit and save mosquitto.conf

    3- Edit rc so mosquitto starts on reboot

    4- start mosquitto

    5- restore ISY into IoP

    6- restore PG3

    7- make sure all is running

    8- do a Upgrade Packages from IoP... (I left this to last, since I do not yet dare upgrade to 3.1.16 and 5.5.0)

    (feel free to comment on the above!)

    Thanks again for all the input @bpwwer and @Michel Kohanim. You guys are awesome!

    Cheers

     

    • Author

    NO DICE.

    The bottom line seems to be that MQTT doesn't like operating on PG3 running ISY and IoP at the same time. It crashed.

    So, I'm back to PG2, since as of now there is no migration path for Z-Wave on Zmatter/PG3.

    Once that is available and I have my eisy here, I'll have an operating ISY/Polisy system and can try to migrate the whole shebang to IoP/eisy.

    Until then, I'm done with screwing around. Not worth my while.

    I'll still do the migration guide, once we have a Zwave migration for PG3 on Zmatter.

    Once again thank you @bpwwer and @Michel Kohanim for trying to help out. Sorry I wasted all of your time trying to find an interim solution. Lesson learned.

    Guest
    This topic is now closed to further replies.
    Go to topic listing

    Configure browser push notifications
    Chrome (Android)
    1. Tap the lock icon next to the address bar.
    2. Tap Permissions → Notifications.
    3. Adjust your preference.
    Chrome (Desktop)
    1. Click the padlock icon in the address bar.
    2. Select Site settings.
    3. Find Notifications and adjust your preference.