Insteon PLM Component

[bjames3]

Hi Bill,

There should be some output in the lua console. You can turn this on via the Interface tab. I need to see that to determine the devcat/subcat. You can also hit the update button at the bottom of the add/edit tab to see if Girder can recognize the devices.

Smarthome may have changed the dev/sub cats and that is why G is not recognizing them.

Mike, thks for prompt reply. Attached is the console output when I ping all three devices. I also pressed the update button
numerous times but nothing happened.

Bill

[Mike C]

Ok, you need to delete the devices and then re add them and capture output. Paste it here.

[bjames3]

Ok, you need to delete the devices and then re add them and capture output. Paste it here.

Mike, I removed all three devices but only added back the dimmer as the behavior for all is the same (less stuff for you to wade thru).
Once again when I linked the device it was not automatically imported.
After linking I manually added it. The console output is attached.
Thank you.
Bill

[Mike C]

ok, that helps. need to see what the devcat/subcat is of the PLM.

easiest might be to delete the plm on the interfaces tab. clear out the luaconsole window. re add and paste the output here.

[florp]

Mike,

I'm finally making the move from PLC to PLM, but am running into a problem getting InsteonC working. I've done a clean install of Girder 5, but it appears to be failing to create the Transport device:

LUA console error on startup:
Welcome to Promixis Girder 5.0.14 build 551
Timer (pcall): ...uascript\components\Insteon\CommunicationManage r.lua:899: attempt to index local `plmd' (a boolean value)
stack traceback:
...uascript\components\Insteon\CommunicationManage r.lua:899: in function `Handler'
...Tools\Girder5\luascript\Classes/WaitForCondition.lua:49: in function <...Tools\Girder5\luascript\Classes/WaitForCondition.lua:44>

Transport Manager window is empty.

Transport Resources:
Device Manager TCP/IP Listen, Port 20009 (ConnectionFailed)
PLM Serial, Port: 3, 19200 8N 1 N

Insteon Interfaces:
Current default powerline interface No ready transports available
Powerline Interfaces:
PLM [1A.76.6C] Powerlinc Modem Serial - Status: Ok
Preferred default powerline interface: PLM

I've checked the logs for any errors, but don't see any beyond the lua error above.

Any suggestions?

Many thanks,

-Scott

[Mike C]

Scott, just found that bug.

Please update to version 764

[Mike C]

Mike, thks for prompt reply. Attached is the console output when I ping all three devices. I also pressed the update button
numerous times but nothing happened.

Bill

try the latest update - i think this will fix the problem.

[florp]

That fixed it, thanks Mike!

Unfortunately, now that it's transmitting, I'm finding that the PLM isn't able to communicate with any of my existing Insteon devices; none of them respond to the PLM's GetInsteonEngineVersion requests.

The PLC was able to communicate with them from the same location; I don't have to manually link them first, do I? I'm assuming I should be able to add them in the Devices Add/Edit window directly.

Thanks again,

-Scott

Update:

It seems that communication isn't completely dead; the PLM appears to be getting responses to ping requests from some devices 3 to 7 minutes after sending, e.g.:

LOG: Library\Lamp [01.06.6A] : 4 - Error in response to sending last command NAK Ping 15:55:29:399
Rx Transport 1A.76.6C: From: 01.06.6A To: 1A.76.6C Msg: ACKDirect Cmd1:0F Cmd2 00 15:58:37:271

For whatever that's worth.

[bjames3]

try the latest update - i think this will fix the problem.

That seemed to do it. Now I can get to work. Thanks Mike!!

[Mike C]

That fixed it, thanks Mike!

Unfortunately, now that it's transmitting, I'm finding that the PLM isn't able to communicate with any of my existing Insteon devices; none of them respond to the PLM's GetInsteonEngineVersion requests.

The PLC was able to communicate with them from the same location; I don't have to manually link them first, do I? I'm assuming I should be able to add them in the Devices Add/Edit window directly.

Thanks again,

-Scott

Update:

It seems that communication isn't completely dead; the PLM appears to be getting responses to ping requests from some devices 3 to 7 minutes after sending, e.g.:

LOG: Library\Lamp [01.06.6A] : 4 - Error in response to sending last command NAK Ping 15:55:29:399
Rx Transport 1A.76.6C: From: 01.06.6A To: 1A.76.6C Msg: ACKDirect Cmd1:0F Cmd2 00 15:58:37:271

For whatever that's worth.

that is a weird delay until you get an ack. also interesting is that you are getting a NAK to a ping command. what device is doing that? .... you will need to relink devices to the plm. the plugin will try and do that as you add them. make sure you delete all links to the plc.