Motionmounter

[Thund3rstone]

I am experimenting with an app that can set the turn and extend positions of a Vogel’s Motionmount TV mount (Probably is Next 7355, I’ve had it for a couple f years). Currently, I can manually set the turn and extend positions from within the Homey GUI. I have a “then” flow “Goto position” that can set the turn and extend position from within a flow. I broke this with recent modifications, but that’s an easy fix most likely.

I am working on getting the presets in the app, which seems to be possible, but requires some more work and testing.

I have no experience with creating Homey apps, and have not looked at publishing. There also seems to be a difference in creating apps for old and new Homey Pro’s which I have not looked at. I may do that, but only if there are people who have such a MotionMount device and very much want an app to control it. Let me know!

[Dijker]

First of all, welcome to the Homey Community!

To make sure you are aware of the forum rules, please read the Welcome to the forum! post here.

[PochP]

Hey! I have for years once every couple of months googled ”Vogels MotionMount Honey” and here you are! I am very interested in an app like that!

[Thund3rstone]

I have published alpha release 0.0.3 of my app. This is the proof of concept, now including the possibility to set the MotionMount to one of the saved presets. I have done some happy flow testing, and it seems to work. Keep an eye on your device while testing! Also, note that your Homey has to be able to setup a stable bluetooth connection to your Motionmount. I had to move my Homey in range for this. The initial setup may fail if no BLE connection can be made when adding the device. I am working on getting that connection more robust.

The app has been tested by one person other than me, and it was reported that it works. If you do also test, please let me know!

You can test my app from here: https://homey.app/en-nl/app/net.thunderstone.motionmount/Motionmounter/test/

[Timo_Rouwenhorst]

The app works. Although I couldn’t control the Motion Mount the first time I tried. I reinstalled it, and then it worked.

I’ll give it a try over the next few days. It’s great that you created this app!

[Stefaan_Menschaert]

Hi

I also have a motion mount next 7356 (for OLED screen), I have installed the app, but when I search voor motion mounter to add the mount, I don’t find anything.

[Thund3rstone]

So the app searches for a Bluetooth device with the exact name “Vogel’s MotionMount”. Did you rename your device, or does it have a different name by default?

[Thund3rstone]

I have been testing with an option to have a flow card like “when position changed”, but I could not get that to function the way I liked. Also, it either requires a constant BT connection to the device, or a polling of the device and use that poll data to trigger the flow card. The first option makes it that the default Vogel’s app cannot connect, which is really undesirable. The second option causes a significant delay between the changing of the position and the triggering of the card. A poll connects via BT, which at that moment makes other BT connections to the device impossible. So very frequent polls are bad. I might revisit it. But I also wonder how one would use such a flow.

Anyway, I removed that particular flow code, had Claude fix some stuff to make it more robust, changed the way that manual preset selection works (it doesn’t detect presets, you just have to pick one now), enabled polling by default (else the sliders and position numbers are not accurate), and set the polling default to five minutes and the minimum to 60 seconds. Still seems to work pretty well here.

You can test version 0.1.0 here: Motionmounter | Homey

If no issues are reported on this version I will see if I can get it certified. Please test and let me know.

[Stefaan_Menschaert]

I changed the name, but I changed it back to the default name, and now I can add him to my homey, but when I want to control him, nothing happens, I also can’t see the presets I have made in de Vogel’s app or when i want to control the motionmount through the app nothing happens.

[Stefaan_Menschaert]

"Hi Thund3rstone, I’m testing v0.1 with a NEXT 7356 (you and the other testers were probably on the 7355). Adding it only worked after I set the mount back to its exact default name ‘Vogel’s MotionMount’ — small tip: the name filter is quite strict right now.

After adding, the app connects (the reconnect error disappeared), and both the turn and extend setpoints follow the sliders correctly. But the mount doesn’t move, and the read-back positions both stay empty (no position updates at all). This applies equally to turning and extending, so it doesn’t look like a preset or direction issue but rather a difference in the GATT characteristics between the 7355 and the 7356.

I’d be happy to help: shall I send an nRF Connect dump of the services/characteristics (UUIDs, with read/write/notify) of my 7356 so you can compare them against your 7355? Let me know which format is most convenient for you."

[Thund3rstone]

So the name filter is something that is not really appropriate for finding motion mounts. Will have to see if there’s a better way. I think I searched for a device that advertised a specific service in an early build of the app. But that probably would also have been restricted to the 7355.

