Hello,
New external integration to control shutters, switches, lamps, and sensors from a Devmel AirSend radio gateway. ![]()
Available on the store in about an hour ![]()
Hello,
New external integration to control shutters, switches, lamps, and sensors from a Devmel AirSend radio gateway. ![]()
Available on the store in about an hour ![]()
Version 2 is out with widgets, triggers, and actions ![]()
Bug fixes are also part of the package ![]()
Hello
I just integrated the DEVEMEL integration and I control all my SOMFY IO and RTS shutters, I have a Tubauto gate and it gives me an error when I want to integrate it to Gladys I copied the Json file as described in the Doc
I donât know if you can help me here is the code
HTTP 422 â UNPROCESSABLE_ENTITY â t_device_feature.min cannot be null; t_device_feature.max cannot be null
Xavier
Thanks for the report
This is normally fixed in version 2.0.3
The cause
The fix
Thanks for the feedback, itâs good, it works now ![]()
Hello, and thank you for this integration, the remotes mechanism works well.
My airsend.cloud export contains 8 Somfy RTS shutters and 4 âgroupâ inputs, all on pid 13920 (RFY):
Each shutter lists in its remotes the channel of its group and that of the centralized command, and the three groups list the centralized channel. In this sense, it works: an order sent from Gladys (or by a remote control copied to the group address) on âCentralized Shuttersâ updates the 3 groups and the 8 shutters.
Nothing is reported in the other direction:
A group (an input whose channel appears in the remotes of other inputs, or an explicit members list) would recalculate its state in Gladys only, without emitting anything on the radio, every time one of its members publishes a state:
This would also cover the case âall shutters raised one by one â the centralized command displays openâ.
I can test a branch on my installation (Gladys 5.3.2, AirSend service integrated, a single box).
Hello @XDECO,
Thank you for this very detailed feedback!
Itâs in place in version 3.3.0, available now.
A group now displays in Gladys the actual state of its shutters. It is calculated in the integration, and nothing is sent over the radio:
travel_up / travel_down) displays the average position of its shuttersGladys does not have an âundeterminedâ state: âstoppedâ is the closest state, that of a shutter halfway.
âCentralized Shuttersâ correctly counts your 8 shutters, going through the South / West / North groups. If you raise the 8 shutters one by one, it goes to âopenâ.
The remotes you already have are sufficient: a shutter that has a group address in its remotes is a member of that group.
4 group(s) of shutters show what their shutters showI couldnât test it on real hardware, so your feedback is very interesting to me, especially with your 8 shutters and 4 groups.
Thank you again for the tests! ![]()
Thanks @prohand for the 3.3.0, itâs tested and it works!
On startup, I have « 4 group(s) of shutters show what their shutters show ».
For the South group:
- I open Volet Cuisine Sud alone â Volets Sud and Volets CentralisĂ©s go to « stopped »;
- I open Volet Porte FenĂȘtre Sud â Volets Sud goes to « open », Volets CentralisĂ©s remains « stopped » (Ouest and Nord still closed);
- I close Volets Sud â the 2 shutters follow and Volets CentralisĂ©s goes back to « closed ».
Two remarks in the logs, without visible consequences:
Every 4 minutes: « Could not keep the link to âAirSend boxâ warm: The box did not carry the order: UNSUPPORTED (event type 262) », followed by « Woke the link ⊠in 0.2 s ». My box seems not to accept the keep-alive order.
On startup: « Ignored a radio frame (unreliable, graded 0): pid 1 ⊠Set the listening channel to âgenericâ », while listening is already on channel 1 (deduced). The advice goes in circles.
Iâm still testing the wall controls and the West / North groups, and Iâll get back to you.
Thanks @XDECO for these detailed tests, it helps a lot! ![]()
**Shutter groups**: everything works as expected. A group displays:
- « open » if **all** its shutters are open,
- « closed » if **all** are closed,
- « stopped » in other cases.
So with only Cuisine Sud open, « Volets Sud » correctly goes to « stopped ». And « Volets Centralisés » remains « stopped » as long as West and North are closed.
**The two log messages you reported are fixed in 3.3.1**:
1. **âCould not keep the link warm⊠UNSUPPORTED (event type 262)â every 4 min**
To keep the link active, the integration reads a sensor from the box. Your AirSend doesnât have a sensor, so it responds « UNSUPPORTED »⊠but it responds, and thatâs all we ask of it (your log actually shows a wake-up in 0.2 s). So it wasnât an error: the log now clearly states this.
2. **âIgnored a radio frame (unreliable, graded 0): pid 1â with the advice to switch listening to « generic »**
You were right, the advice was going in circles. The integration now takes into account the current listening. If it is already on this protocol, it says thereâs nothing to change: itâs usually a frame from a neighborâs device or radio interference.
3.3.1 is available, you can update whenever you want.
Iâm waiting for your feedback on the wall-mounted remote controls and the West and North groups ![]()