GQuack

I agree, had the same problem, updated the app, problem is gone. Thank you..

Thanks Javi, didn't see it in the non-production store. I'll check it out, thanks.

There is no Global Cache NS. Have to look at other options.

Global Cache NS, I’m not using that currently and didn’t know there is one. Let me check that out..

Is there a way to programmatically check the results of a Network Resource call? I've been using an Global Cache iTach IR to send IR signals to a split unit A/C. It's been working flawlessly for quite some time but I recently upgraded to a new router and was unable to attach to the iTach unit given the restrictions of the iTach to 802.11b standard. I solved that by configuring my old router as an access point with a dedicated 802.11b network used solely for the iTach. Not wanting this as a long-term solution, I purchased the newer model Global Cache Flex device which supports more of the wireless standards. I had zero issues with setting that up and getting it to connect to the new router but I am getting inconsistent results with the A/C unit. I am using exactly the same base code with the only exception being the IP address of the new Flex unit as opposed to the IR unit so something is happening somewhere with the network resource call but I am at a loss as to how to find the issue. I see no errors in the error log. Any suggestions?

Verified the update I made is to version 7.18.3, still unsuccessful with any recognition of trying to add a device. This Z-wave stuff has just been a big pain in the a.. since day 1 for me. Guess if I'm going to continue trying to use these devices, I'm going to have to move to the Zmatter device. or see if I can revert back to version 7.15 and see if that works.

Missed that thank you. Now to figure out what’s happening with mine…

I like your method, let's try this. He plugs this stick you show in the picture into one of the two devices shown. Polisy (blue) or eisy (Black). Do you know which one?

What controller device, not z-wave device?

@mmbIs he running on a Polisy or eisy?

Ok, just upgraded from Polisy to eisy but didn’t want to fork out more money for the zmatter device. Chris helped me get the eisy off the zmatter default and back to the Zooz dongle. In order to make that work, needed to remove all z -wave devices and re-add them. Removed all of them, thought I would be smart and start over from scratch, did a reset of the z-wave dongle to factory settings, then upgraded the dongle to the newest firmware version through the anything but simple Simplicity Studio, typically the right course of action. Now, I can’t add any z-wave devices, no response at all to add device even when holding the z-wave device in close proximity to the eisy. Event viewer shows “Unrecognized Z-wave firmware version/library [7.18]” Perhaps need to revert back to a previous erosion for some reason or???

Just upgrade to pg3x. I couldn't figure out where / why the IS994 would have an entry in Polyglot but your comment makes sense. I did have an Elk plugin so perhaps that started the problem. I have deleted the IS994 entry from Polyglot and I also had a Portal entry for that same device which I removed as well. I have been seeing multiple Polisy restarts throughout the day for no reason I can explain. Let's see if these changes make a difference.

My setup: ISY994 used solely for IR processing and a Polisy recently upgraded to (5.8.4), for responding to the IR requests and doing everything else. There are two entries in the ISY portal, one for the ISY994 showing a valid UUID along with a warning for "Access license is not active" and one entry for the Polisy showing a valid UUID. Within the Polglot 3X website, there are likewise two IoX's listed under IoX Configuration, one which is the correct entry for the Polisy and one which I assume is for the IS994 but shows a UUID of zeros which obviously does not match the UUID shown in the ISY Portal. When I select the IoX of zeros on the Polyglot site, I see exactly the same node servers as I have added for the Polisy but all are Unmanaged. When I select the IoX for the Polisy with it's correct UUID, the node servers display as expected, all being managed appropriately I am seeing issues with the Polisy dropping connection multiple times a day and upon reconnecting, creating a multitude of bogus errors, etc. Wondering if any of this is due to the two entries within the Portal and / or Polyglot website. Do I need the portal entry for the ISY994 at all for the limited IR processing or conversely, will deleting that entry cause any issues? Likewise, I would also consider deleting the IoX entry for the UUID of all zeros from the Polyglot site. Not sure which should come first, deleting the portal entry and thinking in turn that may also remove the UUID of zeros or perhaps needing to delete both manually. Thanks in advance for any help.

@bpwwer Doing some maintenance on the Polisy and noticed I had triplicate entries for each of the zones on my MCA-66. Figured I would delete the NS, reinstall and go fresh. Installed the NS into the same slot as previously located, but the Add Controller button is nowhere to be found on the Configuration screen???? Have restarted Polisy several times, same for Polyglot, no help.

OK, installed the new beta version and my impression is that everything is working correctly. There are now many other choices for input selections. I tried a number of these including the ones most likely for me including cblsat, Stream, Game, AM, FM and all worked great. I also tried several others Aux1, Aux2, Sirius but these were non responsive, most likely due to a lack of this capability on my receiver. Thank you @firstone for this enhancement.

I’ll try it today and report back. Thank you.

@firstone are you still out there?