Anyway, I can look at an nrf dump for sure, but don’t know if that will be enough to figure everything out. The way I found the services/characteristics was to compare two dumps after changing the device position, and trying to put values in writable services and see if the mount would change position. If I look at the current nrf connect data on my iPad, it is easy to see the turn and extend position services. App layout seems to have changed, they are the first two services that have read, write and notify. The move is at the Botton of the output, second-to-last with only write.

So maybe it is possible to figure out how to control th 7356 with a dump indeed. I can give that a try.

[Thund3rstone]

First of all, full disclosure: Claude is doing all the coding.
Anyway, I had some issues with Bluetooth becoming stuck on both the mount and the Homey. I have an old Homey Pro. I made some changes to try and make it more robust. Hanging BT is unacceptable. If anyone has any programming tips regarding BT I would appreciate that very much.
There was one crash report, and that should be fixed now. Also, the discovery is done on service UUID, so a renamed mount will be discovered. 7356 UUID will be added as soon as someone gives it to me.
Device polling, to show the correct extend and turn positions in the gui, might be an issue for old Homey’s. In the end, I might simplify the app, remove polling, and just do presets, which might eliminate the BT problems.

Anyway, some improvements in version 0.1.8 now, so if you are testing please update to the latest version. Has been done automatically if you have it on auto update.

[Erbru]

Hi There. I just bought the Vogel’s TVME 5675. Any plans to support this device?

[Thund3rstone]

Hi, cool! I would like to support te device, but I cannot just add it. Different device types have different Bluetooth message IDs, and possibly have a different protocol for BT messaging. I need to at least know the service UUID. And to know if I have the right address for changing the mount’s position, I need to know the address to write to.
This can all be figured out with an app called nRF Connect. You can connect to the mount, tap on the bullet list icon at the top (on iPhone second from left). It will show the advertised services, which should be one entry and I can use that to find the device and connect to it.
Below the connected services, the first two entries in primary service can be used to determine the mounts current turn and extend position. You can tap the downward arrow to get the current value when connected to the mount via BT.
The 33rd entry is a writable entry that can be used to write a new position. On my mount that’s C0005FA21-0651-4800-B000-0000000000000. With nRF Connect you can write a value to that and see if the mount changes position. I would use something close to the current position.If I have that info I can update the app and it may work on the 5675. I’m also waiting for this info from the 7356.

I updated the test app to version 0.2.4 just now. The app is simplified, the polling is removed, you can no longer set the mounts precise precision but only select from the configured presets. I have been testing this for weeks and it seems stable here.

[Erbru]

Thanks for your fast response. I used the nRF Connect app on Android (new to me) and created these two pictures (I removed the address of my device). I was not able to send a message to the device. Probably due to not completely understanding the nRF app.

If you need more information or have a hint on how to send from the nRF app, I can execute and share requested data

[Thund3rstone]

I am not sure what in this screenshot is the advertised service UUID that I can use to detect the mount in a BT scan. It may be the SMP service UUID, but the information on your screenshot differs a lot from mine in the top part.
The characteristics are probably 94fffa00-7129-4446-8057-4a1ab3b2ebc1 and similar.
That would mean that 94fffa210-7129-4446-8057-4a1ab3b2ebc1 should be a write only characteristic. 94fffa0a-7129-4446-8057-4a1ab3b2ebc1 and 94fffa0b-7129-4446-8057-4a1ab3b2ebc1 contain the position and names of the first two presets. Can you give me the names of the two presets from the app, and the contents of the three addresses above? Once connected you may have to tap a download button to actually download the value. I at least need to know if the characteristics are the same and in the same place.

[Erbru]

I managed to get more detailed logging. My two presets are named Preset 1 and Preset 7.

In this list there is no information on 94fffa210-7129-4446-8057-4a1ab3b2ebc1. There is more info on the other s

This is the list:

nRF Connect, 2026-10-25

TV (DC:78:0F:D2:2F:F2)

V 16:33:13.556 Connecting to DC:78:0F:D2:2F:F2…

D 16:33:13.556 gatt = device.connectGatt(autoConnect = false, TRANSPORT_LE, preferred PHY = LE 1M)

D 16:33:13.782 [Broadcast] Action received: android.bluetooth.device.action.ACL_CONNECTED

D 16:33:13.794 [Callback] Connection state changed with status: 0 and new state: CONNECTED (2)

I 16:33:13.794 Connected to DC:78:0F:D2:2F:F2

