The future look bright and shiny. The (new?) class DeviceInformation look pretty complete and seem that every peripheral connected to the computer have and UUID (¿Universal? Unique Identifier):
is the “Id” of the AEOTEC USB Stick connected to the computer USB port.
I want point out the genericness of the Name field:
USB Serial Device (COM3)
and the PID of the Microsoft GPS module:
(…) no comments
Seem I could use it to automatically recognize when the USB STICK is swapped around on different ports (USB and virtual COM).
I’m writing a Windows Store application based on an actual hardware device. I need to be sure things stay idiot proof
Time to start organizing a bit the interface.
Three main (resizable?) sections
1. ON/OFF STATS
2. Behind the curtain USB STICK managment
3. The actual remote controls
4. A customizable view?
save/load node array list with user descriptions and note
Start reorganize the UI
MemoryGetID implemented (usb stick HomeID/NodeID)
Query each node and assign relative classes
Not sure what’s going on but the new (?) Windows.Devices.SerialCommunication is reporting a different virtual COM port than reported in the Device Manager Ports list…
I’ll keep investigating
“Better late than never” app is in developing now.
Finally the serial port support is back in the Windows Universal Application framework.
That’s mean a Windows Store Zwave Remote control and a Raspberry PI implementation.
The ZWave protocol is not complicate at all but every Home Automation solutions seem to rely on the (excellent?) OpenZWave library.
Even the AllSeen Alliance based their framework AllJoyn over it and Microsoft included the framework into the official ISO of Windows-IoT.
I decided to write from scratch my own implementation to be able to troubleshot and manage things a bit more directly and to learn something more about the ZWave and whole home automation scene.
I’ll try to release a working version before Xmas 2015.
The application will be able to manage every ZWave controllers that expose a virtual serial port and it will run over Microsoft Windows; typically an USB Stick. Im using for my tests the excellent AEOTEC ZW090A (Ill do a linux port at some point ).
Link to another post for my initial impressions about the key.
It should be able to manage
1. “learn mode” : inclusion and esclusion of the USB STICK as a secondary controller.
2. “add node” : include new devices to the zwave network.
3. “remove node”: esclude devices from the zwave network.
4. “Recognize BINARY SWITCHES, receive feedbacks and send commands.
5. “Recognize BINARY SENSORS, receive feebacks.
6. Dinamycally monitoring Windows virtual serial ports.
7. Reset the ZWave configuration of the USB STICK.I will implement shortly other neat features (expose the devices over the network for user friendly clients, more complete support of the ZWave protocol, more devices).
Im developing a program to control those handy Zwave USB stick controllers for some nifty home automationing.
Problem is microsoft VisualStudio keep losing the grip over the otherwise perfectly working virtual COM port created by the USB stick driver.
I can’t be the only one with this problem.
Usually deleting the driver and the windows reinstalling it let visual studio see the light again.