Were your smokes previously connected to your alarm system? I was able to get my dumb interconnected smokes to talk to Konnected by installing a relay module on one of the smokes and running 2 wires from the relay to the Konnected pins.
1 Like
Sorry about the late reply been on travel.
FYI, you’ll need to update the firmware link on the main page.
There two independent smoke alarm systems in my house: a hardwired set of USI Electric smokes and a hardwired set of System Sensor smokes. The USI smokes are interconnected and don’t connect to anything else other than mains. The SS smokes are two-wire and connect to and are powered by the ADT panel.
The USI set was installed by the builder per local code and are located in all the “right” places - each bedroom, hallway outside each bedroom, etc. The SS set was installed by ADT after construction to the security system pre-wiring done by the builder. My SS models (2WT-B) are on the list of those that don’t work with Konnected, but disabling those is fine with me because they aren’t in ideal positions (only one in a central location on each floor) and better coverage is provided by the USI set. With Leeo monitoring the USI set, I actually have better coverage for remote monitoring.
Thanks for sharing that relay module link. I hadn’t seen that before. If for some reason the Leeo doesn’t work out, with a it of snaking I could use that relay to tap into the USI set and send the alarm signal to Konnected. Good to know!
Hi @heythisisnate ,
I think the second update of my boards v 2.02 to 2.05 are failing. Firmware is newest, and first update to 2.05 went swimmingly. The second update results in this debug from serial:
NodeMCU 1.5.4.1
Konnected Security 2.0.5
build 20170825 powered by Lua 5.1.4 on SDK 1.5.4.1(39cb9a32)
Heap: 42672 Initializing device
Heap: 38248 Loaded: Startup (compiler & blinker)
Heap: 38136 Connecting to Wifi..
> Heap: 41024 Wifi connected with IP: 192.168.7.124 255.255.255.0 192.168.7.1
Heap: 38368 Updater: running..
I’m thinking a stuck updater?
I solved my problem with a manual update, which with your awesome instructions is very easy. Not sure why the second update failed, but since I rescued easily I’m happy for now. Let me know if I can help with any debugging, but I’ll probably move past this with all three boards here shortly. 
Ok, this setup is awesome, I waited for it for years.
Next challenge: I have a panic button programmed, but it appears to operate backwards. What is the most forward compatible way to change this so that it’s opposite? I don’t want to edit code on device or in SmartThings that would be overridden by an update. I’d prefer a setting that persists for my setup.
Hi All,
Great topic and very excited about this. Is there a similar solution for wireless sensors?
I have a setup with wireless sensors (319.5 MHz) connected to a GE Interlogix system. The system is not connected to any monitoring service, and would like to migrate over to ST.
Is there any instructions/guide/pointers to where to get started for wireless sensors?
Many Thanks!
Hey @ashwinbr as far as I know, there’s no easy way to connect those old alarm system wireless sensors to SmartThings. I think your best bet is replacing them with SmartThings compatible z-wave or zigbee sensors.
Hi Nate,
Thanks so much for your reply. Yes, it seems simple enough to use the Z-Wave sensors, but I am trying to think how best I can use the existing system. Oh well, if that’s the only way out, then I’ll probably replace it with the compatible sensors.
Thank you!
-Ashwin.
@heythisisnate - Just a FYI I had another failed update and had to format my board and reload the 2.1.0 code. I’m not sure if this was a side effect from being on the switch branch or not. I followed the instructions at https://docs.konnected.io/security-alarm-system/misc/updating-2-1-0 and I forced the update since I was already on 2.0.5 firmware…one board seemed to take it fine and the other didn’t. After connecting ESPlorer I found it was in a reboot loop trying to update and I saw it was trying to do so from the switch branch. So since I knew the procedure I just did a format and then uploaded the firmware again (just in case) then the files from the repo and everything seems fine.
Anybody been paying attention to your total uptime on average? I used to get several hours before a disconnect and reset (not sure which version I was on), but now I can’t seem to get more than an hour before it resets. I’m noticing this more and more because I have automation configured with these sensors and the automation is delayed in firing because the NodeMCU is resetting. I watched what happened in ESPlorer and it’s reporting “disconnected with error -11”.
Ah, the dreaded disconnected with error -11 error. I’ve heard of this one from a few people. This particular issue seems to be network related. Some people who experience it get it all the time, but most people will never see this error. Some have had success by replacing their router or upgrading their router firmware.
I’ve tried to look into it, but the error is coming from the NodeMCU firmware itself, not the Konnected code. I also am unable to reproduce it myself. I’m hoping that when I can update Konnected to use NodeMCU 2.0 firmware, this problem will just go away. For now, it seems to be affecting only a small percentage of people using Konnected.
1 Like
Thanks, Nate! Updating the router firmware seems to have fixed it. 9 hours and counting.
1 Like
@sblock23 What kind of router did you have and do you know the firmware version that fixed it? I’d like to put this information on my documentation site so others can benefit from it.
Netgear Nighthawk R7000. I updated the firmware to V1.0.9.6_1.2.19.
1 Like
I see you guys are working on implementing the door chime. The current way of getting a door chime seems to have a lag. My question is if i get one of your current kits, is the door chime feature something that would be updated through software, or would i need to get a newer version of the board? If the answer is a newer version, i may hold off until you get it figured out.
thanks for your time!
Mo
Hey @Scottymo15,
The door chime feature was just announced this week. It’s ready now. See:
https://docs.konnected.io/security-alarm-system/wiring/door-chime
Yes, any improvements will be available as a software update. Does that answer you questions?
I’m not sure if you’ve already found a solution but I use this and it works seamlessly. Easy enough for use by my MIL. I got it on sale for $20 a few months ago:
https://www.lowes.com/pd/Iris-White-Security-Alarm-Keypad-Works-with-Iris/999925326
@heythisisnate What’s an easy way to determine what version I have? Thanks!