-
Posts
732 -
Joined
-
Last visited
Everything posted by MarkJames
-
Could it be that I don't have the necessary apache modules loaded? I ran #sudo a2enmod proxy #sudo a2enmod proxy_wstunnel and those services seemed to start - I rebooted and tried it again ad got #sudo a2enmod proxy Module proxy already enabled #sudo a2enmod proxy_wstunnel Considering dependency proxy for proxy_wstunnel Module proxy already enabled Module proxy_wstunnel already enabled
-
In the RequestHeader - where you have 'Basic <password>' is 'Basic' in your case the user name? If not then where does the ISY Username fit into this? mark
-
Ok - /etc/apache2/sites-available/000-default.conf now reads like this <VirtualHost *:80> ServerName www.homeonthewater.com ServerAdmin webmaster@homeonthewater.com DocumentRoot /var/www/html ProxyRequests Off ProxyPreserveHost On KeepAlive On KeepAliveTimeout 5000 ProxyVia Off <Proxy *> AuthName "Authentication Required" AuthType Basic AuthUserFile /etc/htpasswd-isy AuthGroupFile /dev/null require valid-user Order deny,allow Allow from all </Proxy> RequestHeader set Authorization "Basic xxxxxxxx" ProxyPass "/rest/subscribe" "ws://192.168.0.171/rest/subscribe" retry=4 ProxyPassReverse "/rest/subscribe" "ws://192.168.0.171/rest/subscribe" retry=4 ProxyPass /rest http://192.168.0.171/rest ProxyPass /services http://192.168.0.171/services ProxyPass /WEB http://192.168.0.171/WEB ProxyPass /USER http://192.168.0.171/USER CustomLog ${APACHE_LOG_DIR}/access.log combined ErrorLog ${APACHE_LOG_DIR}/error.log </VirtualHost> The actual file contains my password where the xxxxxxxx is I also tried it without the servername directive - no difference I rebooted the Raspi after each set of changes. .htaccess looks like AuthType Basic AuthName "Password Protected Area" AuthUserFile "/etc/htpasswd-isy" Require valid-user I had already created a user - contents of /etc/htpasswd-isy mark:$apr1$Hj3JPcuN$0jOuugXPPG7mrb3ND2CfF/ I don't even get as far as the authentication, though. All I get is connection reset mark
-
Ok - so I copied your virtualhost setup to my /etc/apache2/sites-available/000-default.conf file. I changed the ServerName and the IP's - hopefully those don't matter. Mine looks like this: <VirtualHost *:80> ServerName www.homeonthewater.com ServerAdmin webmaster@homeonthewater.com DocumentRoot /var/www/html ProxyRequests Off ProxyPreserveHost On KeepAlive On KeepAliveTimeout 5000 ProxyVia Off <Proxy *> AuthName "Authentication Required" AuthType Basic AuthUserFile /etc/htpasswd-isy AuthGroupFile /dev/null require valid-user Order deny,allow Allow from all </Proxy> RequestHeader set Authorization "Basic xxxxxxxxxxxxxxxxxxxx" ProxyPass /custom ! ProxyPass "/rest/subscribe" "ws://192.168.0.171/rest/subscribe" retry=4 ProxyPassReverse "/rest/subscribe" "ws://192.168.0.171/rest/subscribe" retry=4 ProxyPass / http://192.168.0.171/ CustomLog ${APACHE_LOG_DIR}/access.log combined ErrorLog ${APACHE_LOG_DIR}/error.log SSLEngine on SSLCertificateFile /etc/ssl/certs/wc.domain.com.pem SSLCertificateKeyFile /etc/ssl/private/wc.domain.com.key SSLCertificateChainFile /etc/ssl/AlphaSSLchain.crt </VirtualHost> # vim: syntax=apache ts=4 sw=4 sts=4 sr noet I then made the changes to the .htaccess file, removing the rewrite rule so isyProxy.php isn't used. It looks like this AuthType Basic AuthName "Password Protected Area" AuthUserFile "/etc/htpasswd-isy" Require valid-user After making the changes I reboot the RasPI. My website will load from within my LAN but REST calls fail with ERR_CONNECTION_RESET [edit] actually my website will NOT load from within my LAN - CONNECTION_RESET From outside my LAN (my cell phone) I get ERR_CONNECTION_REFUSED I've saved your socket test code from http://forum.universal-devices.com/topic/15248-problems-creating-a-websocket-connection/?p=150499 as socket.htm in both my root folder (/var/www/html) and also in a subfolder (/var/www/html/myapp). I cannot load either of these files from www.homeonthewater.com/socket.htm nor www.homeonthewater.com/myapp/socket.htm. Both return ERR_CONNECTION_RESET Mark
-
I just noticed that I had a choice between a wildcard certificate and a standard one. The price difference was significant so I took a standard one. Was that a mistake? I note your example uses lights.domain.com so I suspect that a standard certificate would not work for just domain.com. makr
-
I found instructions for installing the certificate - Copy the Certificate files to your server. Download your Intermediate (DigiCertCA.crt) and Primary Certificate (your_domain_name.crt) files from your Customer Area, then copy them to the directory on your server where you will keep your certificate and key files. Make them readable by root only. Find the Apache config file to edit. The location and name of the config file can vary from server to server - especially if you use a special interface to manage your server configuration. Apache's main configuration file is typically named httpd.conf or apache2.conf. Possible locations for this file include /etc/httpd/ or /etc/apache2/. For a comprehensive listing of default installation layouts for Apache HTTPD on various operating systems and distributions, see Httpd Wiki - DistrosDefaultLayout. Often, the SSL Certificate configuration is located in a <VirtualHost> block in a different configuration file. The configuration files may be under a directory like /etc/httpd/vhosts.d/, /etc/httpd/sites/, or in a file called httpd-ssl.conf. One way to locate the SSL Configuration on Linux distributions is to search using grep, as shown in the example below. Type the following command: grep -i -r "SSLCertificateFile" /etc/httpd/ Where "/etc/httpd/" is the base directory for your Apache installation. Identify the SSL <VirtualHost> block to configure. If you need your site to be accessible through both secure (https) and non-secure (http) connections, you will need a virtual host for each type of connection. Make a copy of the existing non-secure virtual host and configure it for SSL as described in step 4. If you only need your site to be accessed securely, configure the existing virtual host for SSL as described in step 4. Configure the <VirtualHost> block for the SSL-enabled site. Below is a very simple example of a virtual host configured for SSL. The parts listed in bold are the parts that must be added for SSL configuration: <VirtualHost 192.168.0.1:443> DocumentRoot /var/www/html2 ServerName www.yourdomain.com SSLEngine on SSLCertificateFile /path/to/your_domain_name.crt SSLCertificateKeyFile /path/to/your_private.key SSLCertificateChainFile /path/to/DigiCertCA.crt </VirtualHost> Adjust the file names to match your certificate files: SSLCertificateFile should be your DigiCert certificate file (eg. your_domain_name.crt). SSLCertificateKeyFile should be the key file generated when you created the CSR. SSLCertificateChainFile should be the DigiCert intermediate certificate file (DigiCertCA.crt) If the SSLCertificateChainFile directive does not work, try using the SSLCACertificateFile directive instead. Test your Apache config before restarting. It is always best to check your Apache config files for any errors before restarting, because Apache will not start again if your config files have syntax errors. Run the following command: (it is apache2ctl on some systems) apachectl configtest Restart Apache. You can use apachectl commands to stop and start Apache with SSL support: apachectl stop apachectl start Note: If Apache does not start with SSL support, try using "apachectl startssl" instead of "apachectl start". If SSL support only loads with "apachectl startssl" we recommend you adjust the apache startup configuration to include SSL support in the regular "apachectl start" command. Otherwise your server may require that you manually restart Apache using "apachectl startssl" in the event of a server reboot. This usually involves removing the <IfDefine SSL> and </IfDefine> tags that enclose your SSL configuration.
-
eek - ok - stymied before I even got past getting the certificate... I went to get my certificate and got to this. I have no idea what to do with this and it says that if I get it wrong it can't be changed.... sorry for all the handholding needed Server Information You must have a valid "CSR" (Certificate Signing Request) to configure your SSL Certificate. The CSR is an encrypted piece of text that is generated by the web server where the SSL Certificate will be installed. If you do not already have a CSR, you must generate one or ask your web hosting provider to generate one for you. Also please ensure you enter the correct information as it cannot be changed after the SSL Certificate has been issued. Web Server Type Please choose one... AOL Apache +ModSSL Apache-SSL (Ben-SSL, not Stronghold) C2Net Stronghold and all these that are likely not relevant.... Cobalt Raq Covalent Server Software cPanel / WHM Ensim H-Sphere IBM HTTP Server IBM Internet Connection Server iPlanet Java Web Server (Javasoft / Sun) Lotus Domino Lotus Domino Go! Microsoft IIS 1.x to 4.x Microsoft IIS 5.x and later Netscape Enterprise Server Netscape FastTrack Novell Web Server Oracle Plesk Quid Pro Quo R3 SSL Server Raven SSL RedHat Linux SAP Web Application Server Tomcat Website Professional WebStar 4.x and later WebTen (from Tenon) Zeus Web Server Other (not listed) CSR here it asks for a csr. I imagine I have to generate that on my server but have no idea how.
-
Just working on this now.... Looks like the Raspi3 installed 2.4.10 by default. Looking in apache2.conf I see I'm limping along here but I'm hoping that this means that mod_proxy_wstunnel and mod_proxy are both installed and enabled already? I just purchased a certificate and am waiting for it but in the meantime I'm trying to sort out the next step in your instructions about I'll do some googling to figure this out - I'm also not sure how to install the certificate that I get but that should be easily found on the web too. baby steps....
-
Thanks Michael. Company just left and I'm looking this over. FYI - the wiki is empty - you may want to check that. Is this the contents of virtualhost.conf or .htaccess? The authtype and require-valid-user fields make me think .htaccess but the servername and serveradmin looks like virtualhost.conf. I'm gonna play with this first thing in the morning. I have a couple of questions though. In the first example you say This is the example I put on the wiki (it proxies everything to ISY including the websocket subscription - except for the /custom path which is sent to the path /var/www/lights/custom for serving) What is the purpose of the custom path? My entire site lives in /var/www/html. Do I need to break out the rest or socket portions into a different folder? In the second example you say This example will serve everything from /var/www/lights - EXCEPT for /rest (which will be proxied to the ISY and handle the websocket subscription): This sounds like the more appropriate option for me - but does it mean that I need to keep the rewrite rule and isyproxy? Thanks so much for doing this - I'm sure many will benefit from this down the road. mark
-
I'm very much interested. Today is Canada day up here in the great white North and I've had far too many beer to be doing any coding but I'll look into that tomorrow and see if I can make it work. Many thanks, Mark
-
My home automation webpage is working well now but it polls ISY using the REST interface. I'd like to recode it using websockets. I'll preface this by saying that I can get websockets working - thanks to the help of mWareman - if my site is hosted by the ISY. However I'd like to be able to host my page on a raspberry pi 3 running apache. The reason for this is that I would like my site accessible across the WAN with no VPN but I want access control such as I can get from a php login page or by setting users up with .htaccess. I've not found a way to control access to an ISY based web page without using the cloud module or a VPN. AFAIK the isy webserver doesn't support php (correct me if I'm wrong as tbh I haven't tried) Mwareman was kind enough to backport his apache to my version and make changes to the virtuahosts.conf file which allowed him to subscribe from a server within the LAN but not on the ISY. However my application also uses the REST interface to turn lights on/off. That requires me using isyProxy.php (again, correct me if I'm wrong). With forward and reverse proxy setup in the virtualhosts.conf file and the rewrite rule that curls things through isyproxy.php I can't even load my page - it just stops - likely due to the rewrite rule. Is there a documented way to both subscribe to ISY AND use the REST interface to control it from a non-ISY hosted page? Or a way to control the ISY other than by a method which requires isyproxy.php? Thanks in advance, mark
-
Thanks Michael! I'd found the repository on github with a full implementation but it was for a test server and had little documentation with it - I think it was for more advanced programmers than myself. This is more my speed. Out of curiosity - before I rewrite chunks of code - is websockets compatible across most browsers? I've got a raspberry pi 3 hosting my site and it's not bothered by the constant polling. If the ISY isn't hurt by it either then I'm inclined to leave it the way it is if websockets might cause me some browser compatibility issues. mark
-
Thanks Michel, I've been learning javascript for the sole purpose of creating this page. I wasn't aware that subscribing/websockets was even an option. I'll see if I can find some more info about or some sample code in the wiki. mark
-
I've got a custom page designed to display the status of all the El;k zones, keypads, and areas in my house. There's about 45 total items to display. I'm using the REST interface to call /rest/elk/get/status and then parsing the xml to update all my html elements. I haven't found a way to specifically query an individual zone/area/keypad - all I've found is all or nothing. The REST call returns the status of, from what I can tell, everything known to the Elk - including the default 208 outputs. Anyways - it happens right quick and to give the appearance of 'real time' monitoring I've been updating the status of my html every few seconds - basically changing the color/text of a series of buttons according to their corresponding zone state - Violated, Normal, Bypass My question is at what point will the ISY start seeing degraded performance because of the frequent REST calls? Is there a recommended minimum interval between calls? Will frequent REST calls slow program flow/trigger? Thanks, mark
-
Definitely not a scene - just single devices. I'm just getting around to coding my site for scenes so I know there's none in there. I was thinking it might be a timing issue or collision issue between the REST interface and the 'regular' communication.... asynchronous stuff can be funny that way. I suspect ISY internally regulates it's communication to prevent collisions but has no way of knowing when I come along and throw a REST call into the mix mark
-
I'm finishing up a personal webpage for lighting control that uses the rest interface to turn lights on and off. It works fine but I've noticed that once in a while after the rest calls to turn on a light I'll get a 'cannot communicate with <light I just switched>' error from ISY admin console related to the light that I just controlled or polled via the rest interface. It doesn't matter, really, and if the admin console is closed then I wouldn't even know it. I'm just curious if there's something quirky that I'm doing with my rest calls or if this is just normal behavior when controls and queries come from the rest interface.. Thanks, mark
-
I think (hope) that the problem is solved. The recent PLM swap I did was to a v9B that I had as a spare. It caused a LOT of all-ons so I pulled it and replaced it with a 1617 v9E. Turns out my wife saw the v9B sitting on the counter, thought it was a 2443 access point and plugged it in. So I had 2 PLM's running - one of them the v9B. Hopefully the problem goes away now. Plus - on a bright note - the vendor (Aartech Canada) is swapping my 9B for a new 9E even though it's well out of warranty. Kudos to them for going above and beyond. mark
-
What I have are a series of programs that turn things off depending on flags that I've set. So the programs will run every ten minutes or so and turn lights off, say, if it's light out and it's an outdoor light, or if it's dark out, nobody is home, and it's a closet or something like that. The main program calls a series of sub programs something like this Run program ,<a> Run program <b> Run program <c> then I have program <a> turn off light 1 turn off light 2 turn off light 3 program <b> turn off light 4 turn off light 5 turn off light 6 program <c> - possible overlap here turn off light 5 turn off light 6 turn off light 7 turn off light 8 My understanding is that when ISY encounters a Run command in a program it starts that program running but doesn't wait for it to complete before executing the next line. Correct me here if I'm wrong. If that's true then it could be that I'm setting a dozen or more programs running nearly simultaneously that are all turning off lights and possibly causing the collisions? mark
-
I've modified my energy saver programs by adding a 2 second wait between each scene that it turns off. Does that seem like a reasonable first step? mark
-
Sigh.... So my ALL ON events continue. I'm back to one a day or so now despite having switched to a build 1617 v9E PLM This is the event viewer log of the minute or so leading up to the all-on. If you have a chance, Lee, could you see if anything looks 'suspect' to you? Sorry there's a bit here - I cut/pasted the last 15 seconds or so. At 8:09:25 a series of programs that turn off unneeded lights started - that's what sets all the traffic in motion. I can see that in the log file. I've highlighted an odd one with device 0C.80.93. It's a switchlinc Relay v.2C Thanks, mark Fri 06/10/2016 08:09:16 AM : [VAR 2 9 ] 1 Fri 06/10/2016 08:09:16 AM : [iNST-TX-I1 ] 02 62 10 A8 E0 0F 14 00 Fri 06/10/2016 08:09:16 AM : [iNST-TX-I1 ] 02 62 0C 80 93 0F 14 00 Fri 06/10/2016 08:09:16 AM : [ Time] 08:09:25 11(0) Fri 06/10/2016 08:09:16 AM : [iNST-ACK ] 02 62 10.A8.E0 0F 14 00 06 LTOFF-F(00) Fri 06/10/2016 08:09:16 AM : [iNST-SRX ] 02 50 10.A8.E0 40.D1.EC 2B 14 00 LTOFF-F(00) Fri 06/10/2016 08:09:16 AM : [std-Direct Ack] 10.A8.E0-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 06/10/2016 08:09:16 AM : [iNST-ACK ] 02 62 0C.80.93 0F 14 00 06 LTOFF-F(00) Fri 06/10/2016 08:09:17 AM : [iNST-SRX ] 02 50 0C.80.93 40.D1.EC 27 14 00 LTOFF-F(00) Fri 06/10/2016 08:09:17 AM : [std-Direct Ack] 0C.80.93-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Fri 06/10/2016 08:09:17 AM : [iNST-SRX ] 02 50 0C.80.93 40.D1.EC 23 14 00 LTOFF-F(00) Fri 06/10/2016 08:09:17 AM : [std-Direct Ack] 0C.80.93-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Fri 06/10/2016 08:09:17 AM : [iNST-TX-I1 ] 02 62 00 00 57 CF 14 00 Fri 06/10/2016 08:09:17 AM : [iNST-TX-I1 ] 02 62 00 00 36 CF 14 00 Fri 06/10/2016 08:09:17 AM : [iNST-TX-I1 ] 02 62 10 A8 E0 0F 14 00 Fri 06/10/2016 08:09:17 AM : [iNST-ACK ] 02 62 00.00.57 CF 14 00 06 LTOFF-F(00) Fri 06/10/2016 08:09:17 AM : [iNST-TX-I1 ] 02 62 0C 80 93 0F 14 00 Fri 06/10/2016 08:09:18 AM : [iNST-ACK ] 02 62 00.00.36 CF 14 00 06 LTOFF-F(00) Fri 06/10/2016 08:09:18 AM : [iNST-ACK ] 02 62 10.A8.E0 0F 14 00 06 LTOFF-F(00) Fri 06/10/2016 08:09:19 AM : [iNST-SRX ] 02 50 10.A8.E0 40.D1.EC 2B 14 00 LTOFF-F(00) Fri 06/10/2016 08:09:19 AM : [std-Direct Ack] 10.A8.E0-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 06/10/2016 08:09:19 AM : [iNST-ACK ] 02 62 0C.80.93 0F 14 00 06 LTOFF-F(00) Fri 06/10/2016 08:09:19 AM : [iNST-TX-I1 ] 02 62 00 00 58 CF 14 00 Fri 06/10/2016 08:09:19 AM : [iNST-TX-I1 ] 02 62 00 00 18 CF 14 00 Fri 06/10/2016 08:09:19 AM : [iNST-ACK ] 02 62 00.00.58 CF 14 00 06 LTOFF-F(00) Fri 06/10/2016 08:09:20 AM : [iNST-SRX ] 02 50 0C.80.93 40.D1.EC 2B 14 00 LTOFF-F(00) Fri 06/10/2016 08:09:20 AM : [std-Direct Ack] 0C.80.93-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 06/10/2016 08:09:20 AM : [iNST-TX-I1 ] 02 62 3D 2A 20 0F 11 FF Fri 06/10/2016 08:09:20 AM : [iNST-TX-I1 ] 02 62 00 00 4C CF 14 00 Fri 06/10/2016 08:09:20 AM : [iNST-ACK ] 02 62 3D.2A.20 0F 11 FF 06 LTONRR (FF) Fri 06/10/2016 08:09:20 AM : [iNST-TX-I1 ] 02 62 08 66 4B 0F 14 00 Fri 06/10/2016 08:09:21 AM : [iNST-SRX ] 02 50 3D.2A.20 40.D1.EC 2B 11 FF LTONRR (FF) Fri 06/10/2016 08:09:21 AM : [std-Direct Ack] 3D.2A.20-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 06/10/2016 08:09:21 AM : [iNST-SRX ] 02 50 3D.2A.20 40.D1.EC 23 11 FF LTONRR (FF) Fri 06/10/2016 08:09:21 AM : [std-Direct Ack] 3D.2A.20-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Fri 06/10/2016 08:09:21 AM : [iNST-ACK ] 02 62 00.00.4C CF 14 00 06 LTOFF-F(00) Fri 06/10/2016 08:09:21 AM : [iNST-TX-I1 ] 02 62 23 7D A0 0F 11 FF Fri 06/10/2016 08:09:21 AM : [iNST-TX-I1 ] 02 62 00 00 16 CF 14 00 Fri 06/10/2016 08:09:21 AM : [iNST-TX-I1 ] 02 62 00 00 5A CF 14 00 Fri 06/10/2016 08:09:21 AM : [iNST-ACK ] 02 62 08.66.4B 0F 14 00 06 LTOFF-F(00) Fri 06/10/2016 08:09:22 AM : [iNST-SRX ] 02 50 08.66.4B 40.D1.EC 23 14 00 LTOFF-F(00) Fri 06/10/2016 08:09:22 AM : [std-Direct Ack] 08.66.4B-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Fri 06/10/2016 08:09:22 AM : [iNST-ACK ] 02 62 23.7D.A0 0F 11 FF 06 LTONRR (FF) Fri 06/10/2016 08:09:22 AM : [iNST-TX-I1 ] 02 62 00 00 30 CF 14 00 Fri 06/10/2016 08:09:22 AM : [iNST-TX-I1 ] 02 62 00 00 21 CF 14 00 Fri 06/10/2016 08:09:22 AM : [iNST-TX-I1 ] 02 62 23 7E 01 0F 11 FF Fri 06/10/2016 08:09:22 AM : [iNST-ACK ] 02 62 00.00.16 CF 14 00 06 LTOFF-F(00) Fri 06/10/2016 08:09:23 AM : [iNST-SRX ] 02 50 23.7D.A0 40.D1.EC 2B 11 FF LTONRR (FF) Fri 06/10/2016 08:09:23 AM : [std-Direct Ack] 23.7D.A0-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 06/10/2016 08:09:23 AM : [iNST-TX-I1 ] 02 62 10 A8 E0 0F 14 00 Fri 06/10/2016 08:09:23 AM : [iNST-TX-I1 ] 02 62 0C 80 93 0F 14 00 Fri 06/10/2016 08:09:23 AM : [iNST-TX-I1 ] 02 62 00 00 2C CF 13 00 Fri 06/10/2016 08:09:23 AM : [iNST-ACK ] 02 62 00.00.30 CF 14 00 06 LTOFF-F(00) Fri 06/10/2016 08:09:23 AM : [ Time] 08:09:32 11(0) Fri 06/10/2016 08:09:24 AM : [iNST-TX-I1 ] 02 62 00 00 57 CF 14 00 Fri 06/10/2016 08:09:24 AM : [iNST-TX-I1 ] 02 62 00 00 36 CF 14 00 Fri 06/10/2016 08:09:24 AM : [iNST-TX-I1 ] 02 62 10 A8 E0 0F 14 00 Fri 06/10/2016 08:09:24 AM : [iNST-ACK ] 02 62 00.00.21 CF 14 00 06 LTOFF-F(00) Fri 06/10/2016 08:09:24 AM : [iNST-TX-I1 ] 02 62 0C 80 93 0F 14 00 Fri 06/10/2016 08:09:24 AM : [iNST-TX-I1 ] 02 62 00 00 58 CF 14 00 Fri 06/10/2016 08:09:24 AM : [iNST-TX-I1 ] 02 62 00 00 18 CF 14 00 Fri 06/10/2016 08:09:24 AM : [iNST-ACK ] 02 62 23.7E.01 0F 11 FF 06 LTONRR (FF) Fri 06/10/2016 08:09:25 AM : [iNST-SRX ] 02 50 23.7E.01 40.D1.EC 2F 11 FF LTONRR (FF) Fri 06/10/2016 08:09:25 AM : [std-Direct Ack] 23.7E.01-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Fri 06/10/2016 08:09:25 AM : [iNST-ACK ] 02 62 10.A8.E0 0F 14 00 06 LTOFF-F(00) Fri 06/10/2016 08:09:25 AM : [iNST-SRX ] 02 50 10.A8.E0 40.D1.EC 23 14 00 LTOFF-F(00) Fri 06/10/2016 08:09:25 AM : [std-Direct Ack] 10.A8.E0-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Fri 06/10/2016 08:09:25 AM : [iNST-ACK ] 02 62 0C.80.93 0F 14 00 06 LTOFF-F(00) Fri 06/10/2016 08:09:26 AM : [iNST-TX-I1 ] 02 62 3D 2A 20 0F 11 FF Fri 06/10/2016 08:09:26 AM : [iNST-TX-I1 ] 02 62 00 00 4C CF 14 00 Fri 06/10/2016 08:09:26 AM : [iNST-ACK ] 02 62 00.00.2C CF 13 00 06 LTOFFRR(00) Fri 06/10/2016 08:09:26 AM : [iNST-TX-I1 ] 02 62 08 66 4B 0F 14 00 Fri 06/10/2016 08:09:26 AM : [iNST-SRX ] 02 50 0C.80.93 40.D1.EC 2B 14 00 LTOFF-F(00) Fri 06/10/2016 08:09:26 AM : [std-Direct Ack] 0C.80.93-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 06/10/2016 08:09:27 AM : [iNST-TX-I1 ] 02 62 23 7D A0 0F 11 FF Fri 06/10/2016 08:09:27 AM : [iNST-TX-I1 ] 02 62 00 00 16 CF 14 00 Fri 06/10/2016 08:09:27 AM : [iNST-ACK ] 02 62 00.00.36 CF 14 00 06 LTOFF-F(00) Fri 06/10/2016 08:09:27 AM : [iNST-TX-I1 ] 02 62 00 00 5A CF 14 00 Fri 06/10/2016 08:09:27 AM : [iNST-ACK ] 02 62 10.A8.E0 0F 14 00 06 LTOFF-F(00) Fri 06/10/2016 08:09:28 AM : [iNST-TX-I1 ] 02 62 00 00 30 CF 14 00 Fri 06/10/2016 08:09:28 AM : [iNST-TX-I1 ] 02 62 00 00 21 CF 14 00 Fri 06/10/2016 08:09:28 AM : [iNST-ACK ] 02 62 0C.80.93 0F 14 00 06 LTOFF-F(00) Fri 06/10/2016 08:09:28 AM : [iNST-ACK ] 02 62 0C.80.93 0F 14 00 06 LTOFF-F(00): Duplicate or ACK for a different device Fri 06/10/2016 08:09:28 AM : [iNST-TX-I1 ] 02 62 23 7E 01 0F 11 FF Fri 06/10/2016 08:09:28 AM : [iNST-SRX ] 02 50 10.A8.E0 40.D1.EC 2B 14 00 LTOFF-F(00) Fri 06/10/2016 08:09:28 AM : [std-Direct Ack] 10.A8.E0-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 06/10/2016 08:09:28 AM : [iNST-ACK ] 02 62 00.00.58 CF 14 00 06 LTOFF-F(00) Fri 06/10/2016 08:09:28 AM : [iNST-SRX ] 02 50 10.A8.E0 40.D1.EC 23 14 00 LTOFF-F(00) Fri 06/10/2016 08:09:28 AM : [std-Direct Ack] 10.A8.E0-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Fri 06/10/2016 08:09:29 AM : [iNST-ACK ] 02 62 00.00.18 CF 14 00 06 LTOFF-F(00) Fri 06/10/2016 08:09:29 AM : [iNST-ACK ] 02 62 3D.2A.20 0F 11 FF 06 LTONRR (FF) Fri 06/10/2016 08:09:30 AM : [iNST-SRX ] 02 50 3D.2A.20 40.D1.EC 2B 11 FF LTONRR (FF) Fri 06/10/2016 08:09:30 AM : [std-Direct Ack] 3D.2A.20-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 06/10/2016 08:09:30 AM : [iNST-ACK ] 02 62 00.00.00 CF 11 FF 06 LTONRR (FF) Fri 06/10/2016 08:09:30 AM : [iNST-SRX ] 02 50 3D.2A.20 40.D1.EC 23 11 FF LTONRR (FF) Fri 06/10/2016 08:09:30 AM : [std-Direct Ack] 3D.2A.20-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Fri 06/10/2016 08:09:30 AM : [iNST-ACK ] 02 62 08.66.4B 0F 14 00 06 LTOFF-F(00) Fri 06/10/2016 08:09:31 AM : [iNST-SRX ] 02 50 08.66.4B 40.D1.EC 2B 14 00 LTOFF-F(00) Fri 06/10/2016 08:09:31 AM : [std-Direct Ack] 08.66.4B-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 06/10/2016 08:09:31 AM : [iNST-SRX ] 02 50 08.66.4B 40.D1.EC 23 14 00 LTOFF-F(00) Fri 06/10/2016 08:09:31 AM : [std-Direct Ack] 08.66.4B-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Fri 06/10/2016 08:09:31 AM : [iNST-ACK ] 02 62 23.7D.A0 0F 11 FF 06 LTONRR (FF) Fri 06/10/2016 08:09:31 AM : [iNST-SRX ] 02 50 23.7D.A0 40.D1.EC 2F 11 FF LTONRR (FF) Fri 06/10/2016 08:09:31 AM : [std-Direct Ack] 23.7D.A0-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Fri 06/10/2016 08:09:31 AM : [iNST-ACK ] 02 62 00.00.16 CF 14 00 06 LTOFF-F(00) Fri 06/10/2016 08:09:32 AM : [iNST-ACK ] 02 62 00.00.5A CF 14 00 06 LTOFF-F(00) Fri 06/10/2016 08:09:32 AM : [iNST-ACK ] 02 62 00.00.30 CF 14 00 06 LTOFF-F(00) Fri 06/10/2016 08:09:33 AM : [iNST-ACK ] 02 62 00.00.21 CF 14 00 06 LTOFF-F(00) Fri 06/10/2016 08:09:33 AM : [iNST-ACK ] 02 62 23.7E.01 0F 11 FF 06 LTONRR (FF) Fri 06/10/2016 08:09:33 AM : [iNST-SRX ] 02 50 23.7E.01 40.D1.EC 2F 11 FF LTONRR (FF) Fri 06/10/2016 08:09:33 AM : [std-Direct Ack] 23.7E.01-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Fri 06/10/2016 08:09:47 AM : [FileOpen ] Open failed for [/CONF/NET/WOL.CFG] ® Fri 06/10/2016 08:10:15 AM : [VAR 2 9 ] 0
-
Hi Michel, These are the big ones (though they're a couple of years older now) - the 2440's. I can write to them but not if they're right beside an AP or dualband device. I generally put them in a drawer or cupboard and then they write just fine. It may be that my situation is different as I have quite a number of access points (2443) in my install. My home has an unusual powerline system. Back in the early '80s the power company offered a program where they charged heating/cooling at a reduced rate. They would install a second meter in your home so that the power came in to the main meter and then a subpanel was fed from the main *through* a second meter. At the end of the billing cycle they would total up your use and subtract the amount that was used on the second panel. That difference was charged at regular rates while the heating meter rate was half that. We have that system to this day - we get charged 3.5 cents/kWh for heating power. Obviously I'm not giving up a great deal like that! Anyways - sorry to drone on - but the end result is that I have a meter interfering with my install. Most devices are on one side of it but some are on the other. Insteon (and previously X10) signals have a hard time flowing reliably through the meter so I've put in a number of AP's to wirelessly bridge this deficiency. It took some time to get my Insteon system (92 devices) running reliably. I've got a couple of the original Signalincs still in use as well as multiple Signal Bridges (I have 7 panels in the house). At this time it's pretty solid - though even with my recent v9E PLM I'm getting occasional ALL-ON events that I'm troubleshooting my way through. It could well be that it's the multiple AP's or Signalincs that cause the write trouble, though I've got at least a dozen or more dual band devices now as well that could be involved. Anyways - I just noticed this thread and figured that I had encountered a similar problem - 2440's directly beside a dual band (2413s) PLM won't write at all. As soon as I get some distance from the PLM or tuck it in a drawer it starts to write just fine. mark
-
This is a bit late of a response to this but I thought I'd throw this in here in case anyone else has this problem I have the same issue writing to my remotelincs. For some reason if I'm too close to an AP or dual-band device it won't write. Rather than walk around the house, though, looking for an area that works better I just put my remotelinc in a kitchen cupboard or desk drawer. That seems to weaken the signal strength to it enough to get a successful write. mark
-
Thanks Paul, I've put it in feature requests here http://forum.universal-devices.com/topic/19088-keypadlinc-button-numbers-be-displayed/ Cheers! mark
-
Yep - I definitely *could have* or *should have* put a designation of some sort with each of my 160 KPL buttons but you know what they say about hindsight... The alphabetizing is the problem. If there was either a way to turn the alphabetizing off or to have the UI indicate which button is which I think that would be an improvement. Perhaps I'll put this in as a feature request...
-
I'm not - I use the button names. It's just for organization. I wanted to make the left button on the second row into a controller for a different scene than it was already assigned to. Without going down and looking at it I didn't know which scene the left button on the second row was already assigned to. I suppose if I'd taken all the buttons off a KPL without noting what they were assigned to it would be a bigger problem - I'd have to reinstall it and press each button individually to figure out which was which. mark