JPaul

For some reason when I click on Authenticate in PG3x it directs me to the wrong url. Instead of the auth_endpoint set in my OAuth Config, it send me to a URL that looks like the following. The Polyglot IP just being the ip I use for my eisy. https://<polyglot ip>:3000/undefined?response_type=code&redirect_uri=https://my.isy.io/api/cloudlink/redirect&client_id=undefined&state=64872c3813d796ee4f2888ac Here is my OAuth set in Node Server Management. I've also added the "oauth": true to the server.json file. { "name": "eWeLink", "client_id": "879120348723984723987", "client_secret": "917349823748343873", "auth_endpoint": "https://c2ccdn.coolkit.cc/oauth/index.html", "token_endpoint": "https://us-apia.coolkit.cc/v2/user/oauth/token", "cloudlink": true } Thanks, James

@Jimbo.Automates thanks. I was looking at the older ISY dev guide.

Feature Request (Add dBm Unit of Measure)

Bob thanks! That was it. I had I_STATUS instead of I_STATE for the editor. I can't believe I been pulling my hair on this one that long. Thanks for the tip with the Java console. Had no idea you could see that info there. Regards, James

The child node is not in the drop down at all, that's what's confusing. In my other node servers I see the child nodes in the dropdown like you said they don't display in a hierarchy but they are listed in the dropdown. However in this case the child node is nowhere to be found in the dropdown.

I've created a new node server and installed the node server to IoX. As you can see it is a child node of the controller. Now when I go into programs and create a condition you cannot see the child node only the controller. Here is a shot of the Polyglot nodes I've try countless things to try and get this to work to no avail. Any ideas would help. Here is the code if you want to look. https://github.com/jamespauly/udi-ewelink-poly.git Thx

@rob7419 Thanks for the help. I think what is going on it that for lightning data the app is calling the report API. I'm going to just mimic what the app does when I get a little time. I'll ping you all when it's ready.

@tlightne Do me a favor and send a screen shot of the dashboard. Are you using the web based on the mobile app? Thanks, James

@tlightne Sorry download again I fixed the issue.

@tlightne it should install on its own when you install the NS. If you do have issues then I can walk you through it.

@rob7419 @tlightne I pushed a new version up. Give it a shot. Also note that you have to install the jsonpath-ng python module.

@rob7419Intresting on the Atlas Node. Thanks for pointing out. I'm able to replicate so I'll look at this right away.

@tlightne @rob7419 I think I see what's happening with the lightning data. Give me a little bit as I'm going to have to change up the way I call the api's. Again thanks for all your feedback. With a bit of hard work I think we can make this NS solid.

@tlightne Thanks for the info. I noticed that on mine as well. I reached out to Acurite support because one item I noticed is in the API those 2 are always the same in the data that I get back. I'm going to see if there is another way to get that data, if not, I can probably dissect what they are doing in their app.

@tlightne The lightning data for last and closest strike are published in the api until the next event. So I'm going to change this to check the strike count and if the strike count is 0 then it will make last and closest strike 0. I'll make this configurable.

Let me look into the timing issue. I could make the last strike and closest strike configurable by day.

Thanks I put a a new version which should fix the issue. I don't have a Lightning tower device to test with so you will need to test this for me Thanks, James

Do me a favor. Turn on the logs to debug and restart then send me the logs. Thanks for your patience.

Screen shot from my test.

My apologies for not responding sooner. Between kids end of school activities and Covid running through the family I've been a little behind. Ive had to make some updates due to a slight change to the Acurite API. They no longer pass a value from feels like if it is the same as the temperature. So I had to add a clause to populate "Feels Like" with the current temperature if the "Feels Like" does not exist. This was wrecking havoc on the rest of the NS. Give it a shot and let me know. I'm following this topic now so let me know what you find.

