TLinkWebPortal is now NeoHub! #1
Replies: 6 comments 7 replies
|
HI! I just had a DSC PowerSeries NEO HS2032PCBCP01 installed. It is being monitored via a wireless transmitter to my alarm company. Will this interfere with my monitoring service? Also, any suggestions on where to buy the part needed for this integration? I am no tech genius, but I can read and follow directions. Do you think this is something I could handle? Thanks! |
|
I'm far from a DSC expert, but I expect that if you have a TL280LE communicator module which is a secondary board installed with the alarm board that allows cellular connectivity to the monitoring company as well as providing an ethernet port on the board.. If that is true, then you already have all the hardware you need. The alarm setup is kinda tricky, and could be further complicated by you having an existing service as they can potentially put installer codes that you may not know which would prevent us from being able to configure the system as we need. I would call NeoHub pre-alpha release at this time and isn't ready for the general public. What I need right now are technical people who understand their hardware and how to set it up to help with testing. Brian |
|
I just ordered a TL280E so I could join in the fun. Is the setup obvious? Is there a write up somewhere describing how to install the comms board and add it to a home network? Thanks! Mike |
|
At the moment I wouldn't call any of this obvious. It will almost certainly involve some pain and frustration. I'll leave the physical install of the board to DSC and any instructions they may provide. Once you have that operational, you can take a run at the setup and see how you do. Do you have a plan for hosting NeoHub? Brian |
|
Hmm... OK. I'll see what I can figure out on my own. Regarding hosting NeoHub, I have an old NUC that I'm taking out of service. Also, I have a Synology NAS. I suppose either could host the docker container. |
|
Great development! I'm testing both the NeoHub server and the Home Assistant integration. So far, I can confirm that the status report for my DSC zones is working perfectly. The only thing I can't do yet is arm and disarm; I suppose this isn't fully implemented. I'm also getting a "yellow light on my keypad" warning indicating communication problems, which is strange because the NeoHub server is running without issues. I assume it's something on the DSC control panel side that needs to receive data from the server to confirm a stable connection. |
|
You are correct that Arm/Disarm isn't implemented yet. Getting that working as well as the controller config are my next priority. The yellow light is interesting. I think I have seen something similar on my setup, but I don't remember why. I think I did a reboot to solve it, but I don't remember why. Brian |
|
After several tests, I found the problem with the "yellow LED." I had enabled the option [851][100] - 1 - Ethernet Receive 1 enable. I thought it was necessary, but it wasn't. Even when disabled, it still communicates perfectly with the NeoHub server. I believe it's because the communication is done through [851][425] - Integration Over Ethernet. Another thing I noticed is that the Docker container sometimes hangs and starts consuming excessive resources, and I have to restart it. I understand that these are things to refine in the future. |
|
Glad you figured out the warning light. As for the container hanging, that's a little concerning. I haven't seen anything like that on my side. I have run the server on my local machine and the GC pressure seemed stable, moreover I took care to manage resources so I'm a little concerned with what you're seeing. What makes you think it's hanging? Does the UI become unresponsive or something? I have seen the UI require a page refresh to reconnect but this is a Blazor thing. Brian |
|
I think the problem started when I changed the logging level to debug, because every time I went into the web app and accessed the Diagnostics option, the container would freeze and start consuming resources. I had to delete the entire container and the persistent volume to recreate the server without that setting, and now it seems to be working fine. |
|
You can also reduce the number of log lines it will store. I set the default to 5000 but maybe that is a bit much? |
|
Finally got a chance to test this. Thanks for getting this working @BrianHumlicek! I've successfully connected NeoHub (running on TrueNAS) to my alarm system and set up the Home Assistant integration, and I'm seeing zones appear as they get triggered. Trying to sort out whether some things that I'm seeing aren't implemented or are expected to work:
Anyways, this is already incredible progress and I'm so happy and excited to see this finally work! |
|
Getting a full zone update on connection is on the horizon. What it does now was good enough for proof of concept. The zone list naming I honestly haven't looked too hard at but what you're describing is what I see here too. I do plan on making NeoHub an add on. I originally thought I would try to build everything into a HA integration, but it seems like a lot to figure out in Python when .NET is my wheelhouse. This definitely works, and integrations like zwave-is seem to work well enough with the design. Long term, who knows. For now, use it and let me know how it goes. I'll keep the updates coming. Brian |
Uh oh!
There was an error while loading. Please reload this page.
For the people that have been following the project DSC.TLink or TLinkWebPortal, this is the new home where all further development will continue. I have chosen to rebrand as NeoHub because it is a simpler name that still conveys its purpose. I forsee this project being long lived, and therefore want to build a foundation that will last a while starting with the name.
All reactions