D 16:33:13.800 wait(1600ms)

D 16:33:14.080 [Broadcast] Action received: android.bluetooth.device.action.ENCRYPTION_CHANGE, encryption: ENABLED, algorithm: AES (16 bytes), transport: TRANSPORT_LE, status: 0

I 16:33:14.451 Connection parameters updated (interval: 30.0ms, latency: 0, timeout: 420ms)

V 16:33:15.401 Discovering services…

D 16:33:15.401 gatt.discoverServices()

D 16:33:15.410 [Callback] Services discovered with status: 0

I 16:33:15.410 Services discovered

V 16:33:15.431 Generic Attribute (0x1801)

- Service Changed [I] (0x2A05)

Client Characteristic Configuration (0x2902)

- Client Supported Features [R W] (0x2B29)

- Database Hash [R] (0x2B2A)

Generic Access (0x1800)

- Device Name [R W] (0x2A00)

- Appearance [R] (0x2A01)

- Peripheral Preferred Connection Parameters [R] (0x2A04)

SMP Service (8d53dc1d-1db7-4cd3-868b-8a527460aa84)

- SMP Characteristic [N WNR] (da2e7828-fbce-4e01-ae9e-261174997c48)

Client Characteristic Configuration (0x2902)

Unknown Service (94ff08d8-7129-4446-8057-4a1ab3b2ebc1)

- Unknown Characteristic [N R SW W] (94fffa00-7129-4446-8057-4a1ab3b2ebc1)

Client Characteristic Configuration (0x2902)

- Unknown Characteristic [N R SW W] (94fffa01-7129-4446-8057-4a1ab3b2ebc1)

Client Characteristic Configuration (0x2902)

- Unknown Characteristic [R SW W] (94fffa02-7129-4446-8057-4a1ab3b2ebc1)

Client Characteristic Configuration (0x2902)

- Unknown Characteristic [N R SW W] (94fffa03-7129-4446-8057-4a1ab3b2ebc1)

Client Characteristic Configuration (0x2902)

- Unknown Characteristic [R SW] (94fffa07-7129-4446-8057-4a1ab3b2ebc1)

Client Characteristic Configuration (0x2902)

- Unknown Characteristic [R SW W] (94fffa0a-7129-4446-8057-4a1ab3b2ebc1)

Client Characteristic Configuration (0x2902)

- Unknown Characteristic [R SW W] (94fffa0b-7129-4446-8057-4a1ab3b2ebc1)

Client Characteristic Configuration (0x2902)

- Unknown Characteristic [R SW W] (94fffa0c-7129-4446-8057-4a1ab3b2ebc1)

Client Characteristic Configuration (0x2902)

- Unknown Characteristic [R SW W] (94fffa0d-7129-4446-8057-4a1ab3b2ebc1)

Client Characteristic Configuration (0x2902)

- Unknown Characteristic [R SW W] (94fffa0e-7129-4446-8057-4a1ab3b2ebc1)

Client Characteristic Configuration (0x2902)

- Unknown Characteristic [R SW W] (94fffa0f-7129-4446-8057-4a1ab3b2ebc1)

Client Characteristic Configuration (0x2902)

- Unknown Characteristic [R SW W] (94fffa10-7129-4446-8057-4a1ab3b2ebc1)

Client Characteristic Configuration (0x2902)

- Unknown Characteristic [R SW W] (94fffa14-7129-4446-8057-4a1ab3b2ebc1)

Client Characteristic Configuration (0x2902)

- Unknown Characteristic [R SW] (94fffa15-7129-4446-8057-4a1ab3b2ebc1)

Client Characteristic Configuration (0x2902)

- Unknown Characteristic [R SW] (94fffa16-7129-4446-8057-4a1ab3b2ebc1)

Client Characteristic Configuration (0x2902)

- Unknown Characteristic [R SW] (94fffa17-7129-4446-8057-4a1ab3b2ebc1)

Client Characteristic Configuration (0x2902)

- Unknown Characteristic [R SW] (94fffa06-7129-4446-8057-4a1ab3b2ebc1)

Client Characteristic Configuration (0x2902)

- Unknown Characteristic [N R SW] (94fffa23-7129-4446-8057-4a1ab3b2ebc1)

Client Characteristic Configuration (0x2902)

- Unknown Characteristic [R SW] (94fffa29-7129-4446-8057-4a1ab3b2ebc1)

Client Characteristic Configuration (0x2902)

