When following the build docs I get a build failure of the following:

CC app/user/user_main.c
user_main.c:81:42: error: 'NODEMCU_EAGLEROM_PARTITION' undeclared here (not in a function)
     { NODEMCU_PARTITION_EAGLEROM,         0x00000,     0x0B000},
                                          ^
user_main.c:85:42: error: 'NODEMCU_IROM0TEXT_PARTITION' undeclared here (not in a function)
     { NODEMCU_PARTITION_IROM0TEXT,        0x10000,      0x0000},
                                          ^
user_main.c:86:42: error: 'NODEMCU_LFS0_PARTITION' undeclared here (not in a function)
     { NODEMCU_PARTITION_LFS,              0x0,          LUA_FLASH_STORE},
                                          ^
user_main.c:87:42: error: 'NODEMCU_SPIFFS0_PARTITION' undeclared here (not in a function)
     { NODEMCU_PARTITION_SPIFFS,           0x0,          SPIFFS_MAX_FILESYSTEM_SIZE},
                                          ^
user_main.c: In function 'nodemcu_init':
user_main.c:302:5: error: implicit declaration of function 'dbg_printf' [-Werror=implicit-function-declaration]
     NODE_ERR("\n");
     ^
cc1: all warnings being treated as errors
../../Makefile:422: recipe for target '.output/eagle/debug/obj/user_main.o' failed

This seems to be caused by the recent 3.0 "release" of nodemcu. Checking out the latest 2.x release in the nodemcu dir using git checkout 2.2.1-master_20190405 fixes this.

After updating to the latest version of HA v0.81.2, the following error is reported

Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/homeassistant/setup.py", line 145, in _async_setup_component
    hass, processed_config)
  File "/usr/local/lib/python3.6/site-packages/homeassistant/components/konnected.py", line 159, in async_setup
    ConfiguredDevice(hass, device).save_data()
  File "/usr/local/lib/python3.6/site-packages/homeassistant/components/konnected.py", line 241, in save_data
    DOMAIN, {'device_id': self.device_id})
TypeError: load_platform() missing 1 required positional argument: 'hass_config'

Any ideas on how to fix this?

Hi -
I set up two ESPs running Konnected and have been getting random reboots on both of them. I first noticed as the power to one of my relays kept getting turned off and my relay switches were out of sync with Home Assistant. I confirmed this by loading up the Konnected Device status webpage on both of them and noted that with a refresh the uptime would decrease with a refresh every once and a while. I pulled down one of the controllers to hook it up to serial and I caught one of the reboots. This is the error reported. I have no sensors hooked up. Googling suggest this is a missing HTTP module in the firmware but I see it listed as included in "firmware/2.2.0/app/include/user_modules.h"
Thoughts?

Heap: 	32936	Responded to UPnP Discovery request from 192.168.20.5:56672
Heap: 	32952	Responded to UPnP Discovery request from 192.168.20.26:43810
PANIC: unprotected error in call to Lua API (?:0: attempt to concatenate a nil value)

 ets Jan  8 2013,rst cause:2, boot mode:(3,6)

load 0x40100000, len 26212, room 16 
tail 4
chksum 0xfc
load 0x3ffe8000, len 2340, room 4 
tail 0
chksum 0xeb
load 0x3ffe8924, len 136, room 8 
tail 0
chksum 0x2b
csum 0x2b

Konnected firmware 2.2
NodeMCU 2.2.0.0 build 20180405 powered by Lua 5.1.4 on SDK 2.2.1(cfd48f3)
Heap: 	39856	Initializing Konnected
Heap: 	35312	Version: 	2.2.0
Heap: 	33688	Connecting to Wifi..
> Heap: 	37536	Wifi connected with IP: 	192.168.20.199	255.255.255.0	192.168.20.1
Heap: 	37504	UPnP: 	Listening for UPnP discovery
Heap: 	37296	HTTP: 	Starting server at http://192.168.20.199:9664
Heap: 	37128	Loaded: 	server
Heap:	32160	Initializing actuator pin:	1	Trigger:	0
Heap:	32128	Initializing actuator pin:	2	Trigger:	0
Heap:	32128	Initializing actuator pin:	5	Trigger:	0
Heap:	32128	Initializing actuator pin:	6	Trigger:	0
Heap: 	31880	Loaded: 	application
Heap: 	32936	Responded to UPnP Discovery request from 192.168.20.5:56672
Heap: 	26992	HTTP: 	Discovery

Heap: 30480 HTTP Call: 204 state 0 pin 7
HTTP client: Disconnected with error: -8
HTTP client: Connection timeout
Heap: 32240 HTTP Call: -1 state 1 pin 7
ets Jan 8 2013,rst cause:2, boot mode:(3,6)

I have 3 board, one connected to 5 motion sensors and a siren, other one connected to garage door opener,temp sensor & siren and a third test board connected only to 1 motion sensor. Board with motion sensors reboots very often, maybe every few hours and above is the log. 2nd board with 1 motion sensor reboots too but not that often,maybe because it only has 1 motion sensor. 3rd board garage door one, is rock solid. Please let me know if and how I can do more troubleshooting or provide more logs. It's a bit hard to capture on esplorer,had to leave a laptop connected.
Thanks

I can get an intermittent beep with 3.3v piezo buzzer using the following in Home Assistant:

    switches: 
       - pin: 8
          name: 'Warning buzzer'
          momentary: 500
          pause: 500
          repeat: 15

However, if I want a continuous beep which stays on until switched off, the following code from the documentation does not work as expected:

      switches: 
        - pin: 8
          name: 'Warning buzzer'
          momentary: 500
          pause: 500
          repeat: -1

