Are you willing to share? I lost ALL versions in a major crash. I would really like version 4.1
Does anyone have version 3.8. I have 4 and 6, glad to share, but I need 3.8 for a LT 2000 (Standard) CCU.
For those that want litetouch 2k support:
1 Like
Hello new friends. I just purchased a home with a Litetouch 2000 system and I’m looking for the best place to start. I have a Ubiquity network rack all set up, but I haven’t yet played with home assistant. I wanted to get confirmation on my options before I started diving in. I will be integrating my solar, powerwalls, EVs, cameras, and wireless smart switches. Hopefully also my Litetouch! Anyone have any suggestions for me? Probably in over my head at this point but I’m sure I’ll figure it out eventually.
Use my matterbridge plugin above. I’ve been using it for a few weeks and it works great. You’ll need a raspberry pi and need to make a special cable.
Ordering a pi now. I should have everything I need to make a cable. Then I just install Matterbridge on the pi and plug it in to the 2000? I have not yet used any matter devices specifically. I got heavily into the Apple HomeKit stuff for a while… I assume matter devices will show up in Apple home? Or is there a better place before I get more involved with home assistant?
You’ll need to edit the config file for the plugin to tell it the load ID’s and the names of the loads. It’s in the readme, and there’s a sample file. Make sure you don’t forget the commas after each line in the config file, syntax matters. I couldn’t figure out a way to do this in matterbridge UI. I’m sure there’s a way.
Once it’s set up, matterbridge will have a QR code in the UI that you scan with Apple Home on your phone when you click add device. Also, that’s in the readme.
I unhooked the unused pins in my serial cable. It probably doesn’t matter. But if you don’t tie together pins 7 and 8 in the CCU side, nothing is going to work. I just used 2 of these: Amazon.com: ANMBEST 10PCS DB9 Male Ethernet Adapter, 9 Pin Serial Port Male to RJ45 Ethernet LAN Extend Modular Converter, M/F : Electronics
Insert the leads for 7&8, cut the wires, strip and twist/solder them together. 7&8 don’t need to, and shouldn’t, connect to the raspberry pi side. They should only be tied together at the CCU.
Again, you want load ID’s, not keypad ID’s. Unless someone left behind a spreadsheet of what is what, you’re gonna spend an hour or two figuring out what each load is used for.
Mine is running on an old Pi 3b. So you don’t need a new faster one for it. Except you will need a usb-serial dongle also. I’ve seen people take those RS-232->rj-45 plugs linked above and then plug one into an ethernet port and wonder why it doesn’t work. 
I was left a whole treasure trove of stuff. Blank buttons and new wall plates, old floppy disks with software, several books and binders full of information, electrical schematics, and an old dot matrix printout of all 297 switches and their corresponding addresses and module assignments. There is also a blueprint of the house with each switch number labeled in their correct locations.
I dream of one day having a web interface that will let me reassign modules and switch types remotely. And of course automation… Lots to learn!
Can you get those manuals scanned to pdf and send them to me or post them? And, get copies of the software on those disks? This would be AWESOME to have this. I have some stuff that I was able to download, and one piece of software that allows me to upload/download the config from the CCU, but that’s it.
Getting the documentation and software to properly manage these has proven extremely difficult.
Hi everyone, big update on this. I’ve created a new repository for the replacement custom component.
I’ll be fully transparent, this was vibe/AI coded. However, it’s been working pretty well (after some minimal debugging). It is built with async in mind which is the preferred method of Home Assistant.
https://github.com/patmann03/async_litetouch
For installation. You’ll need to remove the original custom_component with this new one. Place the litetouch folder in the custom_component folder.
You’ll need to redo your YAML as this integration no longer uses loadid / switches to turn loads on or off. It uses the module output function. This grants 2 new features that didn’t work in the original.
- Set Transition (you can have the light turn on over a couple of seconds (or minutes).
- Ability to keep track of the dimmer level.
See the github with a sample yaml. This places the integration under the light: component. I may pull this out later and have it separate.
You’ll minimally need the module number “0001” and the output 0-7. The litetouch modules 1-8 are 0 based so subtract one value.
In addition, I’ve exposed a couple of other commands as services to grant additional flexibility.
- Set Clock - the controller has a tendency to drift so this works well with an automation once a day.
- Set Load On/Off - This allows you to call the loadid (similar to the original implementation). That way you can use a master switch to turn off / on all lights.
- Set Load Level - Same as above, but you can pass a value 0…100 to set the level of the load.
These are nice for automation’s. With these I created a template light to manage a mass shut off / on button. I check to see if any light is on within a label group (couldn’t make floor work). Then I send a command to the load group to turn it on or off.
I also created light groups to mimic the load groups in litetouch. However, it seems the controller can’t handle much more than 5-7 commands within a second. So if you need more than that I’d create a template light and use one of the services to call the loadid.
If you’re happy with the current integration, no need to switch. This one gives some flexibility with additional functionality. It allows you to control each individual relay.
1 Like
added remaining services from the controller.
System can be setup using the yaml file or config_flow. Once loaded with yaml, the yaml file can even be removed and managing the entities right in the integration is pretty straight forward. Reloads happen automatically once an update to the entities is done. This is feeling fairly feature complete at this point.
I have a full set of docs for the 2000, i can easily scan them.
Sorry for disappearing. Life gets fun sometimes….
Here’s is a somewhat unorganized folder with some scans I made.
For those looking for LiteTouch LiteWare program files and docs, I’ve uploaded all versions I have to Archive.org so they’ll be permanently preserved and online. See here.
If you have different versions or additional docs please upload them to Archive.org. It’s easy and free. Links on Google Docs and other file sharing sites eventually stop working but Archive.org is non-profit and forever so ideal for abandware like this.
Thanks for scanning your docs! However, it appears you didn’t set the PDF files to be downloadable by others, so they can only be read online. Please change that option. Ideally, you should also upload them to Archive.org so they’ll be permanently preserved and accessible forever. I’ve uploaded all my LiteTouch docs and software versions there (but I have an LC5000). See here.
Links on Google Docs eventually go bad but Archive.org is open, non-profit and forever so ideal for abandware like this.
Hello everyone. Has anyone had an issue with dropping entities. I have 5000LC using Pats previous component. It was working fine until spring where 75% of my light entities were no longer working. I then tried the new integration but that didnt change anything. I am assuming there is some kind of communication lost between the CCU and HA.
I can ping the CCU fine but cannot tell if there is actual data transfer. I appreciate any help or ideas.