Mecheng70

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?

Something like this? switch: - platform: template switches: rgb_network: friendly_name: "Network" value_template: "{{ is_state('light.network', 'on') }}" turn_on: service: isy994.send_node_command data: command: fast_on target: entity_id: light.network turn_off: service: isy994.send_node_command data: command: fast_off target: entity_id: light.network I believe that this creates a switch.rgb_network

Ok. I'll look into that. Thanks

@shbatm Is there anyway to default the Fast On to the normal and not just On. Have 4 Aeotec RGB bulbs that have a parameter to change the ramp rate but that does not work like the "Fast On" and "Fast Off" buttons in AC.

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

Evidently the issue is with my site name. My site name has a "/" in it and both the solaredge poly node servers are not working when communicating with the eisy. I was on for 1.5hrs with michel yesterday. Currently waiting for the non-production node server to roll to 1.1.01. Right now only 1.1.0 is showing up. Did communicate with the photogeek. I was able to get around it by changing the name in the URL and launching it.

I am actually contemplating moving from pfsense to opnsense

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.