Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Only one awning detected in system with two awnings installed... #14

Open
Aaroneisele55 opened this issue Jun 15, 2024 · 0 comments
Open

Comments

@Aaroneisele55
Copy link

Hello,
I have two identical Warema awnings, and I would like to control them using this add-on in HA.
One awning gets detected and works as it should, but it doesn't detect the second one.
They are on the same location just near each other, so RF range isn't the problem.
I am using the forked version of the add-on, but in its Github repo I can't create an Issue, so I'm trying it here...
My logs are

-----------------------------------------------------------
 Add-on: Warema Bridge
 Control your Warema WMS system
-----------------------------------------------------------
 Add-on version: dev
 You are running the latest version of this add-on.
 System: Home Assistant OS 12.3  (aarch64 / raspberrypi4-64)
 Home Assistant Core: 2024.6.2
 Home Assistant Supervisor: 2024.06.0
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing... 
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[07:19:54] INFO: Starting the Warema bridge...
[07:19:54] INFO: Setting WMS_KEY to 4724B11B56AF0037082D583AC24C7CB4
[07:19:54] INFO: Setting WMS_PAN_ID to 09E5
[07:19:55] INFO: Setting WMS_CHANNEL to 17
[07:19:55] INFO: Setting WMS_SERIAL_PORT to /dev/ttyUSB1
[07:19:55] INFO: MQTT available, fetching server detail ...
[07:19:55] INFO: MQTT server settings not configured, attempting auto-discovery...
[07:19:56] INFO: Configuring 'mqtt://core-mosquitto:1883' mqtt server
[07:19:56] INFO: MQTT credentials not configured, attempting auto-discovery...
[07:19:57] INFO: Configuring 'addons' mqtt user
Connected to MQTT
Warema init completed
Scanning...
15 07:19:59.010 I Interval for position update: 30 seconds.
15 07:19:59.090 I /dev/ttyUSB1 Scanned device: EEBB01 Type 20 Actuator UP      
15 07:19:59.121 I /dev/ttyUSB1 Scanned device: 84E001 Type 63 Web control      
15 07:19:59.185 I /dev/ttyUSB1 Scanned device: EEBB01 Type 20 Actuator UP      
15 07:19:59.203 I /dev/ttyUSB1 Scanned device: 84E001 Type 63 Web control      
15 07:19:59.297 I /dev/ttyUSB1 Scanned device: EEBB01 Type 20 Actuator UP      
15 07:19:59.382 I /dev/ttyUSB1 Scanned device: 84E001 Type 63 Web control      
15 07:19:59.771 I wmsTimeout 750 scanRequest 000000 "{R04FFFFFF702009E502}".
15 07:19:59.840 I /dev/ttyUSB1 Scanned device: 84E001 Type 63 Web control      
15 07:19:59.871 I /dev/ttyUSB1 Scanned device: EEBB01 Type 20 Actuator UP      
15 07:19:59.946 I /dev/ttyUSB1 Scanned device: EEBB01 Type 20 Actuator UP      
15 07:19:59.947 I /dev/ttyUSB1 Scanned device: 84E001 Type 63 Web control      
15 07:20:00.055 I /dev/ttyUSB1 Scanned device: EEBB01 Type 20 Actuator UP      
15 07:20:00.103 I /dev/ttyUSB1 Scanned device: 84E001 Type 63 Web control      
15 07:20:00.534 I wmsTimeout 750 scanRequest 000000 "{R04FFFFFF702009E502}".
15 07:20:00.614 I /dev/ttyUSB1 Scanned device: EEBB01 Type 20 Actuator UP      
15 07:20:00.663 I /dev/ttyUSB1 Scanned device: 84E001 Type 63 Web control      
15 07:20:00.743 I /dev/ttyUSB1 Scanned device: EEBB01 Type 20 Actuator UP      
15 07:20:00.758 I /dev/ttyUSB1 Scanned device: 84E001 Type 63 Web control      
15 07:20:00.830 I /dev/ttyUSB1 Scanned device: EEBB01 Type 20 Actuator UP      
15 07:20:00.910 I /dev/ttyUSB1 Scanned device: 84E001 Type 63 Web control      
15 07:20:01.296 I wmsTimeout 750 scanRequest 000000 "{R04FFFFFF702009E502}".
Scanned devices.
Registering 113646
Adding device 113646 (type 20)
Registering 123012
Unrecognized device type: 63
[ { snr: 113646, snrHex: 'EEBB01', name: '113646' } ]

I assume that the device id 123012 is either my second awning or my remote control ("Handsender comfort"), but I hope that I can get the add-on to discover both awnings...

Best regards
Aaron

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant