Heh, Sorry guys, can't help with the hardware...yet...
I ordered a HDK, but they cancelled it on me... (they probably want to see some form of progress)
I'm not sure how Insteon would work in 50Hz countries... It's not in the spec... It depends on how they sense the zero crossing...
Also, on the RF side, I don't know if the frequencies are legal in europe...
Here in Canada, it's not a problem.. 60Hz, 120/240 Single phase..
Thanks a ton! It's nice to hear praise once in a while... I don't think webPaul1 gets enough, he's really the brains of this whole project... I'm just taking a small tidbit of his masterpiece, and enhancing a bit.
Heh, If your going to throw your Zwave away, send it my way... I'll see what I can do with that..
Insteon does have it's quirks.. but it's a far cry from the ole CM11A I used for years..
I've been also keeping an eye on your MAME project with amaze... can't wait to see that happen...
Can you send the beer to Canada?
I think you're right about coming up with a grouping mechanism... You got me started, for that I am grateful!
The spidering of the network - in order for monitor mode to work, either the sender or the receiver MUST be in the PLM's link database.
I can track the Database Delta and compare that to detect if a database has changed.. this way I don't have to read the whole database, just the delta.
Spidering will simply be going out to all known devices, reading their database, and making sure all devices in their database linked to the PLM.
Ideally, when ANY new device gets linked to ANY current device, the 'spidering' should be able to detect it, and add it to the PLM.
this spidering scheme SHOULD be relatively fast too.. detecting if a database has changed or not is a simple 1 command/response. Depending on if the device supports DATA commands, reading the whole database could be as simple as 1 command, and receiving Extended packets back. (I'm working on that also) If the device does not support Data, then peeking into the database is the only option, however, I think I should be able to optimize what I need to actually read... thus not requiring to read the whole thing...
I haven't dug deep enough (for me anyway) into the security... but if I'm not mistaken, 2 of the 3 bytes ARE transmitted. It might take some time, but that only requires 256 different combinations to try to PING the device..
of course, with the timeouts, it may take a while, but eventually, it should 'catch' the right insteon ID.
More important, what if the device REALLY IS at your neighbour's place???
Let me think on that.. I don't know if I really want to HACK Insteon's security scheme... Is it really worth it, and is is really needed, if all you have to do is link the device with ANY other device..the spider process works so much better..
On a sadder note, I woke up today with my development PC dead.. Processor fan choked.. Processor is still good, replaced the fan, but now windoze won't boot...
So I had to add a serial port dongle to my Fiire Engine (It's about time eh?) and I'll be continueing development on my laptop.
so now, I have to make sure the dongle I added to the fiire has the right pinouts... (can't find the pinouts for it) I hope its standardized...