bpwwer

Would a windows command line utility that did this be helpful? Not that I need more things to do but this seems pretty simple. Even a GUI based app wouldn't be too hard, I have most of the code to do this in one of my plug-ins already.

ST = Status (current device on level (0 - 255) OL = On Level, the level the device will go to when switched on RR = Ramp Rate. The Web Services output does define some (maybe all?) of the stuff you'll see in the log but it's not really in an easy to read format. If you want to try, point your browser to http://your ISY's IP address/WEB/udiws10.ws and you should get some XML that describes all the methods, parameters, constants, etc. supported by the ISY. Buried in there is some information about what you see in the log.

I just checked and double checked and I'm not seeing any problems. When I subscribe, I get a node status event for each node and then start getting the _0 heartbeat events. It's working for both my plug-in code and if I just telnet to the ISY send the subscribe XML. I didn't have to change anything in my code after upgrading to 2.6.7. I am using the reuse socket and timeout infinite values for the subscription.

Michael, I used the PLC plug-in for a while and then played around with the PLM plug-in beta. But now, like you, I don't have either connected to the ML machine. Currently, the plug-in allows control of devices using commands like MLISY|Hall Light~DON~200 It also keeps a set of variables in ML synced with the current status of each device. So right now, you could create rules that fire things off when a variable status changes. I had forgotten about the ability to assign ML commands to buttons inside the plug-in. That should be possible. Of course this means I'll have to figure out how to create and manipulate databases using .net so I can save all this type of info. I'd say I probably have an alpha quality release right now. The features that are there work, but it is missing things. Also, the installation is all manual right now.

Michael, Before you go spend any money on another PLM... I've been working on a plug-in to allow interaction between ML and the ISY. It's still got some issues so it's not yet ready for general testing. Can you explain and/or post an example of how you're controlling the whole house audio via Insteon? I do have a Russound hooked up to ML so maybe I can test this out and make sure my Plug-in can provide equivalent functionality to what you have now.

I do have an extra PLM, but I won't be able to unplug the current one until tonight. However, it is still mostly working. I am able to control devices via the web interface and bring up the admin console, as long as I don't re-boot it. If I do, then I'll have to power it down for a couple of hours before I can use it again. As soon as I do anything that requires a re-boot (switch back to using DHCP, firmware update, etc.) it thinks the cable is unplugged and I have to power it off for a while. I think this is consistent with a problem I've had with this box for a while. For the past few firmware updates, I've had to power cycle it to get it working. It would do the firmware update, reboot, and then it would not be accessible until I power cycled it. It's just getting worse now. A quick update to note that it wasn't the upgrade itself that failed. It seems there may be a heat related issue with the network hardware itself. After sitting unplugged all night, I plugged it back in on a whim and it worked ... for a little while.

A quick update to note that it wasn't the upgrade itself that failed. It seems there may be a heat related issue with the network hardware itself. After sitting unplugged all night, I plugged it back in on a whim and it worked ... for a little while.

Both MEM and ERR are flashing on 2 seconds off 3 seconds. The link light on the ethernet port is lit. After a power cycle, all the lights flash and it seems like it is communication with the PLM because it's light and other insteon devcices' lights are flashing too. This happens for about 1 minute and then it goes back to flashing the mem/err lights as above. It doesn't appear to have requested an address from the DHCP server at any point. Ahh, connection up the serial port provides a bit more info. it's displaying "network cable disconnected or DHCP server error" over and over. Resetting the router/dhcp server makes no difference Manually configuring the network on the ISY makes no difference Replacing the network cable makes no difference. Switching to a different port on the router makes no difference.

On my ISY26: Something when wrong when I updated. I downloaded the zip file and manually updated. Now the box is dead (well not accessible via the ethernet port). I've tried power cycling it and it still doesn't come back. When I say not accessible, I mean it's not sending the UPNP broadcasts and it's not responding on the IP address previously used. I don't have physical access to the box right now so I can't see the lights. When I do get back home, is there anything I should check before trying to factory reset it?