-
Notifications
You must be signed in to change notification settings - Fork 1
Hidden tests - @fabi9163 #1
Replies: 5 comments · 64 replies
-
|
Hi @fabi9163, Could you join me here as well ? |
Beta Was this translation helpful? Give feedback.
All reactions
-
|
Of course I want to help/test. Is this a fork of the official repo für hidden tests? Should we install it on top of the actual version as described in the readme? |
Beta Was this translation helpful? Give feedback.
All reactions
-
|
Yes this is for "hidden" tests 😉 You can see that as a preview of the next release which will add support for Eltako. The configuration is the same, you can reuse the same settings. Once this new addon is installed and started, tell me so we can proceed to further tests. |
Beta Was this translation helpful? Give feedback.
All reactions
-
|
Hi @fabi9163, I updated the enoceanmqtt.devices.sample file with an example of how to add your FSB14 in the device file. |
Beta Was this translation helpful? Give feedback.
All reactions
-
|
Hi @mak-gitdev, I've installed the Test-Addon and added your enoceanmqtt.devices.sample as device-file, enabled debugging, mapped on my ID and restarted. Then I pressed the switch (switch ID is FEE2011F):
Please tell me what tests and logfiles you need! PS. Why is there no "a5" telegram, is there something missing? |
Beta Was this translation helpful? Give feedback.
All reactions
-
|
|
Beta Was this translation helpful? Give feedback.
All reactions
-
|
I wrote the previous message before seeing your message.
Yes this is better I think, so all data available at the same location. 👍 |
Beta Was this translation helpful? Give feedback.
All reactions
-
|
hehe, made a suggestion. Feel free to optimize/change or give feedback |
Beta Was this translation helpful? Give feedback.
All reactions
-
|
Perfect ! Thanks a lot |
Beta Was this translation helpful? Give feedback.
All reactions
-
|
Hi @fabi9163, By tonight, I will push 0.0.5 which will add the mapping above (FHD60SB, FSB14, FSB61, FSR61, FSR14). |
Beta Was this translation helpful? Give feedback.
All reactions
-
👍 1
-
|
I've updated to 0.0.5 and removed my own mapping-file. Seems weather the light nor the cover is working. Do I have to pair again? |
Beta Was this translation helpful? Give feedback.
All reactions
-
|
Hi @fabi9163, Sorry I just saw your message. No need to pair again. Need only to clean your device database.
If not, then use your custom mapping file. That will fix it for sure. |
Beta Was this translation helpful? Give feedback.
All reactions
-
|
Hi, PS: You told at first there will only be a up/down cover. But it seems also the percentage is available and looks good on some first tests, hehe👌 Hope I will find some more time for declare all the other covers and some tests. |
Beta Was this translation helpful? Give feedback.
All reactions
-
|
Hi @fabi9163, Yes I had time this weekend to play a bit with my FSB61 and check that the cover entity was ok. Regarding the issue with entities, normally it has been fixed. |
Beta Was this translation helpful? Give feedback.
All reactions
-
👍 1
-
|
Hi @mak-gitdev,
the mqtt-devices list is empty. After adding everything back two devices seems to be in the "old" mode, see (version 0.0.10) Any idea? |
Beta Was this translation helpful? Give feedback.
All reactions
-
Beta Was this translation helpful? Give feedback.
All reactions
-
|
Hi @fabi9163, Regarding your second message. As you may have noticed, I just started my journey with Eltako devices.
So I thought this was the same for Eltako as well. Anyway, no problem at all, you can add a specific sender ID per device like below: To know you USB300 Base ID, have a look at this page. You will unfortunately have to do the pairing again. Sorry for that. |
Beta Was this translation helpful? Give feedback.
All reactions
-
|
Nevermind my last comments, seems I have to switch every toggle one time to change it's style to a toggle |
Beta Was this translation helpful? Give feedback.
All reactions
-
|
Thanks for the feedback. |
Beta Was this translation helpful? Give feedback.
All reactions
-
|
No Problem and thanks for asking. Last TODO for me is to get the FSR61 working. Paired it and the switch is already working. But the virtual toggle is switching back -> the feedbackloop is somhow broken until now. But last time with virtual-switches the problem was the same and could be solved by another pairing-process...not figured out what exactly causes the problem |
Beta Was this translation helpful? Give feedback.
All reactions
-
👍 1
-
|
No, it's not working... Paired it in Mode "40" aka "Direction Key/Switch" and enabled acknowledgment-telegrams. Legend: This is the result I get in Logs if I press a manual Rocker And the logs if I press the Switch in HA: @mak-gitdev are the acknowledgment-telegrams from 04:26:01:61 correct? |
Beta Was this translation helpful? Give feedback.
All reactions
-
|
Realized the problem is bigger, also states of the FSR14 aktors is not working correcly, will add some logs soon |
Beta Was this translation helpful? Give feedback.
All reactions
-
|
Configuration Legend: Actual State:
triggering Manual Rocker Light is on triggering HA-Switch Light still on |
Beta Was this translation helpful? Give feedback.
All reactions
-
|
Hi, After finding time to create some automations to controll all shutters I'm getting some strange behaviour: Automations for sunrise/sunset: The state of the screenshot was after triggering sunrise -> every cover should be partially or fully opened. But only some shutters were triggered. Is this problem related to the cover entity? Or do I need to trigger the service one after the other to avoid parallel overlapping of the wireless signals? (Info: I'm running still version 0.0.10) |
Beta Was this translation helpful? Give feedback.
All reactions
-
|
Hi @fabi9163, Not sure this is related to the cover entity as you are able to control them manually. If possible, it would be interesting to have a log when sunrise or sunset is triggered. Anyway, I think your proposed solution should work with as low as a 1 second delay between each service call. |
Beta Was this translation helpful? Give feedback.
All reactions
-
|
Thanks for the quick answer, initial positions: closed everywhere Trigger "open"/sunrise on ~11:43:20Triggered "close"/sunset on 11:46:30Result: Open againResult: Like always: Feel free to ask if some more tests can help And thanks a lot! PS: Will now try a delay in the automation |
Beta Was this translation helpful? Give feedback.
All reactions
-
|
Thanks for the log (I reformatted your answer to add collapsible sections for the logs. At first glance, I can't see any performance issue from enoceanmqtt. |
Beta Was this translation helpful? Give feedback.
All reactions
-
|
(Thanks for reformatting, much better) |
Beta Was this translation helpful? Give feedback.
All reactions
-
👍 1




Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi @schlegel,Could you please join me here ?Beta Was this translation helpful? Give feedback.
All reactions