Xero wrote:I can't seem to find any documentation on code "616" which is being sent from my panel.
The raw code I get is, for example:
And I am assuming this is code 616 with the data 0000200000000000
I suspect it has something to do with zone bypassing, as I was testing some stuff related to that and started getting exceptions due to this unhandled code. Is there any documentation as to what this is? I was almost hoping maybe it's an output of the bypassed zones, which might actually be useful to me....
I also suspect this must be a new feature? I don't recall having my code throw exceptions after bypassing zones until now.
Oh, my bad. Yes we added the long requested "bypass status" for DSC and upcoming UNO versions. This was done initially with the customer portals in mind but we also added a command for TPI users. I'll ask Mike to upload the latest version of the doc on this thread but in the mean time you are correct, 616 is...
Bypassed Zones Bitfield Dump
This command is issued upon leaving Zone Bypass programming (*1 on the keypad). It is a 16 character HEX string representing an 8 byte bitfield. This bitfield indicates which zones are currently in bypass. A “1” indicates the zone is in bypass. The lower 8 zones are in the first position of the bitfield. The developer can force this dump by using the keystring commands to enter and leave zone bypassing. i.e. “*1#”
local selfId = fibaro:getSelfId();
local ip = fibaro:get(selfId, 'IPAddress');
local port = fibaro:get(selfId, 'TCPPort');
tcpSocket = Net.FTcpSocket(ip, port);
bytes, errorCode = tcpSocket:write("what do I put here")