bigDvette

I had similar experience. If you click manually it will show the password. Still couldn't get it to finish.

Well, it isn't working. I cleared java cache, downloaded start.jnlp again and re-installed. Upon launch the Polisy and my 994 are in the list, no eisy. I can add it manually and it finds it and loads the model and isy version. I open the admin console and go to configuration page. You can see no timezone is selected. The clock is off by 2 hours (to pacific from central). I select dallas and click ok. Come back, still nothing selected. At top of screen the time has adjusted 5 hours backwards to 7:04 am, it is really 3:04 pm. If I ssh in to eisy the time there is still set as pacific time. On the PG3 front, sometimes I can't even log in. currently I can not. It redirects me to portal for login, and then local login to webpage just won't even login. I tried localhost, 127.0.0.1, the actual IP and nothing works. Any way to start over? I also couldn't get wifi setup to work, ended up plugging in to the wired connection. happy to allow some debugging on this box. I did do a restore from my polisy backup so I have nodes. I know zwave has migration issues, but can't I move the insteon PLM. I only have 7 zwave devices and was considering re-doing the zwave piece.

1). I can not set the time in eisy. You click change location, you can pick a location and then it adjusts the time but incorrectly. If you close the admin console and re-open is has lost the setting. 2). I can not get the pg3 to discover the isy. I can add the isy manually and it simply will not connect. Can't continue testing until these work. The eisy is on 5.5.0.

I want to move from my Polisy to the Eisy. I got as far as setting up the eisy in portal and remembered the last time I had dead hardware. So a few questions. Despite the fact I can't get the PG3 to see the IoX and adding it manually doesn't help, how will we move our purchased node servers to the new Eisy from the Polisy. They show up as different devices in my.isy.io. How do we migrate all the Amazon / Google and other integrations from the portal to the new Eisy. Can we use the zooz 700 stick with the Eisy? Is it as simple as after we restore the Eisy from the Polisy, you plug in the PML and ZooZ stick and it should work? I can't get auto discover to work on the network. I end up having to add it to the launcher manually and if I restart I have to re-add it again (after delete) or it never detects the version. In ISY portal is says version is 5.5.0. I the about page it says it is 5.4.5. Again, can't get pg3 to see the ivy and setting up localhost:8080 or 127.0.0.1:8080 or even the ip address:8080 seems to work. Anyone have any luck migrating off a policy to the eisy.

Sorry I posted and ran. Had some family stuff over holidays. I updated yesterday and it does seem to work now. I did remove my nodes (thermostats) and re-scan for them after removing and re-installing the node server.

The PG3 version has a similar problem to the PG2 version. The Heat/Cool State shows correctly on the device screen (Idle, Heating, Cooling ...). However, the Heat/Cool State can not be used for any programs. Currently I am using a workaround to look at Mode and Fan State (check if On) to know if it is running, but would be nice to be able to use Heat/Cool State in programs. It doesn't trigger regardless of value and you can see in the programs the if statement is never true regardless of the value used in the statement.

No, I've rebooted ISY and Polisy multiple times. None of my wireless devices are working. I did figured out the other motion sensor not working, somehow the option of when to report (Never, Always, after dark ...) in the options was changed to Never. I'm going around and restoring all my leak sensors (about 18 of them) and the first 7 restored fine and started working. Something happened with the update as everything was working prior (last Tuesday) and took till Wednesday for me to start getting status messages there was no heartbeat on wireless sensors.

After upgrading to 5.4.4 all my battery devices are acting strange. My motion sensors are not reporting motion. I have restored them and 1 of them is working, the other is not. I have all 2 way devices and it has never been an issue. Also, all my leak sensors are missing their heartbeat interval. I have programs that monitor for a heartbeat every 48 hours, none of them are getting heartbeat messages. Anyone else seeing this behavior? Was on 5.4.3 prior and it was working fine.

thanks!