Thank you @firstone. Here is the documentation in full for input select if anyone else is interested. For stream, “SLI 11”. SLI: name: input-selector aliases: ['source'] description: Input Selector Command values: '00': name: [video1, vcr, dvr, stb, dvr] description: sets VIDEO1, VCR/DVR, STB/DVR models: set1 '01': name: [video2, cbl, sat] description: sets VIDEO2, CBL/SAT models: set1 '02': name: [video3, game/tv, game, game1] description: sets VIDEO3, GAME/TV, GAME, GAME1 models: set1 '03': name: [video4, aux1] description: sets VIDEO4, AUX1(AUX) models: set1 '04': name: [video5, aux2, game2] description: sets VIDEO5, AUX2, GAME2 models: set1 '05': name: [video6, pc] description: sets VIDEO6, PC models: set1 '06': name: video7 description: sets VIDEO7 models: set1 '07': name: '07' description: Hidden1 EXTRA1 models: set1 08: name: 08 description: Hidden2 EXTRA2 models: set1 09: name: 09 description: Hidden3 EXTRA3 models: set1 '10': name: [dvd, bd, dvd] description: sets DVD, BD/DVD models: set1 '11': name: strm-box description: sets STRM BOX models: set1 '12': name: tv description: sets TV models: set1 '20': name: [tape-1, tv/tape] description: sets TAPE(1), TV/TAPE models: set1 '21': name: tape2 description: sets TAPE2 models: set1 '22': name: phono description: sets PHONO models: set1 '23': name: [cd, tv/cd] description: sets CD, TV/CD models: set1 '24': name: fm description: sets FM models: set1 '25': name: am description: sets AM models: set1 '26': name: tuner description: sets TUNER models: set1 '27': name: [music-server, p4s, dlna] description: sets MUSIC SERVER, P4S, DLNA models: set1 '28': name: [internet-radio, iradio-favorite] description: sets INTERNET RADIO, iRadio Favorite models: set1 '29': name: [usb, usb] description: sets USB/USB(Front) models: set1 2A: name: usb description: sets USB(Rear) models: set1 2B: name: [network, net] description: sets NETWORK, NET models: set1 2C: name: usb description: sets USB(toggle) models: set1 2D: name: aiplay description: sets Aiplay models: set1 2E: name: bluetooth description: sets Bluetooth models: set1 2F: name: usb-dac-in description: sets USB DAC In models: set2 '41': name: line description: sets LINE models: set2 '42': name: line2 description: sets LINE2 models: set2 '44': name: optical description: sets OPTICAL models: set2 '45': name: coaxial description: sets COAXIAL models: set2 '40': name: universal-port description: sets Universal PORT models: set1 '30': name: multi-ch description: sets MULTI CH models: set1 '31': name: xm description: sets XM models: set1 '32': name: sirius description: sets SIRIUS models: set1 '33': name: dab description: 'sets DAB ' models: set1 '55': name: hdmi-5 description: sets HDMI 5 models: set1 '56': name: hdmi-6 description: sets HDMI 6 models: set1 '57': name: hdmi-7 description: sets HDMI 7 models: set1 UP: name: up description: sets Selector Position Wrap-Around Up models: set1 DOWN: name: down description: sets Selector Position Wrap-Around Down models: set1 QSTN: name: query description: gets The Selector Position models: set1

I am using this node server for my Onkyo receiver and overall works pretty well. There are a multitude of Select Input options available but missing is a streaming device, such as an Apple TV. I see game_tv but on my receiver, I have both a game port and a streamer device port. @firstone Can I request the addition of streamer as an input select?

Hi @photogeek54. Yes, confirmed the node server is production. Will send you the api_key.

@bpwwer Greetings, our SolarEdge installation has 2 inverters, each with 1 battery attached. When I restart the node server, the log shows finding 2 inverters and 2 batteries, but there is only a single battery node with a node name of battery 1.5 and a single battery in the Polisy. Are the two batteries being consolidated? 2023-08-19 11:09:48,914 Thread-1 udi_interface INFO solaredge-poly:discover: Discovering SolarEdge sites and equipment... 2023-08-19 11:09:49,807 Thread-1 udi_interface INFO solaredge-poly:discover: Found 1 sites 2023-08-19 11:09:49,808 Thread-1 udi_interface INFO solaredge-poly:discover: Found Active site id: 1003126, name: Quackenbush1, TZ: Pacific/Honolulu 2023-08-19 11:09:49,809 Thread-1 udi_interface INFO solaredge-poly:discover: Adding site id: 1003126 2023-08-19 11:09:49,811 Thread-1 udi_interface.interface INFO interface:addNode: Adding node Quackenbush1(1003126) [None] 2023-08-19 11:09:49,813 Thread-1 udi_interface INFO solaredge-poly:discover: Requesting site inventory... 2023-08-19 11:09:51,069 Thread-1 udi_interface INFO solaredge-poly:discover: Found: 8 meters, 0 sensors, 0 gateways, 2 batteries, 2 inverters 2023-08-19 11:09:51,070 Thread-1 udi_interface INFO solaredge-poly:discover: Adding inverter 7F177E6B-7F 2023-08-19 11:09:51,073 Thread-1 udi_interface.interface INFO interface:addNode: Adding node Inverter 1(7f177e6b7f) [None] 2023-08-19 11:09:51,075 Thread-1 udi_interface INFO solaredge-poly:discover: Adding inverter 7F16EF1C-A0 2023-08-19 11:09:51,078 Thread-1 udi_interface.interface INFO interface:addNode: Adding node Inverter 2(7f16ef1ca0) [None] 2023-08-19 11:09:51,080 Thread-1 udi_interface INFO solaredge-poly:discover: Adding battery R15563P3SSEG12204231694 2023-08-19 11:09:51,082 Thread-1 udi_interface.interface INFO interface:addNode: Adding node Battery 1.5(r15563p3sseg12) [None]

The bigger question: why are these occurring? Is this an issue or not?

Like others have mentioned, I am now seeing many on-line and off-line notifications per day, screen shot posted. This does not look normal to me.. I am running both an ISY for the IR capability alongside the Polisy but haven’t noticed any system “issues” per se.

Wow, I have only been running the “new” Polisy for six months and now another new piece of hardware. If I had known the EISY was imminent, I would not have spent the money to move from the ISY to the Polisy. I understand technology marches on but this feels unfortunate. Did I miss that this latest generation was coming soon?

Guess my lesson may have to wait for another day. My wife just told me she prefers to control the hall lights…GASP, manually! What is this world coming to???