Javi

@Jimbo , I think you are on to something. This appears to be the behavior in other nodeServers as well as the following will always be true also. NodeDef <st id="GV16" editor="UV"/> Editor <editor id="UV"> <range uom="71" min="0" max="15" prec="1"/> </editor> Variable Test - [ID 0084][Parent 000F] If 'WeatherBit Weather' UV Index is not '$Int_test UV Index' Then Set 'Devices / Basement / Basement Computer Room Lights' Beep $Int_test = 'WeatherBit Weather' UV Index UV Index Else - No Actions - (To add one, press 'Action')

The value is numerical but raw. I believe "a.bcd" would be equal to "abcd". That said it appears you are correct that the voltage does not update its value to a variable so there may be an issue with the nodeServer or this may not be a comparable type. Maybe @Jimbo will know. "Battery level" appears to work so this may be a work around until the Voltage issue can be resolved. Jimbo, is it possible that this does not work because there is no "prec" declared in the Editor?

@briantreese are you using the url to isy? Also be sure the username an password are not wrapped with a new line char, local connection to the ISY will accept requests with some mistakes but the portal will not.

Thanks! I have spent too much time on this issue, funny how my.isy.io worked but when adding the isyKey it would fail. The malformed /reportURL must have been a copy paste error. Fixing the SOAPAction worked! Passing the isyKey in the Header also works.

@bmercier I am running into a couple of problems. I tried to use HttpURLConnection but the line "Post reuse HTTP/1.1" in the header before the first <Event>...</Event> will throw an exception so I guess I have to stick with SSLSocketFactory (or SocketFactory for local) for the raw output. So my question is, Can the URL to ISY be placed in the request header? POST /isy/url_to_isy/services HTTP/1.1 Host: my.isy.io Content-Type: text/xml; charset=utf-8 Authorization: Basic base64UsernamePassword Content-Length: 192 SOAPAction: urn:udi-com:device:X_Insteon_Lighting_Service:1#Subscribe <s:Envelope><s:Body><u:Subscribe xmlns:u='urn:udi-com:service:X_Insteon_Lighting_Service:1'><reportURL>REUSE_SOCKET</reportURL<duration>infinite</duration></u:Subscribe></s:Body></s:Envelope> Making a request with the header/envelope above will return either " HTTP/1.1 500 Internal Server Error" "Invalid response header received from ISY" on the first request, then "HTTP/1.1 817 unknown" "<?xml version="1.0" encoding="UTF-8"?><s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope"><s:Body><UDIDefaultResponse><status>817</status><info>n/a</info></UDIDefaultResponse></s:Body></s:Envelope>" on subsequent requests. It appears that 817 is listed as "You are already subscribed and there's no need to subscribe again" in the docs.

Thanks @bmercier, I am short of time today but now that I know it is on my side (again) I will try to find a fix in my code. This is for a a native android app (Java) and I was going off my my logs which did not show the actual socket request. Upon looking at my request the socket was using the host (url.getHost) which removed the endpoint. I am using the SSLSocketFactory Library so I may have to use a different library as it appears this only accepts the host and not an endpoint. Thanks again for your time! Javier

I just go around to installing multiple ISY on my portal account and have run into a problem. It appears that no matter which "URL to ISY" I use the (SOAP) socket will always connect to "My preferred ISY". This is not an issue with REST. If I delete "My preferred ISY" i get a Code 400 "Preferred ISY not set on user profile". How can we direct a socket connection to a specific ISY?

Thanks for your time and my apologies for not catching something so simple before posting. It was an error on my side, my app was adding the port to the wrong location (...isy.io/isy/XXXX:PORT instead of my.isy.io:PORT). I guess I have only used local connection for the past month.

Thanks, it appears that adding the port after the URL is causing the error. Was this changed? Edit: Sorry, it appears I made this change adding the port about a month ago. Not sure why it only presented itself now.

@bmercier maybe I am missing something, can you be more specific? This error appears to have started today. The indicator is Green, I am (and have been) using the credentials used for the Portal. Not sure why the SOAP Socket would work with this URL/credentials and REST would fail.