The '-1' switch results in the piezo sounding once and then switcihing off in HA - my understanding from the documentation is that it should continue to sound until switched off?

I am using HA 0.85.0, with Konnected firmware 2.0.5, software 2.1.3.

Hey there, I'm running Konnected v2.2.7 and Home Assistant 0.93.2 and everything works except for the Siren. I can turn it on, but turning it back off doesn't due to a connection refused error. This is intermittent but happens frequently. Attached is the full log of the error.

Log Details (ERROR)
Tue Jul 02 2019 19:16:21 GMT-0400 (Eastern Daylight Time)
HTTPConnectionPool(host='10.10.10.171', port=13017): Max retries exceeded with url: /device (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f64ad8062b0>: Failed to establish a new connection: [Errno 111] Connection refused',))
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.6/site-packages/urllib3/connection.py", line 141, in _new_conn
    (self.host, self.port), self.timeout, **extra_kw)
  File "/srv/homeassistant/lib/python3.6/site-packages/urllib3/util/connection.py", line 83, in create_connection
    raise err
  File "/srv/homeassistant/lib/python3.6/site-packages/urllib3/util/connection.py", line 73, in create_connection
    sock.connect(sa)
ConnectionRefusedError: [Errno 111] Connection refused

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.6/site-packages/urllib3/connectionpool.py", line 601, in urlopen
    chunked=chunked)
  File "/srv/homeassistant/lib/python3.6/site-packages/urllib3/connectionpool.py", line 357, in _make_request
    conn.request(method, url, **httplib_request_kw)
  File "/usr/local/lib/python3.6/http/client.py", line 1239, in request
    self._send_request(method, url, body, headers, encode_chunked)
  File "/usr/local/lib/python3.6/http/client.py", line 1285, in _send_request
    self.endheaders(body, encode_chunked=encode_chunked)
  File "/usr/local/lib/python3.6/http/client.py", line 1234, in endheaders
    self._send_output(message_body, encode_chunked=encode_chunked)
  File "/usr/local/lib/python3.6/http/client.py", line 1026, in _send_output
    self.send(msg)
  File "/usr/local/lib/python3.6/http/client.py", line 964, in send
    self.connect()
  File "/srv/homeassistant/lib/python3.6/site-packages/urllib3/connection.py", line 166, in connect
    conn = self._new_conn()
  File "/srv/homeassistant/lib/python3.6/site-packages/urllib3/connection.py", line 150, in _new_conn
    self, "Failed to establish a new connection: %s" % e)
urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPConnection object at 0x7f64ad8062b0>: Failed to establish a new connection: [Errno 111] Connection refused

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.6/site-packages/requests/adapters.py", line 449, in send
    timeout=timeout
  File "/srv/homeassistant/lib/python3.6/site-packages/urllib3/connectionpool.py", line 639, in urlopen
    _stacktrace=sys.exc_info()[2])
  File "/srv/homeassistant/lib/python3.6/site-packages/urllib3/util/retry.py", line 388, in increment
    raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPConnectionPool(host='10.10.10.171', port=13017): Max retries exceeded with url: /device (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f64ad8062b0>: Failed to establish a new connection: [Errno 111] Connection refused',))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.6/site-packages/konnected/__init__.py", line 57, in put_device
    r = requests.put(url, json=payload, timeout=10)
  File "/srv/homeassistant/lib/python3.6/site-packages/requests/api.py", line 131, in put
    return request('put', url, data=data, **kwargs)
  File "/srv/homeassistant/lib/python3.6/site-packages/requests/api.py", line 60, in request
    return session.request(method=method, url=url, **kwargs)
  File "/srv/homeassistant/lib/python3.6/site-packages/requests/sessions.py", line 533, in request
    resp = self.send(prep, **send_kwargs)
  File "/srv/homeassistant/lib/python3.6/site-packages/requests/sessions.py", line 646, in send
    r = adapter.send(request, **kwargs)
  File "/srv/homeassistant/lib/python3.6/site-packages/requests/adapters.py", line 516, in send
    raise ConnectionError(e, request=request)
requests.exceptions.ConnectionError: HTTPConnectionPool(host='10.10.10.171', port=13017): Max retries exceeded with url: /device (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f64ad8062b0>: Failed to establish a new connection: [Errno 111] Connection refused',))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/websocket_api/commands.py", line 121, in handle_call_service
    connection.context(msg))
  File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/core.py", line 1141, in async_call
    self._execute_service(handler, service_call))
  File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/core.py", line 1163, in _execute_service
    await handler.func(service_call)
  File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/helpers/entity_component.py", line 194, in handle_service
    required_features
  File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/helpers/service.py", line 316, in entity_service_call
    future.result()  # pop exception if have
  File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/helpers/service.py", line 337, in _handle_service_platform_call
    await getattr(entity, func)(**data)
  File "/usr/local/lib/python3.6/concurrent/futures/thread.py", line 56, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/konnected/switch.py", line 89, in turn_off
    self._pin_num, int(self._activation == STATE_LOW))
  File "/srv/homeassistant/lib/python3.6/site-packages/konnected/__init__.py", line 60, in put_device
    raise Client.ClientError(err)
