Feedback V2.0.0b

[dmamontov]

Feedback V2.0.0b

[dmamontov]

@FaserF I copied the logs for myself, I understand.

[dmamontov]

@FaserF https://github.com/dmamontov/hass-miwifi/releases/tag/v2.0.1b

[dmamontov]

1. Unfortunately the only option is to use only mac, they are unique. In previous versions, there was a bug that I myself encountered, this is when the names of the devices intersect, or when I want to rename it to MiWifi

2. Do you need 2 minutes with the debug mode enabled. Everything works. You can send them to telegram.

3. Not all routers have a temperature sensor (I only have one. But the api does not reflect this, but simply returns 0.

4. I think the logs from point 2 will also help (only with the addition of 2 integrations). Everything is fine with me, though I have different routers. Sensors should not be transferred, poppies are different.

And a screenshot of the settings, if possible, for both)

[FaserF]

Thanks for the fast feedback.
How can I enable debug mode?

Device 1 settings:

Only containing device_tracker entities, no entities to control the miwifi device itself:

(those two options come from my fritzbox router, but I am missing the options for the device itself)

Device 2 settings:

There are all the controls from the first miwifi router (the mac adress also is from the first router, but its settings are under the second integration. And I am missing the controls for the second integration:

Strangly the device info is correct from the second device, but all switches, sensors etc are from the first device integration

I think I have found something that could produce the issue:

Logger: homeassistant.components.switch
Source: helpers/entity_platform.py:593
Integration: Switch (documentation, issues)
First occurred: 08:14:17 (7 occurrences)
Last logged: 09:04:59

Platform miwifi does not generate unique IDs. ID None-wifi_2_4 is already used by switch.miwifi_28_d1_27_fc_ab_d8_wifi_2_4g - ignoring switch.miwifi_9c_9d_7e_30_89_fb_wifi_2_4g
Platform miwifi does not generate unique IDs. ID None-wifi_5_0 is already used by switch.miwifi_28_d1_27_fc_ab_d8_wifi_5g - ignoring switch.miwifi_9c_9d_7e_30_89_fb_wifi_5g

Logger: homeassistant.components.sensor
Source: helpers/entity_platform.py:593
Integration: Sensor (documentation, issues)
First occurred: 08:14:17 (19 occurrences)
Last logged: 09:04:59

Platform miwifi does not generate unique IDs. ID None-devices_2_4 is already used by sensor.miwifi_28_d1_27_fc_ab_d8_devices_2_4g - ignoring sensor.miwifi_28_d1_27_fc_ab_d8_devices_2_4g
Platform miwifi does not generate unique IDs. ID None-devices_5_0 is already used by sensor.miwifi_28_d1_27_fc_ab_d8_devices_5g - ignoring sensor.miwifi_28_d1_27_fc_ab_d8_devices_5g
Platform miwifi does not generate unique IDs. ID None-temperature is already used by sensor.miwifi_28_d1_27_fc_ab_d8_temperature - ignoring sensor.miwifi_9c_9d_7e_30_89_fb_temperature
Platform miwifi does not generate unique IDs. ID None-devices is already used by sensor.miwifi_28_d1_27_fc_ab_d8_devices - ignoring sensor.miwifi_9c_9d_7e_30_89_fb_devices
Platform miwifi does not generate unique IDs. ID None-mode is already used by sensor.miwifi_28_d1_27_fc_ab_d8_mode - ignoring sensor.miwifi_9c_9d_7e_30_89_fb_mode

Logger: homeassistant.components.device_tracker
Source: helpers/entity_platform.py:593
Integration: Device tracker (documentation, issues)
First occurred: 08:29:10 (5 occurrences)
Last logged: 08:54:04

Platform miwifi does not generate unique IDs. ID miwifi-DC:68:EB:06:27:4E is already used by device_tracker.miwifi_dc_68_eb_06_27_4e - ignoring device_tracker.miwifi_dc_68_eb_06_27_4e
Platform miwifi does not generate unique IDs. ID miwifi-34:51:80:D0:44:29 is already used by device_tracker.miwifi_34_51_80_d0_44_29 - ignoring device_tracker.miwifi_34_51_80_d0_44_29
Platform miwifi does not generate unique IDs. ID miwifi-F8:4F:AD:4F:82:72 is already used by device_tracker.miwifi_f8_4f_ad_4f_82_72 - ignoring device_tracker.miwifi_f8_4f_ad_4f_82_72

[FaserF]

Log about point 2:

This error originated from a custom integration.

Logger: custom_components.miwifi.updater
Source: custom_components/miwifi/updater.py:697
Integration: MiWifi (documentation, issues)
First occurred: 08:23:27 (73 occurrences)
Last logged: 09:27:55

Unexpected error fetching MiWifi updater data: 'last_activity'
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 187, in _async_refresh
self.data = await self._async_update_data()
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 147, in _async_update_data
return await self.update_method()
File "/config/custom_components/miwifi/updater.py", line 238, in update
self._clean_devices()
File "/config/custom_components/miwifi/updater.py", line 697, in _clean_devices
device[ATTR_TRACKER_LAST_ACTIVITY], "%Y-%m-%dT%H:%M:%S"
KeyError: 'last_activity'

[dmamontov]

logger:
  default: error
  logs:
    custom_components.miwifi: debug

Add a parameter and restart, there will be many times more logs. I found one mistake and corrected it.

[dmamontov]

What version of hass? Have you removed any integrations before?

[FaserF]

Home Assistant Core version 2022.3.8 (latest)
Homeassistant OS version: 7.6 (latest)

I have removed all miwifi integrations before updating.
I will send you the new logs from the debug mode once they are ready, I am now restating hass

[FaserF]

Thank you for the quick fix! Seems to be working now 👍🏼 🥇