So the last 2 nights, at or around 4am the ELK Node server does a query and does the same thing it would do when it starts up. Just like when it starts up, the variable is set to Off and then On. Setting to Off activate my test program that notifies me when it goes off. I also have a program to tell me when it is set to On. Even though when I go to look at variable it shows on, I only get the notification when it is set off. It looks like it is initializing the value. Below is when this starts (prior to that it is just doing it's polling thing) and then specifically the lines specific to the variable. START 2022-05-24 04:03:18,905 Command udi_interface INFO Controller:query: ELK Controller: 2022-05-24 04:03:18,906 Command udi_interface DEBUG Controller:check_params: ELK Controller: host=XXXXXXXXXXXXXXX 2022-05-24 04:03:18,907 Command udi_interface DEBUG Controller:check_params: exit: config_st=True 2022-05-24 04:03:18,907 Command udi_interface.node INFO node:reportDrivers: Updating All Drivers to ISY for ELK Controller(controller) 2022-05-24 04:03:18,908 Command udi_interface.interface DEBUG interface:send: PUBLISHING {'set': [{'address': 'controller', 'driver': 'GV1', 'value': 1, 'uom': 25}, {'address': 'controller', 'driver': 'ST', 'value': '1', 'uom': 25}]} 2022-05-24 04:03:19,105 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message query 2022-05-24 04:03:19,107 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING query 2022-05-24 04:03:19,107 Command udi_interface INFO BaseNode:query: area_1:1 - Main House: 2022-05-24 04:03:19,107 Command udi_interface BUNCH OF STUFF QUERYING EVERY AREA AND ZONE UNTIL IT GETS TO OUTPUTS OUTPUT VARIABLE 2022-05-24 04:03:22,454 Command udi_interface DEBUG Output:set_drivers: House On: force=False reportCmd=True 2022-05-24 04:03:22,455 Command udi_interface INFO Output:set_onoff: House On: val=None force=False reportCmd=True 2022-05-24 04:03:22,456 Command udi_interface DEBUG BaseNode:set_driver: House On: ST,100 default=0 force=False,report=True 2022-05-24 04:03:22,456 Command udi_interface DEBUG Output:set_onoff: House On: Send DON 2022-05-24 04:03:22,457 Command udi_interface.interface DEBUG interface:send: PUBLISHING {'command': [{'address': 'output_63', 'cmd': 'DON'}]} 2022-05-24 04:03:22,459 Command udi_interface.node INFO node:reportDrivers: Updating All Drivers to ISY for House On(output_63) 2022-05-24 04:03:22,459 Command udi_interface.interface DEBUG interface:send: PUBLISHING {'set': [{'address': 'output_63', 'driver': 'ST', 'value': 100, 'uom': 78}, {'address': 'output_63', 'driver': 'TIME', 'value': '0', 'uom': 58}]} 2022-05-24 04:03:22,721 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message query 2022-05-24 04:03:22,722 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING query

I've setup a program to notify me when it happens, it may go weeks or a month.

I've had to turn off all my scenes that use an elk output as a trigger. It seems they randomly reset/go on-off audit triggers my scene which in this case shuts down the whole house.

FYI - even when on current version, dashboard says there is a new version available. Not sure what causes that but the store says 4.0.4 and the node server detail screen says 4.0.4.

I also have all the zones and schedules and will keep an eye on it.

the other day all my node server except one did not show the product store blue tag. I couldn't get them to come back. I deleted and re-installed and they came back. I was in a hurry and didn't feel like reporting it. However I noticed at the time my purchases was empty as well. Today I saw a message come by. I knew I had a mix of trial and purchased node servers previously and was trying to figure which ones I had bought while the bugs were being worked out on others. here is the error. 4/22/2022, 16:28:59 [pg3] error: unhandledRejection REPORT THIS!: [object Promise], reason: TypeError: store.getPurchaseEntry is not a function

That made it 1 setup further. The error now seems to be about the controller (not bridge) not being a parent. Discovering nodes on Rachio Controller Rachio-Lake (80a589e0a70c) 2022-04-22 15:35:35,866 Thread-8 udi_interface INFO rachio-poly:discover: 16 Rachio zones found on "Rachio-Lake" controller. Adding to ISY 2022-04-22 15:35:35,867 Thread-8 udi_interface ERROR rachio-poly:discover: Error discovering and adding Zones on Rachio Controller Rachio-Lake (80a589e0a70c): 'RachioController' object has no attribute 'parent' 2022-04-22 15:35:35,867 Thread-8 udi_interface INFO rachio-poly:discover: 2 Rachio schedules found on "Rachio-Lake" controller. Adding to ISY 2022-04-22 15:35:35,868 Thread-8 udi_interface ERROR rachio-poly:discover: Error discovering and adding Schedules on Rachio Controller Rachio-Lake (80a589e0a70c): 'RachioController' object has no attribute 'parent' 2022-04-22 15:35:35,868 Thread-8 udi_interface INFO rachio-poly:discover: 3 Rachio Flex schedules found on "Rachio-Lake" controller. Adding to ISY 2022-04-22 15:35:35,869 Thread-8 udi_interface ERROR rachio-poly:discover: Error discovering and adding Flex Schedules on Rachio Controller Rachio-Lake (80a589e0a70c): 'RachioController' object has no attribute 'parent'

@bpwwerany doc on the custom typed config params at the bottom. See there is a save changes and refresh but no doc and no add. Just curious. I have new version setup and am testing.

I am seeing same behavior. Also, the node server is not receiving the rest call from weewx. It is setup the same, I configured the same port and on PG2 it was working fine. As said above, if you restart the node server it deletes all the nodes on ISY (you can watch them go) and then recreates them. If I hit stop it doesn't act like it stops, have to refresh the browser to see it is not running. 2-01-31 23:01:47,800 MainThread udi_interface.interface INFO interface:addNode: Adding node WeatherPoly(controller) [None] 2022-01-31 23:01:47,939 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message getAll 2022-01-31 23:01:47,940 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING getAll 2022-01-31 23:01:47,943 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: load {'Port': '8081', 'Units': 'us', 'IncomingUnits': 'metric', 'humidity-inside': '23', 'humidity-main': '3', 'pressure-station': '10', 'pressure-trend': '18', 'rain-daily': '9', 'rain-hourly': '47', 'rain-monthly': '19', 'rain-rate': '8', 'rain-yearly': '20', 'rain-yesterday': '21', 'temperature-dewpoint': '4', 'temperature-heatindex': '41', 'temperature-inside': '22', 'temperature-main': '2', 'temperature-max': '26', 'temperature-min': '28', 'temperature-windchill': '24', 'wind-avgwindspeed': '5', 'wind-gustdir': '46', 'wind-gustspeed': '40', 'wind-winddir': '7', 'wind-windspeed': '6'} 2022-01-31 23:01:47,945 Command udi_interface.custom DEBUG custom:load: CUSTOM: load {} 2022-01-31 23:01:47,945 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking Port / 8081 2022-01-31 23:01:47,946 Command udi_interface.interface DEBUG interface:_handleInput: Key nsdata should be passed to node server. 2022-01-31 23:01:47,947 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking Units / us 2022-01-31 23:01:47,949 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking IncomingUnits / metric 2022-01-31 23:01:47,949 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking humidity-inside / 23 2022-01-31 23:01:47,950 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking humidity-main / 3 2022-01-31 23:01:47,951 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking pressure-station / 10 2022-01-31 23:01:47,951 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking pressure-trend / 18 2022-01-31 23:01:47,952 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking rain-daily / 9 2022-01-31 23:01:47,952 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking rain-hourly / 47 2022-01-31 23:01:47,953 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking rain-monthly / 19 2022-01-31 23:01:47,954 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking rain-rate / 8 2022-01-31 23:01:47,954 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking rain-yearly / 20 2022-01-31 23:01:47,955 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking rain-yesterday / 21 2022-01-31 23:01:47,956 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking temperature-dewpoint / 4 2022-01-31 23:01:47,956 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking temperature-heatindex / 41 2022-01-31 23:01:47,957 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking temperature-inside / 22 2022-01-31 23:01:47,957 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking temperature-main / 2 2022-01-31 23:01:47,958 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking temperature-max / 26 2022-01-31 23:01:47,959 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking temperature-min / 28 2022-01-31 23:01:47,959 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking temperature-windchill / 24 2022-01-31 23:01:47,960 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking wind-avgwindspeed / 5 2022-01-31 23:01:47,961 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking wind-gustdir / 46 2022-01-31 23:01:47,962 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking wind-gustspeed / 40 2022-01-31 23:01:47,962 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking wind-winddir / 7 2022-01-31 23:01:47,963 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking wind-windspeed / 6 2022-01-31 23:01:47,963 Thread-1 udi_interface.custom DEBUG custom:clear: CUSTOM: Clear ...saving 2022-01-31 23:01:47,964 Thread-1 udi_interface.custom INFO custom:_save: Sending data notices to Polyglot. 2022-01-31 23:01:47,965 Thread-1 udi_interface.interface DEBUG interface:send: PUBLISHING {'set': [{'key': 'notices', 'value': {}}]} 2022-01-31 23:01:47,967 Thread-1 udi_interface INFO weatherstation:set_configuration: Check for existing configuration value 2022-01-31 23:01:47,967 Thread-1 udi_interface INFO weatherstation:map_nodes: Trying to create a mapping 2022-01-31 23:01:47,968 Thread-1 udi_interface INFO weatherstation:map_nodes: MAPPING 23 to humidity-inside 2022-01-31 23:01:47,969 Thread-1 udi_interface INFO weatherstation:map_nodes: MAPPING 3 to humidity-main 2022-01-31 23:01:47,969 Thread-1 udi_interface INFO weatherstation:map_nodes: MAPPING 10 to pressure-station 2022-01-31 23:01:47,970 Thread-1 udi_interface INFO weatherstation:map_nodes: MAPPING 18 to pressure-trend 2022-01-31 23:01:47,971 Thread-1 udi_interface INFO weatherstation:map_nodes: MAPPING 9 to rain-daily 2022-01-31 23:01:47,971 Thread-1 udi_interface INFO weatherstation:map_nodes: MAPPING 47 to rain-hourly 2022-01-31 23:01:47,972 Thread-1 udi_interface INFO weatherstation:map_nodes: MAPPING 19 to rain-monthly 2022-01-31 23:01:47,973 Thread-1 udi_interface INFO weatherstation:map_nodes: MAPPING 8 to rain-rate 2022-01-31 23:01:47,973 Thread-1 udi_interface INFO weatherstation:map_nodes: MAPPING 20 to rain-yearly 2022-01-31 23:01:47,974 Thread-1 udi_interface INFO weatherstation:map_nodes: MAPPING 21 to rain-yesterday 2022-01-31 23:01:47,975 Thread-1 udi_interface INFO weatherstation:map_nodes: MAPPING 4 to temperature-dewpoint 2022-01-31 23:01:47,977 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message getNsInfo 2022-01-31 23:01:47,978 Thread-1 udi_interface INFO weatherstation:map_nodes: MAPPING 41 to temperature-heatindex 2022-01-31 23:01:47,979 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING getNsInfo 2022-01-31 23:01:47,980 Thread-1 udi_interface INFO weatherstation:map_nodes: MAPPING 22 to temperature-inside 2022-01-31 23:01:47,981 Thread-1 udi_interface INFO weatherstation:map_nodes: MAPPING 2 to temperature-main 2022-01-31 23:01:47,982 Thread-1 udi_interface INFO weatherstation:map_nodes: MAPPING 26 to temperature-max 2022-01-31 23:01:47,983 Thread-1 udi_interface INFO weatherstation:map_nodes: MAPPING 28 to temperature-min 2022-01-31 23:01:47,983 Thread-1 udi_interface INFO weatherstation:map_nodes: MAPPING 24 to temperature-windchill 2022-01-31 23:01:47,984 Thread-1 udi_interface INFO weatherstation:map_nodes: MAPPING 5 to wind-avgwindspeed 2022-01-31 23:01:47,984 Thread-1 udi_interface INFO weatherstation:map_nodes: MAPPING 46 to wind-gustdir 2022-01-31 23:01:47,985 Thread-1 udi_interface INFO weatherstation:map_nodes: MAPPING 40 to wind-gustspeed 2022-01-31 23:01:47,986 Thread-1 udi_interface INFO weatherstation:map_nodes: MAPPING 7 to wind-winddir 2022-01-31 23:01:47,986 Thread-1 udi_interface INFO weatherstation:map_nodes: MAPPING 6 to wind-windspeed 2022-01-31 23:01:47,987 Thread-1 udi_interface INFO weatherstation:map_nodes: Try to create node definition profile based on config. 2022-01-31 23:01:47,989 Thread-1 udi_interface INFO write_profile:write_profile: write_profile: Writing profile/nodedef/nodedefs.xml 2022-01-31 23:01:47,993 Thread-1 udi_interface INFO write_profile:write_profile_zip: write_profile_zip: profile/version.txt as version.txt 2022-01-31 23:01:47,997 Thread-1 udi_interface INFO write_profile:write_profile_zip: write_profile_zip: profile/nls/en_us.txt as nls/en_us.txt 2022-01-31 23:01:48,000 Thread-1 udi_interface INFO write_profile:write_profile_zip: write_profile_zip: profile/editor/editors.xml as editor/editors.xml 2022-01-31 23:01:48,003 Thread-1 udi_interface INFO write_profile:write_profile_zip: write_profile_zip: profile/nodedef/nodedefs.xml as nodedef/nodedefs.xml 2022-01-31 23:01:48,006 Thread-1 udi_interface INFO write_profile:write_profile: write_profile: done. 2022-01-31 23:01:48,007 Thread-1 udi_interface.interface INFO interface:installprofile: Sending Install Profile command to Polyglot. 2022-01-31 23:01:48,007 Thread-1 udi_interface.interface WARNING interface:installprofile: installprofile() is deprecated. Use updateProfile() instead. 2022-01-31 23:01:48,008 Thread-1 udi_interface.interface DEBUG interface:send: PUBLISHING {'installprofile': {'reboot': False}} 2022-01-31 23:01:48,010 Thread-1 udi_interface INFO weatherstation:discover: Creating nodes. 2022-01-31 23:01:48,011 Thread-1 udi_interface INFO weatherstation:discover: Creating Temperature node 2022-01-31 23:01:48,013 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2022-01-31 23:01:48,013 Thread-1 udi_interface.interface INFO interface:addNode: Adding node Temperatures(temperature) [None] 2022-01-31 23:01:48,015 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2022-01-31 23:01:48,016 Thread-1 udi_interface.interface DEBUG interface:send: PUBLISHING {'addnode': [{'address': 'temperature', 'name': 'Temperatures', 'nodeDefId': 'temperature', 'primaryNode': 'controller', 'drivers': [{'driver': 'GV0', 'value': 0, 'uom': 17}, {'driver': 'GV2', 'value': 0, 'uom': 17}, {'driver': 'GV4', 'value': 0, 'uom': 17}, {'driver': 'ST', 'value': 0, 'uom': 17}, {'driver': 'GV15', 'value': 0, 'uom': 17}, {'driver': 'GV16', 'value': 0, 'uom': 17}, {'driver': 'GV1', 'value': 0, 'uom': 17}], 'hint': 16777215, 'private': None}]} 2022-01-31 23:01:48,019 Thread-1 udi_interface INFO weatherstation:discover: Creating Humidity node 2022-01-31 23:01:48,020 Thread-1 udi_interface.node DEBUG node:_updateDrivers: Update humidity default ST to 0 / 51 2022-01-31 23:01:48,022 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message notices 2022-01-31 23:01:48,022 Thread-1 udi_interface.interface INFO interface:addNode: Adding node Humidity(humidity) [None] 2022-01-31 23:01:48,024 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING notices 2022-01-31 23:01:48,025 Thread-1 udi_interface.interface DEBUG interface:send: PUBLISHING {'addnode': [{'address': 'humidity', 'name': 'Humidity', 'nodeDefId': 'humidity', 'primaryNode': 'controller', 'drivers': [{'driver': 'GV0', 'value': 0, 'uom': 51}, {'driver': 'ST', 'value': 0, 'uom': 51}], 'hint': 16777215, 'private': None}]} 2022-01-31 23:01:48,026 Command udi_interface.custom DEBUG custom:load: CUSTOM: load {} 2022-01-31 23:01:48,028 Thread-1 udi_interface INFO weatherstation:discover: Creating Pressure node 2022-01-31 23:01:48,030 Thread-1 udi_interface.interface INFO interface:addNode: Adding node Barometric Pressure(pressure) [None] 2022-01-31 23:01:48,030 Thread-1 udi_interface.interface DEBUG interface:send: PUBLISHING {'addnode': [{'address': 'pressure', 'name': 'Barometric Pressure', 'nodeDefId': 'pressure', 'primaryNode': 'controller', 'drivers': [{'driver': 'ST', 'value': 0, 'uom': 23}, {'driver': 'GV1', 'value': 0, 'uom': 25}], 'hint': 16777215, 'private': None}]} 2022-01-31 23:01:48,032 Thread-1 udi_interface INFO weatherstation:discover: Creating Wind node 2022-01-31 23:01:48,033 Thread-1 udi_interface.interface INFO interface:addNode: Adding node Wind(wind) [None] 2022-01-31 23:01:48,034 Thread-1 udi_interface.interface DEBUG interface:send: PUBLISHING {'addnode': [{'address': 'wind', 'name': 'Wind', 'nodeDefId': 'wind', 'primaryNode': 'controller', 'drivers': [{'driver': 'GV4', 'value': 0, 'uom': 48}, {'driver': 'GV2', 'value': 0, 'uom': 14}, {'driver': 'GV1', 'value': 0, 'uom': 48}, {'driver': 'GV0', 'value': 0, 'uom': 14}, {'driver': 'ST', 'value': 0, 'uom': 48}], 'hint': 16777215, 'private': None}]} 2022-01-31 23:01:48,036 Thread-1 udi_interface INFO weatherstation:discover: Creating Precipitation node 2022-01-31 23:01:48,037 Thread-1 udi_interface.interface INFO interface:addNode: Adding node Precipitation(rain) [None] 2022-01-31 23:01:48,038 Thread-1 udi_interface.interface DEBUG interface:send: PUBLISHING {'addnode': [{'address': 'rain', 'name': 'Precipitation', 'nodeDefId': 'precipitation', 'primaryNode': 'controller', 'drivers': [{'driver': 'GV1', 'value': 0, 'uom': 105}, {'driver': 'GV0', 'value': 0, 'uom': 105}, {'driver': 'GV3', 'value': 0, 'uom': 105}, {'driver': 'ST', 'value': 0, 'uom': 24}, {'driver': 'GV4', 'value': 0, 'uom': 105}, {'driver': 'GV6', 'value': 0, 'uom': 105}], 'hint': 16777215, 'private': None}]} 2022-01-31 23:01:48,039 Thread-1 udi_interface INFO weatherstation:discover: Deleting orphaned light node 2022-01-31 23:01:48,040 Thread-1 udi_interface.interface INFO interface:delNode: Removing node light 2022-01-31 23:01:48,041 Thread-1 udi_interface.interface DEBUG interface:send: PUBLISHING {'removenode': [{'address': 'light'}]} 2022-01-31 23:01:48,042 Thread-1 udi_interface INFO weatherstation:discover: Deleting orphaned lightning node 2022-01-31 23:01:48,043 Thread-1 udi_interface.interface INFO interface:delNode: Removing node lightning 2022-01-31 23:01:48,043 Thread-1 udi_interface.interface DEBUG interface:send: PUBLISHING {'removenode': [{'address': 'lightning'}]} 2022-01-31 23:01:48,049 MQTT udi_interface.interface INFO interface:_message: Successfully set key = notices 2022-01-31 23:01:48,178 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message addnode 2022-01-31 23:01:48,179 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING addnode 2022-01-31 23:01:48,182 Thread-3 udi_interface INFO weatherstation:start: Starting WeatherPoly Node Server 2022-01-31 23:01:48,184 Thread-3 udi_interface.interface INFO interface:updateProfile: Sending Install Profile command to Polyglot. 2022-01-31 23:01:48,185 Command udi_interface.interface DEBUG interface:_handleResult: add node response: {'id': '26b33782-5f46-4357-928c-eb11e240c36c', 'uuid': '00:0d:b9:52:c1:80', 'profileNum': 9, 'address': 'controller', 'name': 'WeatherPoly', 'nodeDefId': 'WeatherPoly', 'nls': None, 'hint': '0x00000000', 'controller': 0, 'primaryNode': 'controller', 'private': None, 'isPrimary': 1, 'enabled': 1, 'timeAdded': 1643689747722, 'timeModified': 1643689747722, 'dbVersion': 1} 2022-01-31 23:01:48,185 Thread-3 udi_interface.interface DEBUG interface:send: PUBLISHING {'installprofile': {'reboot': False}} 2022-01-31 23:01:48,355 Thread-3 udi_interface.interface DEBUG interface:setCustomParamsDoc: Sending customparamsdoc to Polyglot. 2022-01-31 23:01:48,356 Thread-3 udi_interface.interface DEBUG interface:send: PUBLISHING {'set': [{'key': 'customparamsdoc', 'value': '<h2>Configuration</h2>\n\n<p>The WeatherPoly node server has the following user configuration\nparameters:</p>\n\n<ul>\n<li>Port : The TCP port to listen on for connections from weather software.</li>\n<li>Units : The units used to display the data. Valid settings are: \'metric\', \'us\', or \'uk\'. The default is \'metric\'</li>\n<li>IncomingUnits: The units used by the data provider. Valid settings are \'metric\', \'us\', and \'uk\'. Default is \'metric\'.</li>\n</ul>\n\n<p>A mapping between the incoming data fields and the node server\'s nodes must be configured. The key is a node and data type combination and the value represents the incoming data field. How a data field is represented depends on the weather software.</p>\n\n<p>Valid nodes are: temperature, humidity, pressure, rain, wind, light, and lightning. See <a href="NODE_VALUE.md">node-value combinations</a> for a full list of node-values that can be used.</p>\n\n<h3>Cumulus software</h3>\n\n<p>Cumulus software allows you to configure what text string is used to represent each value. See the Cumulus documentation for a list of valid tags. A Cumulus HTTP API value of:</p>\n\n<p>http://<node server ip>:8080/cumulus?temp=&lt;#temp>&amp;humidity=&lt;#humidity></p>\n\n<p>Will send temperature and humidity data. This can be mapped to node server nodes using:</p>\n\n<p>temperature-main : temp\nhumidity-main : humidity</p>\n\n<h3>acuparse</h3>\n\n<p>acuparse software for Acurite weather stations https://github.com/acuparse/acuparse can be configured to send data to a generic service. To configure acuparse to send data to WeatherPoly, set the generic URL to:</p>\n\n<p>http://<node server ip>:8080/acuparse</p>\n\n<h4>Configure WeatherPoly with the following mapping:</h4>\n\n<ul>\n<li>temperature-main = tempf</li>\n<li>temperature-dewpoint = dewptf</li>\n<li>humidity-main = humidity</li>\n<li>pressure-sealevel = baromin</li>\n<li>wind-windspeed = windspeedmph</li>\n<li>wind-winddir = winddir</li>\n<li>wind-avgwindspeed = windspdmph_avg2m</li>\n<li>rain-rate = rainin</li>\n<li>rain-daily = dailyrainin</li>\n</ul>\n\n<p>Input units should be set as US.</p>\n\n<h3>WeeWX</h3>\n\n<p>WeeWX data is supported through an extension to WeeWX called weewx-crt which can output the data in Cumulus Real Time format. The weewx-crt extension is configured by setting the realtime_url to:</p>\n\n<p>http://<node server ip>:8080/weewx</p>\n\n<h4>Configure WeatherPoly mappings:</h4>\n\n<p>The real-time data file is a fixed format file with the weather values separated by spaces. This is split so that the space separated value\'s index is mapped to the node servers nodes-values. For example:\n* temperature-main = 2\n* temperature-dewpoint = 3\n* humidity-main = 4\n* etc.</p>\n\n<h3>MeteoBridge</h3>\n\n<p>MeteoBridge data is supported using the Home Weather Station weather network configuration. For the API URL use</p>\n\n<p>http://<node server ip>:8080/</p>\n\n<p>MeteoBridge will send a space separated list of values. These are mapped to the node server\'s nodes using the value\'s position in that list. The table below shows the values and numeric position.</p>\n\n<h4>MeteoBridge Field list</h4>\n\n<p><a href="METEOBRIDGE.md">MeteoBridge field list</a></p>\n'}]} 2022-01-31 23:01:48,358 Thread-3 udi_interface INFO weatherstation:discover: Creating nodes. 2022-01-31 23:01:48,359 Thread-3 udi_interface INFO weatherstation:discover: Creating Temperature node 2022-01-31 23:01:48,359 Thread-3 udi_interface.interface INFO interface:delNode: Removing node temperature 2022-01-31 23:01:48,360 Thread-3 udi_interface.interface DEBUG interface:send: PUBLISHING {'removenode': [{'address': 'temperature'}]} 2022-01-31 23:01:48,362 Thread-3 udi_interface.interface INFO interface:addNode: Adding node Temperatures(temperature) [None] 2022-01-31 23:01:48,363 Thread-3 udi_interface.interface DEBUG interface:send: PUBLISHING {'addnode': [{'address': 'temperature', 'name': 'Temperatures', 'nodeDefId': 'temperature', 'primaryNode': 'controller', 'drivers': [{'driver': 'GV0', 'value': 0, 'uom': 17}, {'driver': 'GV2', 'value': 0, 'uom': 17}, {'driver': 'GV4', 'value': 0, 'uom': 17}, {'driver': 'ST', 'value': 0, 'uom': 17}, {'driver': 'GV15', 'value': 0, 'uom': 17}, {'driver': 'GV16', 'value': 0, 'uom': 17}, {'driver': 'GV1', 'value': 0, 'uom': 17}], 'hint': 16777215, 'private': None}]} 2022-01-31 23:01:48,364 Thread-3 udi_interface INFO weatherstation:discover: Creating Humidity node 2022-01-31 23:01:48,365 Thread-3 udi_interface.interface INFO interface:delNode: Removing node humidity 2022-01-31 23:01:48,366 Thread-3 udi_interface.interface DEBUG interface:send: PUBLISHING {'removenode': [{'address': 'humidity'}]} 2022-01-31 23:01:48,368 Thread-3 udi_interface.node DEBUG node:_updateDrivers: Update humidity default ST to 0 / 51 2022-01-31 23:01:48,368 Thread-3 udi_interface.interface INFO interface:addNode: Adding node Humidity(humidity) [None] 2022-01-31 23:01:48,369 Thread-3 udi_interface.interface DEBUG interface:send: PUBLISHING {'addnode': [{'address': 'humidity', 'name': 'Humidity', 'nodeDefId': 'humidity', 'primaryNode': 'controller', 'drivers': [{'driver': 'GV0', 'value': 0, 'uom': 51}, {'driver': 'ST', 'value': 0, 'uom': 51}], 'hint': 16777215, 'private': None}]} 2022-01-31 23:01:48,371 Thread-3 udi_interface INFO weatherstation:discover: Creating Pressure node 2022-01-31 23:01:48,371 Thread-3 udi_interface.interface INFO interface:delNode: Removing node pressure 2022-01-31 23:01:48,372 Thread-3 udi_interface.interface DEBUG interface:send: PUBLISHING {'removenode': [{'address': 'pressure'}]} 2022-01-31 23:01:48,374 Thread-3 udi_interface.interface INFO interface:addNode: Adding node Barometric Pressure(pressure) [None] 2022-01-31 23:01:48,375 Thread-3 udi_interface.interface DEBUG interface:send: PUBLISHING {'addnode': [{'address': 'pressure', 'name': 'Barometric Pressure', 'nodeDefId': 'pressure', 'primaryNode': 'controller', 'drivers': [{'driver': 'ST', 'value': 0, 'uom': 23}, {'driver': 'GV1', 'value': 0, 'uom': 25}], 'hint': 16777215, 'private': None}]} 2022-01-31 23:01:48,376 Thread-3 udi_interface INFO weatherstation:discover: Creating Wind node 2022-01-31 23:01:48,377 Thread-3 udi_interface.interface INFO interface:delNode: Removing node wind 2022-01-31 23:01:48,377 Thread-3 udi_interface.interface DEBUG interface:send: PUBLISHING {'removenode': [{'address': 'wind'}]} 2022-01-31 23:01:48,379 Thread-3 udi_interface.interface INFO interface:addNode: Adding node Wind(wind) [None] 2022-01-31 23:01:48,380 Thread-3 udi_interface.interface DEBUG interface:send: PUBLISHING {'addnode': [{'address': 'wind', 'name': 'Wind', 'nodeDefId': 'wind', 'primaryNode': 'controller', 'drivers': [{'driver': 'GV4', 'value': 0, 'uom': 48}, {'driver': 'GV2', 'value': 0, 'uom': 14}, {'driver': 'GV1', 'value': 0, 'uom': 48}, {'driver': 'GV0', 'value': 0, 'uom': 14}, {'driver': 'ST', 'value': 0, 'uom': 48}], 'hint': 16777215, 'private': None}]} 2022-01-31 23:01:48,381 Thread-3 udi_interface INFO weatherstation:discover: Creating Precipitation node 2022-01-31 23:01:48,382 Thread-3 udi_interface.interface INFO interface:delNode: Removing node rain 2022-01-31 23:01:48,383 Thread-3 udi_interface.interface DEBUG interface:send: PUBLISHING {'removenode': [{'address': 'rain'}]} 2022-01-31 23:01:48,385 Thread-3 udi_interface.interface INFO interface:addNode: Adding node Precipitation(rain) [None] 2022-01-31 23:01:48,386 Thread-3 udi_interface.interface DEBUG interface:send: PUBLISHING {'addnode': [{'address': 'rain', 'name': 'Precipitation', 'nodeDefId': 'precipitation', 'primaryNode': 'controller', 'drivers': [{'driver': 'GV1', 'value': 0, 'uom': 105}, {'driver': 'GV0', 'value': 0, 'uom': 105}, {'driver': 'GV3', 'value': 0, 'uom': 105}, {'driver': 'ST', 'value': 0, 'uom': 24}, {'driver': 'GV4', 'value': 0, 'uom': 105}, {'driver': 'GV6', 'value': 0, 'uom': 105}], 'hint': 16777215, 'private': None}]} 2022-01-31 23:01:48,387 Thread-3 udi_interface INFO weatherstation:discover: Deleting orphaned light node 2022-01-31 23:01:48,388 Thread-3 udi_interface.interface INFO interface:delNode: Removing node light 2022-01-31 23:01:48,389 Thread-3 udi_interface.interface DEBUG interface:send: PUBLISHING {'removenode': [{'address': 'light'}]} 2022-01-31 23:01:48,390 Thread-3 udi_interface INFO weatherstation:discover: Deleting orphaned lightning node 2022-01-31 23:01:48,391 Thread-3 udi_interface.interface INFO interface:delNode: Removing node lightning 2022-01-31 23:01:48,391 Thread-3 udi_interface.interface DEBUG interface:send: PUBLISHING {'removenode': [{'address': 'lightning'}]} 2022-01-31 23:01:48,393 Thread-3 udi_interface INFO weatherstation:start: WeatherPoly Node Server Started. 2022-01-31 23:01:48,494 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message addnode 2022-01-31 23:01:48,495 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING addnode 2022-01-31 23:01:48,497 Command udi_interface.interface DEBUG interface:_handleResult: add node response: {'id': 'ed9085ae-f475-4e41-8967-aa58daebfbfd', 'uuid': '00:0d:b9:52:c1:80', 'profileNum': 9, 'address': 'temperature', 'name': 'Temperatures', 'nodeDefId': 'temperature', 'nls': None, 'hint': '16777215', 'controller': 0, 'primaryNode': 'controller', 'private': None, 'isPrimary': 0, 'enabled': 1, 'timeAdded': 1643691483025, 'timeModified': 1643691708348, 'dbVersion': 1} 2022-01-31 23:01:48,574 MQTT udi_interface.interface INFO interface:_message: custom data response {'customparamsdoc': '<h2>Configuration</h2>\n\n<p>The WeatherPoly node server has the following user configuration\nparameters:</p>\n\n<ul>\n<li>Port : The TCP port to listen on for connections from weather software.</li>\n<li>Units : The units used to display the data. Valid settings are: \'metric\', \'us\', or \'uk\'. The default is \'metric\'</li>\n<li>IncomingUnits: The units used by the data provider. Valid settings are \'metric\', \'us\', and \'uk\'. Default is \'metric\'.</li>\n</ul>\n\n<p>A mapping between the incoming data fields and the node server\'s nodes must be configured. The key is a node and data type combination and the value represents the incoming data field. How a data field is represented depends on the weather software.</p>\n\n<p>Valid nodes are: temperature, humidity, pressure, rain, wind, light, and lightning. See <a href="NODE_VALUE.md">node-value combinations</a> for a full list of node-values that can be used.</p>\n\n<h3>Cumulus software</h3>\n\n<p>Cumulus software allows you to configure what text string is used to represent each value. See the Cumulus documentation for a list of valid tags. A Cumulus HTTP API value of:</p>\n\n<p>http://<node server ip>:8080/cumulus?temp=&lt;#temp>&amp;humidity=&lt;#humidity></p>\n\n<p>Will send temperature and humidity data. This can be mapped to node server nodes using:</p>\n\n<p>temperature-main : temp\nhumidity-main : humidity</p>\n\n<h3>acuparse</h3>\n\n<p>acuparse software for Acurite weather stations https://github.com/acuparse/acuparse can be configured to send data to a generic service. To configure acuparse to send data to WeatherPoly, set the generic URL to:</p>\n\n<p>http://<node server ip>:8080/acuparse</p>\n\n<h4>Configure WeatherPoly with the following mapping:</h4>\n\n<ul>\n<li>temperature-main = tempf</li>\n<li>temperature-dewpoint = dewptf</li>\n<li>humidity-main = humidity</li>\n<li>pressure-sealevel = baromin</li>\n<li>wind-windspeed = windspeedmph</li>\n<li>wind-winddir = winddir</li>\n<li>wind-avgwindspeed = windspdmph_avg2m</li>\n<li>rain-rate = rainin</li>\n<li>rain-daily = dailyrainin</li>\n</ul>\n\n<p>Input units should be set as US.</p>\n\n<h3>WeeWX</h3>\n\n<p>WeeWX data is supported through an extension to WeeWX called weewx-crt which can output the data in Cumulus Real Time format. The weewx-crt extension is configured by setting the realtime_url to:</p>\n\n<p>http://<node server ip>:8080/weewx</p>\n\n<h4>Configure WeatherPoly mappings:</h4>\n\n<p>The real-time data file is a fixed format file with the weather values separated by spaces. This is split so that the space separated value\'s index is mapped to the node servers nodes-values. For example:\n* temperature-main = 2\n* temperature-dewpoint = 3\n* humidity-main = 4\n* etc.</p>\n\n<h3>MeteoBridge</h3>\n\n<p>MeteoBridge data is supported using the Home Weather Station weather network configuration. For the API URL use</p>\n\n<p>http://<node server ip>:8080/</p>\n\n<p>MeteoBridge will send a space separated list of values. These are mapped to the node server\'s nodes using the value\'s position in that list. The table below shows the values and numeric position.</p>\n\n<h4>MeteoBridge Field list</h4>\n\n<p><a href="METEOBRIDGE.md">MeteoBridge field list</a></p>\n'} 2022-01-31 23:01:48,697 MQTT udi_interface.interface INFO interface:_message: Successfully set key = customparamsdoc 2022-01-31 23:01:48,830 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message addnode 2022-01-31 23:01:48,832 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING addnode 2022-01-31 23:01:48,834 Command udi_interface.interface DEBUG interface:_handleResult: add node response: {'id': 'c0746f83-7cb1-4edf-8c14-61f22ab5b991', 'uuid': '00:0d:b9:52:c1:80', 'profileNum': 9, 'address': 'humidity', 'name': 'Humidity', 'nodeDefId': 'humidity', 'nls': None, 'hint': '16777215', 'controller': 0, 'primaryNode': 'controller', 'private': None, 'isPrimary': 0, 'enabled': 1, 'timeAdded': 1643691483092, 'timeModified': 1643691708604, 'dbVersion': 1} 2022-01-31 23:01:48,878 MQTT udi_interface.interface INFO interface:_message: Profile installation finished 2022-01-31 23:01:48,920 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message addnode 2022-01-31 23:01:48,921 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING addnode 2022-01-31 23:01:48,923 Command udi_interface.interface DEBUG interface:_handleResult: add node response: {'id': '4c6a8d07-a50e-41d1-a158-83f9b7a4f3fb', 'uuid': '00:0d:b9:52:c1:80', 'profileNum': 9, 'address': 'pressure', 'name': 'Barometric Pressure', 'nodeDefId': 'pressure', 'nls': None, 'hint': '16777215', 'controller': 0, 'primaryNode': 'controller', 'private': None, 'isPrimary': 0, 'enabled': 1, 'timeAdded': 1643691483263, 'timeModified': 1643691708754, 'dbVersion': 1} 2022-01-31 23:01:49,215 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message addnode 2022-01-31 23:01:49,217 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING addnode 2022-01-31 23:01:49,220 Command udi_interface.interface DEBUG interface:_handleResult: add node response: {'id': '23280b2a-9a68-4027-b460-107ae2707b06', 'uuid': '00:0d:b9:52:c1:80', 'profileNum': 9, 'address': 'wind', 'name': 'Wind', 'nodeDefId': 'wind', 'nls': None, 'hint': '16777215', 'controller': 0, 'primaryNode': 'controller', 'private': None, 'isPrimary': 0, 'enabled': 1, 'timeAdded': 1643691483403, 'timeModified': 1643691708972, 'dbVersion': 1} 2022-01-31 23:01:49,413 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message addnode 2022-01-31 23:01:49,415 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING addnode 2022-01-31 23:01:49,417 Command udi_interface.interface DEBUG interface:_handleResult: add node response: {'id': '8ae43c48-33df-4d74-86fe-34ff286e9810', 'uuid': '00:0d:b9:52:c1:80', 'profileNum': 9, 'address': 'rain', 'name': 'Precipitation', 'nodeDefId': 'precipitation', 'nls': None, 'hint': '16777215', 'controller': 0, 'primaryNode': 'controller', 'private': None, 'isPrimary': 0, 'enabled': 1, 'timeAdded': 1643691483547, 'timeModified': 1643691709071, 'dbVersion': 1} 2022-01-31 23:01:49,453 MQTT udi_interface.interface ERROR interface:_message: Invalid command received in message from PG3: 'removenode' [{'address': 'light', 'success': False}] 2022-01-31 23:01:49,621 MQTT udi_interface.interface ERROR interface:_message: Invalid command received in message from PG3: 'removenode' [{'address': 'lightning', 'success': False}] 2022-01-31 23:01:49,941 MQTT udi_interface.interface INFO interface:_message: Profile installation finished 2022-01-31 23:01:50,145 MQTT udi_interface.interface ERROR interface:_message: Invalid command received in message from PG3: 'removenode' [{'address': 'temperature', 'success': True}] 2022-01-31 23:01:50,337 MQTT udi_interface.interface ERROR interface:_message: Invalid command received in message from PG3: 'removenode' [{'address': 'humidity', 'success': True}] 2022-01-31 23:01:50,578 MQTT udi_interface.interface ERROR interface:_message: Invalid command received in message from PG3: 'removenode' [{'address': 'pressure', 'success': True}] 2022-01-31 23:01:50,723 MQTT udi_interface.interface ERROR interface:_message: Invalid command received in message from PG3: 'removenode' [{'address': 'wind', 'success': True}] 2022-01-31 23:01:50,807 MQTT udi_interface.interface ERROR interface:_message: Invalid command received in message from PG3: 'removenode' [{'address': 'rain', 'success': True}] 2022-01-31 23:01:51,075 MQTT udi_interface.interface ERROR interface:_message: Invalid command received in message from PG3: 'removenode' [{'address': 'light', 'success': False}] 2022-01-31 23:01:51,204 MQTT udi_interface.interface ERROR interface:_message: Invalid command received in message from PG3: 'removenode' [{'address': 'lightning', 'success': False}] 2022-01-31 23:01:57,188 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2022-01-31 23:01:57,190 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2022-01-31 23:01:57,987 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2022-01-31 23:01:57,988 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2022-01-31 23:02:02,190 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2022-01-31 23:02:02,192 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll

