Here is some of the output and screenshot i got from some quick testing. I'm not sure what you need but this is what it looks like. I broke it up into a few sections for each of the captures
Announcement
Collapse
No announcement yet.
KinCony KC868-COLB
Collapse
X
-
Actually, I checked the log you provided, it's sufficient for now, so I don't really need to remote at this stage.
The only problem - looks like the log does not show the message headers/footers, only the data, i.e. it says "data length: 61", but only shows "01 00" - which can be a problem without documentation.
Is it using WiFi or RS232?
Are you familiar with Wireshark or Fiddler? https://www.educba.com/wireshark-vs-fiddler/
- Likes 1
Comment
-
I found this: https://github.com/markvdb/kc868col/...hexprotocol.md
And I like the comment there: "In short, you might get decent hardware, but don't expect anything resembling customer service"
Comment
-
The above document seems to match the log, i.e. https://github.com/markvdb/kc868col/...-switch-0xc023 matches "Send ReadSwitchCmd:5E 01 23 C0 01 00 00 ..."
Comment
-
Originally posted by alexbk66 View PostI found this: https://github.com/markvdb/kc868col/...hexprotocol.md
And I like the comment there: "In short, you might get decent hardware, but don't expect anything resembling customer service"
I have wireshark capture already from earlier. It's mostly gibberish but if you want it for the headers then it may be what youre looking for
Comment
-
Originally posted by alexbk66 View PostI found this: https://github.com/markvdb/kc868col/...hexprotocol.md
And I like the comment there: "In short, you might get decent hardware, but don't expect anything resembling customer service"
I reached out to him after purchasing the colb because it wasn't working over Ethernet. The board was acting strange with only WiFi working. He responded pretty fast saying to post on the forum because it was late in China or wait till the next day to ask him directly. Turns out there was something wrong with the firmware on the board based on a find from someone else with a different issue. After flashing it, all started working fine. It's still acting strange but since the inputs are all working I'll reach out later to resolve
Comment
-
Originally posted by doomngloom View PostI have wireshark capture already from earlier. It's mostly gibberish but if you want it for the headers then it may be what youre looking for
Comment
-
Originally posted by doomngloom View PostIn all honesty if he had an analog input board alone similar to the AI board of his I wouldn't bother with this one. I just want the digital and analog inputs to work with
[EDIT]
I personally prefer ControlByWeb devices - 100 times more professional https://forums.homeseer.com/forum/hs...et-and-web-i-o
Comment
-
Originally posted by alexbk66 View Post
I just don't really understand what exactly they are sending. They call the protocol "HEX", but really I guess they send binary, but HEX is only used for display in the debug tool? Or they actually send the HEX string?Attached Files
- Likes 1
Comment
-
I personally prefer ControlByWeb devices - 100 times more professional https://forums.homeseer.com/forum/hs...et-and-web-i-o
Comment
-
Originally posted by alexbk66 View Post
How many analog inputs do you need?
Maybe play with it to try and get power monitoring similar to what the brultec does. if its possible. havent played with it yet. i finished most of my digital input testing already and will hopefully start moving my elk devices to them since the plugin is no longer actively supported. I already purchased the blade security and russound plugin so that should hopefully take the place nicely for my sensors.
Comment
-
Originally posted by alexbk66 View PostI personally prefer ControlByWeb devices - 100 times more professional https://forums.homeseer.com/forum/hs...et-and-web-i-o
Comment
Comment