Flo-Schilli / homeassistant-grohe_sense

Grohe Sense integration for Home Assistant
Other
6 stars 2 forks source link

[FIXED] Grohe Blue Home issue [Grohe Sense: No devices or entities] #18

Closed daxyorg closed 1 day ago

daxyorg commented 5 days ago

Hi,

After I selected the component (Grohe sense) and entered my credentials (username/password), I received only this message

Screenshot 2024-09-13 at 20 49 13

And after restarting the integration I don't see any sensors or Guard:

Screenshot 2024-09-13 at 20 52 34

I checked several times: I add correctly my credentials. Is it possible to add manual my credentials or token in config file? Thanks a lot in advance for this repo and help!

Flo-Schilli commented 4 days ago

Hi,

in general you directly should see your devices and be able to assign an area where they are located in. Do you get some errors from the intrgration in the log? In the Grohe app the Grohe Sense is already assigned a location and room, right? If you don't get any errors/warnings in the log, it would be really helpful to have the debug output of the integration.

Thanks in advance.

daxyorg commented 4 days ago

Hi,

I really appreciate and thank you for the quick response! I don't received any error messages in logs. But when I activated the debugging mode, deleted and added again new integration, I received this messages:

Screenshot 2024-09-13 at 23 08 58

Logger: homeassistant.components.valve Source: helpers/entity_platform.py:361 integration: Valve (documentation, issues) First occurred: 11:06:42 PM (1 occurrences) Last logged: 11:06:42 PM

Error while setting up grohe_sense platform for valve Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 361, in _async_setup_platform await asyncio.shield(awaitable) File "/config/custom_components/grohe_sense/valve.py", line 23, in async_setup_entry for device in filter(lambda d: d.type == GroheTypes.GROHE_SENSE_GUARD, devices): File "/config/custom_components/grohe_sense/valve.py", line 23, in for device in filter(lambda d: d.type == GroheTypes.GROHE_SENSE_GUARD, devices): ^^^^^^ File "/config/custom_components/grohe_sense/dto/grohe_device.py", line 43, in type return GroheTypes(self.appliance.type) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/enum.py", line 757, in call return cls.new(cls, value) ^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/enum.py", line 1171, in new raise ve_exc ValueError: 104 is not a valid GroheTypes

I have a location and rooms

Flo-Schilli commented 4 days ago

Thanks for the quick reply.

Do you also have a Grohe Blue Home? Seems like the integration is getting the information of a Grohe Type 104 which is causing it to fail. If it's like that, can you verify that the blue home is having the same sensor values like the blue professional? Or what is not available in the blue home. If it's similar, I can add the blue home with the same sensors like the blue professional and upload it to the dev branch within the next few days.

daxyorg commented 4 days ago

Ok, yes. Sorry I didn't mention. I have Grohe Blue Home. Blue Home and professional are almost the same. Professional has an option for big bottle CO2. Update: Now everything is OK. I added in ondus_types.py Grohe Blue Home with type 104. May be there are some additional editions in other files, but now I see this:

Screenshot 2024-09-13 at 23 46 19 Screenshot 2024-09-13 at 23 48 33
Flo-Schilli commented 4 days ago

That's great that you're seeing the other ones right now already after adding the 104 👍 I'm gonna enhance the other files for the blue. Would you mind testing it afterwards, as I'm not having a Grohe Blue Home.

daxyorg commented 4 days ago

Yes, of course. With pleasure I will test.

Flo-Schilli commented 4 days ago

On develop branch I just fully added the Blue Home with the same settings like the Blue Professional. It could be that it's returning you an error. If it is, can you please post the values from within the debug log after Got the following details for Grohe Blue appliance and without the appliance ID.

daxyorg commented 4 days ago

I sent the log in develop.

Flo-Schilli commented 4 days ago

Thanks for the log. It is really strange that it is saying that the Grohe Blue Home is not within the Enum but in develop it is. That's the reason why you're getting the unknown on all other sensor values. Can you please check that the enum is having the 104 in the ondus_types.py.