@bpwwerare there plans to support P3 with WeatherPoly? Thanks in advance.

Just an update for anyone else and some theories which may or may not be true. My original z-wave issues were that I didn't have the right Zooz stick. If ordering it is the 700 and has a yellow cap. Michael fixed the link in first post I think. Don't setup portal until after you have restored your 994. It seems to get confused. Michael fixed it in 15 minutes on his side and all was good. I think me losing policy in my finder for a while was because of a node server. The weather poly node server defaults to port 8080. So does IoP. So one or the other was clobbering and not able to communicate. Restarting stuff didn't have to work, I powered down. I have the 1amp power supply. I did run in to some funny business (weird behavior). I had a lovely 5amp brick and swapped it out and weirdness went away. My scenes wouldn't work for a while. Turned out it was either the 8080 port problem or a flood of messages I was getting from the node server. I disabled all my pg2 node servers and re-imported and just let it do its thing and my scenes came back. Then I turned on PG2 and let it start (that is how I realized weather poly was on port 8080 as it was complaining. If you are using ELK module, take pictures of your programs. Unlike the zwave stuff, it doesn't leave nice comments ... Just a response 0 or result 0 line. Luckily I exported my programs to xml and have been around enough to be able to read them in their XML format. As a bonus @Michel Kohanimit would be nice if the 994 had an option that if safe mode kicks in you can still get to your programs in admin console. Then you could have the old one up and go back and validate some stuff. Maybe it exists. Maybe not, I couldn't get the 994 programs to come up without the PLM attached I used to have about 22 zwave devices. I got rid of my zwave locks before I did this upgrade and I have a blended homebrige setup (would love an august lock node server for more than 1 lock). 9 of those zwave devices were repeaters. I have a spread out house. The door locks were the weak link. Now, I have 9 devices (2 repeaters and 7 fan switches). It seems everything is faster. My zwave used to seem like it churned. I did have to go re-save all my network resources. Didn't realize I needed to re-input the mail credentials to send alerts. I had a few programs that enabled themselves even though they used to be disabled before the migration. I don't think it is because they had zwave devices in them, but not sure. I have 1 pg3 node. I use 11 node servers, I got rid of ping NS and turned off Roomba because it just seems to be flaky. I installed Sonos in PG3 as I needed to update room names on the nodes anyway. A lot of the NS I use aren't available in PG3 so I think I will wait a little longer. (WeatherPoly, Ventar, Rachio, MyQ, Hue). I started at like 5pm and was done by 11pm making all the changes/fixes and a big portion of that was spent on home bridge, changing my weewx to point at new weather poly port, Alex integration and the stumper was I was using occupancy sensor in portal and couldn't get it to work, moved to occupancy sensor 2 and got everything back up. Thanks for all the earlier posts and the how-to for research. It's not super simple, but what is that's worth it... And now I only have 1 box. @Michel Kohanimdid I read somewhere that we might be able to do ISY to ISY integration other than through network resources in the near future or share node servers between multiple ISYs? Thought I read that somewhere but can't find it. Cheers!

I can control devices after restoring buy none of my scenes work. None of them and I don't get anything in event viewer. Anyone else seen this problem?

Michael linked the correct zooz device above. Their naming is confusing. The zst10 come in 2 flavors. A 500 series and a 700. Michael had linked to zooz page which linked to thesmarterhouse for the 500. If yours didn’t t have a yellow cap it is a 500series. That seems to be my problem. I’m hoping they will refund mine as it was open box and says sales final but it wasn’t expensive so may not be worth the shipping.

yes, if not I don't believe zwave even shows in the menu.

I purchases the zoo s2 zst10 stick. I can see if find when plugged in to my MacBook. When I insert in Polisy it does not show up in ISY on policy and just says not responding. What should the device in /dev be named? When insert it the cuaU0 and lock/init show up as well as ttyU0 and lock/init. But it doesn't register in ISY. I did have to update my polisy manually as I have one of the originally shipped units. Not sure how else to debug.

@Michel Kohanim, I have this problem as well. Sent in a ticket. Can't access polisy on any ports. Router shows no attempts to connect, tried all same steps as @garybixler.