Still have not worked out how to disarm via the HA Alarm Panel.
[Edit: Yes I have now. I was NOT using Arm Away yet, and the HA panel option to Disarm only appears in that mode after arming has finished. As I 99% of the time prefer Arm Home, and it has a bug that drops out to Disarmed after Arming I never saw the Disarm button appear. ]
I have noticed now that I have time to absorb the details and see what HA records, that my system also does not show the ARMED state in the lovelace panel.
When Home Arming via the code pad on the NESS, HA shows āARMINGā but then drops back to āDISARMEDā like others have seen. When disarming via the NESS code pad, HA shows a āPENDINGā status, then āDISARMEDā.
Also now that itās been running for a few days, Iām happy to report that the IP connection to HA via the ESP8266 and the ESP-link firmware is very stable, I have not see anything indicating lack of connection so far. So apart from the status reporting itās a great success.
Hi Guys, Awesome work and special thanks to Nick for his awesome job.
I think Iām experiencing the same issue as mr.sneezy. Arming AWAY works perfectly, as soon as I press āArm Awayā the HA Keypad shows the āarmingā icon in yellow and then once āarmed awayā the icon on the HA Keypad turns red and indicates armed. The physical keypad supports this.
The problem Iām having is with āArm Homeā. When I press this on the HA keypad the icon in the top right goes from a green shield to a yellow āArmingā shield for about 1 second, then it returns to being a green shield while the actual alarm system continues to beep and then arm in Home mode. Even once armed in Home mode the status remains disarmed on the HA Keypad. So via HomeAssistant I canāt see that itās āArmed Homeā and I canāt disarm it because itās not showing armed. The local keypad is still working normally and will show the system as armed Home.
Hope this helps with the diagnosis.
btw my alarm is a Version 8.7 DX16.
[edit] Hereās the ascii data for both types of arming using terminal. The away sequence works works fine.
Mines been great also other than showing the system is Armed Away when its Armed Home and not always picking up the current state of the panel on Home Assistant reboot. Thanks @nickw444
@FrontBottom, @aumatt, Is your component still running? For some reason mine has failed today (i know it is today because i checked it earlier in the day and it was working. The only thing i have done is update to 0.107.6, but when i restored an earlier backup with a previous version, it is still not workingā¦ I get the error as follows
`
Looks like it might be a network connectivity issue. Is 10.0.1.25 the IP if your IP -> RS232 adapter? If so, are you able to get a response if you ping it from your machine on the same network? Likewise, can you get a response if you ping it from the machine that you are running home assistant on?
@Mikkaat Im still on 107.1 and its been working fine, ive had it in the past where after an update I had to physically reset the IP/RS232 convertor to get it communicating again.
@aumatt - thank you very much, you are a genius. I didnt think of this earlier as the control box is located in a place which is not that easy to get to, and the 232 is inside the box. I reset it using the elk-ip232 tool. @nickw444 thank you for responding, yes .25 is my 232 and i was able to ping it, just needed to be reset. Thank you for the great work and effort you have put into this component. It is awesome. In the almost 12 months i have been using it, it has only dropped this one time.
On a related note, did you ever work out the issue with Home mode?
Thanks again for all your help.
I have just flashed the NodeMCU with the JeeLabs standard binary from the original creator found on GitHub. https://github.com/jeelabs/esp-link/releases/tag/v2.2.3
There is a branch here than may be better now. I was hoping theyād implement an option for logic inversion so I could dispense with the RS232<->TTL module (logic voltages seem compatible out of the NESS panel). https://github.com/Stef-aap/RFLink-ESP
Edit:
This is my ESPlink web server accessed configuration in the web browser GUI. My Wifi and IP info has been masked outā¦
Hi All, Iām in the process of making my own serial cable for my D16x alarm and I was hoping someone could tell me which colours go where on the control board 3 pin serial connector.
Iāve pulled the colour pinout for the DB9 connector from some Ness documentation which is;
Black: PIN5
Blue: PIN2
White: PIN3
Having the same issue with Arming Home vs Arming Away, is there anyway you found to get this working again?
@nickw444 I just wanted to say thanks for the plugin, its super responsive for sensors!! and also if you need any testing done for the home / away stuff I can help out!
Hi, I am still really new to this HomeAssistant stuff however I think I may have found a solution to the issue of the āarmed awayā state reverting to the ādisarmedā state. You need to add the phrase: infer_arming_state: true to the ness_alarm heading in the configuration.yaml.
For example my configuration.yaml now appears as below:
ness_alarm:
host: 192.168.1.4
port: 23
infer_arming_state: true
zones:
- name: Garage
id: 1
- name: Storeroom
id: 2
- name: Kitchen
id: 3
- name: Front Entrance
id: 4
- name: Front Door
id: 5
type: door
Since making this change it has been working perfectly for me. The idea came from this document https://readthedocs.org/projects/nessclient/downloads/pdf/stable/ which lists the available parameters on page 3. Hope this helps someone as out as much as the forums have been helping me.
Yeah its a great intergration. Its been solid since the last update, my only issue is it doesnt seem to be able to handle the difference between Armed Away and Armed Home for me.
Yeah infer_arming_state: true has helped with it staying armed but it still doesnt fix the armed home vs armed away situation my case is the same as aumattās above
Thanks very much for this integration, it has been very useful.
Iām having another issue, and Iām not sure where the issue lies between HA and the Ness integration. The motion sensors will initially show up correctly, but soon will stay in a āmotion detected stateā even when motion has long since past. ness-cli will show zones changing from True to False as motion is detected.
Has anyone seen this issue? Not quite sure where to look.
No help sorry. My problem is my battery went flat about 12months ago so I disconnected it and think I ādid something elseā too. Now with a new battery, I canāt work out what else I pulled out/disabled!
and also if you need any testing done for the home / away stuff I can help out!