- Unknown Characteristic [SW W] (94fffa2a-7129-4446-8057-4a1ab3b2ebc1)

Client Characteristic Configuration (0x2902)

- Unknown Characteristic [R SW W] (94fffa2b-7129-4446-8057-4a1ab3b2ebc1)

Client Characteristic Configuration (0x2902)

- Unknown Characteristic [R SW W] (94fffa37-7129-4446-8057-4a1ab3b2ebc1)

Client Characteristic Configuration (0x2902)

- Unknown Characteristic [N R SW W] (94fffa3a-7129-4446-8057-4a1ab3b2ebc1)

Client Characteristic Configuration (0x2902)

- Unknown Characteristic [R SW W] (94fffa3b-7129-4446-8057-4a1ab3b2ebc1)

Client Characteristic Configuration (0x2902)

- Unknown Characteristic [R SW W] (94fffa3c-7129-4446-8057-4a1ab3b2ebc1)

Client Characteristic Configuration (0x2902)

- Unknown Characteristic [R SW W] (94fffa3d-7129-4446-8057-4a1ab3b2ebc1)

Client Characteristic Configuration (0x2902)

- Unknown Characteristic [R SW W] (94fffa3e-7129-4446-8057-4a1ab3b2ebc1)

Client Characteristic Configuration (0x2902)

- Unknown Characteristic [R SW W] (94fffa3f-7129-4446-8057-4a1ab3b2ebc1)

Client Characteristic Configuration (0x2902)

D 16:33:15.431 gatt.setCharacteristicNotification(00002a05-0000-1000-8000-00805f9b34fb, true)

D 16:33:15.433 gatt.setCharacteristicNotification(94fffa00-7129-4446-8057-4a1ab3b2ebc1, true)

D 16:33:15.434 gatt.setCharacteristicNotification(94fffa01-7129-4446-8057-4a1ab3b2ebc1, true)

D 16:33:15.435 gatt.setCharacteristicNotification(94fffa03-7129-4446-8057-4a1ab3b2ebc1, true)

D 16:33:15.436 gatt.setCharacteristicNotification(94fffa23-7129-4446-8057-4a1ab3b2ebc1, true)

D 16:33:15.437 gatt.setCharacteristicNotification(94fffa3a-7129-4446-8057-4a1ab3b2ebc1, true)

I 16:33:15.542 Notification received from 94fffa01-7129-4446-8057-4a1ab3b2ebc1, value: (0x) 9D-FF

A 16:33:15.542 “(0x) 9D-FF” received

I 16:33:16.532 Notification received from 94fffa01-7129-4446-8057-4a1ab3b2ebc1, value: (0x) 9C-FF

A 16:33:16.532 “(0x) 9C-FF” received

I 16:33:17.553 Notification received from 94fffa01-7129-4446-8057-4a1ab3b2ebc1, value: (0x) 9D-FF

A 16:33:17.553 “(0x) 9D-FF” received

I 16:33:18.543 Notification received from 94fffa01-7129-4446-8057-4a1ab3b2ebc1, value: (0x) 9C-FF

A 16:33:18.543 “(0x) 9C-FF” received

W 16:33:18.754 Connection parameters update failed with status 31 (interval: 0.0ms, latency: 0, timeout: 0ms)

E 16:33:18.754 Error 31 (0x1f): UNKNOWN (31)

I 16:33:19.532 Notification received from 94fffa01-7129-4446-8057-4a1ab3b2ebc1, value: (0x) 9D-FF

A 16:33:19.532 “(0x) 9D-FF” received

I 16:33:20.581 Notification received from 94fffa01-7129-4446-8057-4a1ab3b2ebc1, value: (0x) 9C-FF

A 16:33:20.581 “(0x) 9C-FF” received

I 16:33:21.546 Notification received from 94fffa01-7129-4446-8057-4a1ab3b2ebc1, value: (0x) 9D-FF

A 16:33:21.546 “(0x) 9D-FF” received

I 16:33:22.574 Notification received from 94fffa01-7129-4446-8057-4a1ab3b2ebc1, value: (0x) 9C-FF

A 16:33:22.574 “(0x) 9C-FF” received

I 16:33:23.553 Notification received from 94fffa01-7129-4446-8057-4a1ab3b2ebc1, value: (0x) 9D-FF

A 16:33:23.553 “(0x) 9D-FF” received

I 16:33:24.545 Notification received from 94fffa01-7129-4446-8057-4a1ab3b2ebc1, value: (0x) 9C-FF

