Mecheng70

that doesn't work. I have a monitor and keyboard connected and the username and password do not work. also have quite a few errors.

My upgrade isn't going so well. can't ssh into the device with the admin username and password. Can't connect with bluetooth, adding a monitor is able to see the login screen but the login screen will not allow me to pass it with the username/password (username and password was not and has not changed).

I think that I am hosed. can't ssh into the eisy. not accepting my password. I may have to put a ticket.

Confused on this as I do have DHCP reservation and managed switch. when I ping eisy, I get: Pinging eisy.home.icu [172.16.5.251] with 32 bytes of data: Reply from 172.16.5.251: bytes=32 time=3ms TTL=64 Reply from 172.16.5.251: bytes=32 time=3ms TTL=64 Reply from 172.16.5.251: bytes=32 time=2ms TTL=64 Reply from 172.16.5.251: bytes=32 time=1ms TTL=64 Ping statistics for 172.16.5.251: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 1ms, Maximum = 3ms, Average = 2ms How are you determining the DHCP UID?

I just upgraded without really knowing as I just happen to log in a the system was requesting a reboot. Then I clicked the upgrade no realizing it was a major upgrade. (saw email post click) Unit has been down for 30 minutes now (1240 PST). Edit: I am currently at an hour and the unit is not back up. OS was at 13.2 last time I checked

Question for you. I have 5.8.3 and 3.2.22, can I update the PG3x to 3.2.27 from the my.iso portal? Or does that attempt to pull both the IoX and PG3x?

Isy notifies me when it is off or online. And other that the major hardware failure I've been dealing with for the last 36 hours. Everything is up and running now, it still shows as offline. But voice commands work.

All the devices show up on my.isy and it was set to use all. I changed to preferred isy. Devices show up in Google home but are grayed out. After I made the change for the "My Preferred ISY", the commands were resend to Google Home. Tried google voice and it did work, BUT the devices on the google home go offline and online all the time. Here is a video: https://photos.app.goo.gl/b7G2vo9gF7N3n3taA

Mine hasn't worked for a few weeks now. Even removed and readded and nothing.

Up and running. Can see them in UD Mobile. THANK YOU!

Also deleted all NS and rebooted. Reinstalled into slot 6. Updated to 1.1.01 and then it reverted to 1.1.0. Here are the log files.solaredge_poly_6-21-2023_83403_PM.zip

Installed the solaredge_poly in slot 10: Notice that the current version is 1.1.0 Updated it using the Update button and the same thing happened where after the update, the current version changed from 1.1.01 to 1.1.0. Only one node shows up in AC for each of the NS.:

Trying to upgrade the beta solaredge_poly. @photogeek54 mentioned to copy @bpwwer. Been having 2 issues. Solaredge NS not sending child nodes to AC. Was on with Michel and he thinks that the issue is the space or something in the site name that comes from Solaredge. I think that is it the "/" messing it up. Can't update to the 1.1.01 solaredge_poly non production nodeserver. Focusing on number 2 as number 1 may go away when upgrading. I have installed, uninstalled, deleted, restarted the node and PG3X and still the version indicates that the newer version is loaded, however, on refresh it reverts back to the previous revision. The update doesn't update as it reverts back. Here is a video showing it reverting back. https://photos.app.goo.gl/MpHj22nM7a3HagLJ9 Here are the PG3 debug log. pg3_6-20-2023_14724_PM.zip @photogeek54 identified this being strange. 6/20/2023, 13:44:30 [pg3] error: unhandledRejection REPORT THIS!: [object Promise], reason: TypeError: Cannot read properties of undefined (reading 'status') 6/20/2023, 13:44:30 [pg3] error: IoX Response: [Try: 1] [00:21:b9:02:62:25] :: [404 - OK] :: 0.947786ms - http://127.0.0.1:8080/rest/ns/1/nodes/n001_dy1352992/report/status/ST/16.0/33 For backstory: In order to get the nodes added to AC, I copied and pasted them into a browser with the name without the "/" in the URL. The "/" gets translated to %2F FROM /rest/ns/1/nodes/n001_1352992/add/SESITE?primary=n001_1352992&name=NAME%20-%20NEC6518%2FNBTC6804 TO http://172.16.5.251:8080/rest/ns/1/nodes/n001_1352992/add/SESITE?primary=n001_1352992&name=3036Street

Upgraded from 5.6.0 to 5.6.2. System seems to really lag around 2100-2200 hrs (PST) pretty unresponsive that requires a reboot to get it to do anything. I have a couple of programs that run at 2100 and will disable to see if that helps. These haven't been an issue in the past.

Submitted.

I have 2.

The same thing happened with the non-beta version, so I was curious if this was a system thing. solaredge_poly_6-13-2023_112000_AM.zip

Using the solaredge_poly ns from the beta store. Have the following nodes in PGx: The nodes are not showing up in AC: Have attempted to add all nodes but still nothing. What am I missing?

Had to reboot using the power button and am up and running.

Followed the instructions, but my version has not changed from 3.1.28. The PG3 did say that I needed to reboot. Have rebooted twice. thoughts?

I use a 10ft USB (make sure it is of high quality) that allows the Zmatter module to be mounted at the top of the closet. As for the zwave locks, have you attempted to heal the network to see if that helps? Or update it with interview? Maybe one of the experts will confirm is removing and readding it in the place where the final resting area is makes any sense.

Aeotec recessed door sensors are still not working. Have tried compatibility mode and write changes and sync.

Do you have a screen shot? Sometimes they are added, zwave tends to have child nodes. If you right click and group them, they are easier to visualize. As for the function, some are a mystery.

I have it to only one lock that isn't functional. Pulled the batteries before I left town. Another lock doesn't seem to indicate alarm status. Chris mentioned a fix coming.

Well that would be going back several months ago. So maybe a rebuild or move to another hub. I have readded/reset several devices post migration.