My adaptor was a cheap eBay one I got years ago. Couldn’t tell you the model but it is powered by a 12v supply. Rs232 does require normally at least a signal greater than 5v. How are you powering your converter?
i’ve been reading up on rs232. You are right generally 5-25v.
The USB RS232 have voltage boosters, but it seems like they boost to 7-8v only.
A 12v power adapter with the rs-232 ethernet adapter. That is interesting the USR-TCP232-302 only uses a 5v adapter. Just ordered one off aliexpress. $34. This 5v adaptor is getting me worried now.
I’m also having the same issue using the USR-TCP232-302. Keen to see how this develops.
Out of interest what version is your panel?
Did we all blow the rx pin on the panel…
Does anyone know of a usb to rs232 that actually works with ness?
The NESS IP232 is actually a 12v product, hence it could be why, its not registering.
Its very hard to find a true 12v transmit rs232 now days.
Closest is probably MAX3232 TTL to RS232 probably at 10v.
Does anyone know of a usb to rs232 that actually works with ness?
Confirming that I’m also using the USR-TCP232 dongle for the panel at my parent’s place. Seems to work as expected though… Unsure what the panel version is though, as finding that out would require me to go on location to find out. Will check next time I am there.
Actually, looking from an earlier message in this thread, I have panel version 7.8. The version of my IP module is V4018
Hey @beatmag, I saw your DM, but posting here publicly in case it helps anyone else in the future.
I’ve been trying to get my d8x working in hass, so far not having much luck.
I wanted to ask you what panel version is your d8x or d16x?
I have v5.8 , I can seem to get status from panel but it doesn’t seem to accept any of the commands I send to it.
Anything I send to it simply echo’s back and thats about it. Im suspecting the panel is just echoing what I send to it, and thats it. Is there some option I need to enable for it to accept commands via serial port?
Not sure if you figured this out, but IIRC the panel needs to be in installer mode in order for it to respond to commands via RS232.
The proceedure to enable two way comms for nessclient is the same as for iComms:
A good way to actually test your RS232 connection would be to try connect with the iComms app to eliminate the nessclient library integration being problematic here.
Hi nick,
thanks for replying.
I have enabled P199E, to enable 2 way comms.
Do I still need to be in Installer Mode? I got the understanding that nesscomms requires installer mode.
Neither of these work on my panel.
I’ve ordered a sabrent rs232 ftdi usb cable to see if i get more luck with ftdi chipset. The pl2303 cable i got just seems abit weird.
Its as if, the panel doesnt’ get any messages at all.
The only thing I can think of is that we either all blew the RX pin on the ness panel.
Or the voltages aren’t high enough to register on the ness panel.
Do I still need to be in Installer Mode? I got the understanding that nesscomms requires installer mode.
From my vague recollection, I think it needs to remain in installer mode. Not 100% sure though, I might be wrong. Weird it doesn’t work at all.
The only thing I can think of is that we either all blew the RX pin on the ness panel.
It sounds like something with hardware problems might be likely here. Just wondering, is the panel sending messages to the laptop at all? (e.g. one way communication). If not, then perhaps it might be that the TX/RX is swapped (e.g. null modem cable being used) meaning panel TX is connected to PC TX. IIRC I had to modify the RS232 cable I had handy to cross the pins from TX->TX to TX->RX on either side. I think @OzGav had this issue:
Yes, we are all receiving information from the panel.
When I arm or disarm the panel. The information comes down fine via the serial interface.
Just cant give it any commands.
So the RX on the computer or IP323 is correct.
Have you tried with the Ness iComms app? Would be interesting to rule out any protocol weirdness with the nessclient library or manually issuing commands.
nesscomms same result.
In installer mode also.
cannot detect the panel at all.
set panel version correctly and product. Then use direct connect and select com port.
Fails to detect panel and refuses to proceed further.
Does nesscomms required P90E to enable remote access?
I’ve turned it on recently but dont recall if i tried ness comms again. I’m pretty sure I tried.
quick update.
received a sabrent rs232 ftdi cable.
https://www.amazon.com.au/Sabrent-Serial-Adapter-Chipset-CB-FTDI/dp/B006AA04K0/ref=sr_1_2_sspa?crid=1QHR12YL9HUQ&keywords=sabrent+rs232&qid=1642732469&sprefix=sabrent+rs232%2Caps%2C465&sr=8-2-spons&psc=1&spLa=ZW5jcnlwdGVkUXVhbGlmaWVyPUExTUZLT0o3WUxFS0VBJmVuY3J5cHRlZElkPUEwOTE0MTQ3M01QQTVSTTdJMk04MiZlbmNyeXB0ZWRBZElkPUExSEpaRDZLVVNQSkhTJndpZGdldE5hbWU9c3BfYXRmJmFjdGlvbj1jbGlja1JlZGlyZWN0JmRvTm90TG9nQ2xpY2s9dHJ1ZQ==
still same, echo’ing. and no real data coming back.
not sure if its cable shielding or something wrong with panel.
but i think im going to give up. I might try to crimp new wires to test it. doubt anything will change.
@beatmag, are you getting data back from the panel other than the echo’d data? e.g. do you get zone state change updates stream through?
hi nick,
not getting anything. the panel just echo’s back anything we send.
feels like we’ve blown the board to me.
have any of you, reversed the tx and rx pins…and then got it working???
Test 1 - plugged into d8x panel
Sending data - echos anything we send.
Arming from keypad - sends status
Test 2 - unplugged rs232-
sending data - no echo
Test 3 - connect tx with rx.
sending data - echos sent data back.
If you’re not getting anything back at all (other than echoing what you’re sending) then I think it’s very possible that TX/RX need to be swapped.
Arming from keypad - sends status
So you’re saying that you see this update come back through on the terminal after arming from the keypad? If that’s the case then it sounds like RX/TX is in the correct polarity. If so, do you mind sharing the payload you’re attempting to send to the panel via RS232? IIRC there’s a checksum part of the message which must be correct in order for the panel to respond to the data being sent.
But if not, then I think the echoing you might be seeing is just the echo functionality of the terminal emulator or RS232 adapter you’re using. I am 90% sure I had to swap my TX/RX pins, have a slight recollection of making a custom cable by soldering onto a RS232 plug I bought from Jaycar. (or alternatively, I think you can use a null modem cable).
yes i get the messages when i arm from keypad.
I’m just pressing the keypad in home assistant. with your component.
But the panel just echos exactly what gets sent to it.
I’m getting this error in my logs:
2022-04-09 18:01:50 DEBUG (MainThread) [nessclient.client] Decoding data: '8300360S00E9'
2022-04-09 18:01:50 DEBUG (MainThread) [nessclient.packet] Decoding bytes: '8300360S00E9'
2022-04-09 18:01:50 WARNING (MainThread) [nessclient.client] Failed to decode packet
Traceback (most recent call last):
File "/usr/local/lib/python3.9/site-packages/nessclient/client.py", line 135, in _recv_loop
event = BaseEvent.decode(pkt)
File "/usr/local/lib/python3.9/site-packages/nessclient/event.py", line 39, in decode
return StatusUpdate.decode(packet)
File "/usr/local/lib/python3.9/site-packages/nessclient/event.py", line 151, in decode
request_id = StatusUpdate.RequestID(int(packet.data[0:2], 16))
ValueError: invalid literal for int() with base 16: 'S0'
Have I got something messed up somewhere? I’m running the USR-TCP232-302 V4018.
This is the relevant section in my configuration.yaml
ness_alarm:
host: 10.11.12.24
port: 8234
scan_interval: "00:00:02"
zones:
- name: Front Door
id: 1
type: door
- name: Garage
id: 2
- name: Lounge
id: 3
- name: Living
id: 4
- name: Laundry Door
id: 5
type: door
logger:
default: info
logs:
homeassistant.components.ness_alarm: debug
homeassistant.components.alarm_control_panel.ness_alarm: debug
homeassistant.components.binary_sensor.ness_alarm: debug
nessclient: debug
I’m running HA on a Raspberry Pi 4
Have you just installed this? If so you might be suffering from the echo problem?