Integrations unavailable

Hello Team…

Did I make the right choice?

I just noticed that the TUYA integration was in error and I just discovered that you have to renew the APIs (what the sea lion ???) the problem is that it doesn’t work. So I wanted to delete my project but impossible without deleting my house on Gladys (it’s not a big deal I’m in test mode) Will I have to do this every month? (damn I talk too much… I’m going to take a Doliprane).

The problem comes from me…or rather from my generation…command lines etc…no thanks (I’m part of the generation of yogurt jars with string!!!)

Node-RED …tough tough

ChatGPT misled me more than once (it’s okay I don’t go mushroom picking)

for example …

Hi @Fabrice and welcome!

Ooooooh a fan of Les Inconnus :star_struck: I love it :rofl:

I don’t know if I’ll be able to help you because you’re using almost everything I don’t have :grimacing:

For Tuya, you’ll need @pierre-gilles to reply, I don’t know it well because I avoid using the cloud and therefore that integration.
However I didn’t understand:

I therefore wanted to delete my project but it’s impossible without deleting my home on Gladys

What do you mean by « project »?

For your Daewoo alarm, if it connects to your Lidl gateway, I imagine you control it with the Lidl Home app (or HA?). By the way, what’s the exact model?
Then for the integration into Gladys, there are two things to look at in my opinion:

  • is your alarm supported by zigbee2mqtt ? (it’s what Gladys uses to communicate over zigbee with devices)
  • if yes, you might need an adjustment in Gladys at the code level (by the devs) to get it.

Finally, it’s possible to have both systems in parallel, that’s what I do when I can’t find a simple solution in Gladys or if a very specific integration doesn’t exist (yet).
There is node-red but I admit I avoid using it too much because I don’t understand much about payloads, messages to process and send back to Gladys (via MQTT).
I pass everything through MQTT: HA retrieves the values I’m missing and publishes them to MQTT, Gladys retrieves these values which I can then display on one of the dashboards. It’s also possible for commands.

Hi mutmut

Actually, for the Tuya integration, I had to create an account AND a project on iot.tuya.com. The APIs (quickly) expired and it was impossible to reactivate them. I thought no big deal, I would delete them to start fresh BUT to reset my plugs I had to erase my project… impossible without deleting my home on Gladys.

So I’m starting from zero but nothing serious, I’m in discovery mode with a view to changing home.

However, with the Tuya app on my phone there’s no problem.

For my DAEWOO alarm, it manages to see my Zigbee gateway but the communication is one-way (Vigilia alarm).

Gladys is installed on a mini PC used only for that. Gladys does « see » the gateway but doesn’t support it. I would have liked to use the Lidl gateway as a bridge between my alarm and Gladys.

So on my phone I have the Daewoo, Tuya, and Shelly apps and I can’t get everything consolidated on Gladys

And if instead of reactivating or deleting this project, you create another one and so you’ll have another token that you can put in Gladys, would that work?
That doesn’t solve the rapid expiration problem but it prevents you from having to start from scratch each time.
Another piece of information I just found: there would be a trial version for Tuya and if it stops, it’s possible to extend it: Configuration de l'intégration Tuya - #7 par Francis66
It’s also stated in the docs of the Tuya integration.

Is that the one? Système d'alarme Vigilia – Daewoo Security
Because there is only Wi‑Fi or Wi‑Fi+4G, no mention of Zigbee :thinking:
Here it talks about Zigbee but only for the Touch (AM301 / AM302), not the Vigilia.
On the Daewoo Security site, the Elite has Zigbee built-in.

For Shelly, which communication protocol do you have: BT (Bluetooth), Zigbee, Matter, Wi‑Fi?
We can now manage Shelly devices thanks to the Matterbridge platform and the Shelly plugin which allows routing all your Shelly devices through Matter.

The LIDL box is normally Tuya so if the Tuya integration works on Gladys :crossed_fingers:, you should be able to retrieve your already paired devices.

EDIT: maybe you can enable only the zigbee2mqqt integration in Gladys and integrate Tuya directly into zigbee2mqtt. It looks a bit tricky but if it works better, why not.

Hello,

This weekend I started learning how to use MQTT (for my BOSE speaker). I created features (play, pause, etc…). Then with MQTTX I made the topics…

On my dashboard I can see my box.

The question is: what is the procedure for providing the speaker’s IP address?

I saw that BO

Hello,

There isn’t really a place to enter your speaker’s IP address.

What you need to do is connect the speaker to the MQTT broker. I can’t tell you exactly how to do it since I don’t have a speaker.

An AI search:

Since Bose speakers do not include a native MQTT client, 
the solution is to create a bridge. 
This bridge will listen to messages on your MQTT broker and translate them into 
HTTP (REST) or WebSockets requests understandable by the speaker.

You could possibly use Node-RED and install the node node-red-contrib-bose-soundtouch

Alternatively, the AI gives the following example:

Example structure of an API (REST) request

The Bose API listens on port 8090. You can test directly with a curl from your broker:

  • To raise the volume:
curl -X POST -d '\u003cvolume\u003e30\u003c/volume\u003e' http://[IP_DE_L_ENCEINTE]:8090/volume
  • To simulate pressing a button (e.g., Preset 1):
curl -X POST -d '\u003ckey state="press" sender="GAVS"\u003ePRESET_1\u003c/key\u003e' http://[IP_DE_L_ENCEINTE]:8090/key
1 Like

I don’t know if you saw this article about the Bose SoundTouch: Bose libère l'API de ses enceintes SoundTouch avant leur fin de vie | Posts | Le site de Korben
Is your speaker affected?
For info, here are the APIs documented by Bose: https://assets.bosecreative.com/m/496577402d128874/original/SoundTouch-Web-API.pdf

However, if you want to test some functions that @_Will_71 mentioned above, here is a quick tutorial via Gladys (not tested because I don’t have a Bose speaker), without having to go through a terminal or something even geekier.

Get information from your Bose:

  • create a scene in Gladys
  • create an action of type Make an HTTP request
  • choose the GET method
  • put in URL: http://ip-de-la-bose:8090/info
  • click Try
    If you get a response then it works, otherwise it will show a red message and you will need to adjust a few things.

Get the volume of your Bose:

Change the volume of your Bose:


For the body, I’m not sure about it — it needs to be tested in real life.

1 Like

Thank you for the help you’re giving me.

I’ll look at it this weekend because this week my schedule doesn’t line up with my free time.

THANK YOU!!!

Hello to you…

Well, there you go… nothing works… and as I suspected, I’m throwing in the towel.

Here are the difficulties I encountered (this is my point of view)

Integrations that no longer work (e.g., Bluetooth not available)

Tuya is in trial mode and needs to be renewed

Scenes are too complicated to create

Too many steps, e.g., to create the weather box and the same for the Tuya integration

Having knowledge of different programming languages (not enough free time to seriously learn… work obligations)

Thank you for trying to help me

Fabrice

Hi!

I’m sorry to see you’re throwing in the towel, but what’s great is the feedback you took the time to give here, which may avoid these points of friction in the future!

It’s always difficult to switch from one system to another, depending on the hardware you have.

Personally, I immediately chose to use devices compatible with zigbee2mqtt and to avoid cloud services (Tuya etc.) as much as possible. But when you already have gear you have no desire to change everything!