CallerId Automation Problem - SOLVED

Purchased another USB Modemn that returns the caller id information.

All,

I am trying to use the CallerId Sensor to automate notification of incoming calls. I picked up a Dell (Conexant) USB modem and I’ve got the automation working as seen here:

2019-09-24 20:50:53 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=sensor.modem_callerid, old_state=<state sensor.modem_callerid=idle; cid_time=0, cid_number=, cid_name=, friendly_name=Modem CallerID, icon=mdi:phone-classic @ 2019-09-24T20:40:39.593025-04:00>, new_state=<state sensor.modem_callerid=ring; cid_time=2019-09-24T16:50:53.059085-04:00, cid_number=, cid_name=, friendly_name=Modem CallerID, icon=mdi:phone-classic @ 2019-09-24T20:50:53.059323-04:00>>

2019-09-24 20:50:53 DEBUG (MainThread) [homeassistant.components.websocket_api.http.connection.22457731236048] Sending {'id': 2, 'type': 'event', 'event': <Event state_changed[L]: entity_id=sensor.modem_callerid, old_state=<state sensor.modem_callerid=idle; cid_time=0, cid_number=, cid_name=, friendly_name=Modem CallerID, icon=mdi:phone-classic @ 2019-09-24T20:40:39.593025-04:00>, new_state=<state sensor.modem_callerid=ring; cid_time=2019-09-24T16:50:53.059085-04:00, cid_number=, cid_name=, friendly_name=Modem CallerID, icon=mdi:phone-classic @ 2019-09-24T20:50:53.059323-04:00>>}

The issue is that neither the caller name nor caller number is picked up by the HA sensor.

I found a possible documented bug here that appears to be addressing the same issue.

Is there a fix available for this issue? Could it be that my modem is the culprit?
Any other work arounds?

Larry

1 Like

This ever get resolved?

I fixed this by purchasing a different modem.

Thanks Larry, which modem?

JR

USB 56K External Dial Up Voice Fax Data Modem Windows 10/8/7/XP/Vista https://www.amazon.com/dp/B077YBTC2J/ref=cm_sw_r_cp_apa_i_oo2YDbG0MYMMZ

Works great over usb 2.0. Shows up as /dev/ttyACMx. Still not sure about usb 3.0.