Replies: 3 comments 14 replies
-
|
Something is causing interference with the garage light receiving messages. If you have replaced the device, the only other idea is to add other nearby devices to increase the signal strength. Auto updates is living dangerously. Breaking changes can happen and will be documented in the changelog, I usually like to look at those first. This library is not likely to have security updates often if ever, which is really the only reason to need an auto-update. I suspect it isn't working because you installed the plug in using SSH and the |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, I get it, delays like this are not helpful. The issue is that the device is not receiving the first message. If the delay is 5 seconds, it means the second message is received, if the delay is 10 seconds, it means the third message.... The reason the subsequent messages are received is the hop count is incremented +1 each time. The solution, and I have been dragging my feet on it because I am not super excited about it, is to allow setting the minimum hop count on a per device basis. This has a few downsides:
Let me look at the issue, this afternoon. |
Beta Was this translation helpful? Give feedback.
-
|
OK, if you are able to run a branch, try out this branch https://github.com/krkeegan/insteon-mqtt/tree/Min_Hops There is no documentation. But basically amend your device entry in the config file as follows: devices:
dimmer:
- 11.22.33: "device that turns on slowly name"
min_hops: 1Note that there is no dash before the min_hops. Try it with the setting of 1 first. If that doesn't work you can increment up by one to a maximum of 3. |
Beta Was this translation helpful? Give feedback.
-
|
Wow, you got that done FAST ! :) I am using HASS-OS on a RPi. I don't know if I can or cannot run a branch, but I sure would like to try! Could you kindly tell me how I would do that? Thanks so much for the help!!! |
Beta Was this translation helpful? Give feedback.
-
|
Yeah much of the work was actually duplicative code. Writing the documentation, examples, and unit tests will take a bit more time. If you are comfortable with SSH, and git, then yes you can test this out. I wrote up some sparse instructions here that would point you in the right direction. But they are not a recipe you can just copy, you would have to at least vaguely understand git to get the proper repository and branch. Otherwise, it will probably be about a week to finish up the changes, test them out, and push a new release. |
Beta Was this translation helpful? Give feedback.
-
|
Just piggybacking on this, but I have auto-update on HASS as well and I'm still running 0.7.2. Is upgrading broken or requires manual intervention? @krkeegan |
Beta Was this translation helpful? Give feedback.
-
|
OK, there is an option for Let me know if this solves your delay issue. |
Beta Was this translation helpful? Give feedback.
-
|
Don't take any offence to this, but it seems to be hard to keep you focused on one problem. I feel like every response always takes a slightly different direction each time with new variables and multiple problems. It is hard for me to tell what exactly you think the "problem" is in all of these cases. But I think you are saying that sometimes things take 5 seconds and sometimes they don't. I don't think the item triggering the light to change matters. If I am reading between the lines well enough, I think in each of these scenarios you describe
HomeAssistant is in the middle handling the automation. Is that correct? I looks to me like each of the automations trigger a call to turn on the Taking the issues I see one at a time:
These log details:
and
Are telling you that the initial command sent to these devices did not make it to the device. The subsequent line tells you that the hops had to be increased. For the Messages like this may happen from time to time. We know from experience that the Bottom line, and I know this sounds like I get a commission from Insteon, but my guess is that you just don't have a high enough concentration of Insteon devices to have a consistent mesh network working all the time. |
Beta Was this translation helpful? Give feedback.
-
|
First of all, absolutely no offense taken. I have been troubleshooting Navy electronic systems for many years, and I really felt I could get a handle on this. The reason I went down this different path was because I realized that the other automations in my house were responding perfectly. Even when I add the garage light to that automation, just as a test. I was starting to think it was more than just bad insteon comms. So I tried the other things. Again, no offense taken. So, I tried increasing to min_hops: 2 and ran it again. And I saw the debug message that it was increasing max_hops to 3. So I increased it to three, and now it still says increasing max_hops to 3. That surprised me, so I restarted the insteon-mqtt and I still get the same messages. As for the number of devices in that area, the PLM is still sitting on top of the refrigerator, but I have unplugged it while testing. It is three feet, direct line of sight to the switch. The PLM is less than six months old, and the garage switch is dual band. The switch in in a dual gang box with an insteon dimmer (the garage light is an on-off switch). And I have a dual band appliancelinc in line of sight. The PLM and these devices are all on the same circuit in my house. Four devices within a six foot diameter circle, all line of sight. Do you really think I might need more in there? I do have one more dual band appliancelinc dimmer that I can put in there. Here's the latest log, with min_hops set to 3: I promise to not go down any other paths! I very much appreciate your help, and the least I can do is confuse the matter with my home grown science experiments! |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, so sadly, it looks like this is a problem in Insteon network:
My recommendation is probably to stay with Is a message sent from the garage device to the modem. It has In the longer run, I would see if it is at all possible to add another device somewhere between the modem and the garage. A device not on the same circuit but between them could still help with wireless signals. A device on the same circuit might be even better because it would strengthen the wired signal. Adding a device would mean that when the additional hops occur, both the modem and the extra device would be yelling at the same time and that might help. I don't think there is much more I can add or that we can do from our side for this device. But I am happy to help with the next problem if you have one. |
Beta Was this translation helpful? Give feedback.
-
|
Totally tracking what you are saying. I can make a modem scene with these three devices and see how that helps. I'll keep trying. I do appreciate your help very much! If I get it solved, I'll be sure to let you know though. |
Beta Was this translation helpful? Give feedback.
-
|
A modem scene won't do anything to increase the likelihood that the garage light will hear the message. That said, it may make things more palatable for you, since the other lights will likely react immediately rather than getting blocked by waiting for the garage to acknowledge the command. |
Beta Was this translation helpful? Give feedback.
-
|
Just adding another data point. I had a 2477S switch that was engine version i2CS. A few months ago it started having issues with i2 commands. Then most recently it started to fail 50% to on/off commands. I assumed the device was bad and replaced it. But right away, I noticed that the new device was also acting funny. So I plugged a few mobile devices into the same electrical circuit thinking maybe it can't hear commands. This only provided mild relief. I turned the circuit off and identified the other electrical devices in the circuit. I decided, somewhat arbitrarily, that a powered subwoofer and possibly a power strip (powering an audio amplifier, a directv box, a wifi access point, and a chromecast) could be causing issues. So I plugged in a FilterLinc to isolate the powerstrip and the subwoofer. And poof, all the issues went away. The new device works perfect. Even the old device wired up in another location works perfect. I can't yet say which device was causing the issue, but it is pretty clear that one of them was causing a lot of noise and interference. The wireless portion of Insteon was not enough by itself to overcome the issue. The only bummer, is it seems like Insteon may no longer be making the Filterlinc devices. Not sure why that is, or whether other generic power filtering devices could be used instead. Anyways, I hope this helps someone, sometimes you have to test whether non-Insteon devices are causing interference. |
Beta Was this translation helpful? Give feedback.
-
For the longest time, I have had a problem with my garage light. My Home Assistant RPi is in the garage, so it's good and close. But still, it regularly take five seconds or so to come on. I even replaced the switch with a brand new device, but I still have the same problem. Weird. Here's my original thread about this:
#242
I am using HASS-OS and currently on 0.7.4, and I have auto-update checked. I think question number one is how do I upgrade to a newer version? And if anyone has any ideas why I would be having problems with just this one location, I'd appreciate their thoughts :)
Skip
Beta Was this translation helpful? Give feedback.
All reactions