daxyorg commented 4 days ago

Thanks for the log. It is really strange that it is saying that the Grohe Blue Home is not within the Enum but in develop it is. That's the reason why you're getting the unknown on all other sensor values. Can you please check that the enum is having the 104 in the ondus_types.py.

After 10-15 minutes data was extracted:

Screenshot 2024-09-14 at 9 25 28

Now I just need to figure out how to visualize the data from Grohe Blue Home.

Flo-Schilli commented 4 days ago

And are you seeing the blue home as well listed as a device within the intrgration?

daxyorg commented 4 days ago

And are you seeing the blue home as well listed as a device within the intrgration?

Not yet. Just Guard and sensors.

Error log: 2024-09-14 01:57:47.363 WARNING (MainThread) [custom_components.xxxxx.sensor] Unrecognized appliance <custom_components.grohe_sense.dto.grohe_device.GroheDevice object at 0x7f63f4d0e0>, ignoring.

Flo-Schilli commented 4 days ago

In general it should be there once the integration is running okay. Are there any other errors in the Log. Is still the 104 error active even with the latest commit from develop?

daxyorg commented 4 days ago

In general it should be there once the integration is running okay. Are there any other errors in the Log. Is still the 104 error active even with the latest commit from develop?

I reinstall a repo and edited the 4 files after that I sign-in and visualise a guard and sensors, in logs there are no errors, only these warnings:

2024-09-14 10:01:00.475 WARNING (MainThread) [custom_components.xxxxx.sensor] Unrecognized appliance <custom_components.grohe_sense.dto.grohe_device.GroheDevice object at 0x7f54XXXX30>, ignoring. 2024-09-14 10:01:00.706 WARNING (MainThread) [custom_components.grohe_sense.api.ondus_api] URL https://idp2-apigw.cloud.grohe.com/v3/iot/locations/XXXXXXX/rooms/XXXXXX/appliances/xxxxxxx-a55d-xxxx-xxxx-xxxxxxxxxx/data/aggregated?from=2024-09-14 returned status code 405

Maybe this status code 405 means something?

Flo-Schilli commented 4 days ago

Can you please activate the debug logging for the integration, there should then be more information available within the logs. Can you also please verify that the appliance for which you're gettting the 405 is the Grohe Blue Home or if it is another device. In the debug log you should see Got the following details for Grohe Blue appliance somewhen after starting the integration, that output would be interesting for me. Also right after the start of the integration you should see a message similar to this: Found in location XXXXXXX and room XXXXXXX the following appliance: XXXXXXX from type 103 with name SenseGuard which will provide you the information to check in the URL for the aggregated data if it's the Grohe Blue Home or not. Are you checking out the repository and moving the files manually to HA or are you using HACS? Please also use the latest develop branch as I just formated the debug log to match with this comment

daxyorg commented 2 days ago

Hello,

Sorry for the delay. What I did: copy and paste new grohe_sense with debug mode. The log is with 3435 rows. Please, let me know where can I find "Got the following details for Grohe Blue appliance", because in my HA Yellow, I know only for these logs:

Screenshot 2024-09-16 at 9 41 13

And there is no info about it. In log also cannot find info about location nr or rooms.

Thanks in advance!

Flo-Schilli commented 2 days ago

Hi,

after you have changed the log level to debug you should be able to see (and probably have to scroll a little bit) it under Settings -> System -> Logs and click there on 'Load Full Logs'. Best would be, before doing this - and for you to search less - restart the home assistant before. Quite at the beginning - after all integrations loaded successfully - you should see it and should also be able to search for the above mentioned value within the logs

daxyorg commented 1 day ago

Hi,

What I did: fully pre-installed HA Yellow, then just added the folder grohe_sense (developer) in custom_components. I think the case is closed, because now I see the info below. I don't get any errors anymore (the debug log is activated). If you think I can be useful with other tests, please write.

Screenshot 2024-09-17 at 13 46 06
Flo-Schilli commented 1 day ago

Thats great that it is working now 👍 also pushed to Main already 😊 thanks for the feedback