One thing I noticed when I upgraded to 5.4.2 is my programs are not loading in the UI. When I call the GetProgram Web Service I see all the programs are still there. Just another note. I also cleared the Java Cache and reinstalled the client. The programs always show up in the mobile app. If I restart ISY on the Polisy I can see the programs for a little while but then it just goes blank again. From the Error Log Fri 2022/04/01 10:49:27 AM 0 -170001 <s:Envelope><s:Body><u:GetNodeDef xmlns:u="urn:udi-com:service:X_Polisy_Service:1"><id>0</id></u:GetNodeDef></s:Body></s:Envelope> Fri 2022/04/01 10:49:27 AM 0 -170001 <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_Polisy_Service:1"></u:GetSystemStatus></s:Body></s:Envelope> Fri 2022/04/01 10:49:28 AM 0 -170001 <s:Envelope><s:Body><u:RefreshDeviceStatus xmlns:u="urn:udi-com:service:X_Polisy_Service:1"><sid>uuid:29</sid></u:RefreshDeviceStatus></s:Body></s:Envelope> Fri 2022/04/01 10:49:28 AM 0 -170001 <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_Polisy_Service:1"></u:GetSystemStatus></s:Body></s:Envelope> Fri 2022/04/01 10:49:31 AM 0 -170001 <s:Envelope><s:Body><u:GetDisclaimerStatus xmlns:u="urn:udi-com:service:X_Polisy_Service:1"></u:GetDisclaimerStatus></s:Body></s:Envelope> Fri 2022/04/01 10:49:38 AM 0 -170001 <s:Envelope><s:Body><u:GetSysConf xmlns:u="urn:udi-com:service:X_Polisy_Service:1"><name>/CONF/NET/WOL.CFG</name></u:GetSysConf></s:Body></s:Envelope> Fri 2022/04/01 10:49:38 AM 0 -170001 <s:Envelope><s:Body><u:GetAllD2D xmlns:u="urn:udi-com:service:X_Polisy_Service:1"></u:GetAllD2D></s:Body></s:Envelope> Fri 2022/04/01 10:49:39 AM 0 -170001 <s:Envelope><s:Body><u:GetAllD2DStatus xmlns:u="urn:udi-com:service:X_Polisy_Service:1"><key></key></u:GetAllD2DStatus></s:Body></s:Envelope> Fri 2022/04/01 10:52:40 AM 0 -170001 <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_Polisy_Service:1"></u:GetSystemStatus></s:Body></s:Envelope> Fri 2022/04/01 10:54:58 AM 0 -170001 <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:ns="http://www.universal-devices.com/wsdk/isy/3.0"> <soap:Header/> <soap:Body> <ns:GetProgram/> </soap:Body></soap:Envelope> Fri 2022/04/01 10:54:58 AM 0 -10011 n/a Fri 2022/04/01 10:54:58 AM 0 -170001 <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:ns="http://www.universal-devices.com/wsdk/isy/3.0"> <soap:Header/> <soap:Body> <ns:GetProgram/> </soap:Body></soap:Envelope> Fri 2022/04/01 10:55:01 AM 0 -170001 <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:ns="http://www.universal-devices.com/wsdk/isy/3.0"> <soap:Header/> <soap:Body> <ns:GetProgram/> </soap:Body></soap:Envelope> Fri 2022/04/01 10:55:01 AM 0 -10011 n/a Fri 2022/04/01 10:55:01 AM 0 -170001 <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:ns="http://www.universal-devices.com/wsdk/isy/3.0"> <soap:Header/> <soap:Body> <ns:GetProgram/> </soap:Body></soap:Envelope> Fri 2022/04/01 10:56:05 AM 0 -170001 <s:Envelope><s:Body><u:GetErrorLog xmlns:u="urn:udi-com:service:X_Polisy_Service:1"></u:GetErrorLog></s:Body></s:Envelope>

I ended up pulling the power on the ISY and plugging it back in. It seems to have resolved the issue.

It appears the Insteon Wireless Thermostat v.0E 2441ZTH does not work correctly. I does not display any information. Sometimes it will show Humidity. I tested a 2441TH and it worked fine. I also tested the same 2441zth on my older ISY994i and it worked fine. Regards, James

NP I figured you guys would. Still an awesome product. No complaints here.

Same here I bought a new ISY with the new Z-Wave module and 5.3 installed and my z-wave Schlage locks no longer work. Hooked up my old ISY with the old modules re-added all the z-wave devices and re-synced the networks and it works great. There is a issue with firmware 5.2 and above I guess. So I removed all my z-wave devices factory reset all of them and tried the new ISY again and still same results. I even put the ISY much closer to the door and had the same results. I did the same process to my old device and it works great. For now I would stay away from 5.2 and 5.3. -JP