Hi @bmercier, The credentials are valid and the Socket is working however REST commands are failing with the 423 error. This can be replicated in the (Chrome) browser also. https://my.isy.io/isy/XXXXXX:443/rest/nodes/22 89 3A 1/cmd/DOF Where XXXXX is URL to ISY Returns "Requested ISY not found in the user's domain"

@Michel Kohanim I have a report of the Portal not accepting HTTP GET Rest requests and have verified I can also not make the requests Error Code: 423 Response: Requested ISY not found in the user's domain

All is good here also. Although it would be nice to know what causes this error as this is the second day in the last month where I have encountered this error code.

Ok not just me. I have had this error all day but it has not resolved. Rest working, but socket returns the following Code 404 Error contacting sub.server:ETIMEOUT @Michel Kohanim

How are you connecting to the ISY? I am having errors with the portal socket connect today. Came here to see if it is just me

I did something similar but used a dimmer switch as the countdown timer, this also incorporated a humidity sensor. Documented here: https://voiceforiot.wordpress.com/2018/12/22/automation-of-bathroom-fan-for-humidity-and-odor/

Thanks guys, I was able to change the user of the dir to polyglot from root which allowed the node server to run. I am still having a few issues, but the NS is running which should allow me to locate any other problems. One other question: Is it safe to delete the directories in the polyglot/nodeserver for a NS which I am not using?

Are there detailed instructions on installing a node server from a git repo via SSH to the Polisy? I have cloned a fork of the Notification NS to /var/polyglot/nodeservers and have run install.sh. The Node server appears in Register New Node Server and can be added but will never start. Log 2020-3-1 23:58:23 [polyglot] info: Notification(3): Attempting to install Notification NodeServer into ISY. 2020-3-1 23:58:23 [polyglot] info: Notification(3): Installed into ISY sucessfully. Profile uploaded, restart Admin console. 2020-3-1 23:58:23 [polyglot] info: Registered new local NodeServer: Notification(3) 2020-3-1 23:58:23 [polyglot] info: Waiting 10 seconds before starting Notification for the first time. 2020-3-1 23:58:33 [polyglot] info: NS: Starting Local NodeServer Notification profile number 3 :: Version 0.1.8 2020-3-1 23:58:35 [polyglot] error: NSChild STDERR: Notification: Traceback (most recent call last): File "./notification-poly.py", line 6, in <module> import polyinterface File "/var/polyglot/.local/lib/python3.7/site-packages/polyinterface/__init__.py", line 1, in <module> from .polyinterface import Interface, Node, Controller, LOGGER, unload_interface, get_network_interface File "/var/polyglot/.local/lib/python3.7/site-packages/polyinterface/polyinterface.py", line 83, in <module> LOGGER = setup_log() File "/var/polyglot/.local/lib/python3.7/site-packages/polyinterface/polyinterface.py", line 59, in setup_log os.makedirs('./logs') File "/usr/local/lib/python3.7/os.py", line 221, in makedirs mkdir(name, mode) PermissionError: [Errno 13] Permission denied: './logs' 2020-3-1 23:58:35 [polyglot] info: Notification(3): NodeServer Disconnected.

Just thought I would mention that you also have access to Global Caché's Control Tower Database which has ir codes for many devices. If i remember correctly you are only allowed 5 downloads per day (a download is a single ir code or a whole set, so be sure to select he whole set). If you do decide to go with the Global Caché's I recommend you do not get the WiFi versions as they are difficult to connect ( can provide links to setup if requested). Global Caché's also provides Windows (not sure about ios from memory) software to test/create/learn ir codes from the iTach. If anyone is interested I created a python script a couple of years ago to parse the email sent from the Control Tower Database so all ir codes can be saved to a .csv file. Link https://github.com/JavierRefuerzo/Global-Cache-Control-Tower-Email-Parser

I have a few Insteon Open Close and motion sensors but have converted most of the main entries to zwave. As I convert more sensors to zwave the insteon sensors are being placed on closet doors to trigger lights. My ISY (not the PLM), all networking equipment, and CCTV are on a UPS. I tried to document most of the features but I may have missed some things. The chime feature which can use tts to speak when a door opens may help you with the chimes you mentioned in the first post. It will also prevent you from arming if a sensor such as a door/window is violated (this can be disabled for motion sensors) and show you which sensor is violated. Let me know if you have any questions, Javier