A 16:33:24.545 “(0x) 9C-FF” received

V 16:33:25.183 Reading descriptor 00002902-0000-1000-8000-00805f9b34fb

D 16:33:25.183 gatt.readDescriptor(00002902-0000-1000-8000-00805f9b34fb)

I 16:33:25.234 Read Response received from descr. 00002902-0000-1000-8000-00805f9b34fb, value: (0x) 01-00

A 16:33:25.234 “Notifications enabled” received

I 16:33:25.563 Notification received from 94fffa00-7129-4446-8057-4a1ab3b2ebc1, value: (0x) 5F-00

A 16:33:25.563 “(0x) 5F-00” received

I 16:33:25.564 Notification received from 94fffa01-7129-4446-8057-4a1ab3b2ebc1, value: (0x) 9D-FF

A 16:33:25.564 “(0x) 9D-FF” received

I 16:33:26.553 Notification received from 94fffa00-7129-4446-8057-4a1ab3b2ebc1, value: (0x) 5F-00

A 16:33:26.553 “(0x) 5F-00” received

I 16:33:26.554 Notification received from 94fffa01-7129-4446-8057-4a1ab3b2ebc1, value: (0x) 9D-FF

A 16:33:26.554 “(0x) 9D-FF” received

I 16:33:27.552 Notification received from 94fffa01-7129-4446-8057-4a1ab3b2ebc1, value: (0x) 9C-FF

A 16:33:27.552 “(0x) 9C-FF” received

I 16:33:30.572 Notification received from 94fffa01-7129-4446-8057-4a1ab3b2ebc1, value: (0x) 9D-FF

A 16:33:30.572 “(0x) 9D-FF” received

I 16:33:31.563 Notification received from 94fffa01-7129-4446-8057-4a1ab3b2ebc1, value: (0x) 9D-FF

A 16:33:31.563 “(0x) 9D-FF” received

I 16:33:32.553 Notification received from 94fffa01-7129-4446-8057-4a1ab3b2ebc1, value: (0x) 9C-FF

A 16:33:32.553 “(0x) 9C-FF” received

I 16:33:33.574 Notification received from 94fffa01-7129-4446-8057-4a1ab3b2ebc1, value: (0x) 9D-FF

A 16:33:33.574 “(0x) 9D-FF” received

I 16:33:34.566 Notification received from 94fffa01-7129-4446-8057-4a1ab3b2ebc1, value: (0x) 9D-FF

A 16:33:34.566 “(0x) 9D-FF” received

I 16:33:35.552 Notification received from 94fffa01-7129-4446-8057-4a1ab3b2ebc1, value: (0x) 9C-FF

A 16:33:35.552 “(0x) 9C-FF” received

I 16:33:37.564 Notification received from 94fffa00-7129-4446-8057-4a1ab3b2ebc1, value: (0x) 5F-00

A 16:33:37.564 “(0x) 5F-00” received

I 16:33:37.565 Notification received from 94fffa01-7129-4446-8057-4a1ab3b2ebc1, value: (0x) 9D-FF

A 16:33:37.565 “(0x) 9D-FF” received

I 16:33:38.555 Notification received from 94fffa00-7129-4446-8057-4a1ab3b2ebc1, value: (0x) 5F-00

A 16:33:38.555 “(0x) 5F-00” received

I 16:33:38.585 Notification received from 94fffa01-7129-4446-8057-4a1ab3b2ebc1, value: (0x) 9C-FF

A 16:33:38.586 “(0x) 9C-FF” received

I 16:33:39.573 Notification received from 94fffa00-7129-4446-8057-4a1ab3b2ebc1, value: (0x) 5F-00

A 16:33:39.573 “(0x) 5F-00” received

I 16:33:40.564 Notification received from 94fffa01-7129-4446-8057-4a1ab3b2ebc1, value: (0x) 9D-FF

A 16:33:40.564 “(0x) 9D-FF” received

I 16:33:41.555 Notification received from 94fffa01-7129-4446-8057-4a1ab3b2ebc1, value: (0x) 9D-FF

A 16:33:41.555 “(0x) 9D-FF” received

I 16:33:42.579 Notification received from 94fffa01-7129-4446-8057-4a1ab3b2ebc1, value: (0x) 9D-FF

A 16:33:42.579 “(0x) 9D-FF” received

I 16:33:43.566 Notification received from 94fffa01-7129-4446-8057-4a1ab3b2ebc1, value: (0x) 9D-FF

