Groove Vision AI V2 - I can't get Homeassistant to work

djairjr · May 11, 2024, 4:27pm

In step 11 of the wiki - Connecting to Home Assistant | Seeed Studio Wiki, I can’t get Groove Vision AI V2 to be found by Homeassistant. Looking at the EMQX Logs, I notice that the board connects with MQTT. But in step by step, I can’t make the connection. Timeout error occurs.

The system does not automatically find my device, and manual configuration is required. In this case, when filling out the SETUP MQTT SERVER form with my server information, I cannot connect through setup.

MQTT connection timeout

EMQX - Connection Info

Session Info

djairjr · June 11, 2024, 7:23pm

Same issue. Used the mqtt2uart example and get wifi and mqtt connected. EQMX detects the board, but the alleged integration not… Exactly one month, and this still not working and there is no support.

Seeed_Seraphina · June 12, 2024, 10:07am

I’m sorry I’m late. I will test it for your situation. We apologize for the inconvenience. We’ll be sure to contact you here as soon as we have the results.

djairjr · June 24, 2024, 3:53pm

Another hint is, when SenseCraft extension try to integrate my Groove Vision AI V2, the name header start with grove_vision_ai_we2_uniqueid and not grove_vision_ai_v2_uniqueid.

djairjr · July 12, 2024, 7:52pm

If you arrived at this topic after trying unsuccessfully to configure your Groove Vision Ai V2 to work with Home Assistant, first take a look at the date of previous messages and the response time between them.

PJ_Glasso · July 14, 2024, 3:26am

Hi there,
Sounds like an Island… LOL, I’m about to embark on the same journey, HA with Gove Vision Ai V2 and a coral AI M2 e-key version all in an Intel NUC as host machine. It’s an I5 so plenty of juice for the squeeze also some IP cameras too. I anticipate some hurdles.
GL PJ

djairjr · July 17, 2024, 2:40pm

In file strings.json, the name of the board is typed wrong.
grove_vision_ai_we2 instead of grove_vision_ai_v2

Proposed correction, but I will try it mannualy sometime.

github.com

Seeed-Solution/SenseCraft-HomeAssistant/blob/main/custom_components/sensecraft/strings.json

{
  "config": {
    "flow_title": "{name}",
    "abort": {
      "mdns_missing_mac": "Missing MAC address in MDNS properties.",
      "mdns_missing_host": "Missing Host in MDNS properties.",
      "mdns_missing_port": "Missing Port in MDNS properties.",
      "mdns_missing_mqtt": "Missing Mqtt in MDNS properties."
    },
    "error": {
      "invalid_auth": "Login failed",
      "no_apikey": "NO API key",
      "setup_error": "Setup failed",
      "mqtt_connect_timeout": "MQTT connection timeout",
      "mqtt_connect_error": "MQTT connection error",
      "mqtt_connect_except": "MQTT connection exception"
    },
    "step": {
      "user": {
        "title": "SenseCraft",

This file has been truncated. show original

djairjr · August 4, 2024, 12:54pm

I’ve already upgraded to the current version, which adds Watcher support. But it still doesn’t work with my boards here. I attached the screens so you can see the inconsistency. The board is connected to wifi, to the MQTT server, it receives messages, but the SenseCraft integration does not detect it.

My suspicion was the inconsistency in the customer names, but after testing, the problem persists. I also analyzed the source code of the AT firmware for ESP32 and did not find anything in it that would cause this problem.

djairjr · August 4, 2024, 1:03pm

Are you still here? I keep trying to get the Home Assistant integration to work, but it doesn’t. I saw that you updated to support the future Watcher, but it still doesn’t work on Grove Vision AI V2 and it’s possible that the problem with this integration will continue like this.

Something is wrong. Either the tutorial has a missing step, or the integration does not work as advertised.

PJ_Glasso · August 4, 2024, 7:20pm

or cliffs…
HA is a moving target anyway , looks like this will make it even more elusive. I can only wish they slow down and clean up what they have, well I can hope anyway. They need like 10 more engineers IMO.

Citric · August 6, 2024, 11:21am

Just to confirm, which device’s IP address is 192.168.15.29?

djairjr · August 6, 2024, 5:42pm

This address is for my HomeAssistant server, an Orange Pi 3 LTS.