Hi. I have been testing v1.4.25, but I can not see any change in behavior. I still have the duplicated log entries (norwegian and english) and both my garage doors sooner or later ends up with a door open state in Homey. I am 100% sure there is no change of door state in HA. Physical doors are closed.
Hm, strange.
I don’t know if I aksed already… is it a HP19 or HP23?
Did you already check the app log for connect errors?
And please send me a diagnostic report. Perhaps I can see something there…Thanks.
Yes, indeed strange. Are you sure the changes you made for 1.4.25 is really in there? I could not see any changes at all since 1.4.24.
I have HP19.
I checked the log and found no errors at all.
I will restart the app. in Homey. Both doors will then get the right status in Homey (both tile and door closed switch).
After a while they will change status to open in Homey. I asume that this will be the time to send diagnostics report. Right?
Yes. I wonder what’s happening in background.
Just sent you c1c98df3-50eb-4d91-bf15-e17a13e8ff70.
Hey, found the reason for duplicated entries… Used the wrong value for insights parameter (true instead of false) 
New test version 1.4.26 should show only one timeline entry.
You restarted the app first? Then the log only contains new entries since the start.
Can you keep an eye on this behaviour and send a log again after the wrong state appears again?
You can also check the app log by yourself from time to time in repair view:
If there are errors, you can send a diagnostic log.
It did happend for both doors within a minute after restart. After that I sent you the diagnostics.
Here’s the log since the app restart:
[log] 2023-09-22 16:46:1 [APP] Prepare COVER devices list.
[log] 2023-09-22 16:45:59 [Driver:cover] onRepair()
[log] 2023-09-22 16:40:53 [APP] updateLight: true {"entity_id":"light.taklys","brightness":145.35}
[log] 2023-09-22 16:38:40 [APP] updateLight: true {"entity_id":"light.taklys_3","brightness":155.54999999999998}
[log] 2023-09-22 16:38:39 [APP] updateLight: true {"entity_id":"light.taklys_3","brightness":28.05}
[log] 2023-09-22 16:34:19 [APP] Connection check: OK.
[log] 2023-09-22 16:34:8 [APP] updateLight: true {"entity_id":"light.taklys_3","brightness":0}
[log] 2023-09-22 16:34:7 [APP] updateLight: true {"entity_id":"light.taklys_3","brightness":0}
[log] 2023-09-22 16:33:37 [APP] updateLight: true {"entity_id":"light.taklys_3","brightness":28.05}
[log] 2023-09-22 16:31:54 [APP] updateLight: true {"entity_id":"light.taklys","brightness":0}
[log] 2023-09-22 16:31:24 [APP] updateLight: true {"entity_id":"light.taklys","brightness":17.85}
[log] 2023-09-22 16:30:0 [APP] updateLight: true {"entity_id":"light.taklys_2","brightness":25.5}
[log] 2023-09-22 16:19:19 [APP] Connection check: OK.
[log] 2023-09-22 16:17:33 [APP] updateLight: true {"entity_id":"light.taklys_3","brightness":155.54999999999998}
[log] 2023-09-22 16:17:32 [APP] updateLight: true {"entity_id":"light.taklys_3","brightness":28.05}
[log] 2023-09-22 16:16:50 [APP] updateLight: true {"entity_id":"light.taklys","brightness":145.35}
[log] 2023-09-22 16:16:35 [APP] updateLight: false {"entity_id":"light.skaplys_kontor"}
[log] 2023-09-22 16:04:31 [APP] Check device availability...
[log] 2023-09-22 16:04:24 [Device:Skapbelysning Kontor] Device init data. ID: light.skaplys_kontor Name: Skapbelysning Kontor Class: light
[log] 2023-09-22 16:04:24 [Device:Uplights Soverom] Device init data. ID: light.uplights Name: Uplights Soverom Class: light
[log] 2023-09-22 16:04:24 [Device:Taklampe Gjesterom] Device init data. ID: light.taklampe_3 Name: Taklampe Gjesterom Class: light
[log] 2023-09-22 16:04:24 [Device:Taklampe Stue] Device init data. ID: light.taklampe_2 Name: Taklampe Stue Class: light
[log] 2023-09-22 16:04:24 [Device:Taklampe Garderobe] Device init data. ID: light.taklampe Name: Taklampe Garderobe Class: light
[log] 2023-09-22 16:04:24 [Device:Spotlights Spisestue] Device init data. ID: light.spotlights Name: Spotlights Spisestue Class: light
[log] 2023-09-22 16:04:24 [Device:Skapbelysning Soverom] Device init data. ID: light.skapbelysning Name: Skapbelysning Soverom Class: light
[log] 2023-09-22 16:04:24 [Device:Blomsterbenk Loftstue] Device init data. ID: light.plantebelysning Name: Blomsterbenk Loftstue Class: light
[log] 2023-09-22 16:04:24 [Device:Lysekrone Gang] Device init data. ID: light.lysekrone_2 Name: Lysekrone Gang Class: light
[log] 2023-09-22 16:04:24 [Device:Lysekrone Spisestue] Device init data. ID: light.lysekrone Name: Lysekrone Spisestue Class: light
[log] 2023-09-22 16:04:24 [Device:Karnappspotter Stue] Device init data. ID: light.karnapplys Name: Karnappspotter Stue Class: light
[log] 2023-09-22 16:04:24 [Device:Hjørnelampe Stue] Device init data. ID: light.hjornelampe Name: Hjørnelampe Stue Class: light
[log] 2023-09-22 16:04:24 [Device:Takspotter Soverom] Device init data. ID: light.taklys_4 Name: Takspotter Soverom Class: light
[log] 2023-09-22 16:04:24 [Device:Takspotter Kjøkken] Device init data. ID: light.taklys_3 Name: Takspotter Kjøkken Class: light
[log] 2023-09-22 16:04:23 [Device:Takspotter Bad] Device init data. ID: light.taklys_2 Name: Takspotter Bad Class: light
[log] 2023-09-22 16:04:23 [Device:Takspotter Loftstue ] Device init data. ID: light.taklys Name: Takspotter Loftstue Class: light
[log] 2023-09-22 16:04:23 [Device:Garasjeport 1] Device init data. ID: cover.garasjeport_1 Name: Garasjeport 1 Class: windowcoverings
[log] 2023-09-22 16:04:23 [Device:Garasjeport 2] Device init data. ID: cover.garasjeport_2 Name: Garasjeport 2 Class: windowcoverings
[log] 2023-09-22 16:04:23 [Device:Kaffetrakter] Device init data. ID: homey.kaffetrakter Name: Kaffetrakter Class: sensor
[log] 2023-09-22 16:04:23 [Device:Kaffemaskin] Device init data. ID: homey.kaffemaskin Name: Kaffemaskin Class: coffeemachine
[log] 2023-09-22 16:04:23 [Device:Luftavfukter Garasjekjeller] Device init data. ID: homey.luftavfukter Name: Luftavfukter Garasjekjeller Class: sensor
[log] 2023-09-22 16:04:23 [Device:Vaskemaskin] Device init data. ID: homey.vaskemaskin Name: Vaskemaskin Class: sensor
[log] 2023-09-22 16:04:23 [Device:Tørketrommel] Device init data. ID: homey.torketrommel Name: Tørketrommel Class: sensor
[log] 2023-09-22 16:04:23 [Device:Oppvaskmaskin] Device init data. ID: homey.oppvaskmaskin Name: Oppvaskmaskin Class: sensor
[log] 2023-09-22 16:04:23 [Device:Kjølehjørne] Device init data. ID: homey.kjolehjorne Name: Kjølehjørne Class: sensor
[log] 2023-09-22 16:04:23 [Device:Varmegjennvinner] Device init data. ID: homey.varmegjenvinner Name: Varmegjennvinner Class: sensor
[log] 2023-09-22 16:04:23 [Device:Varmtvannsbereder] Device init data. ID: homey.varmtvannsbereder Name: Varmtvannsbereder Class: socket
[log] 2023-09-22 16:04:23 [Device:Varmepumpe Garasje] Device init data. ID: climate.varmepumpe_i_garasje Name: Varmepumpe Garasje Class: thermostat
[log] 2023-09-22 16:04:23 [Device:Varmepumpe Stue] Device init data. ID: climate.varmepumpe_i_stue Name: Varmepumpe Stue Class: thermostat
[log] 2023-09-22 16:04:23 [Device:Kamera Veranda] Device init data. ID: camera.aarlo_veranda Name: Kamera Veranda Class: camera
[log] 2023-09-22 16:04:23 [Device:Kamera Inngangsparti] Device init data. ID: camera.aarlo_inngangsparti Name: Kamera Inngangsparti Class: camera
[log] 2023-09-22 16:04:23 [Device:Kamera Gårdsplass] Device init data. ID: camera.aarlo_gardsplass Name: Kamera Gårdsplass Class: camera
I can’t see any errors or any status changes for the door.
There must be something that changes the door state internaly in the Homey app. Maybe an internal variable that holds the state from HA is set by mistake to boolean value instead of the string value from HA state? Looks like a variable is set after a while to something else than “closed”. Only the string value “closed” is considered as closed, right? All other string values are considered as open?
Ok, no errors in the log.
But entity changes are not logged. That would cause a lot of entries 
But such state changes are only caused by an entity update via Websocket.
And yes, only state “cloded” causes the tile to be inactive and the “garagedoor_closed” swith to be on. All other states will act as “open” (reverse).
I’ll check if I can provide additional (optional) logging.
After restart of the app, I get a lot of norwegian log entries for the device without anything changing in HA:
I’am still on v. 1.4.25.
New test version 1.4.27:
- extended logging:
Log entity state or attribute changes in app log.
Activate exended logging in repair view:
Now you can see a lot of entity/attribute changes:
Please use this feature carefully for debugging. Deactivate it if not needed.
To check the log it’s easier to copy/paste the content and use a text editor. This way you can search for entities or attributes. The log entry contains the entity state and all entity attributes. So a line can be very long.
@JOR1
I added additional entity logging. You can activate it and check the log if your garage door state changes again.
I think something changes in entity attributes on HA side and this triggers an update via Websocket interface. Perhaps attributes are not logged in HA. I hope we can see now what happens
Yes, indeed.
My tilt sensors for the doors have additional entities.
Temperature and battery level are probably the only ones that will ever change value.
I saw when temperature was updated in the log below, the door imidiately changed state to open in Homey. I also see that no value is provided for the actual open/close state.
Does that mean that open/close state is set to blank? I guess blank (no value) is considered as door open?
Maybe a blank value for door state could be treated as no change? We do not want to change state from open to closed or vice versa.
Many thanks. Device entities was the missing link.
While adding the possibility to add further HA device entities to a Homey device, I added a check to all devices to update the devie state only for the main entity - except the cover as I saw now.
That’s why all entity uopdates (cover, temperature…) are were used to check the state. And because temperature is not “closed”, the device state in homey changed to “open” 
You can delete the login your previous post.
This should be fixed with test version 1.4.28
- Fix for cover state update if device entities are added to the cover device.
2 Likes
Thanks a lot.
Issue is solved.
My garage doors now have correct status in Homey.
1 Like
I have Philips Hue Tap 2 Dial Switch. It has 4 buttons working superb via Philips Hue HP23 app. I cannot manage to make dial/rotation wheel working. My HA is detecting wheel with no problem. How can I forward this to my HP23? Virtual device or any other way?
Hi, the Hue integration only supports events for tap dial actions.
You can take this flow as example.
Use the app flow trigger to react on HA events. There is no HA device or entity for the tap dial you could add as device.
Thanks, I will check it now.
Dial rotation can be managed by Node-red. Please check it here: Make the Philips Hue Tap dial control anything in your home, using Node-RED - Node-RED - Home Assistant Community
