Status update

[BrianHumlicek]

In light of some new understanding of how transactions work, I'm reworking some of the brains of the TLink library. Once I get that solid again, I think I need to focus on shoring up some of my quick and dirty technical debt, such as documentation among other things. After that I'm going to figure out how to pull a full panel config and status on connection.

Eventually I see the web console being used for configuration of the panel to rename zones and setup their attributes, but I have a ways to go before we're there.

Brian

[mtwo]

Sounds great. Protocol documentation would be fantastic, as that was what was blocking me when I was attempting to make progress last summer. The more of the protocol that gets documented, the more easily others (and AI coding tools) can assist.

[BrianHumlicek]

I've been working in the branch low level refactor. I reworked the client and session to align with my current understanding. I have tested this and it seems to be working well. I went ahead and started cleaning up some leftovers from previous iterations in the extensions and logging and revamped the serializer.

I have moved on and added a dev console for testing messages and responses. It's proving to be helpful and I am currently testing a command to get the zone labels. What is still elusive is how best to find out what zones are configured. Part of me is beginning to think the expected usage was to assume all zones are active. If I don't find a command that will report it I will look into reading the actual section config and figure it out from there. Things are progressing.

On a side note, GitHub Copilot has forever changed how I approach development, it's a new world where I alone am producing the output of a small/medium team. It's been truly incredible.

Brian

[mtwo]

If you haven't tried them already, I've had even better luck with Claude Code and OpenAI Codex. Might be worth checking out!

[BrianHumlicek]

I figured out how to pull zone and partition status and labels at will. The only caveat is, I still don't know how many zones are 'configured'. I can just pull all 32 zones (or how ever many your controller has). I may just make this a setting for the time being until I figure out how to actually get the number.

Maybe before the weekend is over I'll have an update that gets a full partition status on connection so you don't have to wait and trigger zones to get it to show up.

Brian

[BrianHumlicek]

I have been working on the the section read so I can get which zones are actually enabled, and I think I was able to get the data for the first time. It will be a bit before I have it all working, but we should have real zone config soon. Along with this will come the ability to configure things too which should be handy.

FYI, this required the ConfigEnter commands to work which was figured out with the zone bypass that was added, so we are building on what we learn.

Brian

[BrianHumlicek]

I think there was a bug with the attributes. I have a big change that should fix it and add more stuff coming in a few minutes actually.

Brian

[BrianHumlicek]

Actually it looks like I already pushed the majority of changes.

[BrianHumlicek]

I have added file save and load as well as print. I'm feeling pretty good about the functionality now, though it needs testing. From here I think I just need to add more relevant sections.

[piotrantosik]

Tested it, works fine - attributes are read and written correctly.

I'm currently working on mapping zones to proper types in Home Assistant; however, this depends on your branch as it needs the panel config
I'm currently working on mapping zones to proper types in Home Assistant. However, this depends on your branch as it needs the panel config - for now, it always sends as a door.

[BrianHumlicek]

I went ahead and merged it. I'll add more section data as I see the need.