-
|
Background: I am migrating my Insteon devices from Indigo to Home Assistantinsteon-mqtt, using the same Insteon modem. I had essentially no issues with dimmers/switches/outlets/io_lincs, but I've had great difficulty with my hidden door sensors. Finally/eventually I got all but two of the hidden door sensors working with insteon-mqtt/home-assistant. Now I am attempting to add two new hidden door sensors, and nothing I've tried works. Any advice about what I am doing wrong, and how I can get this to work? |
Beta Was this translation helpful? Give feedback.
Replies: 7 comments 10 replies
-
|
Did you figure this out? If not, please provide the version you are currently on, the relevant configuration for the devices, and the relevant log output. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @krkeegan I'm having this problem too. I have the exact problem above, which is so weird. Two hidden door sensors work but none thereafter will work. insteon-mqtt 1.1.1 No amount of joining/pairing works. Even though the devices appear to sync with the 2413U modem, I then get this in insteon-mqtt:
I can see activity in MQTT Explorer as well:
|
Beta Was this translation helpful? Give feedback.
-
|
The error |
Beta Was this translation helpful? Give feedback.
-
|
@dcj did you ever figure this out? Now I am wondering if it's perhaps an older firmware issue. |
Beta Was this translation helpful? Give feedback.
-
|
This is super weird. I am able to force the device to pair with the modem via but then... and it's in both my config files. this is consistent for all older door sensors. I think it may be related to this: #12 |
Beta Was this translation helpful? Give feedback.
-
|
More logs: |
Beta Was this translation helpful? Give feedback.
-
|
But then I try a different hidden door sensor (a working one) and get this: |
Beta Was this translation helpful? Give feedback.
-
|
When I go look at the links I see something interesting. For the working door sensor we see this: For the not-working one: The responder data is all 0x00. Is this a faulty unit or a user error? |
Beta Was this translation helpful? Give feedback.
-
|
I'm able to force the RESP value with |
Beta Was this translation helpful? Give feedback.
-
|
So it's weird — we can clearly see it's linked somehow to the modem, it's in the db, but insteon-mqtt doesn't think so. |
Beta Was this translation helpful? Give feedback.
-
|
AFAICT I have finally worked through this issue....
I had this issue with two different hidden door sensors, and after the above, they both seem to be working.... |
Beta Was this translation helpful? Give feedback.
-
|
everything is defined correctly
…On Thu, Feb 03, 2022 at 11:47 AM, Kevin Robert Keegan < ***@***.*** > wrote:
The error ERROR: Unknown broadcast device 23.3a.ef I think can only happen
if the device is not defined in the config.yaml file. Make sure you did
that correctly.
—
Reply to this email directly, view it on GitHub (
#349 (reply in thread)
) , or unsubscribe (
https://github.com/notifications/unsubscribe-auth/AACTW56ZOEMDT7V6PASW5ALUZLLVXANCNFSM4XNPHPHQ
).
Triage notifications on the go with GitHub Mobile for iOS (
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
) or Android (
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub
).
You are receiving this because you commented. Message ID: <TD22057/insteon-mqtt/repo-discussions/349/comments/2106333
@ github. com>
|
Beta Was this translation helpful? Give feedback.
-
|
Can you post an excerpt of your config.yaml file for the |
Beta Was this translation helpful? Give feedback.
-
some of these others work. 23.3a.ef does not. no idea why. |
Beta Was this translation helpful? Give feedback.
-
|
That looks fine. Are there any errors on startup, particularly related to
My confusion is that the code in this area is very straightforward and is not at all specific to a battery_sensor: device = self.modem.find(msg.from_addr)
if not device:
LOG.error("Unknown broadcast device %s", msg.from_addr)
return Msg.UNKNOWNI don't know how else you could be getting this error. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks @krkeegan i have good news and bad news. The bad news is i uninstalled and reinstalled insteon-mqtt So I wonder if it's a cache issue. In the future, is there something I could delete or run to try to clear insteon-mqtt's cache? I would recommend anyone else having a mystery device issue like this in the future try an uninstall/reinstall/start/stop/restart (the HA equivalent of a 30-30-30 😁 ) |
Beta Was this translation helpful? Give feedback.
-
|
Well glad it is working. I doubt the cache had anything to do with it. 1) the cache doesn't come into play for receiving messages, 2) I doubt you deleted the cache, it can't be removed by uninstalling Insteon-MQTT, as it is stored with the config file in the |
Beta Was this translation helpful? Give feedback.
AFAICT I have finally worked through this issue....
I lived with it for most of the year, but today I "bit the bullet" and upgraded to
v.1.1.1(see #468)For a hidden door sensor with address xx.yy.zz, I:
awake xx.yy.zzjoin xx.yy.zz,pair xx.yy,zzandrefresh xx.yy.zzI had this issue with two different hidden door sensors, and after the above, they both seem to be working....
I wonder if the distance between my modem (main house basement) and my home office (detached structure in back yard) makes it difficult f…