My issue, or concern if you will, is that Securifi as a company fails, then we are all left holding on to unsupported and potentially dead end hardware. I'm not saying it will happen, but I'm certainly not getting a warm and fuzzy feeling from the current lack of communication, which is why I posted what I did. I'm happy enough now with how it works, as I haven't even tried using rules yet, but I'd love if it worked better.
The point of this thread is that there are people willing and able to help test and debug new sensors for free, but we haven't gotten a 'no thanks' from Securifi, much less a response at all. That's what concerns me.
Securifi is ok financially (take a look at the PTD papers filed in India & TW then do a little digging) but IF something should happen, we would be stuck just like we would be with any product from a defunct vendor.
The Z-Wave alliance has rules about what can be made public, that's why Open Z-Wave came into existence. There are something we just aren't going to have access to, that's just the way it is with Z-Wave. Now there are plenty of folks that have reversed engineered a lot of Z--Wave info and that's out there if you look for it but doing so goes against Securifi's Terms and Conditions.
Same thing holds true with certain driver info as it relates to Realtek. @Lars mentioned as much in a few posts. Then there is the whole buy out thing of Realtek and what is happening there. Bottom line, Realtek strong urged Securifi to use a specific version of OpenWRT and not something newer. The original chip selection by Securifi had them sticking their neck out a bit (a few articles out there about the chip selection concern) and I doubt they are going to go against the chip manufacturer's recommendation.
So, we have a toolchain and an SDK. Looking at the startup files and log files, we can get an idea of what is going on and work with that. What we can't do is mod haserver code.
Securifi has been pretty willing to look at new sensors if someone sends them something. My experience with direct technical support has been very positive and timely. (i.e. sending logs, exchanging emails)
No, there isn't as much "presence" as there was with Lars, but to be honest, there isn't much user action here on the board either.
Every specific issue I have, incorrect sensor management or reporting to IOS or Android Apps, is being worked and for all I have a workaround. My voice response, shell scripts and apps are all working and I don't see any major stumbling block with Open HAB integration or integrating with several other open source options.
IF someone is actually going to work up a new sensor, I don't see a problem with getting that done either. Use the existing command classes, identify the unique manufacturer specific info, generate the XML info needed, identify the hooks for the server code and send one to Securifi. Have at it.