I am using a very old Nexus 7 which would not work for surfing the web anymore because of speed and security issues. Aside from turning off by itself a few times a year it is solid. I needed a keypad also for my Mother in law and neighbors whom have access to my home. The app should work with any android phone or tablet with android 19 (released 2013) or above . I have tried it on a $30 Amazon fire tablet (with Google Play Services installed) as well and it works but the resolution is horrible. Once the app is out of testing I could add it to the Amazon App Store As well. I still have a lot of work to do on the app but it has been functional for over a year now with no issues (at least for me). The app is in open testing on Google Play and there appear to be a few other installs aside from mine but I have not received any feedback. One of the reasons I started making the Go2ISY Android App is to get a greater understanding of the ISY so I could make the IoT Security Panel App better. Once I am at a good place with Go2ISY I will be updating the IoT Security Panel to have many of the same features such as better Icons and UI.

I have done something similar. Looked everywhere for a keypad that would work (even direct from China) but could not find something reliable. You can see my solution here https://iotsecuritypanel.wordpress.com/setup/ and here: https://forum.universal-devices.com/topic/25580-new-app-iot-security-panel/ I tried Insteon Keypad links but it was too much trouble with too much inconsistency. I'd be happy to go into detail if requested. As for others comments: This is a trend with most IOT devices in the home. Let's try to make this better for the people whom decide to go this route. This may be a better solution than no monitoring.

Thanks Michel, Is there an updated 1_fam also?

Hi, I am looking at [id]_fam.xml files and ISY-WS-SDK and ISY-WS-SDK-Z-Wave for both versions 4.4.6 and 5.0.4. It appears that the [id]_fam.xml files have not been updated to reflect current devices as the documents do not match ISY-WS-SDK-Z-Wave section 7.3. Also I have an Insteon device which for which a nodeSubCategory is not listed. If I am reading the docs correctly The insteon Device <type> has the following format: "device category.device subcategory.version.reserved" So, <nodeCategory id="0" name="Controllers" >, but nodeSubCategory id=26 is not listed in 1_fam.xml. It appears there should be a few devices between the last id=18 and 26. If this is true where could I find this information? <node flag="0"> <address>3E EC D2 8</address> <name>mini - G</name> <parent type="3">57752</parent> <type>0.26.57.0</type> <enabled>true</enabled> <deviceClass>0</deviceClass> <wattage>0</wattage> <dcPeriod>0</dcPeriod> <startDelay>0</startDelay> <endDelay>0</endDelay> <pnode>3E EC D2 1</pnode> <ELK_ID>P11</ELK_ID> <property id="ST" value="0" formatted="0" uom="%/on/off"/> </node> Also I have the following Z-Wave device <node flag="128"> <address>ZW005_1</address> <name>Front Door Battery Level</name> <family>4</family> <parent type="3">19023</parent> <type>4.7.1.0</type> <enabled>true</enabled> <deviceClass>0</deviceClass> <wattage>0</wattage> <dcPeriod>0</dcPeriod> <startDelay>0</startDelay> <endDelay>0</endDelay> <pnode>ZW005_1</pnode> <sgid>1</sgid> <devtype> <gen>4.7.1</gen> <mfg>600.3.130</mfg> <cat>185</cat> </devtype> <ELK_ID>D12</ELK_ID> </node> I was able to find the <cat> in the ISY-WS-SDK-Z-Wave but I think UD should update 4_fam.xml doc to reflect current values to help others. 184 = Barrier (this is the last item in 4_fam.xml in both 4.4.6 and 5.0.4) 185 = Notification Sensor (this is the last item in ISY-WS-SDK-Z-Wave 7.3 in 4.4.6) 186 = Color Switch (this is the last item in ISY-WS-SDK-Z-Wave 7.3 in 5.0.4) Thanks, Javier

I have not updated to 5.xx, and they are available. Are programs available? Also I purchased the Network Module many years ago this may be a requirement for the Portal. Maybe ask about A/V availability in the part of the forum dedicated to the portal as my experience is limited.