konnected.Client.ClientError: HTTPConnectionPool(host='10.10.10.171', port=13017): Max retries exceeded with url: /device (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f64ad8062b0>: Failed to establish a new connection: [Errno 111] Connection refused',))

I am up to the step where I would ordinarily mount my ESP8266 and start wiring. However, the connection between the Konnected smartapp and the esp8266 is having issues.

When I look at the smartapps on my phone, there is no app for Konnected. When I try to add it manually via an option to "Add a Konnected device". When I tap on this, I see, via esplorer console, "HTTP: Discovery" and then "Responded to uPnP Discovery request" -- but the smartthing app on the iphone just spins -- eventually have to force close the app.

I can view info on esp8266 web interface, connection via wifi is 100%.

Web interface also shows:
Software -> 2.1.0
Firmware -> 2.0.5
IP Address and gateway are consistent with my network.

I see the item in the troubleshooting FAQ — but is not clear to me what needs to be changed for my hub/location. My URL is graph.api.smartthings.com for the web interface — but I do not understand the URL I should be looking for.

any suggestions or areas to look at ?

Thank you.

My main alarm. board reboots randomly and I've been trying to figure out why. I set up another test board with a motion sensor. I've narrowed it down to motion sensor updates as my other board connected to garage door never reboots. I can now pretty much replicate the issue by requesting a HTTP Status from the app and if the motion sensor is also updating at that time, board reboots. see below. My main alarm board reboots randomly at times when I've not requested a status update like early this morning. Firmware and file system is latest 2.2.5
I am sure it will be easy to replicate and hopefully there will be a fix. Happy to provide more information.
E:M 80
PANIC: unprotected error in call to Lua API (error loading module 'httpd_res' from file 'httpd_res.lc':
not enough memory)

Again I tried and it rebooted, log below so I can pretty much replicate it.
Heap: 30960 Responding to UPnP Discovery request from 192.168.1.19:34962
Heap: 25832 HTTP: Index
Heap: 25336 HTTP: Status
Heap: 25424 HTTP: Index
Heap: 25080 HTTP: Status
E:M 80
PANIC: unprotected error in call to Lua API (error loading module 'httpd_res' from file 'httpd_res.lc':
not enough memory)

With the recent home assistant .106 update I get a notification for discovering a new device which point to the konnected integration (this is already set up in my yaml and working. when clicking on the check it out link, it takes me to the below interface of which it asks for a konnected port........... how do I find out the konnected port?

"Please enter the host information for your Konnected Panel."
Konnected Device IP Address = No problem here
Konnected Device Port = How do I find this out? It is not documented on either the Konnected Website nor the "https://www.home-assistant.io/integrations/konnected/"

Thanks in advance

Ability to log into the the device remotely via lightweight web interface to test triggers, switches and upgrade the firmware OTA.

2.3.1 Release files reference 2.3.0 konnected-firmware-2-3-0.bin

https://github.com/konnected-io/konnected-security/releases

Not sure if this is a naming issue or the wrong file?

Hi.
Thank you for the device. Received recently and replaced Integra64 .
I see that devices are sending information to Hubitat every time there is a change in sensors.
Is there a plan to add MQTT support?
Would be cool to use this protocol. It would be easier to add monitoring later

When SSDP is being troublesome it would be great if the Hubitat connector had the ability to enter the IP and port manually.

For some reason, I have a couple of contacts that bounce and sometimes even stick open. I keep chasing a loose connection on the board but no luck solving it from that end.

I had attempted a webcore hack to debounce the switch before I realized the lag on events was too long to wait... So I think it needs to be in the lua.

I'll go down a rabbit hole on how to edit this script and compile it and so forth... Or maybe I can file copy it into my hardware, IDK... I'll probably just put in a simple delay between where this loop detects a state change and where it commits the changed value to the variable. I hope I can do this with a second or so delay.

If I get really bored I guess I'll figure out how to let the user specify the debounce time in ms somewhere but I'd have to google a lot to get that done.

Thanks for a great app!

Henry

Board rebooting constantly. Panic unprotected error in call to Lua API (/opt/lua/application:lua:45: bad argument #1 to ‘alarm’ (Range: 1-6870947))
I have 1 temp sensor and a 2 channel relay connected controlling garage door and a siren.today I updated to 2.30 but I believe board has been rebooting for sometime. It was running an older firmware and has been stable so far or till whenever it started rebooting. I have flashed few times to try and understand when this error starts and it starts as soon as I change the polling interval to 120 minutes.
Looks like maximum you can put is 6870947 ms which is 114 mins?? Is that correct? Is this why I’m having issues??

Wondering when this was getting home assistant support as Samsung smart things is unavailable in my country

What level of security is implemented in the communication between the smartthings hub and the device?

I don't see anything mentioned about a security implementation but I figure there must be some decent encryption/security for a security device

I recently upgraded my konnected security firmware on NodeMCU and since then it's not updating the state of the connected sensors.

My config file looks like below.

#Konnected Security System konnected: access_token: !secret konnected_access_token devices: - id: !secret konnected_motion_detectors binary_sensors: - pin: 1 type: motion name: Kitchen Motion Detection - pin: 2 type: motion name: Hallway Motion Detection - id: !secret konnected_door_window binary_sensors: - pin: 1 type: door name: Front Door - pin: 2 type: door name: Back Door - pin: 5 type: door name: Deck Door - pin: 6 type: window name: Dining Room Window - pin: 7 type: window name: Family Room Window - pin: 9 type: window name: Kitchen Window

I checked sensors with a multimeter continuity test. They seem to be working fine.

Homeassitant Configuration

HassOS 2.12
HA Version - 0.96.5
DuckDNS with NGINX Home Assistant SSL proxy as recommended on this page - https://help.konnected.io/support/solutions/articles/32000023964-set-up-hass-io-with-secure-remote-access-using-duckdns-and-nginx-proxy

Let me know if any more information is needed. I will be happy to debug or provide logs.

AFAICT, the only method supported for connecting to homeassistant is via upnp and homeassistant's discovery system. This restricts supported networking configurations between konnected and homeassistant to those where they both reside on the same layer 2 network and can share multicast data. One example of where this does not work is a configuration where konnected and homeassistant are on separate networks (this is the case if homeassistant is running in docker).

It would be great to support a non-discovery based setup method. e.g. allowing a user to manually enter either the homeassistant api info as part of configuring konnected, or allowing a user to configure homeassistant to know the uri to reach konnected.

Hi Nate,
I recently added a NodeMCU and 5V relay to my garage door along with an open/close sensor.
The setup worked very well.
The only problem that I am facing right now is whenever NodeMCU reboots, reconnects or we make changes to the pins in Konnected(connect) app the device restarts and connect again to the WiFi and it also toggles/activates the replay. This causes the garage door to open (when it should stay closed).
I was just wondering if there is fix that can be added the code which will recognize the last state of of actuator and not change it during reboot.

Hardware-
Node MCU - ESP8266 Development Board NodeMCU Lua V3 WIFI with CH340G USB and Base Shield
5V replay - 2 Channel Relay Module With Optocoupler 5V Active Low Level Amplifier Trigger

Connections-
VCC and GND of relay connected to NodeMCU 5v and GND
IN2 pin of relay connected to NodeMCU PIN8
"+" of garage door connected to NO2 of replay
"-" of garage door connected to COM2 of replay

Setting in APP-
Low Level Trigger - Enabled
Momentary Delay - 500 milliseconds

When home assistant api has a password, konnected cannot inform sensors status to home assistant

The Luna MCU won't connect to a Google Mesh WIFI.
I have been a user of the Konnected / Smarthings integration since 2.0 days… I recently upgraded to the google wifi mesh network with 3 Access points and the konnected node mcu stopped functioning. it seems to connect to the network and get an IP(I can ping it) but it will not readd to Smarthings. The search for device never finds the device.

I have tested the latest release and prior releases of firmware will not work with a google wifi mesh network. Is it possible that this functionality could be added to a future release? I will gladly participate in the development and testing effort.

Hello,
Great project Nate. Sharing my issue here to see if there is a solution among the masses. Non-technical, so I need help from others out there who understand this stuff. I have two devices behaving identically. I would think there is a solution of some sort...

My setup:
Modem: Xfinity rented. TG862G rev5, software: 9.1.103
Wifi: Luma Surround WiFi, with three hubs. latest firmware 2017.10.25-0
NodeMCU ESP8266 12, flashed with Konnected Security 2.0.5
build 20170825 powered by Lua 5.1.4 on SDK 1.5.4.1(39cb9a32)

The behavior:
The setup is fine from plug in to setting up pins. Using an open/close sensor on any pin D1, D2, D5, D6, D7, when the first change in state is detected (0 or 1), the device errors and resets 5-7 times. getting stuck at 'application'. Eventually it stabilizes. But, the moment another change is detected, it cycles again. I've flashed it and reinstalled, same behavior.

The problem:
its getting stuck in the application step. I believe the error is happening at
line 14: timeout:register(10000, tmr.ALARM_SEMI, node.restart)
I think it is stalling out after 10 seconds and forcing the restart, then if I had to guess, it takes the http a portion of time to jettison whatever caused it to time out, then once its gone, it settles down again...

Please help. This project is awesome and I would really like to get it working.

<begin copy/paste>

Heap: 31904 HTTP Call: 204 Pin: 1 State: 0
HTTP client: Disconnected with error: -11
HTTP client: Connection timeout

ets Jan 8 2013,rst cause:2, boot mode:(3,6)

load 0x40100000, len 24580, room 16
tail 4
chksum 0xa2
load 0x3ffe8000, len 2268, room 4
tail 8
chksum 0x7d
load 0x3ffe88dc, len 136, room 0
tail 8
chksum 0x89
csum 0x89
„ã�ì�Ã'ä’{Ãón<ä�$ dld`�„ã;›$Œd�Œþ

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: 41096 Initializing Konnected
Heap: 36664 Version: 2.1.0
Heap: 35016 Connecting to Wifi..
'> Heap: 39304 Wifi connected with IP: 192.168.55.225 255.255.255.0 192.168.55.1
Heap: 35656 UPnP: Listening for UPnP discovery
Heap: 35240 HTTP: Starting server at http://192.168.55.225:17068
Heap: 34896 Loaded: server
Heap: 32048 Initializing sensor pin: 1
Heap: 31792 Loaded: application
Heap: 31904 HTTP Call: 204 Pin: 1 State: 1

Hooking up to a serial port monitor I see the boot messages:

Konnected firmware 2.3.0 NodeMCU 2.2.0.0 build 20190805 powered by Lua 5.1.4 on SDK 2.2.1(6ab97e9) 
Heap: 41744 Initializing Konnected (dc4f2218ef45) 
Heap: 40680 Application Version: 2.3.0 
Heap: 39528 Connecting to Wifi.. > 
Heap: 42248 Wifi connected with IP: 172.16.x.x Gateway: 172.16.x.x
Heap: 40984 Time sync failed! 

There are no further messages and the device does not respond to the status endpoint.

As you can see the WIFI connection is set and the information is verified correct via nmap.

NOTE: MY SECURITY SYSTEM IS ON A PRIVATE NETWORK AND DOES NOT, BY_DESIGN, HAVE INTERNET ACCESS. I do have an NTP server on the network as well, but the device doesn't have that information configured. Time sync failure should not prohibit firmware boot, yes?

Providing Internet access is not an option.

X-Post from support forum.

Error doing job: Future exception was never retrieved

Traceback (most recent call last):
File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/local/lib/python3.7/site-packages/homeassistant/components/konnected/init.py", line 131, in device_discovered
setup_device(host, port)
File "/usr/local/lib/python3.7/site-packages/homeassistant/components/konnected/init.py", line 121, in setup_device
discovered.setup()
File "/usr/local/lib/python3.7/site-packages/homeassistant/components/konnected/init.py", line 284, in setup
self.sync_device_config()
File "/usr/local/lib/python3.7/site-packages/homeassistant/components/konnected/init.py", line 388, in sync_device_config
if self.desired_settings_payload() != self.current_settings_payload():
File "/usr/local/lib/python3.7/site-packages/homeassistant/components/konnected/init.py", line 368, in current_settings_payload
settings = self.status['settings']
KeyError: 'settings'

"Devices should wait a random interval less than 100 milliseconds before sending an initial set of advertisements in order to
reduce the likelihood of network storms; this random interval should also be applied on occasions where the device obtains a
new IP address or a new network interface is installed. "

http://www.upnp.org/specs/arch/UPnP-arch-DeviceArchitecture-v1.0-20080424.pdf

Hi,

I've recently started doing a lot more with ESPlib in home assistant and find it brilliant, adding new devices is a breeze and I love the way they show up in the integrations section of home assistant, as well as providing a whole host of functionality that just makes connecting, troubleshooting and seeing the status of your devices easier.

I wondered if there are any plans to adopt this approach with Konnected? Just as an example I built a doorbell with ESPlib with no prior knowledge of it or ESP devices in a couple of hours from scratch. Everything from the first flash of firmware using my home assistant machine, to easily deploying new code changes with the OTA feature were super easy and I had a nice UI to guide me through.

Once a new device was added, I immediately got a notification in home assistant of the discovery of that device, and could then see a range of information on my new door bell, from IP address to MAC address and pin states to WIFI signal strength.

It would be awesome if we could do something similar with Konnected :)

Cheers

Andy

I've purchased 5 AM2302 DHT22 Digital Temperature & Humidty Sensor Module (5V) and updated to Konnected.IO Firmware release 2.2.0. I've configured two DIY Konnected modules with a DHT22 sensor and both are providing live temperature and humidity feedback via the SmartThings app.

DHT22 - Device Calibration Offset Feature:
Given the fidelity limits of these relatively inexpensive sensors limits I've found that the two DHT22 report slightly different temp and humidity readings even though both are co-located. Would it be possible to add a calibration feature to the device handler allowing a user to offset the temp and humidity of each of the sensors. I've seen this feature in some of the SmartThings Multipurpose devices so I know it possible. I'm not a groovy coder but would be willing to attempt adding a feature to the handle if I could get some suggestions on where to start.

Missing DHT Pin Definition:
I used the Konnected (Connect) SmartApp to configured two devices on my module P5-Konnected-827777. Pin D1 as a Beep/Blink Switch and Pin D2 as a Temperature & Humidity sensor. However, when I review the P5 module device status the Configuration only shows the Pin D1 entry as an actuator and no entry for the DTH22 on Pin D2 in the Sensors (see attached files). I believe this maybe the reason I can't find this DHT22 sensor in my SmartThing list when using ActionTiles. Any thoughts of suggestions?

Screen Snapshot of Konnect Device Status:

-Greg

This worked seamlessly on my first attempt. The second ESP8266 NodeMCU module I tried has worked with other firmware. Every time I try to flash it with Konnected firmware it fails to reboot. The LED is flashing rapidly as if it is rebooting and not finding the bootloader. Is there a way around this? If I re-flash with the Arduino API it seems to work still, so the chip does not seem to have any permanent damage.

./scripts/flash
esptool.py v2.2-dev
Connecting....
Detecting chip type... ESP8266
Chip is ESP8266EX
Uploading stub...
Running stub...
Stub running...
Configuring flash size...
Auto-detected Flash size: 4MB
Flash params set to 0x0240
Compressed 479444 bytes to 311295...
Wrote 479444 bytes (311295 compressed) at 0x00000000 in 27.5 seconds (effective 139.6 kbit/s)...
Hash of data verified.

Leaving...
Hard resetting...
opening port /dev/tty.SLAB_USBtoUART with 115200 baud
Traceback (most recent call last):
File "//anaconda/bin/nodemcu-uploader", line 11, in
sys.exit(main_func())
File "//anaconda/lib/python2.7/site-packages/nodemcu_uploader/main.py", line 252, in main_func
uploader = Uploader(args.port, args.baud, start_baud=args.start_baud)
File "//anaconda/lib/python2.7/site-packages/nodemcu_uploader/uploader.py", line 78, in init
__sync()
File "//anaconda/lib/python2.7/site-packages/nodemcu_uploader/uploader.py", line 76, in __sync
raise DeviceNotFoundException('Device not found or wrong port')
nodemcu_uploader.exceptions.DeviceNotFoundException: Device not found or wrong port

Setup a new NodeMCU running Konnected. Install, WIFI setup and initial Home Assistant (0.81.5) upload/programming all worked fine, however, after restart home assistant for a non-konnected updated (just adding some known-devices) I now get the following every 20-30 seconds and then it resets (and continues to reset every 20-30 seconds):

Heap:   27968   UPnP:   Sent SSDP NOTIFY
PANIC: unprotected error in call to Lua API (/opt/nodemcu-firmware/local/fs/httpd_req.lua:26: bad argument #2 to 'sub' (number expected, got nil))

During the time between boot and reset I've tested a single door sensor is working, this is output from such a test:

Heap:   31432   Initialized actuator Pin:       5       Trigger:        1      Initial state:   0
Heap:   31744   HTTP Call:      200     state   1       pin     1
Heap:   31808   HTTP Call:      200     state   1       pin     2
Heap:   31912   HTTP Call:      200     state   1       pin     5
Heap:   32008   HTTP Call:      200     state   1       pin     6
Heap:   32080   HTTP Call:      200     state   0       pin     5
Heap:   27968   UPnP:   Sent SSDP NOTIFY
PANIC: unprotected error in call to Lua API (/opt/nodemcu-firmware/local/fs/httpd_req.lua:26: bad argument #2 to 'sub' (number expected, got nil))

What I've found is that subsequent home assistant restarts and uploads make it stable again (i.e. no resets) then further home assistant restarts (all just basic configuration updates to non-konnected devices) might cause it to go in to the PANIC loop again.

Happy to run diagnostics if anyone can give me the details as I can pretty readily recreate.

Would it be possible to add functionality for a luminance sensor such as the TSL2561 or TSL2591?

I've been looking for a way to mount a lux sensor outside to govern lighting rules based on luminosity rather than timers and I find using local weather stations lux reading to be wildly unpredictable.

Hello Nate,

I recently updated 3 nodeMCUs with latest 2.2.4 release.
the first nodemcu worked perfectly without any problems, i only have contact sensors setup on this.

second one has pin8 setup as siren and third has pin8 assigned as momentary switch. for both of these i am getting following error.

Konnected firmware 2.2.4
NodeMCU 2.2.0.0 build 20180917 powered by Lua 5.1.4 on SDK 2.2.1(6ab97e9)
Heap: 39688 Initializing Konnected (84f3eb0dc90b)
Heap: 33992 Version: 2.2.4
Heap: 32320 Connecting to Wifi..

Heap: 37136 Wifi connected with IP: 10.0.0.20 255.255.255.0 10.0.0.1
Heap: 35928 HTTP: Starting server at http://10.0.0.20:8903
Heap: 35920 Loaded: server
Heap: 28728 Initializing sensor pin: 5
Heap: 28696 Initializing sensor pin: 1
Heap: 28696 Initializing sensor pin: 6
Heap: 28696 Initializing sensor pin: 9
Heap: 28696 Initializing sensor pin: 7
Heap: 28696 Initializing sensor pin: 2
Heap: 28336 Endpoint: https://graph-na04-useast2.api.smartthings.com:443/api/smartapps/installations/****************************
Heap: 28304 Loaded: application
Heap: 32920 HTTP Call: 200 state userdata: 00000000 pin 8
PANIC: unprotected error in call to Lua API (/opt/nodemcu-firmware/local/fs/application.lua:122: bad argument #2 to 'write' (number expected, got userdata))

ets Jan 8 2013,rst cause:2, boot mode:(3,6)

load 0x40100000, len 25784, room 16
tail 8
chksum 0xd8
load 0x3ffe8000, len 2344, room 0
tail 8
chksum 0x03
load 0x3ffe8928, len 136, room 0
tail 8
chksum 0xca
csum 0xca
Œã�ä�ƒoì›;ƒûg|ì�l�ld$`��#“���Ÿ|�{Û�$œnà�ƒnâ

E:M 32
PANIC: unprotected error in call to Lua API (error loading module 'httpd_req' from file 'httpd_req.lc':
not enough memory)
Reboots every time Siren goes off or if I try to test by testing siren. Tested on two boards both running 2.2.6 Device discovery and blink both are off.
Above is what ESplorer shows when I test the siren.'
And also this when I tried again just now -
eap: 4856 HTTP: Device
Heap: 2488 Actuator Pin: 8 State: 1
E:M 536
E:M 1584
E:M 1584
HTTP client: Disconnected with error: 46
HTTP client: Connection timeout
Heap: 29496 HTTP Call: -1 state 1 pin 1
Heap: 29528 HTTP Call: 204 state 1 pin 1 retry 1

This doesn’t happen if I remove the motion sensor. Looks like it errors out if motion sensor is also updating status at the sa e time as Siren is trying to activate which might be an issue at the time of an actual intrusion as with my tests when the board reboots siren doesn’t go off.

I believe it has to do with device ID strategy.

As seen here, the app will update the corresponding device via dni

However during discovery, if the NodeMCU is connected to certain extenders, it will be assigned a random MAC address. Yet the application still reports on its hardware MAC.

Is there any way to change the ID strategy so that this isn't an issue?

Hello,
could you please post instruction how to build the firmware?
Thank you

I just found a low temperature sensor that was wired to my old security alarm. I don't see a device handler for this yet but I can try writing one and testing out this device.

Good morning,

Love that we can now set a toggled Siren for the beep blink handler, I was wondering if it would be possible to add more preseets?

I'd like to use one sounder to bleep out different patterns for different events, Ideally by configuring a handful of presets then calling the presets from webcore or similar.

I use Cast-Web-Api to control my Google home and its method of triggering presets is quite elegant

You have a great product and code Nate. As I am attempting to get my first NodeMCU online, the unit connects to Wifi, loads the server, initializes the six sensor pins, loads the application, and then disconnects with a HTTP client error. The printout is shown below. Any advice?

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: 41264 Initializing Konnected
Heap: 36776 Version: 2.1.0
Heap: 35024 Connecting to Wifi..

Heap: 39648 Wifi connected with IP: 192.168.0.22 255.255.255.0 192.168.0.1
Heap: 36120 UPnP: Listening for UPnP discovery
Heap: 35688 HTTP: Starting server at http://192.168.0.22:9827
Heap: 35344 Loaded: server
Heap: 31656 Initializing sensor pin: 5
Heap: 31608 Initializing sensor pin: 7
Heap: 31608 Initializing sensor pin: 2
Heap: 31608 Initializing sensor pin: 1
Heap: 31608 Initializing sensor pin: 9
Heap: 31608 Initializing sensor pin: 6
Heap: 31360 Loaded: application
HTTP client: Disconnected with error: -11
HTTP client: Connection timeout
HTTP client: Connection timeout

ets Jan 8 2013,rst cause:2, boot mode:(3,6)

load 0x40100000, len 24580, room 16
tail 4
chksum 0xa2
load 0x3ffe8000, len 2268, room 4
tail 8
chksum 0x7d
load 0x3ffe88dc, len 136, room 0
tail 8
chksum 0x89
csum 0x89
„â�ì2‚nì’sƒòN|ì�$ l$l`�Œãr’lŒ$�Œþ

Hello Nate! Thanks for putting this project together. I am hopping you can take a look at some errors I am getting when trying to upload the files in the src folder:

Konnected firmware 2.2.7
NodeMCU 2.2.0.0 build 20190424 powered by Lua 5.1.4 on SDK 2.2.1(6ab97e9)

Uploading to ESP file actuators.lua...Success
Uploading to ESP file dht_sensors.lua...Success
Uploading to ESP file ds18b20_sensors.lua...Success
Uploading to ESP file enduser_setup.html.gz...Success
Uploading to ESP file http_favicon.ico.gz...Success
Uploading to ESP file http_index.html.gz...Success
Uploading to ESP file init.lua...Success
Uploading to ESP file sensors.lua...Success
Uploading to ESP file settings.lua...Success

rl $
No LFS image loaded

Konnected firmware 2.2.7
NodeMCU 2.2.0.0 build 20190424 powered by Lua 5.1.4 on SDK 2.2.1(6ab97e9)
Heap: 40048 Initializing Konnected (807d3a3e0d52)
Heap: 37008 Compiling: ssdp.lua
Heap: 37008 Compiling: ssdp_notify.lua
Heap: 33200 Compiling: variables_build.lua
Heap: 33400 Compiling: start.lua
Heap: 33896 Compiling: dht_sensors.lua
Heap: 33504 Compiling: application.lua
Heap: 37008 Compiling: wifi.lua
Heap: 30832 Compiling: device.lua
Heap: 35152 Compiling: server_device.lua
Heap: 28832 Compiling: variables_set.lua
Heap: 34480 Compiling: server.lua
Heap: 37008 Compiling: httpd_req.lua
Heap: 32880 Compiling: httpd_res.lua
Heap: 30824 Compiling: wipe.lua
Heap: 33144 Compiling: server_status.lua
Heap: 33416 Compiling: sensors.lua
Heap: 33656 Compiling: led_flip.lua
Heap: 32704 Compiling: server_settings.lua
Heap: 32080 Compiling: server_receiver.lua
Heap: 32152 Compiling: ds18b20_sensors.lua
Heap: 36592 Compiling: actuators.lua
Heap: 36200 Compiling: settings.lua
Heap: 35896 Compiling: ssdp_response.lua
Heap: 36384 Application Version: 2.2.7
lua: cannot open wifi.lua
stack traceback:
[C]: in function 'dofile'
init.lua:16: in main chunk
[C]: ?

Then I noticed that you moved most or all the lua files to the lfs folder, so I uploaded those files instead, and got this error:

Uploading to ESP file application.lua...Success
Uploading to ESP file device.lua...Success
Uploading to ESP file httpd_req.lua...Success
Uploading to ESP file httpd_res.lua...Success
Uploading to ESP file init.lua...Success
Uploading to ESP file led_flip.lua...Success
Uploading to ESP file server.lua...Success
Uploading to ESP file server_device.lua...Success
Uploading to ESP file server_receiver.lua...Success
Uploading to ESP file server_settings.lua...Success
Uploading to ESP file server_status.lua...Success
Uploading to ESP file ssdp.lua...Success
Uploading to ESP file ssdp_notify.lua...Success
Uploading to ESP file ssdp_response.lua...Success
Uploading to ESP file start.lua...Success
Uploading to ESP file variables_build.lua...Success
Uploading to ESP file variables_set.lua...Success
Uploading to ESP file wifi.lua...Success
Uploading to ESP file wipe.lua...Success

s$
No LFS image loaded

Konnected firmware 2.2.7
NodeMCU 2.2.0.0 build 20190424 powered by Lua 5.1.4 on SDK 2.2.1(6ab97e9)

** Note ** I changed the file name from _init.lua to just init.lua.

The LFS image is not in the scr/lfs location as indicated in the "spiffs.lst" under scripts

Thanks in advance for your help!

I cannot open the zip for the .img file. I get the error, "it does not appear to be a valid archive." any ideas?

Hello, I am interested in using this on an ESP32 board for the added GPIO, performance, ethernet, etc.

Has anyone tried this? Do we know what it looks like to make this happen? I am a NodeJS programmer and could help as needed (though I know lua is a lot different)

I saw some distant chatter about it but just wanted to check on it for real.

Thanks for the awesome software!

(and yes, I accidentally posted this before typing a message and somehow GitHub let me send it 🤦‍♂️ )

I don't want to use smartthings or other home automation systems but need a REST api for my own app. is there a REST api?

So, I just updated my config to do some additional testing and now I'm stuck in a reboot loop as soon as my ESP gets the config information from Home Assistant. Each time it errors with HTTP Call: -1 state 1 pin 7
I'm running a docker of the latest dev branch of Home Assistant (0.70.0.dev0) which has konnected integration.
I had a jumper on D7 to ground during the update but it continues the loop even with nothing connected.
Log shows:

Konnected firmware 2.2
NodeMCU 2.2.0.0 build 20180405 powered by Lua 5.1.4 on SDK 2.2.1(cfd48f3)
Heap: 	39856	Initializing Konnected
Heap: 	35312	Version: 	2.2.0
Heap: 	33688	Connecting to Wifi..
> print(uart.setup(0, 15200, 8, 0, 1, 1 ))
115200
> 
Communication with MCU..Got answer! Communication with MCU established.
AutoDetect firmware...

Can't autodetect firmware, because proper answer not received (may be unknown firmware). 
Please, reset module or continue.
 IP: 	192.168.20.199	255.255.255.0	192.168.20.1
Heap: 	37824	UPnP: 	Listening for UPnP discovery
Heap: 	37608	HTTP: 	Starting server at http://192.168.20.199:9664
Heap: 	37432	Loaded: 	server
Heap:	32024	Initializing actuator pin:	1	Trigger:	0
Heap:	31992	Initializing actuator pin:	2	Trigger:	0
Heap:	31992	Initializing actuator pin:	5	Trigger:	0
Heap:	31992	Initializing actuator pin:	6	Trigger:	0
Heap: 	31736	Loaded: 	application
Heap: 	30080	HTTP: 	Status
Heap: 	28304	HTTP: 	Settings
Heap: 	25008	Wrote: 	smartthings.lua
Heap: 	24976	Wrote: 	sensors.lua
Heap: 	24704	Wrote: 	actuators.lua
Settings updated! Restarting in 5 seconds...

 ets Jan  8 2013,rst cause:2, boot mode:(3,6)

load 0x40100000, len 26212, room 16 
tail 4
chksum 0xfc
load 0x3ffe8000, len 2340, room 4 
tail 0
chksum 0xeb
load 0x3ffe8924, len 136, room 8 
tail 0
chksum 0x2b
csum 0x2b

Konnected firmware 2.2
NodeMCU 2.2.0.0 build 20180405 powered by Lua 5.1.4 on SDK 2.2.1(cfd48f3)
Heap: 	39856	Initializing Konnected
Heap: 	35312	Version: 	2.2.0
Heap: 	33688	Connecting to Wifi..
> Heap: 	37536	Wifi connected with IP: 	192.168.20.199	255.255.255.0	192.168.20.1
Heap: 	37504	UPnP: 	Listening for UPnP discovery
Heap: 	37288	HTTP: 	Starting server at http://192.168.20.199:9664
Heap: 	37112	Loaded: 	server
Heap:	32128	Initializing sensor pin:	7
Heap:	32096	Initializing actuator pin:	1	Trigger:	0
Heap:	32096	Initializing actuator pin:	2	Trigger:	0
Heap:	32096	Initializing actuator pin:	5	Trigger:	0
Heap:	32096	Initializing actuator pin:	6	Trigger:	0
Heap: 	31848	Loaded: 	application
Heap: 	32488	Responded to UPnP Discovery request from 192.168.20.18:38442
Heap: 	31968	Responded to UPnP Discovery request from 192.168.20.5:56672
Heap: 	25528	HTTP: 	Discovery
HTTP client: Connection timeout
Heap:	35248	HTTP Call:	-1	state	1	pin	7

 ets Jan  8 2013,rst cause:2, boot mode:(3,6)

load 0x40100000, len 26212, room 16 
tail 4
chksum 0xfc
load 0x3ffe8000, len 2340, room 4 
tail 0
chksum 0xeb
load 0x3ffe8924, len 136, room 8 
tail 0
chksum 0x2b
csum 0x2b

My config for this unit is:

  # Test Module
  - id: 1964f1
    binary_sensors:
      - pin: 7
        type: door
        name: 'Konnected Test Door'
    switches:
      - pin: 1
        name: 'Konnected Test Relay 1'
        activation: low
      - pin: 2
        name: 'Konnected Test Relay 2'
        activation: low
      - pin: 5
        name: 'Konnected Test Relay 3'
        activation: low
      - pin: 6
        name: 'Konnected Test Relay 4'
        activation: low

After upgrading to 2.3.3 both garage door & siren turn on if board reboots. It’s working fine otherwise. Only momentary switch for garage door and siren connected to board. D5 momentary switch for garage door & D6 is set for Siren. It was all fine before upgrade. Low level trigger is checked in app for both devices. Has something changed in the firmware or file system?

Can anything be done/tweaked to help reduce the latency from a motion sensor being triggered to turning on lights.

Using a Konnected Interface on a Honeywell Galaxy 2-20
SmartThings Routine to turn on Hue lights

The current delay is around 3-5 seconds before lights come on.

Not sure if this is an issue but just thought I'll put it here. Just flashed 2.2.5 and after flashing Esplorer still shows 2.2.4. Is that normal?
Konnected firmware 2.2.4
NodeMCU 2.2.0.0 build 20180917 powered by Lua 5.1.4 on SDK 2.2.1(6ab97e9)
Heap: 33568 Initializing Konnected (68c63ae19c2a)
Heap: 32376 Version: 2.2.5
Heap: 30728 Connecting to Wifi…
Heap: 30344 WiFi not configured
Heap: 30312 Entering Wifi setup mode
Heap: 23496 WiFi Setup started

I cannot open the zip for the .img file. I get the error, "it does not appear to be a valid archive." any ideas?