KNX - Device not responding. #2643
Comments
jeylites
changed the title
|
Hi, The device 2 of the wiki example just send a KNX command but only pressing the physical button1. So, if you are toggling the relay by using MQTT or the web interface, it will not do anything. Device 2 is expecting a press on the button to send the command. The device 1 is sending the relay1 status, that's why, if a MQTT or Web interface or rule, etc change the relay 1 status, the device 1 will send the KNX Command. |
|
Hmm, even pressing the physical button it works one direction. |
|
How do I get both devices (1&2) to work as bi-directional ON/ OFF via physical press? |
|
Let's see what is going on. Please use the command weblog 4 on the console and press the button to see what is doing. and then, also, if you can, please, do a save on the KNX menu. It prints out the config on the console also. thanks |
|
I apologize, my honest mistake. I think something didn't get set correctly and reconfiguring everything from scratch fixed it. Now both devices work accordingly to my needs. I assume I can't have the same behavior via MQTT? I'm using Homekit which allows grouping of switches as one, which pretty much solves my issue :) but just curious to see if it's possible on the KNX end. |
|
By MQTT you can have the same behaviour. Please see example 2 of rules on wiki By KNX you can have a direct communication device to device From the example, you will have the desired behaviour but device to MQTT broker to device. But both approaches will work. |
|
Happy to see your issues solved :) |
|
Rules is the next best feature! Will definitely consider for other things. Thank you! |
|
Love your idea of using KNX and MQTT together as one to be the backup of the other. Thanks for sharing. |
|
I encounter a problem today where Device 1 was able to turn ON Device 2 but not OFF. For Device 1, When the physical button is pressed, I get a sent KNX sent message and receive on Device 2. However when Device 2 is pressed , sent is seen but no receive on Device 1. All got fix after a hard reset on Device 1. Will try to get some logs |
|
I encounter a problem today where Device 1 was able to turn ON Device 2 but not OFF. Issue got fixed after doing a hard reset. Device 1 |
|
Device 1 Device 2 |
|
Hi, Seems that your MQTT broker is turning OFF the device: 05:59:28 RSL: Received Topic cmnd/jey1/POWER1, Data Size 3, Data OFF May a retained message on your MQTT Broker? |
|
What is the cause of the broker turning off ? May a retained message on your MQTT Broker? - What do you mean? |
|
Depending on your broker, you can set to retain messages and be re sended. |
|
Here is a copy of my Config in Homebridge `{ ], |
|
further testing seems like Device 1 is able to "ON/OFF" Device 2 via the
physical button. However, Device 2 is not able to do the same to Device 1
after a while of running. Only a hard reset fixes the issue.
Pulling up console I see Device 2 is sending a message but Device 1 is not
receiving. And the retain kicks in depending the "ON/OFF" state of Device
1.
Assuming I have Device 1 & Device 2 on "ON" state and I intentionally turn
OFF Device 2, it will turn "OFF" but Device 1 remains "ON". A few seconds
later, the retain on Device 1 kicks in to turn "ON" Device 2
Is it possible to set both devices to be responders if that makes any
sense...
*Jey Kasi*
…On Wed, May 9, 2018 at 4:32 AM, Adrian Scillato ***@***.***> wrote:
Depending on your broker, you can set to retain messages and be re sended.
You should check the MQTT Broker configuration.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#2643 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AIw6wIFuZ_Kfanv0ZSx6Gs5DhCb4tBkdks5twgDegaJpZM4T0CKk>
.
|
|
Hi, So, 1- Only device 1 is not receiving after sometime of reboot? 2- If you try to send telegrams several times, device 1 stills no respond to any telegram? |
|
3- can you post the knx configuration of device 1? |
|
1- Only device 1 is not receiving after sometime of reboot? Yes, only Device 1 is not receiving after a while eventhough Device 2 is sending messages 2- If you try to send telegrams several times, device 1 stills no respond to any telegram? It does some times, for the most part, it only works after a reboot 3- can you post the knx configuration of device 1? I have included both Device 1 & Device 2, Previously my configuration was same as your Stairs light example (2) on wiki. Had the same problem of Device 1 not receiving so I change it to the below to see if it made any difference.... guess not :(
|
|
mmmm, Seems to be similar to this issue I could not make my devices do that behaviour. That's why I'm looking for the difference on your devices. The key to the problem should be there. I noticed that the firmware build time for both devices is different. The firmware for device 1 and 2 is the same? |
|
They both compiled the same time also I have set up a second device just to make sure... the same problem I'm using Compiled with Arduino 1.8.5 OSX |
|
A second device also have the issue with the same config than the device 1?
El mié., 9 de may. de 2018 02:16, jeylites <notifications@github.com>
escribió:
… They both compiled the same time also I have set up a second device just
to make sure... the same problem
I'm using
Core 2.40 lwIP 1.4 Prebuilt
Tasmota 5.13.1a
Compiled with Arduino 1.8.5 OSX
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2643 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Ahw-hzJ-bYZWrE8kf6HLHIpzOg7xsvW9ks5twnupgaJpZM4T0CKk>
.
|
|
Yes same problem
|
|
Ok. But device 2 is working ok?
El mié., 9 de may. de 2018 02:24, jeylites <notifications@github.com>
escribió:
… Yes same problem
On Wed, May 9, 2018 at 1:22 PM Adrian Scillato ***@***.***>
wrote:
> A second device also have the issue with the same config than the device
1?
>
> El mié., 9 de may. de 2018 02:16, jeylites ***@***.***>
> escribió:
>
> > They both compiled the same time also I have set up a second device
just
> > to make sure... the same problem
> >
> > I'm using
> > Core 2.40 lwIP 1.4 Prebuilt
> > Tasmota 5.13.1a
> >
> > Compiled with Arduino 1.8.5 OSX
> >
> > —
> > You are receiving this because you were mentioned.
> > Reply to this email directly, view it on GitHub
> > <
>
#2643 (comment)
> >,
> > or mute the thread
> > <
>
https://github.com/notifications/unsubscribe-auth/Ahw-hzJ-bYZWrE8kf6HLHIpzOg7xsvW9ks5twnupgaJpZM4T0CKk
> >
> > .
> >
>
> —
> You are receiving this because you modified the open/close state.
> Reply to this email directly, view it on GitHub
> <
#2643 (comment)
>,
> or mute the thread
> <
https://github.com/notifications/unsubscribe-auth/AIw6wAJF2Q1D9ETdiis4c1PYxAW0Ljyzks5twn0WgaJpZM4T0CKk
>
> .
>
--
Sent from Iphone Mobile
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2643 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Ahw-h6HD7Yb2LnLTwc1ImIpfypFbzYYrks5twn2EgaJpZM4T0CKk>
.
|
|
Both Device New and Old that I have setup is going through the same issue
where communication goes one direction. I just flashed another board with
platform io. Will report back
|
Yes, the I will have to test a little more to check for reliability. I have learned problem usually shows up after hours and hours of running. Will report soon on this... |
|
For some reason now I'm unable to compile I get a bunch of error. I googled for help but there's not much info out there |
change to this: comment everything you dont need and just chose one platform like above ( |
Just delete .pioenv folder inside your sonoff project folder And also do a rebuild c/c++ ...
|
|
I have been going through every folder looking for the pioenvs file or folder, are you referring to the pio folder? |
|
the .pioenvs folder is made by platformio inside the sonoff-tasmota folder |
|
So, this issue get solved for you when you recompiled the firmware, right? On the first boot, did you loose the configuration? |
|
the folder doesn't seem to exists in my sonoff-tasmota folder so replaced it with a clean version of 5.13.1a and it took it. Currently testing Core 2.30, Core 2.4.0,Core 2.4.1 Will let you now you know soon. It seem to be an ongoing issue, at anytime do you get access to web browser? I realise using core 2.4.0 & 2.4.1 after a while web browser become unresponsive. Found out that a power cycle of sonoff or reboot of router only brings it back.... The cycle continues. Another thing by accident I found that access is granted if MQTT broker is down after a while. My best guess will be traffic, the esp is unable to keep up. |
|
Hi I think I found the problem ! 😄 I could reproduce this issue. If the sonoff device get disconnected from the wifi router, when reconnecting to the same router it loose the multicast connection for receiving packets. That's why a reboot solve the issue because on boot it opens again the UDP. I will make a PR to solve this. So, The issue was not related to esp lib versions, configurations nor compilation. For the disconnection tests, I just unplug my wifi router and plug it again. So, then with the patched version you should not have problems, but you should look why you have those micro-disconnections from your router ( may be too many wifi devices ? ) There is a very interesting and technical video about wifi routers installation by @davidelang at https://www.usenix.org/conference/lisa12/technical-sessions/presentation/lang_david_wireless Thanks a lot again for all the tests you made. Thanks to all your help was possible to find the root of the problem. 👍 |
Fix KNX Reconnection Issue (arendst#2643)
|
That explain a lot why KNX works on all Core modes. Just saw the push, will test it out soon. Thanks for sharing @davidelang video on wireless router. Very informative!!! |
|
Fixed. |
|
Nice will test it later. |
|
Just tested the latest release 5.13.1a downloaded yesterday. Seem the KNX devices are not receiving messages after running a while. Please see below logs . Device 1 Device 2 |
|
Hi, 1- This is happening to both devices? 2- Are you using a wifi repeater? 3- Can you access to your wifi router configuration to see: |
|
1- This is happening to both devices? 2- Are you using a wifi repeater? 3- Can you access to your wifi router configuration to see: I just drop the RTS value to 2304 from 2346
|
|
Please, Test if the issue persists changing Enable IGMP Snooping to disable |
|
will do. |
|
Also, please check the config on the main router as your AP is not isolated, meaning that your main router is the one that manages everything. |
|
IGMP Snooping to disable, KNX stops receiving. When turn on it's communicating between devices. AP is not in isolated mode. |
exactly, so the multicast is being managed by the main router Please, check the configuration of your main router. And if you can, try to connect both Sonoffs to the main router. If you can't do that, try the isolated turned on, on your AP. |
|
Just an update. I took your tip about moving the KNX Sonoff stuff to the main router. Everything started working right after, also solved few other issue - NTP server sync, Web browser became more reachable and KNX were receiving messages. The puzzling yet disappointing part is the stock ISP router seem far more reliable than the mid range Asus RT- AC55UHP that I have. I also did some research on the Asus router, seems to be a common issue with multicast. It dropout after awhile and the only way to get it back is to do a power cycle. Anyway, all systems been running for 15 hours without any major issue. |
|
Wow. Very good news!
Happy to hear that you found the problem :)
El lun., 14 de may. de 2018 07:02, jeylites <notifications@github.com>
escribió:
… Just an update. I took your tip about moving the KNX Sonoff stuff to the
main router. Everything started working right after, also solved few other
issue - NTP server sync, Web browser became more reachable and KNX were
receiving messages.
The puzzling yet disappointing part is the stock ISP router seem far more
reliable than the mid range Asus RT- AC55UHP that I have.
I also did some research on the Asus router, seems to be a common issue
with multicast. It dropout after awhile and the only way to get it back is
to do a power cycle.
Anyway, all systems been running for 15 hours without any major issue.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2643 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Ahw-h3mqNXJ4R5QsuFcd5ffzrIqTVDiwks5tyVYjgaJpZM4T0CKk>
.
|
|
I've some networking question to ask. SSID Is it advisable to have two different SSID names Tasmota device STA_SSID1 & STA_SSID2 or can they be the same? What is the best wifi tool to use. Currently have WIFI_RETRY Also planing to get a new AP router, what do you have installed perhaps I could look for something similar? |
Really, I don't know what should be the best. You should try. The only advise is (as explained on the davidelang video) be aware of the hidden transmitters, so try that all sonoff that are connected to a specific router, see each other.
Can be the same. No problem with that. I have just one wifi router by now, so I put both SSID the same. So if it disconnects from the wifi will try again.
That depends on what you want to do. I also use WIFI_RETRY so when it disconnects from the wifi it will immediately try to connect to the next SSID - that in my case is the same network.
By now, my setup is just one TP-LINK Wifi Router provided by my ISP. Everything is connected there. |
|
Thank you. I will try setting this up and see where it goes. :)
On Tue, May 15, 2018 at 1:07 PM Adrian Scillato ***@***.***> wrote:
Should I connect all Sonoff devices to the AP or both Main and AP ?
Really, I don't know what should be the best. You should try. The only
advise is (as explained on the davidelang video) be aware of the *hidden
transmitters*, so try that all sonoff that are connected to a specific
router, see each other.
Is it advisable to have two different SSID names Tasmota device STA_SSID1
& STA_SSID2 or can they be the same?
Can be the same. No problem with that. I have just one wifi router by now,
so I put both SSID the same. So if it disconnects from the wifi will try
again.
What is the best wifi tool to use?
That depends on what you want to do. I also use WIFI_RETRY so when it
disconnects from the wifi it will immediately try to connect to the next
SSID - that in my case is the same network.
what do you have installed ?
By now, my setup is just one TP-LINK Wifi Router provided by my ISP.
Everything is connected there.
I'm planning to have another just to avoid the *hidden transmitter* issue.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#2643 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AIw6wPtnEyl6uDcRmY54y1MMhBSVcyPsks5tymKtgaJpZM4T0CKk>
.
--
Sent from Iphone Mobile
|
Make sure these boxes are checked before submitting your issue - Thank you!
status 0@ascillato
I tried to simulate KNX Example 2 from wiki. It seems like Device 2 is able to control the ON/ OFF of Device 1, but not the other way round.
Compiling with core 2.3.0 ran me into wifi disconnection issues. With 2.4.0, KNX seems responsive, no weird behavior like 2.4.1.
Following is my current config
Core: 2.4.0
Tasmota: 5.13.1.a
Hardware: Sonoff T1, 3gang
Device 1
Device 2
The text was updated successfully, but these errors were encountered: