Insteon Plugin Issues

[vitello]

Ron,

The Fixkey worked and I am able to use the Insteon plugin with G5 again. I upgraded to 519. I have a couple of issues:

1) The Insteon plugin Device Manager tab shows none of the device Loc/Name or Description data that I set under G4. I went back to G4 to check and they are fine there, but blank under G5.

2) The Insteon plugin Group Manager tab similarly does not have any of Group Name settings that I edited under G4. All Group names are simply Group 1, ...

3) The Link Manager tab shows about 80 missing links. Under G4 the Link Manager shows no missing links.

4) Under Settings->Plugins->Insteon it states that the Insteon Plugin is Version 1.4.5, APt:3. Under Settings->Insteon->Smarthome DM it states that the Plugin Version is 1.4.1.

5) By default the Smarthome DM and PLC Manager tabs are missing when I first open Settings->Insteon. I found I could get them to show up by unchecking and rechecking one of the other plugins, such as Zip Extensions and doing a lua script reset. This sometimes causes G5 to hang and I have to kill it using the Windows Taskmaster.

Thanks for the fixkey help.

Peter

[Promixis]

Ron,

The Fixkey worked and I am able to use the Insteon plugin with G5 again. I upgraded to 519. I have a couple of issues:

1) The Insteon plugin Device Manager tab shows none of the device Loc/Name or Description data that I set under G4. I went back to G4 to check and they are fine there, but blank under G5.

2) The Insteon plugin Group Manager tab similarly does not have any of Group Name settings that I edited under G4. All Group names are simply Group 1, ...

3) The Link Manager tab shows about 80 missing links. Under G4 the Link Manager shows no missing links.

4) Under Settings->Plugins->Insteon it states that the Insteon Plugin is Version 1.4.5, APt:3. Under Settings->Insteon->Smarthome DM it states that the Plugin Version is 1.4.1.

5) By default the Smarthome DM and PLC Manager tabs are missing when I first open Settings->Insteon. I found I could get them to show up by unchecking and rechecking one of the other plugins, such as Zip Extensions and doing a lua script reset. This sometimes causes G5 to hang and I have to kill it using the Windows Taskmaster.

Thanks for the fixkey help.

Peter



Hi Peter

1,2 .Location of Config files changed in G5. You can copy them from the G4 dir. to the G5 Config dir. in the app data folder.

3. Likely explained by 1

4. Typo :D

5. Interesting... need to look into this. Ron?

[vitello]

Mike,

You were right. there was a problem with the configuration file location. This fixed problems 1-3. I still by default don't see the Smarthome DM or the PLC Manager tabs.

Now I can play around with the Device Manager in NetRemote/NetRemote Designer. I regestered both programs a couple of days ago.

Peter

[quixote]

I can't link any of my devices. I've tried using all three methods mentioned in the instruction manual PDF. What is this fixkey thing you mentioned?
I've just formatted my aux computer and reinstalled Girder 5 and the Insteon plugin, and I haven't been able to link anything yet.

[Promixis]

your coreapp is likely bad

[quixote]

Here is the error message that i get when I try to download the coreapp via the settings panel:


COM error:(.\src\library\tLuaCOM.cpp,403):The server threw an exception.
stack traceback:
[C]: in function `SendText'
.\Insteon.lua:6277: in function <.\Insteon.lua:6276>



EDIT: I've found that that error was caused by my firewall and I've corrected it, however, even after re-downloading the coreapp, it seems that I still cannot link the devices.

[quixote]

Well, It seems that after I repositioned one of my signalincs and waited about 45 minutes the problem somehow righted itself on its own and I now have a (displayed) reliablility of around 70%. It seems reliable enough to me since it works every time.

[Promixis]

Well, It seems that after I repositioned one of my signalincs and waited about 45 minutes the problem somehow righted itself on its own and I now have a (displayed) reliablility of around 70%. It seems reliable enough to me since it works every time.


what coreapp do you see on the sdm page?

[quixote]

It says 12.

Can you please explain to me why this code:



DeviceID="XX.XX.XX"
DeviceLevel = 0

local device = Insteon.DeviceManager:GetDevice(DeviceID)
assert(device,'Device not found')
Insteon.DeviceCommands.SetLevel(DeviceID,DeviceLev el)

Does not work as it did before my reinstall? Also I keep getting


LOG: Insteon : 5 - SDME: NAK from SDM for device:
LOG: Insteon : 5 - DM: Device command unknown to device
LOG: Insteon : 5 - SDME: EXCEPTION: Access violation at address 0058A111 in module 'SDM3.exe'. Read of address 0000000A
LOG: Insteon : 5 - CM: SDM: EXCEPTION: Access violation at address 0058A111 in module 'SDM3.exe'. Read of address 0000000A
LOG: Insteon : 5 - CM: SDM Exception Count: 8


in the Lua console.

[quixote]

Sorry, I forgot to mention that I run the script remotely with Girder to Girder.

[Promixis]

what error are you getting for number 1

and

the other stuff is quality smarthome programming

[quixote]

What do you mean for number 1? If you ask me the whole SDM is number 2.

[quixote]

Where can I download the latest SDM?

[quixote]

Well, it seems that the Insteon plugin is not (directly?) to blame for my complaints. I know I've been a little bit of a PIA lately, but I've been so frustrated lately I've almost given up completely on home automation and setting up my dream HTPC in general. Then I realized that was never going to happen.
I'm sorry if I can't give you guys explict directions on the exact causes of my Girder woes, but we can't all be Mensa material like Mhwlng. ;)
Anyway, I've discovered that the Insteon plugin works fine, but it's actually something to do with the fact that I had a second computer set up to take care of my Insteon functions, and I was trying to use Girder to Girder actions to work them. So, as it turns out when I set up the PLC on my main computer and give up the idea of using DirectX for gaming on it, the Insteon seems to work flawlessly. I appologize for the false alarms.

[tmorten]

Glad to hear it's working! I pulled out some hair with my Insteon setup as well, so it definitely seems like there have been some kinks to work out both on the Smarthome side and with the Girder plug-in. Thanks to Mike for taking in all our feedback, and for writing the Insteon support in the first place!

Best,
Tim

[quixote]

Thanks to Mike for taking in all our feedback, and for writing the Insteon support in the first place!


Yes, and sorry Mike if I didn't seem grateful for implementing Insteon functionality into Girder. Sometimes when I get very frustrated I feel like certain projects that I'm working on are hopeless and I lose sight of the more important things to remember.

[Promixis]

Yes, and sorry Mike if I didn't seem grateful for implementing Insteon functionality into Girder. Sometimes when I get very frustrated I feel like certain projects that I'm working on are hopeless and I lose sight of the more important things to remember.

No problem. If I had saw the programmers of the SDM or PLC I would shoot them on sight. The stuff simply sucks.

The PLM will replace the existing stuff. Looks promising - but of course, its complete 200-300 hour redevelopment for us.