A 16:33:43.566 “(0x) 9D-FF” received

I 16:33:44.586 Notification received from 94fffa00-7129-4446-8057-4a1ab3b2ebc1, value: (0x) 5F-00

A 16:33:44.586 “(0x) 5F-00” received

I 16:33:44.587 Notification received from 94fffa01-7129-4446-8057-4a1ab3b2ebc1, value: (0x) 9C-FF

A 16:33:44.587 “(0x) 9C-FF” received

I 16:33:45.574 Notification received from 94fffa00-7129-4446-8057-4a1ab3b2ebc1, value: (0x) 5F-00

A 16:33:45.574 “(0x) 5F-00” received

I 16:33:45.575 Notification received from 94fffa01-7129-4446-8057-4a1ab3b2ebc1, value: (0x) 9D-FF

A 16:33:45.575 “(0x) 9D-FF” received

I 16:33:46.574 Notification received from 94fffa01-7129-4446-8057-4a1ab3b2ebc1, value: (0x) 9C-FF

A 16:33:46.574 “(0x) 9C-FF” received

I 16:33:47.591 Notification received from 94fffa01-7129-4446-8057-4a1ab3b2ebc1, value: (0x) 9D-FF

A 16:33:47.591 “(0x) 9D-FF” received

I 16:33:48.583 Notification received from 94fffa01-7129-4446-8057-4a1ab3b2ebc1, value: (0x) 9C-FF

A 16:33:48.583 “(0x) 9C-FF” received

I 16:33:49.570 Notification received from 94fffa01-7129-4446-8057-4a1ab3b2ebc1, value: (0x) 9D-FF

A 16:33:49.570 “(0x) 9D-FF” received

I 16:33:50.584 Notification received from 94fffa01-7129-4446-8057-4a1ab3b2ebc1, value: (0x) 9C-FF

A 16:33:50.584 “(0x) 9C-FF” received

I 16:33:52.568 Notification received from 94fffa00-7129-4446-8057-4a1ab3b2ebc1, value: (0x) 5F-00

A 16:33:52.568 “(0x) 5F-00” received

I 16:33:53.590 Notification received from 94fffa00-7129-4446-8057-4a1ab3b2ebc1, value: (0x) 5F-00

A 16:33:53.590 “(0x) 5F-00” received

I 16:33:53.591 Notification received from 94fffa01-7129-4446-8057-4a1ab3b2ebc1, value: (0x) 9D-FF

A 16:33:53.591 “(0x) 9D-FF” received

I 16:33:54.583 Notification received from 94fffa01-7129-4446-8057-4a1ab3b2ebc1, value: (0x) 9C-FF

A 16:33:54.583 “(0x) 9C-FF” received

I 16:33:58.594 Notification received from 94fffa01-7129-4446-8057-4a1ab3b2ebc1, value: (0x) 9D-FF

A 16:33:58.594 “(0x) 9D-FF” received

D 16:33:58.834 [Broadcast] Action received: android.bluetooth.device.action.ACL_DISCONNECTED

I 16:33:58.834 Disconnected

D 16:33:58.853 [Callback] Connection state changed with status: 19 and new state: DISCONNECTED (0)

W 16:33:58.853 Connection terminated by peer (status 19)

[Erbru]

Nog wat extra info na analyse van de BTSNOOP_HCI.log file vanuit Android

[Thund3rstone]

@Erbru

TVME 5675

Hm. This is more difficult than I thought. The log you have doesn’t provide much interesting data. I see characteristics but not contents, and I wonder if the list of characteristics is complete. The 94fffa21-7129-4446-8057-4a1ab3b2ebc1 (note there was a typo in my previous post, so this one is the move characteristic that I expect) is not in the list, so just supporting different service and characteristics UUIDs is not going to work.

Can you connect to the device and in the same screen as you made the screenshots of, scroll down and see of you have 94fffa21-7129-4446-8057-4a1ab3b2ebc1? Are there buttons you can tap next to characteristics to get the current value if you are connected?

Also, that address that you hid in the screenshot, is that an IP address? Do you have network connectivity?

[Erbru]

Today I had time to play more with the nRF Connect app. After reading and using AI I am now able to use the nRF app to change the position of the device. I noted that 02-00 hex is the home position (flat to the wall) and 5E-00 is the largest angle of the device. During the movement I see the first byte changing. The second byte is always 00. Attached are the two screenshots taken for both positions.

Hope this helps