deCONZ - Zigbee gateway van Dresden Elektronik

[belly89]

Mimiix schreef op maandag 17 januari 2022 @ 16:15:
[...]


Draai je de Addon?

Nee, Deconz draait op een W10 omgeving. Wel op dezelfde PC maar HA draait in virtualbox. Ik heb de addon wel geïnstalleerd gehad maar bleek later dat dit dus helemaal niet nodig was. Toen heb ik hem gedisabled. staat nog wel geïnstalleerd.

[Mimiix]

belly89 schreef op maandag 17 januari 2022 @ 16:18:
[...]


Nee, Deconz draait op een W10 omgeving. Wel op dezelfde PC maar HA draait in virtualbox. Ik heb de addon wel geïnstalleerd gehad maar bleek later dat dit dus helemaal niet nodig was. Toen heb ik hem gedisabled. staat nog wel geïnstalleerd.

Kan het zijn dat de IP's veranderen na een reboot?

Dat is meestal wat er gebeurd namelijk, maar dat is met de addon.

Ik heb geen idee verder hoe dit zit. Je zou op het HA Forum kunnen vragen hoe en wat.

[belly89]

Mimiix schreef op maandag 17 januari 2022 @ 16:19:
[...]


Kan het zijn dat de IP's veranderen na een reboot?

Dat is meestal wat er gebeurd namelijk, maar dat is met de addon.

Ik heb geen idee verder hoe dit zit. Je zou op het HA Forum kunnen vragen hoe en wat.

Nee de IP adressen zijn gelijk gebleven! Ik ga nog even verder op zoek. Bedankt in ieder geval

[Wachten...]

belly89 schreef op maandag 17 januari 2022 @ 16:27:
[...]


Nee de IP adressen zijn gelijk gebleven! Ik ga nog even verder op zoek. Bedankt in ieder geval

Heb je al een keer de complete integratie verwijderd, HA opnieuw opgestart, en dan proberen te integratie weer opnieuw toe te voegen.

Ik ben er laatst met @Mimiix wel achter gekomen dat een integratie verwijderen en het herstarten van HA enorm veel problemen op kan lossen.

[belly89]

Wachten... schreef op maandag 17 januari 2022 @ 16:32:
[...]


Heb je al een keer de complete integratie verwijderd, HA opnieuw opgestart, en dan proberen te integratie weer opnieuw toe te voegen.

Ik ben er laatst met @Mimiix wel achter gekomen dat een integratie verwijderen en het herstarten van HA enorm veel problemen op kan lossen.

Nee dat nog niet. Heb nu "aardig" wat apparaten via Deconz gekoppeld aan HA met bijbehorende automations e.d. Nadat ik de integratie opnieuw toevoeg, voegt die dan de apparaten opnieuw toe zodat ze er dubbel in staan of matcht HA ze weer met de bestaande apparaten?

[Wachten...]

belly89 schreef op maandag 17 januari 2022 @ 16:38:
[...]


Nee dat nog niet. Heb nu "aardig" wat apparaten via Deconz gekoppeld aan HA met bijbehorende automations e.d. Nadat ik de integratie opnieuw toevoeg, voegt die dan de apparaten opnieuw toe zodat ze er dubbel in staan of matcht HA ze weer met de bestaande apparaten?

Ik ben altijd voorzichtig met het zeggen "ja alles werkt dan nog"

Mijn ervaring is door het vele vallen en opstaan nu zo:

Deconz (zou iedereen) apart moeten draaien en niet via de addon in HA. De reden is dat als HA toch breekt vanwege een update o.i.d. dat Deconz dan gewoon blijft werken. Al je verlichting zit dus binnen Deconz en niet binnen HA, je maakt enkel een koppeling door de integratie toe te voegen van Deconz toe te voegen binnen HA. En zover ik begrijp doe jij dat ook.

Dus zolang jij Deconz op een aparte VM of wat dan ook draait, en daar een backup van hebt, dan ben je aardig save. HA vind jouw integratie en hij herkend alles zoals je het hebt hernoemd e.d. binnen Deconz.

Als het even kan, probeer dan ook met de "friendly names" te werken en niet met entity_id`s. De "friendly names" zijn de namen die jij in Deconz opgeeft voor de lampen e.d., dus bijvoorbeeld "lamp overloop" Dit wordt dan netjes meegenomen door HA zodra je de integratie doet.

Hoe het precies zit met de entity id`s en wat voor koppeling HA daarmee maakt durf ik niet te zeggen. Wellicht dat @Mimiix hier iets over kan zeggen.

Voorheen was ik altijd de entity id`s aan het hernoemen zoals hieronder. Dit deed ik omdat NodeRED niet met friendly names werkt, maar met entity id`s (heel vervelend). Ik ben wel op aanraden van @Mimiix bezig met de NodeRED Deconz integratie. Deze werkt namelijk wel aan de hand van de friendly names. Ik ben alleen nog even aan het uitvogelen hoe alles precies werkt met die addon. Ik blij het overigens raar vinden dat NodeRED aan de hand van entity id`s werkt, want in theorie maakt de entity id naam echt geen reet uit, zoals je de friendly name maar snapt en goed omschrijft.

[ Voor 23% gewijzigd door Wachten... op 17-01-2022 17:06 ]

[Step5]

Wachten... schreef op maandag 17 januari 2022 @ 16:53:
[...]
. Ik blij het overigens raar vinden dat NodeRED aan de hand van entity id`s werkt, want in theorie maakt de entity id naam echt geen reet uit, zoals je de friendly name maar snapt en goed omschrijft.

[Afbeelding]

HA werkt zelf intern ook met de entity id, alleen zie je dat vaak niet omdat in de UI de friendly name getoond wordt. je hebt in node-red wel de "get entities" node daar kun je op state.friendly_name zoeken maar dat is wel weer een extra stap

[Wachten...]

Step5 schreef op maandag 17 januari 2022 @ 22:40:
[...]

HA werkt zelf intern ook met de entity id, alleen zie je dat vaak niet omdat in de UI de friendly name getoond wordt. je hebt in node-red wel de "get entities" node daar kun je op state.friendly_name zoeken maar dat is wel weer een extra stap

Ja klopt, zo hoort het altijd te werken namelijk
Een entity ID is een soort barcode, het maakt dan ook niet uit wat voor code (entity id) die heeft. De naam van het product is de "friendly name" Zie het als een pak rijst met een barcode bij de supermarkt.

Een entity id hoort uniek te zijn en hoort eigenlijk nooit te veranderen. Zo blijven je automations namelijk altijd werken!

[rjhilbrink]

Wachten... schreef op maandag 17 januari 2022 @ 22:56:
[...]


Ja klopt, zo hoort het altijd te werken namelijk
Een entity ID is een soort barcode, het maakt dan ook niet uit wat voor code (entity id) die heeft. De naam van het product is de "friendly name" Zie het als een pak rijst met een barcode bij de supermarkt.

Een entity id hoort uniek te zijn en hoort eigenlijk nooit te veranderen. Zo blijven je automations namelijk altijd werken!

Je weet dat alle pakken rijst dezelfde barcode hebben?

[tjanssen]

Heeft iemand ervaring met dit device:

https://www.develcoproduc...sensors-and-alarms/keypad

[RiCk]

tjanssen schreef op dinsdag 18 januari 2022 @ 11:08:
Heeft iemand ervaring met dit device:

https://www.develcoproduc...sensors-and-alarms/keypad

Die lijkt nog niet te werken met deCONZ.
Zie https://zigbee.blakadder.com/Develco_KEYZB-110.html

[bing69]

Ben aan het overgaan naar deCONZ, nu probeer ik een Xiaomi contactsensor toe te voegen zowel via Phoscon f zoals de meeste rechtstreeks in Domoticz. Krijg hem echter in zowel Phoscan als in Domoticz niet toegevoegd echter hier zie ik hem wel (onderste)
Wie weet raad?

[Mimiix]

bing69 schreef op dinsdag 18 januari 2022 @ 15:09:
Ben aan het overgaan naar deCONZ, nu probeer ik een Xiaomi contactsensor toe te voegen zowel via Phoscon f zoals de meeste rechtstreeks in Domoticz. Krijg hem echter in zowel Phoscan als in Domoticz niet toegevoegd echter hier zie ik hem wel (onderste)
Wie weet raad?
[Afbeelding]

Welke versie van deCONZ zit je?

Wat heb je zelf al gevonden?

[bing69]

Mimiix schreef op dinsdag 18 januari 2022 @ 15:19:
[...]


Welke versie van deCONZ zit je?

Wat heb je zelf al gevonden?

Ik heb nog niets gevonden, een andere sensor (hetzelfde) werkt wel.

[HoppyF]

Vanmiddag een nieuwe sensor toegevoegd in HA.
Eerst via Phoscon om deze te koppelen.
Dat ging goed.
Sensor (Aqara bewegingssensor) komt in HA en doet het ook.
Op zich niets aan de hand.

Echter vanuit HA kan ik het overzicht Deconz opvragen.
Normaal gesproken zie ik dan de drie nodes.
De conbee zelf en een twee sensoren.
Daar is nu nog een vierde bij gekomen.

In het overzicht staan 4 nodes, echter geen grafisch plaatje meer.
Scherm blijft leeg.
Hoe krijg ik dit terug?
Ik wil niet te veel onnodig herstarten omdat alles immers wel werkt.
Het zal wel iets simpels zijn.
Ik gebruik de HA app op mijn iPad.
Het Deconz scherm is dus nogal klein maar wel te zien.

Als ik links onder op Node List klik zie ik een tabel met vier entries.
Dat is dus in orde.
Alleen het grafisch overzicht ontbreekt.
De balkjes horizontaal of verticaal schuiven maakt geen verschil.

[RudolfR]

@HoppyF

De mesh staat meestal in het midden van de view. Beide scroll bars op het midden dus. Daar ook niks te zien?

[HoppyF]

RudolfR schreef op dinsdag 18 januari 2022 @ 17:29:
@HoppyF

De mesh staat meestal in het midden van de view. Beide scroll bars op het midden dus. Daar ook niks te zien?

Dat was het inderdaad!
Simpel dus (als je het weet…)

[Mimiix]

bing69 schreef op dinsdag 18 januari 2022 @ 16:02:
[...]


Ik heb nog niets gevonden, een andere sensor (hetzelfde) werkt wel.
[Afbeelding]

https://github.com/dresde...k/deconz-rest-plugin/wiki

Dan zou ik daar beginnen

[bing69]

Mimiix schreef op dinsdag 18 januari 2022 @ 21:29:
[...]

https://github.com/dresde...k/deconz-rest-plugin/wiki

Dan zou ik daar beginnen

Thanks, probleem direct gevonden en opgelost

[Rianata]

bing69 schreef op dinsdag 18 januari 2022 @ 22:21:
[...]


Thanks, probleem direct gevonden en opgelost

Misschien handig dat je dan ook hier deelt hoe, zodat een volgende Tweaker met hetzelfde issue jouw oplossing kan gebruiken!

[ Voor 3% gewijzigd door Rianata op 18-01-2022 23:38 ]

[bing69]

Rianata schreef op dinsdag 18 januari 2022 @ 23:37:
[...]


Misschien handig dat je dan ook hier deelt hoe, zodat een volgende Tweaker met hetzelfde issue jouw oplossing kan gebruiken!

Tuurlijk kan ik dat maar ik werd verwezen naar https://github.com/dresde...k/deconz-rest-plugin/wiki daar staat de oplossing!

[Mimiix]

Rianata schreef op dinsdag 18 januari 2022 @ 23:37:
[...]


Misschien handig dat je dan ook hier deelt hoe, zodat een volgende Tweaker met hetzelfde issue jouw oplossing kan gebruiken!

https://github.com/dresde...vices-or-functional-issue

Daar staat ie.

[RudolfR]

Mimiix schreef op woensdag 19 januari 2022 @ 12:21:
[...]

https://github.com/dresde...ices-or-functional-issues

Daar staat ie.

FTFY

[Cranberry]

Ik heb een dimmer voor onze lampen in de kamer (aantal stopcontacten wordt met één schakelaar bediend).

We hebben het nu al een aantal keren gehad dat de verlichting kort uitgaat (één tot een paar seconden) en daarna weer aangaat. Ik weet 100% zeker dat niemand de schakelaar fysiek òf 'digitaal' bediende.

In domoticz dat ik gebruik, zie ik in de log van deze dimmer het volgende:
2022-01-23 20:31:42 On
2022-01-23 20:31:43 On

Dit was het het moment dat het issue zich voordeed. Belangrijk te vermelden dat we heel vaak 2 meldingen kort achter elkaar zien als we de lampen met de dimmer inschakelen.

Zelf neig ik de oorzaak te zoeken in de dimmer zelf en niet in deCONZ, Phoscon of Domoticz.

Twee vragen:
- herkent iemand mss dit gedrag?
- hoe kon ik dit het het beste troubleshooten om uit te sluiten dat het in de Conbee-stick of achterliggende software ligt? Omdat het niet iedere avond optreedt, zou ik detailed logging over langere tijd moeten activeren. Wellicht krijg ik daardoor veel te veel logs.... Tips zijn welkom

[Pred]

Cranberry schreef op maandag 24 januari 2022 @ 10:45:
Ik heb een dimmer voor onze lampen in de kamer (aantal stopcontacten wordt met één schakelaar bediend).

We hebben het nu al een aantal keren gehad dat de verlichting kort uitgaat (één tot een paar seconden) en daarna weer aangaat. Ik weet 100% zeker dat niemand de schakelaar fysiek òf 'digitaal' bediende.

In domoticz dat ik gebruik, zie ik in de log van deze dimmer het volgende:
2022-01-23 20:31:42 On
2022-01-23 20:31:43 On

Dit was het het moment dat het issue zich voordeed. Belangrijk te vermelden dat we heel vaak 2 meldingen kort achter elkaar zien als we de lampen met de dimmer inschakelen.

Zelf neig ik de oorzaak te zoeken in de dimmer zelf en niet in deCONZ, Phoscon of Domoticz.

Twee vragen:
- herkent iemand mss dit gedrag?
- hoe kon ik dit het het beste troubleshooten om uit te sluiten dat het in de Conbee-stick of achterliggende software ligt? Omdat het niet iedere avond optreedt, zou ik detailed logging over langere tijd moeten activeren. Wellicht krijg ik daardoor veel te veel logs.... Tips zijn welkom

Ik heb deze zelfde dimmer, maar geen problemen met plotseling uit en ineens weer aan.

Ik had wel problemen dat deze dimmer na ~2 jaar ineens stopte met werken. Teruggestuurd en een nieuwe ontvangen die inmiddels een jaar zonder problemen werkt.

[belly89]

Cranberry schreef op maandag 24 januari 2022 @ 10:45:
Ik heb een dimmer voor onze lampen in de kamer (aantal stopcontacten wordt met één schakelaar bediend).

We hebben het nu al een aantal keren gehad dat de verlichting kort uitgaat (één tot een paar seconden) en daarna weer aangaat. Ik weet 100% zeker dat niemand de schakelaar fysiek òf 'digitaal' bediende.

In domoticz dat ik gebruik, zie ik in de log van deze dimmer het volgende:
2022-01-23 20:31:42 On
2022-01-23 20:31:43 On

Dit was het het moment dat het issue zich voordeed. Belangrijk te vermelden dat we heel vaak 2 meldingen kort achter elkaar zien als we de lampen met de dimmer inschakelen.

Zelf neig ik de oorzaak te zoeken in de dimmer zelf en niet in deCONZ, Phoscon of Domoticz.

Twee vragen:
- herkent iemand mss dit gedrag?
- hoe kon ik dit het het beste troubleshooten om uit te sluiten dat het in de Conbee-stick of achterliggende software ligt? Omdat het niet iedere avond optreedt, zou ik detailed logging over langere tijd moeten activeren. Wellicht krijg ik daardoor veel te veel logs.... Tips zijn welkom

Ik heb ook deze dimmer maar dit probleem herken ik niet. Zelf gebruik ik HA i.p.v. Domoticz. Wel raar, kan het zijn dat de verbinding kort wegvalt o.i.d.?

[Antonio di]

Cranberry schreef op maandag 24 januari 2022 @ 10:45:
Ik heb een dimmer voor onze lampen in de kamer (aantal stopcontacten wordt met één schakelaar bediend).

We hebben het nu al een aantal keren gehad dat de verlichting kort uitgaat (één tot een paar seconden) en daarna weer aangaat. Ik weet 100% zeker dat niemand de schakelaar fysiek òf 'digitaal' bediende.

In domoticz dat ik gebruik, zie ik in de log van deze dimmer het volgende:
2022-01-23 20:31:42 On
2022-01-23 20:31:43 On

Dit was het het moment dat het issue zich voordeed. Belangrijk te vermelden dat we heel vaak 2 meldingen kort achter elkaar zien als we de lampen met de dimmer inschakelen.

Zelf neig ik de oorzaak te zoeken in de dimmer zelf en niet in deCONZ, Phoscon of Domoticz.

Twee vragen:
- herkent iemand mss dit gedrag?
- hoe kon ik dit het het beste troubleshooten om uit te sluiten dat het in de Conbee-stick of achterliggende software ligt? Omdat het niet iedere avond optreedt, zou ik detailed logging over langere tijd moeten activeren. Wellicht krijg ik daardoor veel te veel logs.... Tips zijn welkom

Gebruik je wel of niet een BYPASS?

[Cranberry]

@Antonio di weet niet wat je precies met een bypass bedoelt, maar volgens mij niet. De dimmer kan out-of-the-box zowel fysiek als via software/domotica bediend worden.

[Antonio di]

Cranberry schreef op maandag 24 januari 2022 @ 12:18:
@Antonio di weet niet wat je precies met een bypass bedoelt, maar volgens mij niet. De dimmer kan out-of-the-box zowel fysiek als via software/domotica bediend worden.

Dat is als je in de dimmer hebt aangesloten zonder een blauwe draad. Je plaats dat een kleine module bij de lamp die er voor zorgt dat de dimmer altijd stroom krijgt.
Zie:
https://www.robbshop.nl/r...aaidimmer-zigbee-2-draads
Ik vroeg dit van de "Bypass" omdat een defect/niet-goed-werkende Bypass ook wel eens de oorzaak van jouw probleem kan zijn.

Ik heb SAMOTECH dimmer (is volgens mij precies hetzelfde als die van ROBB) op Home Assistant/CC2531-stick, aangesloten met blauwe draad (dus zonder Bypass) en dat werkt al 4 maanden prima . Stuurt/dimt 2 Osram Parathom DIM lampen aan (max verbruik 10,5 watt). Zie:
productreview: Samotech Zigbee & Draaiknop dimmer review door Antonio di

[Cranberry]

Duidelijk, dank @Antonio di. Een bypass gebruik idd niet. De dimmer wordt rechtstreeks via een fase- en nuldraad gevoed.

[bing69]

Ben helemaal over op deCONZ en de CC2531 en de Xiaomi hub eruit. De Hue hub blijf ik nog gebruiken omdat ik niet helemaal afhankelijk wil zijn van deCONZ.

echter krijg ik een foutmelding na draaien van een script, alles werkt maar toch die foutmelding.

code:

2022-01-25 09:52:02.233 Status: dzVents: Info: Handling events for: "Pir_Gang2", value: "On"
2022-01-25 09:52:02.234 Status: dzVents: Info: ------ Start internal script: GangLamp_sensor: Device: "Pir_Gang2 (deCONZ)", Index: 1292
2022-01-25 09:52:02.241 Status: dzVents: Info: ------ Finished GangLamp_sensor
2022-01-25 09:52:02.244 Status: EventSystem: Script event triggered: /home/pi/domoticz/dzVents/runtime/dzVents.lua
2022-01-25 09:52:07.145 deCONZ: onCommand called for Unit 43: Parameter 'Off', Level: 0, Hue:
2022-01-25 09:52:07.145 Error: deCONZ: This device doesn't support action

De laatste regel is de foutmelding maar in de een naar laatste verwijst hij naar Unit 43.
Deze kan ik nergens terugvinden. De lamp die aangestuurd wordt zit ook in deCONZ.
Waar kan ik Unit 43 terug vinden?

Hieronder het script:

code:

 return {
    active = true,
    on = {
        devices = {
            1290, --'Pir_Gang WC',
            1292 --'Pir_Gang2'
        }
    },
    execute = function(domoticz, devices)
            local gang = domoticz.devices(1294) --('Lamp_gang')
            local zonondergang = domoticz.devices(86) --('zonondergang')
            local Pir_Gang2 = domoticz.devices(1292) --('Pir_Gang2')
            local Pir_Gang  = domoticz.devices(1290) --('Pir_Gang')
            local schakel = domoticz.devices(1281) --('Gangschakelaar')
    if  (schakel.state == 'Closed') and (zonondergang.state == 'On') then  
            if (Pir_Gang.state == 'On') or (Pir_Gang2.state == 'On') then
               gang.dimTo(20).forSec(200)
            end   
    end
    if (schakel.state == 'Closed') and (Pir_Gang.state == 'Off') and (Pir_Gang2.state == 'Off') then 
            gang.switchOff()
    end
 end
}

[Mimiix]

bing69 schreef op dinsdag 25 januari 2022 @ 10:04:
Ben helemaal over op deCONZ en de CC2531 en de Xiaomi hub eruit. De Hue hub blijf ik nog gebruiken omdat ik niet helemaal afhankelijk wil zijn van deCONZ.

echter krijg ik een foutmelding na draaien van een script, alles werkt maar toch die foutmelding.

code:

2022-01-25 09:52:02.233 Status: dzVents: Info: Handling events for: "Pir_Gang2", value: "On"
2022-01-25 09:52:02.234 Status: dzVents: Info: ------ Start internal script: GangLamp_sensor: Device: "Pir_Gang2 (deCONZ)", Index: 1292
2022-01-25 09:52:02.241 Status: dzVents: Info: ------ Finished GangLamp_sensor
2022-01-25 09:52:02.244 Status: EventSystem: Script event triggered: /home/pi/domoticz/dzVents/runtime/dzVents.lua
2022-01-25 09:52:07.145 deCONZ: onCommand called for Unit 43: Parameter 'Off', Level: 0, Hue:
2022-01-25 09:52:07.145 Error: deCONZ: This device doesn't support action

De laatste regel is de foutmelding maar in de een naar laatste verwijst hij naar Unit 43.
Deze kan ik nergens terugvinden. De lamp die aangestuurd wordt zit ook in deCONZ.
Waar kan ik Unit 43 terug vinden?

Hieronder het script:

code:

 return {
    active = true,
    on = {
        devices = {
            1290, --'Pir_Gang WC',
            1292 --'Pir_Gang2'
        }
    },
    execute = function(domoticz, devices)
            local gang = domoticz.devices(1294) --('Lamp_gang')
            local zonondergang = domoticz.devices(86) --('zonondergang')
            local Pir_Gang2 = domoticz.devices(1292) --('Pir_Gang2')
            local Pir_Gang  = domoticz.devices(1290) --('Pir_Gang')
            local schakel = domoticz.devices(1281) --('Gangschakelaar')
    if  (schakel.state == 'Closed') and (zonondergang.state == 'On') then  
            if (Pir_Gang.state == 'On') or (Pir_Gang2.state == 'On') then
               gang.dimTo(20).forSec(200)
            end   
    end
    if (schakel.state == 'Closed') and (Pir_Gang.state == 'Off') and (Pir_Gang2.state == 'Off') then 
            gang.switchOff()
    end
 end
}

Dit kun je beter vragen in het domoticz topic.

[TWeaKLeGeND]

Ik heb een testnetwerk op zitten bouwen op mijn laptop en een conbee2 stickie, maar dat testnetwerk is inmiddels al best uitgebreid (40 devices oid, ivm het uitstellen van de rpi ben ik dus eigenlijk het testnetwerk als gebruiksnetwerk gaan behandelen..), ik zal een dezer dagen de rpi4 inrichten voor home assistant en deconz of zigbee2mqqt

Ik vraag me nu dus af of mijn netwerk op de conbee2 opgeslagen is en of dat gewoon intact blijft als ik die stick van computer naar computer move van windows naar linux etc of zelfs van deconz op windows naar zigbee2mqqt op de rpi4, of dat mijn netwerk in de deconz software op mijn laptop zit en ik het netwerk straks vanaf 0 moet beginnen. Ik ging er eigenlijk van uit dat de stick het netwerk is en het platform vrij wisselbaar is zonder een nieuw netwerk op te moeten bouwen.

[ Voor 18% gewijzigd door TWeaKLeGeND op 25-01-2022 12:41 ]

[Mimiix]

TWeaKLeGeND schreef op dinsdag 25 januari 2022 @ 12:39:
Ik heb een testnetwerk op zitten bouwen op mijn laptop en een conbee2 stickie, maar dat testnetwerk is inmiddels al best uitgebreid (40 devices oid, ivm het uitstellen van de rpi ben ik dus eigenlijk het testnetwerk als gebruiksnetwerk gaan behandelen..), ik zal een dezer dagen de rpi4 inrichten voor home assistant en deconz of zigbee2mqqt

Ik vraag me nu dus af of mijn netwerk op de conbee2 opgeslagen is en of dat gewoon intact blijft als ik die stick van computer naar computer move van windows naar linux etc of zelfs van deconz op windows naar zigbee2mqqt op de rpi4, of dat mijn netwerk in de deconz software op mijn laptop zit en ik het netwerk straks vanaf 0 moet beginnen. Ik ging er eigenlijk van uit dat de stick het netwerk is en het platform vrij wisselbaar is zonder een nieuw netwerk op te moeten bouwen.

De stick kent alleen de network settings. deCONZ heeft de apparaten en andere zaken. Je kunt een backup maken in Phoscon en restoren op een ander apparaat. Dus in jouw geval op de RPI.

Je kunt niet zomaar switchen naar Z2m. dan zul je alles moeten re-pairen.

[bing69]

Mimiix schreef op dinsdag 25 januari 2022 @ 10:48:
[...]


Dit kun je beter vragen in het domoticz topic.

Daar komt geen antwoord en het lijkt me een melding van deCONZ

[Mimiix]

bing69 schreef op dinsdag 25 januari 2022 @ 13:35:
[...]


Daar komt geen antwoord en het lijkt me een melding van deCONZ

Ik heb geen idee wat Unit 43 is

[rens-br]

bing69 schreef op dinsdag 25 januari 2022 @ 13:35:
[...]


Daar komt geen antwoord en het lijkt me een melding van deCONZ

Het is dan ook niet handig dat je bericht begint met 'opgelost'. Maar maak er eens het onderstaande van:

code:

gang.dimTo(0)

Verder gaat je script hele gekke dingen doen, lees de tekst onder Command options eens.

mportant note when using forAAA(): Let’s say you have a light that is triggered by a motion detector. Currently the light is Off and you do this: light.switchOn().forMin(5). What happens inside Domoticz is this: at t0 Domoticz issues the switchOn() command and schedules a command to restore the current state at t5 which is Off. So at t5 it will switch the light off.

If, however, before the scheduled switchOff() happens at t5, new motion is detected and you send this command again at t2 then something unpredictable may seem to happen: the light is never turned off!

Ik zou dus je script ook aanpassen en het volgende toevoegen:

code:

return {
    active = true,
    on = {
        devices = {
            1290, --'Pir_Gang WC',
            1292 --'Pir_Gang2'
        }
    },
    execute = function(domoticz, devices)
            local gang = domoticz.devices(1294) --('Lamp_gang')
            local zonondergang = domoticz.devices(86) --('zonondergang')
            local Pir_Gang2 = domoticz.devices(1292) --('Pir_Gang2')
            local Pir_Gang  = domoticz.devices(1290) --('Pir_Gang')
            local schakel = domoticz.devices(1281) --('Gangschakelaar')
    if  (schakel.state == 'Closed') and (zonondergang.state == 'On') then  
            if (Pir_Gang.state == 'On') or (Pir_Gang2.state == 'On') then
               gang.cancelQueuedCommands()
               gang.dimTo(20).forSec(200)
            end   
    end
    if (schakel.state == 'Closed') and (Pir_Gang.state == 'Off') and (Pir_Gang2.state == 'Off') then 
            gang.cancelQueuedCommands()
            gang.dimTo(0)
    end
 end
}

[ Voor 79% gewijzigd door rens-br op 25-01-2022 13:59 ]

[bing69]

Helaas er verandert niets.....

rens-br schreef op dinsdag 25 januari 2022 @ 13:54:
[...]


Het is dan ook niet handig dat je bericht begint met 'opgelost'. Maar maak er eens het onderstaande van:

code:

gang.dimTo(0)

Verder gaat je script hele gekke dingen doen, lees de tekst onder Command options eens.


[...]


Ik zou dus je script ook aanpassen en het volgende toevoegen:

code:

return {
    active = true,
    on = {
        devices = {
            1290, --'Pir_Gang WC',
            1292 --'Pir_Gang2'
        }
    },
    execute = function(domoticz, devices)
            local gang = domoticz.devices(1294) --('Lamp_gang')
            local zonondergang = domoticz.devices(86) --('zonondergang')
            local Pir_Gang2 = domoticz.devices(1292) --('Pir_Gang2')
            local Pir_Gang  = domoticz.devices(1290) --('Pir_Gang')
            local schakel = domoticz.devices(1281) --('Gangschakelaar')
    if  (schakel.state == 'Closed') and (zonondergang.state == 'On') then  
            if (Pir_Gang.state == 'On') or (Pir_Gang2.state == 'On') then
               gang.cancelQueuedCommands()
               gang.dimTo(20).forSec(200)
            end   
    end
    if (schakel.state == 'Closed') and (Pir_Gang.state == 'Off') and (Pir_Gang2.state == 'Off') then 
            gang.cancelQueuedCommands()
            gang.dimTo(0)
    end
 end
}

[Mimiix]

Release!

Changelog on [BETA] release with version 2.14.0

This beta release is the successor of v2.13.4 version.

The next stable version is scheduled to be released in few days as v2.14.1 if this version doesn't bring regressions.

Changes

- Add button events for ROBB Smarrt wireless remotes #5610
- Support for POPP Smart Thermostat #5279
- DDF for Develco/frient WISZB-120 open close sensor #5720
- DDF for Develco/frient AQSZB-110 VOC sensor #5719
- DDF for Develco/Frient SPLZB-131 smart plug #5717
- DDF for Sengled E12-N1E #5655
- DDF for Sengled E1C-NB7 #5699
- DDF for Neo NAS-WR01B #5577
- DDF for ubisys C4 #5661
- DDF for ubisys S1 #5707
- DDF for ubisys S2 #5698
- DDF for Wiser socket outlet double 16A #5718
- DDF for Wiser LK FUGA 4 button battery switch #5680
- DDF set Xiaomi MCCGQ14LM DDF status to Gold #5721
- Fix DDF enqueue missing state/lastupdated event for rule handling #5650
- Fix pairing Aqara Smart Wireless Switch WXKG11LM (regression from v2.13.x) #5599
- Fix Xiaomi WXKG11LM regression bug for ZHASwitch resource creation #5647
- Fix Ikea Styrbar lockup of top/bottom buttons short press after long press side buttons #5713
- Fix DDF Xiaomi light sensor (GZCGQ01LM) #5722
- Fix certain sensors become unreachable; ubisys J1 #5675
- Fix working mode for the Tuya sensor from Woox #5704
- Fix ZCLDB appliance and meter cluster descriptions, add LiXee cluster #5592
- Performance improvements and bug fixes for OTA updates.
- Improve performance when drawing nodes.
- Fix rare glitches in deCONZ core when different ConBee/RaspBee have been connected before.
- Fix infinite fetching of Node Descriptor in edge cases.
- Log ZDP Parent Announce messages.

A special thanks to all contributors of the deCONZ GitHub community.

-Dennis / @Mimiix / https://discord.gg/3XGEYY9

[iisworks]

Cool, eens kijken of deze versie mijn problemen met DDF oplost i.c.m. de compacte Tuya plugs (deconz unresponsive)! Na het omzeilen van DDF was alles weer 100% stabiel, maar het heeft wat goodwill gekost hier in huis!

[ Voor 36% gewijzigd door iisworks op 29-01-2022 16:49 ]

[Cranberry]

@iisworks hoe ben je uiteindelijk gevaren met de Tuya plugs? Heb je ze goed werkend gekregen als vebruiksmeter?

[iisworks]

Cranberry schreef op zaterdag 29 januari 2022 @ 20:57:
@iisworks hoe ben je uiteindelijk gevaren met de Tuya plugs? Heb je ze goed werkend gekregen als vebruiksmeter?

Niet best. Ik heb 15 van die nieuwe compacte Tuya plugs met oranje randje klaarliggen, geupdated naar laatste .10 Tuya FW die reporting ondersteunt. Maar na weer een halve dag klooien met DDFs helaas nog niet betrouwbaar werkend op deconz 2.14 i.c.m. custom DDF. Het komt in de buurt, want op zich heb ik ze wel zien rapporteren, maar nooit helemaal betrouwbaar bij in/uitschakelen en met/zonder load.

Helaas waren na het testen ook de bestaande plugs (voornamelijk BW-SHP15 ) dusdanig van slag dat die niet meer rapporteerden omdat sensors ontbraken. Het lijkt erop dat ook andere type plugs, ongeacht de exacte manufacturer naam in de DDF (_TZ3000_mraovvmm etc.) toch ook de settings in die DDF meekrijgen op basis van Model (TS011F)? Uiteindelijk backup van data teruggezet van de avond ervoor en toen werkten bestaande devices in ieder geval weer, maar dit maakt het testen met DDF dus wel lastig.

Ik heb hier mijn recente avonturen beschreven:
https://forum.phoscon.de/...or-tuya-ts011f-plugs/1519

[Update] Heeft iemand anders hier toevallig ook 2.14 draaien met Tuya of Blitzwolf SHP-15 plugs? Ik ben erg benieuwd of dezelfde issues optreden als je DDF activeert (Edit DDF - Hot relaod). Dit issue heeft me al heel wat uren en hoofdbrekens gekost, wat op zich natuurlijk niet erg is (beta enzo), maar iets wat het gewoon doet zou fijn zijn! Ik wacht met smart op een officiele werkende DDF voor TS011F plugs!

[ Voor 27% gewijzigd door iisworks op 02-02-2022 18:28 ]

[The Druid]

Na lang trouble shooten meld ik mij ook maar hier.

Ik zit met een het probleem dat ik mijn Conbee 2 maar niet aan de praat krijg. Meer specifiek ik kan geen nieuwe devices vinden.

Ik draai HA in een virtual machine op mijn Synology. De conbee zit in een USB port van mijn NAS met een usb 2 verlengkabel. Heb netjes de USB 2.0 toegevoegd in de VM settings en hij ziet ook keurig mijn Conbee in de VM omgeving. So far so good.

Op een clean install deConz ge-installeert. Ik kan de Webui openen en een start seaching for new devices opstarten en daar stopt het. Nul devices gevonden.

De Conbee usb met dezelfde Zigbee devices getest op een Windows 10 machine en daar werkt discovery wel.

Onderstaand mijn deConz logfile:

Shoot kan niet copieren uit de VM omgeving blijkbaar. Vanavond even kijken hoe ik dat oplos.

[ Voor 96% gewijzigd door The Druid op 04-02-2022 13:48 ]

[Mimiix]

The Druid schreef op vrijdag 4 februari 2022 @ 13:30:
Na lang trouble shooten meld ik mij ook maar hier.

Ik zit met een het probleem dat ik mijn Conbee 2 maar niet aan de praat krijg. Meer specifiek ik kan geen nieuwe devices vinden.

Ik draai HA in een virtual machine op mijn Synology. De conbee zit in een USB port van mijn NAS met een usb 2 verlengkabel. Heb netjes de USB 2.0 toegevoegd in de VM settings en hij ziet ook keurig mijn Conbee in de VM omgeving. So far so good.

Op een clean install deConz ge-installeert. Ik kan de Webui openen en een start seaching for new devices opstarten en daar stopt het. Nul devices gevonden.

De Conbee usb met dezelfde Zigbee devices getest op een Windows 10 machine en daar werkt discovery wel.

Onderstaand mijn deConz logfile:

code:

172.30.32.2 - - [04/Feb/2022:13:22:38 +0100] "GET /api/03E087A45B/groups?_=1643977359142 HTTP/1.1" 200 12 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/index.html?_v=8204f08632d42e22905a77e111acc552b7770f25,1,5,13&gwid=00212EFFFF07EC3C" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
172.30.32.2 - - [04/Feb/2022:13:22:38 +0100] "GET /api/03E087A45B/config?_=1643977359141 HTTP/1.1" 200 1874 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/index.html?_v=8204f08632d42e22905a77e111acc552b7770f25,1,5,13&gwid=00212EFFFF07EC3C" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
172.30.32.2 - - [04/Feb/2022:13:22:38 +0100] "GET /api/03E087A45B/lights?_=1643977359143 HTTP/1.1" 200 347 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/index.html?_v=8204f08632d42e22905a77e111acc552b7770f25,1,5,13&gwid=00212EFFFF07EC3C" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
172.30.32.2 - - [04/Feb/2022:13:22:38 +0100] "GET /api/03E087A45B/sensors?_=1643977359144 HTTP/1.1" 200 440 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/index.html?_v=8204f08632d42e22905a77e111acc552b7770f25,1,5,13&gwid=00212EFFFF07EC3C" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
172.30.32.2 - - [04/Feb/2022:13:22:38 +0100] "GET /api/03E087A45B/config?_=1643977359145 HTTP/1.1" 200 1874 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/index.html?_v=8204f08632d42e22905a77e111acc552b7770f25,1,5,13&gwid=00212EFFFF07EC3C" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
13:22:48:278 Skip idle timer callback, too early: elapsed 642 msec
13:23:36:295 Device TTL 2535 s flags: 0x7
13:24:02:278 Skip idle timer callback, too early: elapsed 547 msec
13:24:21:279 GW firmware version shall be updated to: 0x26660700
13:24:36:298 Device TTL 2475 s flags: 0x7
13:25:05:279 Skip idle timer callback, too early: elapsed 604 msec
13:25:36:291 Device TTL 2415 s flags: 0x7
13:26:08:278 Skip idle timer callback, too early: elapsed 542 msec
13:26:31:279 GW firmware version shall be updated to: 0x26660700
13:26:36:293 Device TTL 2355 s flags: 0x7
172.30.32.2 - - [04/Feb/2022:13:26:54 +0100] "GET /pwa/index.html HTTP/1.1" 200 113241 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/ingress.html" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
172.30.32.2 - - [04/Feb/2022:13:26:54 +0100] "GET /api/03E087A45B/config?_=1643977615384 HTTP/1.1" 200 1874 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/index.html" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
172.30.32.2 - - [04/Feb/2022:13:26:54 +0100] "GET /api/03E087A45B/config?_=1643977615385 HTTP/1.1" 200 1874 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/index.html" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
172.30.32.2 - - [04/Feb/2022:13:26:54 +0100] "GET /api/03E087A45B/groups?_=1643977615386 HTTP/1.1" 200 12 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/index.html" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
172.30.32.2 - - [04/Feb/2022:13:26:54 +0100] "GET /api/03E087A45B/lights?_=1643977615387 HTTP/1.1" 200 347 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/index.html" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
172.30.32.2 - - [04/Feb/2022:13:26:54 +0100] "GET /api/03E087A45B/sensors?_=1643977615388 HTTP/1.1" 200 440 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/index.html" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
172.30.32.2 - - [04/Feb/2022:13:26:54 +0100] "GET /api/03E087A45B/config?_=1643977615389 HTTP/1.1" 200 1874 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/index.html" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
13:26:55:499 New websocket 127.0.0.1:33128 (state: 3) 
172.30.32.2 - - [04/Feb/2022:13:26:59 +0100] "GET /api/03E087A45B/groups?_=1643977615390 HTTP/1.1" 200 12 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/index.html" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
172.30.32.2 - - [04/Feb/2022:13:26:59 +0100] "GET /api/03E087A45B/lights?_=1643977615391 HTTP/1.1" 200 347 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/index.html" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
172.30.32.2 - - [04/Feb/2022:13:26:59 +0100] "GET /api/03E087A45B/sensors?_=1643977615392 HTTP/1.1" 200 440 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/index.html" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
172.30.32.2 - - [04/Feb/2022:13:26:59 +0100] "GET /api/03E087A45B/config?_=1643977615393 HTTP/1.1" 200 1874 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/index.html" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
172.30.32.2 - - [04/Feb/2022:13:27:00 +0100] "GET /websocket HTTP/1.1" 101 4 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
172.30.32.2 - - [04/Feb/2022:13:27:00 +0100] "GET /pwa/devices-lights.html?_v=8204f08632d42e22905a77e111acc552b7770f25,1,5,13&gwid=00212EFFFF07EC3C HTTP/1.1" 200 19319 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/index.html" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
13:27:00:084 Websocket disconnected 127.0.0.1:33128, state: 0, close-code: 1000, reason: 
172.30.32.2 - - [04/Feb/2022:13:27:00 +0100] "GET /api/03E087A45B/config?_=1643977621251 HTTP/1.1" 200 1874 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/devices-lights.html?_v=8204f08632d42e22905a77e111acc552b7770f25,1,5,13&gwid=00212EFFFF07EC3C" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
172.30.32.2 - - [04/Feb/2022:13:27:00 +0100] "GET /api/03E087A45B/config?_=1643977621252 HTTP/1.1" 200 1874 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/devices-lights.html?_v=8204f08632d42e22905a77e111acc552b7770f25,1,5,13&gwid=00212EFFFF07EC3C" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
172.30.32.2 - - [04/Feb/2022:13:27:00 +0100] "GET /api/03E087A45B/lights?_=1643977621253 HTTP/1.1" 200 347 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/devices-lights.html?_v=8204f08632d42e22905a77e111acc552b7770f25,1,5,13&gwid=00212EFFFF07EC3C" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
172.30.32.2 - - [04/Feb/2022:13:27:00 +0100] "GET /api/03E087A45B/lights?_=1643977621254 HTTP/1.1" 200 347 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/devices-lights.html?_v=8204f08632d42e22905a77e111acc552b7770f25,1,5,13&gwid=00212EFFFF07EC3C" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
172.30.32.2 - - [04/Feb/2022:13:27:01 +0100] "GET /api/03E087A45B/sensors/new HTTP/1.1" 200 45 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/devices-lights.html?_v=8204f08632d42e22905a77e111acc552b7770f25,1,5,13&gwid=00212EFFFF07EC3C" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
13:27:01:359 New websocket 127.0.0.1:33152 (state: 3) 
172.30.32.2 - - [04/Feb/2022:13:27:02 +0100] "GET /websocket HTTP/1.1" 101 0 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
172.30.32.2 - - [04/Feb/2022:13:27:02 +0100] "GET /pwa/settings-view.html?_v=8204f08632d42e22905a77e111acc552b7770f25,1,5,13&gwid=00212EFFFF07EC3C HTTP/1.1" 200 4750 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/devices-lights.html?_v=8204f08632d42e22905a77e111acc552b7770f25,1,5,13&gwid=00212EFFFF07EC3C" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
13:27:02:123 Websocket disconnected 127.0.0.1:33152, state: 0, close-code: 1000, reason: 
172.30.32.2 - - [04/Feb/2022:13:27:02 +0100] "GET /api/03E087A45B/config?_=1643977623170 HTTP/1.1" 200 1874 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/settings-view.html?_v=8204f08632d42e22905a77e111acc552b7770f25,1,5,13&gwid=00212EFFFF07EC3C" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
172.30.32.2 - - [04/Feb/2022:13:27:02 +0100] "GET /api/03E087A45B/config?_=1643977623171 HTTP/1.1" 200 1874 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/settings-view.html?_v=8204f08632d42e22905a77e111acc552b7770f25,1,5,13&gwid=00212EFFFF07EC3C" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
13:27:03:259 New websocket 127.0.0.1:33162 (state: 3) 
172.30.32.2 - - [04/Feb/2022:13:27:03 +0100] "GET /websocket HTTP/1.1" 101 4 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
13:27:03:552 Websocket disconnected 127.0.0.1:33162, state: 0, close-code: 1000, reason: 
172.30.32.2 - - [04/Feb/2022:13:27:03 +0100] "GET /pwa/settings-gateway2.html?_v=8204f08632d42e22905a77e111acc552b7770f25,1,5,13&gwid=00212EFFFF07EC3C HTTP/1.1" 200 54495 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/settings-view.html?_v=8204f08632d42e22905a77e111acc552b7770f25,1,5,13&gwid=00212EFFFF07EC3C" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
172.30.32.2 - - [04/Feb/2022:13:27:03 +0100] "GET /pwa/js/version-compare.js?b3947f= HTTP/1.1" 200 482 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/settings-gateway2.html?_v=8204f08632d42e22905a77e111acc552b7770f25,1,5,13&gwid=00212EFFFF07EC3C" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
2022/02/04 13:27:03 [info] 1091#1091: *400 client 172.30.32.2 closed keepalive connection
172.30.32.2 - - [04/Feb/2022:13:27:03 +0100] "GET /api/03E087A45B/config?_=1643977624629 HTTP/1.1" 200 1874 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/settings-gateway2.html?_v=8204f08632d42e22905a77e111acc552b7770f25,1,5,13&gwid=00212EFFFF07EC3C" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
172.30.32.2 - - [04/Feb/2022:13:27:03 +0100] "GET /api/03E087A45B/config?_=1643977624630 HTTP/1.1" 200 1874 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/settings-gateway2.html?_v=8204f08632d42e22905a77e111acc552b7770f25,1,5,13&gwid=00212EFFFF07EC3C" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
172.30.32.2 - - [04/Feb/2022:13:27:03 +0100] "GET /api/03E087A45B/config?_=1643977624631 HTTP/1.1" 200 1874 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/settings-gateway2.html?_v=8204f08632d42e22905a77e111acc552b7770f25,1,5,13&gwid=00212EFFFF07EC3C" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
13:27:04:789 New websocket 127.0.0.1:33186 (state: 3) 
172.30.32.2 - - [04/Feb/2022:13:27:08 +0100] "GET /api/03E087A45B/config?_=1643977624632 HTTP/1.1" 200 1874 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/settings-gateway2.html?_v=8204f08632d42e22905a77e111acc552b7770f25,1,5,13&gwid=00212EFFFF07EC3C" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
172.30.32.2 - - [04/Feb/2022:13:27:08 +0100] "GET /api/03E087A45B/config?_=1643977624633 HTTP/1.1" 200 1874 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/settings-gateway2.html?_v=8204f08632d42e22905a77e111acc552b7770f25,1,5,13&gwid=00212EFFFF07EC3C" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
13:27:12:279 Skip idle timer callback, too early: elapsed 567 msec
172.30.32.2 - - [04/Feb/2022:13:27:12 +0100] "GET /websocket HTTP/1.1" 101 4 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
13:27:12:853 Websocket disconnected 127.0.0.1:33186, state: 0, close-code: 1000, reason: 
172.30.32.2 - - [04/Feb/2022:13:27:12 +0100] "GET /pwa/js/settings-gateway/settings-gateway-machine.js HTTP/1.1" 200 9205 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/js/settings-gateway2.js?280af1" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
2022/02/04 13:27:12 [info] 1091#1091: *409 client 172.30.32.2 closed keepalive connection (104: Connection reset by peer)
172.30.32.2 - - [04/Feb/2022:13:27:13 +0100] "GET /api/03E087A45B/config?_=1643977633884 HTTP/1.1" 200 1874 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/settings-gateway2.html?_v=8204f08632d42e22905a77e111acc552b7770f25,1,5,13&gwid=00212EFFFF07EC3C" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
172.30.32.2 - - [04/Feb/2022:13:27:13 +0100] "GET /api/03E087A45B/config?_=1643977633885 HTTP/1.1" 200 1874 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/settings-gateway2.html?_v=8204f08632d42e22905a77e111acc552b7770f25,1,5,13&gwid=00212EFFFF07EC3C" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
172.30.32.2 - - [04/Feb/2022:13:27:13 +0100] "GET /api/03E087A45B/config?_=1643977633886 HTTP/1.1" 200 1874 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/settings-gateway2.html?_v=8204f08632d42e22905a77e111acc552b7770f25,1,5,13&gwid=00212EFFFF07EC3C" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
13:27:14:033 New websocket 127.0.0.1:33210 (state: 3) 
172.30.32.2 - - [04/Feb/2022:13:27:20 +0100] "GET /api/03E087A45B/config?_=1643977633887 HTTP/1.1" 200 1874 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/settings-gateway2.html?_v=8204f08632d42e22905a77e111acc552b7770f25,1,5,13&gwid=00212EFFFF07EC3C" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
172.30.32.2 - - [04/Feb/2022:13:27:21 +0100] "GET /api/03E087A45B/config?_=1643977633888 HTTP/1.1" 200 1874 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/settings-gateway2.html?_v=8204f08632d42e22905a77e111acc552b7770f25,1,5,13&gwid=00212EFFFF07EC3C" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
172.30.32.2 - - [04/Feb/2022:13:27:27 +0100] "GET /api/03E087A45B/config?_=1643977633889 HTTP/1.1" 200 1874 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/settings-gateway2.html?_v=8204f08632d42e22905a77e111acc552b7770f25,1,5,13&gwid=00212EFFFF07EC3C" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
172.30.32.2 - - [04/Feb/2022:13:27:33 +0100] "GET /api/03E087A45B/config?_=1643977633890 HTTP/1.1" 200 1874 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/settings-gateway2.html?_v=8204f08632d42e22905a77e111acc552b7770f25,1,5,13&gwid=00212EFFFF07EC3C" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
13:27:36:295 Device TTL 2295 s flags: 0x7
172.30.32.2 - - [04/Feb/2022:13:27:39 +0100] "GET /api/03E087A45B/config?_=1643977633891 HTTP/1.1" 200 1874 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/settings-gateway2.html?_v=8204f08632d42e22905a77e111acc552b7770f25,1,5,13&gwid=00212EFFFF07EC3C" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
172.30.32.2 - - [04/Feb/2022:13:27:44 +0100] "GET /api/03E087A45B/config?_=1643977633892 HTTP/1.1" 200 1874 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/settings-gateway2.html?_v=8204f08632d42e22905a77e111acc552b7770f25,1,5,13&gwid=00212EFFFF07EC3C" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
172.30.32.2 - - [04/Feb/2022:13:27:49 +0100] "GET /api/03E087A45B/config?_=1643977633893 HTTP/1.1" 200 1874 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/settings-gateway2.html?_v=8204f08632d42e22905a77e111acc552b7770f25,1,5,13&gwid=00212EFFFF07EC3C" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
172.30.32.2 - - [04/Feb/2022:13:27:55 +0100] "GET /api/03E087A45B/config?_=1643977633894 HTTP/1.1" 200 1874 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/settings-gateway2.html?_v=8204f08632d42e22905a77e111acc552b7770f25,1,5,13&gwid=00212EFFFF07EC3C" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
172.30.32.2 - - [04/Feb/2022:13:28:00 +0100] "GET /api/03E087A45B/config?_=1643977633895 HTTP/1.1" 200 1874 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/settings-gateway2.html?_v=8204f08632d42e22905a77e111acc552b7770f25,1,5,13&gwid=00212EFFFF07EC3C" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
172.30.32.2 - - [04/Feb/2022:13:28:05 +0100] "GET /api/03E087A45B/config?_=1643977633896 HTTP/1.1" 200 1874 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/settings-gateway2.html?_v=8204f08632d42e22905a77e111acc552b7770f25,1,5,13&gwid=00212EFFFF07EC3C" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
172.30.32.2 - - [04/Feb/2022:13:28:10 +0100] "GET /api/03E087A45B/config?_=1643977633897 HTTP/1.1" 200 1874 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/settings-gateway2.html?_v=8204f08632d42e22905a77e111acc552b7770f25,1,5,13&gwid=00212EFFFF07EC3C" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
13:28:15:279 Skip idle timer callback, too early: elapsed 612 msec
172.30.32.2 - - [04/Feb/2022:13:28:16 +0100] "GET /api/03E087A45B/config?_=1643977633898 HTTP/1.1" 200 1874 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/settings-gateway2.html?_v=8204f08632d42e22905a77e111acc552b7770f25,1,5,13&gwid=00212EFFFF07EC3C" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
172.30.32.2 - - [04/Feb/2022:13:28:21 +0100] "GET /api/03E087A45B/config?_=1643977633899 HTTP/1.1" 200 1874 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/settings-gateway2.html?_v=8204f08632d42e22905a77e111acc552b7770f25,1,5,13&gwid=00212EFFFF07EC3C" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
172.30.32.2 - - [04/Feb/2022:13:28:25 +0100] "GET /api/03E087A45B/config?_=1643977633900 HTTP/1.1" 200 1874 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/settings-gateway2.html?_v=8204f08632d42e22905a77e111acc552b7770f25,1,5,13&gwid=00212EFFFF07EC3C" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
172.30.32.2 - - [04/Feb/2022:13:28:26 +0100] "GET /websocket HTTP/1.1" 101 696 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
13:28:26:929 Websocket disconnected 127.0.0.1:33210, state: 0, close-code: 1000, reason: 
172.30.32.2 - - [04/Feb/2022:13:28:27 +0100] "GET /api/03E087A45B/config?_=1643977708029 HTTP/1.1" 200 1874 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/devices-lights.html?_v=8204f08632d42e22905a77e111acc552b7770f25,1,5,13&gwid=00212EFFFF07EC3C" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
172.30.32.2 - - [04/Feb/2022:13:28:27 +0100] "GET /api/03E087A45B/config?_=1643977708030 HTTP/1.1" 200 1874 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/devices-lights.html?_v=8204f08632d42e22905a77e111acc552b7770f25,1,5,13&gwid=00212EFFFF07EC3C" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
172.30.32.2 - - [04/Feb/2022:13:28:27 +0100] "GET /api/03E087A45B/lights?_=1643977708031 HTTP/1.1" 200 347 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/devices-lights.html?_v=8204f08632d42e22905a77e111acc552b7770f25,1,5,13&gwid=00212EFFFF07EC3C" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
172.30.32.2 - - [04/Feb/2022:13:28:27 +0100] "GET /api/03E087A45B/lights?_=1643977708032 HTTP/1.1" 200 347 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/devices-lights.html?_v=8204f08632d42e22905a77e111acc552b7770f25,1,5,13&gwid=00212EFFFF07EC3C" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
172.30.32.2 - - [04/Feb/2022:13:28:28 +0100] "GET /api/03E087A45B/sensors/new HTTP/1.1" 200 45 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/devices-lights.html?_v=8204f08632d42e22905a77e111acc552b7770f25,1,5,13&gwid=00212EFFFF07EC3C" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
13:28:28:125 New websocket 127.0.0.1:33282 (state: 3) 
172.30.32.2 - - [04/Feb/2022:13:28:32 +0100] "GET /api/03E087A45B/lights?_=1643977708033 HTTP/1.1" 200 347 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/devices-lights.html?_v=8204f08632d42e22905a77e111acc552b7770f25,1,5,13&gwid=00212EFFFF07EC3C" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
172.30.32.2 - - [04/Feb/2022:13:28:33 +0100] "GET /websocket HTTP/1.1" 101 4 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
13:28:33:092 Websocket disconnected 127.0.0.1:33282, state: 0, close-code: 1000, reason: 
172.30.32.2 - - [04/Feb/2022:13:28:33 +0100] "GET /api/03E087A45B/config?_=1643977714135 HTTP/1.1" 200 1874 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/index.html" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
172.30.32.2 - - [04/Feb/2022:13:28:33 +0100] "GET /api/03E087A45B/config?_=1643977714134 HTTP/1.1" 200 1874 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/index.html" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
172.30.32.2 - - [04/Feb/2022:13:28:33 +0100] "GET /api/03E087A45B/groups?_=1643977714136 HTTP/1.1" 200 12 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/index.html" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
172.30.32.2 - - [04/Feb/2022:13:28:33 +0100] "GET /api/03E087A45B/lights?_=1643977714137 HTTP/1.1" 200 347 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/index.html" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
172.30.32.2 - - [04/Feb/2022:13:28:33 +0100] "GET /api/03E087A45B/sensors?_=1643977714138 HTTP/1.1" 200 440 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/index.html" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
172.30.32.2 - - [04/Feb/2022:13:28:33 +0100] "GET /api/03E087A45B/config?_=1643977714139 HTTP/1.1" 200 1874 "http://192.168.1.118:8123/api/hassio_ingress/uc39j-kWKnuuMKkV_iCAx82cYnfy4bxk6NOanWqYdMo/pwa/index.html" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
13:28:34:250 New websocket 127.0.0.1:33320 (state: 3) 
13:28:36:295 Device TTL 2235 s flags: 0x7
172.30.32.2 - - [04/Feb/2022:13:28:36 +0100] "GET /websocket HTTP/1.1" 101 0 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0"
13:28:36:582 Websocket disconnected 127.0.0.1:33320, state: 0, close-code: 1000, reason: 
13:28:41:279 GW firmware version shall be updated to: 0x26660700

Hoi,

Zou je wat deCONZ logs kunnen delen? Deze zijn van de addon namelijk en niet echt relevant. Zie topic warning voor hoe en wat.

[jja2000]

Hoi mensen!

Ik heb sinds kort tweemaal een tradfri lamp met het artikelnr 704.391.58 aangeschaft (de 806lm E27 RGB lamp), maar het lukt me maar niet om deze met mijn conbeeII via phoscon te verbinden.

De reset instructies heb ik gevolgd, dit wanneer phoscon actief naar nieuwe apparaten zoekt. Eén extra uit/aan lijkt hierbij niet te helpen.

Wieowie kan me helpen bij het toevoegen van deze bulbs? Het toevoegen en het uitlezen van mijn PIR gaat prima, dus ik ga er niet van uit dat het aan de conbee ligt.

Extra gegevens:
deCONZ en Phoscon draaien via de Home Assistant integratie op een Raspberry Pi 4. Alles daarin is up-to-date, inclusief de firmware op de conbee. Daar draait nu 0x26720700 op. De Ikea bulbs heb ik na wat pielen met deCONZ aangesloten aan een Tradfri Hub die ik te leen had gekregen, deze werkte prima (en waren ook up-to-date volgens de smart home app).

Logs tijdens het toevoegen:





Vanaf het herhalende Tradfri PIR bericht heb ik de lampen eenmaal in en uitgeschakeld zoals de instructies aangeven. De lampen blijven wel in deCONZ te zien, maar Phoscon pakt ze niet.

[Mimiix]

jja2000 schreef op vrijdag 4 februari 2022 @ 17:01:
Hoi mensen!

Ik heb sinds kort tweemaal een tradfri lamp met het artikelnr 704.391.58 aangeschaft (de 806lm E27 RGB lamp), maar het lukt me maar niet om deze met mijn conbeeII via phoscon te verbinden.

De reset instructies heb ik gevolgd, dit wanneer phoscon actief naar nieuwe apparaten zoekt. Eén extra uit/aan lijkt hierbij niet te helpen.

Wieowie kan me helpen bij het toevoegen van deze bulbs? Het toevoegen en het uitlezen van mijn PIR gaat prima, dus ik ga er niet van uit dat het aan de conbee ligt.

Extra gegevens:
deCONZ en Phoscon draaien via de Home Assistant integratie op een Raspberry Pi 4. Alles daarin is up-to-date, inclusief de firmware op de conbee. Daar draait nu 0x26720700 op. De Ikea bulbs heb ik na wat pielen met deCONZ aangesloten aan een Tradfri Hub die ik te leen had gekregen, deze werkte prima (en waren ook up-to-date volgens de smart home app).

Logs tijdens het toevoegen:

[Afbeelding]
[Afbeelding]
[Afbeelding]

Vanaf het herhalende Tradfri PIR bericht heb ik de lampen eenmaal in en uitgeschakeld zoals de instructies aangeven. De lampen blijven wel in deCONZ te zien, maar Phoscon pakt ze niet.
[Afbeelding]

Kan je logs met de flags maken uit de topic warning?

Voor het copy paste probleem : https://community.home-as...work-configuration/137597

[jja2000]

Mimiix schreef op vrijdag 4 februari 2022 @ 17:07:
[...]


Kan je logs met de flags maken uit de topic warning?

Voor het copy paste probleem : https://community.home-as...work-configuration/137597

Poging 2 (Ik gebruikte de HASS vnc viewer, nu dus TigerVNC):

code:

17:09:22:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:22:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:22:448 APS-DATA.request id: 225, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:09:22:450    asdu (length: 2): 1d00
17:09:22:464 APS-DATA.confirm id: 225, status: 0x00 SUCCESS
17:09:22:465 APS-DATA.confirm request id: 225 -> confirmed, timeout 70292856
17:09:22:469 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:09:22:470    asdu: 1d000100012ed107ffff2e2100407128feff15cd0452e1120001ff
17:09:22:471 APS-DATA.indication request id: 225 -> finished
17:09:22:472 APS-DATA.request id: 225 erase from queue
17:09:22:472 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:09:22:720 API error 1, /PHuXirAnrXI2euYOFmVBUmvOTv4CHEqdOWbueYJ_WbU/api/config, unauthorized user
17:09:23:096 Idle timer triggered
17:09:23:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:23:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:23:596 Daylight now: goldenHour2, status: 180, daylight: 0, dark: 0
17:09:24:096 Idle timer triggered
17:09:24:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:24:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:25:096 Idle timer triggered
17:09:25:099 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:25:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:26:096 Idle timer triggered
17:09:26:099 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:26:102 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:27:096 Idle timer triggered
17:09:27:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:27:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:28:114 Idle timer triggered
17:09:28:117 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:28:118 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:29:139 Idle timer triggered
17:09:29:145 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:29:147 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:30:136 API error 1, /PHuXirAnrXI2euYOFmVBUmvOTv4CHEqdOWbueYJ_WbU/api/config, unauthorized user
17:09:30:143 Idle timer triggered
17:09:30:145 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:30:149 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:31:096 Idle timer triggered
17:09:31:108 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:31:109 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:32:096 Idle timer triggered
17:09:32:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:32:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:33:096 Idle timer triggered
17:09:33:103 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:33:104 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:33:596 Daylight now: goldenHour2, status: 180, daylight: 0, dark: 0
17:09:34:096 Idle timer triggered
17:09:34:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:34:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:35:104 Idle timer triggered
17:09:35:107 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:35:108 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:36:096 Idle timer triggered
17:09:36:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:36:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:37:096 Idle timer triggered
17:09:37:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:37:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:37:225 API error 1, /PHuXirAnrXI2euYOFmVBUmvOTv4CHEqdOWbueYJ_WbU/api/config, unauthorized user
17:09:38:096 Idle timer triggered
17:09:38:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:38:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:38:960 APS-DATA.request id: 37, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:09:38:962    asdu (length: 2): 1e00
17:09:38:988 APS-DATA.confirm id: 37, status: 0x00 SUCCESS
17:09:38:990 APS-DATA.confirm request id: 37 -> confirmed, timeout 70309368
17:09:39:040 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:09:39:041    asdu: 1e000100012ed107ffff2e2100407128feff15cd0452e1120001ff
17:09:39:042 APS-DATA.indication request id: 37 -> finished
17:09:39:042 APS-DATA.request id: 37 erase from queue
17:09:39:043 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:09:39:106 Idle timer triggered
17:09:39:108 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:39:109 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:40:096 Idle timer triggered
17:09:40:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:40:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:41:096 Idle timer triggered
17:09:41:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:41:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:42:096 Idle timer triggered
17:09:42:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:42:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:43:095 Idle timer triggered
17:09:43:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:43:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:43:595 Daylight now: goldenHour2, status: 180, daylight: 0, dark: 0
17:09:44:096 Idle timer triggered
17:09:44:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:44:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:44:328 API error 1, /PHuXirAnrXI2euYOFmVBUmvOTv4CHEqdOWbueYJ_WbU/api/config, unauthorized user
17:09:45:096 Idle timer triggered
17:09:45:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:45:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:46:096 Idle timer triggered
17:09:46:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:46:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:47:096 APS-DATA.request id: 71, addrmode: 0x02, addr: 0xfffc, profile: 0x0000, cluster: 0x0036, ep: 0x00 -> 0x00 queue: 0 len: 3 tx.options 0x00
17:09:47:097    asdu (length: 3): 143201
17:09:47:098 send permit join, duration: 50
17:09:47:099 APS-DATA.request id: 72, addrmode: 0x02, addr: 0xfffc, profile: 0xA1E0, cluster: 0x0021, ep: 0xF2 -> 0xF2 queue: 1 len: 6 tx.options 0x00
17:09:47:100    asdu (length: 6): 191a020b2800
17:09:47:101 Idle timer triggered
17:09:47:101 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:47:102 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:47:807 APS-DATA.confirm id: 71, status: 0x00 SUCCESS
17:09:47:817 APS-DATA.confirm id: 72, status: 0x00 SUCCESS
17:09:47:839 aps request id: 71 finished, erase from queue
17:09:47:920 aps request id: 72 finished, erase from queue
17:09:48:096 sql exec SELECT conf FROM zbconf ORDER BY rowid desc limit 1
17:09:48:098 Idle timer triggered
17:09:48:100 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:48:101 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:49:096 Idle timer triggered
17:09:49:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:49:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:50:096 Idle timer triggered
17:09:50:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:50:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:51:096 Idle timer triggered
17:09:51:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:51:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:51:440 API error 1, /PHuXirAnrXI2euYOFmVBUmvOTv4CHEqdOWbueYJ_WbU/api/config, unauthorized user
17:09:52:096 Idle timer triggered
17:09:52:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:52:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:53:096 Idle timer triggered
17:09:53:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:53:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:53:596 Daylight now: goldenHour2, status: 180, daylight: 0, dark: 0
17:09:54:096 Idle timer triggered
17:09:54:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:54:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:55:096 Idle timer triggered
17:09:55:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:55:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:55:760 APS-DATA.request id: 108, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:09:55:762    asdu (length: 2): 1f00
17:09:55:786 APS-DATA.confirm id: 108, status: 0x00 SUCCESS
17:09:55:788 APS-DATA.confirm request id: 108 -> confirmed, timeout 70326167
17:09:55:850 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:09:55:851    asdu: 1f000100012ed107ffff2e2100407128feff15cd0452e1120001ff
17:09:55:852 APS-DATA.indication request id: 108 -> finished
17:09:55:852 APS-DATA.request id: 108 erase from queue
17:09:55:853 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:09:56:095 Idle timer triggered
17:09:56:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:56:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:57:096 Idle timer triggered
17:09:57:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:57:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:58:095 Idle timer triggered
17:09:58:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:58:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:58:540 API error 1, /PHuXirAnrXI2euYOFmVBUmvOTv4CHEqdOWbueYJ_WbU/api/config, unauthorized user
17:09:59:095 Idle timer triggered
17:09:59:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:59:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:00:096 Idle timer triggered
17:10:00:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:00:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:01:096 Idle timer triggered
17:10:01:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:01:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:02:095 Idle timer triggered
17:10:02:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:02:097 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:03:096 Idle timer triggered
17:10:03:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:03:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:03:596 Daylight now: goldenHour2, status: 180, daylight: 0, dark: 0
17:10:03:616 Master: read param with arg 0x19
17:10:03:643 Device TTL 1529 s flags: 0x7
17:10:04:096 Idle timer triggered
17:10:04:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:04:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:05:096 Idle timer triggered
17:10:05:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:05:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:05:196 sensor 2 (TRADFRI motion sensor): disable presence
17:10:05:396 Set sensor check interval to 1000 milliseconds
17:10:05:647 API error 1, /PHuXirAnrXI2euYOFmVBUmvOTv4CHEqdOWbueYJ_WbU/api/config, unauthorized user
17:10:06:096 Idle timer triggered
17:10:06:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:06:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:07:100 Idle timer triggered
17:10:07:102 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:07:103 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:08:096 Idle timer triggered
17:10:08:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:08:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:09:096 Idle timer triggered
17:10:09:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:09:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:09:452 created username: 7BB98E41FA, devicetype: Phoscon#B1664x937
17:10:10:096 Idle timer triggered
17:10:10:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:10:097 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:10:627 New websocket 127.0.0.1:36936 (state: 3) 
17:10:11:096 Idle timer triggered
17:10:11:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:11:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:12:096 Idle timer triggered
17:10:12:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:12:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:12:560 APS-DATA.request id: 177, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:10:12:562    asdu (length: 2): 2000
17:10:12:586 APS-DATA.confirm id: 177, status: 0x00 SUCCESS
17:10:12:588 APS-DATA.confirm request id: 177 -> confirmed, timeout 70342968
17:10:12:639 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:10:12:640    asdu: 20000100012ed107ffff2e2100407128feff15cd0452e1120001ff
17:10:12:641 APS-DATA.indication request id: 177 -> finished
17:10:12:641 APS-DATA.request id: 177 erase from queue
17:10:12:642 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:10:13:096 Idle timer triggered
17:10:13:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:13:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:13:595 Daylight now: goldenHour2, status: 180, daylight: 0, dark: 0
17:10:14:096 Idle timer triggered
17:10:14:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:14:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:15:095 Idle timer triggered
17:10:15:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:15:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:16:096 Idle timer triggered
17:10:16:099 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:16:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:17:096 Idle timer triggered
17:10:17:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:17:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:18:096 Idle timer triggered
17:10:18:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:18:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:19:096 Idle timer triggered
17:10:19:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:19:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:20:096 Idle timer triggered
17:10:20:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:20:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:21:095 Idle timer triggered
17:10:21:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:21:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:22:096 Idle timer triggered
17:10:22:099 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:22:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:23:096 Idle timer triggered
17:10:23:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:23:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:23:596 Daylight now: goldenHour2, status: 180, daylight: 0, dark: 0
17:10:23:609 Websocket disconnected 127.0.0.1:36936, state: 0, close-code: 1000, reason: 
17:10:24:096 Idle timer triggered
17:10:24:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:24:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:24:712 New websocket 127.0.0.1:36986 (state: 3) 
17:10:25:096 Idle timer triggered
17:10:25:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:25:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:26:096 Idle timer triggered
17:10:26:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:26:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:27:096 Idle timer triggered
17:10:27:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:27:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:28:096 Idle timer triggered
17:10:28:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:28:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:29:096 Idle timer triggered
17:10:29:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:29:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:29:128 APS-DATA.request id: 246, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:10:29:129    asdu (length: 2): 2100
17:10:29:173 APS-DATA.confirm id: 246, status: 0x00 SUCCESS
17:10:29:174 APS-DATA.confirm request id: 246 -> confirmed, timeout 70359535
17:10:29:220 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:10:29:221    asdu: 21000100012ed107ffff2e2100407128feff15cd0452e1120001ff
17:10:29:222 APS-DATA.indication request id: 246 -> finished
17:10:29:223 APS-DATA.request id: 246 erase from queue
17:10:29:224 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:10:30:096 Idle timer triggered
17:10:30:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:30:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:31:095 Idle timer triggered
17:10:31:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:31:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:32:096 Idle timer triggered
17:10:32:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:32:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:33:096 Idle timer triggered
17:10:33:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:33:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:33:596 Daylight now: goldenHour2, status: 180, daylight: 0, dark: 0
17:10:34:096 Idle timer triggered
17:10:34:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:34:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:35:096 Idle timer triggered
17:10:35:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:35:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:36:096 Idle timer triggered
17:10:36:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:36:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:37:096 APS-DATA.request id: 23, addrmode: 0x02, addr: 0xfffc, profile: 0x0000, cluster: 0x0036, ep: 0x00 -> 0x00 queue: 0 len: 3 tx.options 0x00
17:10:37:098    asdu (length: 3): 150001
17:10:37:100 send permit join, duration: 0
17:10:37:101 Idle timer triggered
17:10:37:103 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:37:104 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:37:784 APS-DATA.confirm id: 23, status: 0x00 SUCCESS
17:10:37:848 aps request id: 23 finished, erase from queue
17:10:37:874 Search sensors done
17:10:38:096 Idle timer triggered
17:10:38:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:38:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:39:096 APS-DATA.request id: 32, addrmode: 0x02, addr: 0xfffc, profile: 0x0000, cluster: 0x0036, ep: 0x00 -> 0x00 queue: 0 len: 3 tx.options 0x00
17:10:39:097    asdu (length: 3): 164101
17:10:39:099 send permit join, duration: 65
17:10:39:100 APS-DATA.request id: 33, addrmode: 0x02, addr: 0xfffc, profile: 0xA1E0, cluster: 0x0021, ep: 0xF2 -> 0xF2 queue: 1 len: 6 tx.options 0x00
17:10:39:101    asdu (length: 6): 191b020b2800
17:10:39:102 Idle timer triggered
17:10:39:103 Force read attributes for ZHAPresence SensorNode TRÅDFRI Motion sensor
17:10:39:104 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:39:105 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:39:812 APS-DATA.confirm id: 32, status: 0x00 SUCCESS
17:10:39:823 APS-DATA.confirm id: 33, status: 0x00 SUCCESS
17:10:39:848 aps request id: 32 finished, erase from queue
17:10:39:928 aps request id: 33 finished, erase from queue
17:10:40:096 Wait 3s till query finished
17:10:41:096 Wait 2s till query finished
17:10:42:096 Wait 1s till query finished
17:10:43:096 Wait 0s till query finished
17:10:43:596 Daylight now: goldenHour2, status: 180, daylight: 0, dark: 0
17:10:43:986 APS-DATA.indication srcAddr: 0xe152, srcEp: 0x01 dstAddrMode: 1, profile: 0x0104, cluster: 0x0006, lqi: 255, rssi: -49
17:10:43:988    asdu: 0154420008070000
17:10:43:989 APS-DATA.indication from child 0xE152
17:10:43:991 [INFO] - Button 1002 - TRADFRI motion sensor, broadcast to: 0x0002, endpoint: 0x01, cluster: ONOFF (0x0006), action: On with timed off, payload: 0008070000, zclSeq: 84
17:10:43:993 Force binding of attribute reporting for sensor TRÅDFRI Motion sensor
17:10:44:017 Websocket 127.0.0.1:36986 send message: {"config":{"alert":"none","battery":74,"delay":180,"duration":60,"group":"2","on":true,"reachable":true},"e":"changed","id":"2","r":"sensors","t":"event","uniqueid":"04:cd:15:ff:fe:28:71:40-01-0006"} (ret = 199)
17:10:44:019 Websocket 127.0.0.1:36986 send message: {"e":"changed","id":"2","r":"sensors","state":{"dark":true,"lastupdated":"2022-02-04T16:10:43.993","presence":true},"t":"event","uniqueid":"04:cd:15:ff:fe:28:71:40-01-0006"} (ret = 173)
17:10:44:021 Websocket 127.0.0.1:36986 send message: {"attr":{"id":"2","lastannounced":"2022-02-03T20:42:51Z","lastseen":"2022-02-04T16:10Z","manufacturername":"IKEA of Sweden","modelid":"TRADFRI motion sensor","name":"TRÅDFRI Motion sensor","swversion":"2.0.022","type":"ZHAPresence","uniqueid":"04:cd:15:ff:fe:28:71:40-01-0006"},"e":"changed","id":"2","r":"sensors","t":"event","uniqueid":"04:cd:15:ff:fe:28:71:40-01-0006"} (ret = 373)
17:10:44:096 Idle timer triggered
17:10:44:097 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:44:595 Set sensor check interval to 100 milliseconds
17:10:45:096 Idle timer triggered
17:10:45:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:45:928 APS-DATA.request id: 63, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:10:45:929    asdu (length: 2): 2200
17:10:45:955 APS-DATA.confirm id: 63, status: 0x00 SUCCESS
17:10:45:956 APS-DATA.confirm request id: 63 -> confirmed, timeout 70376335
17:10:46:019 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:10:46:020    asdu: 22000300012ed107ffff2e2100407128feff15cd0452e1120001ff
17:10:46:021 APS-DATA.indication request id: 63 -> finished
17:10:46:022 APS-DATA.request id: 63 erase from queue
17:10:46:098 Idle timer triggered
17:10:46:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:47:096 Idle timer triggered
17:10:47:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:48:096 Idle timer triggered
17:10:48:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:49:096 sql exec SELECT conf FROM zbconf ORDER BY rowid desc limit 1
17:10:49:098 Idle timer triggered
17:10:49:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:50:096 Idle timer triggered
17:10:50:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:51:096 Idle timer triggered
17:10:51:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:52:096 Idle timer triggered
17:10:52:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:53:096 Idle timer triggered
17:10:53:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:53:598 Daylight now: goldenHour2, status: 180, daylight: 0, dark: 0
17:10:54:096 Idle timer triggered
17:10:54:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:54:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:55:096 Idle timer triggered
17:10:55:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:55:097 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:56:095 Idle timer triggered
17:10:56:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:56:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:57:096 Idle timer triggered
17:10:57:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:57:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:58:096 Idle timer triggered
17:10:58:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:58:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:59:096 Idle timer triggered
17:10:59:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:59:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:00:096 Idle timer triggered
17:11:00:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:00:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:01:095 Idle timer triggered
17:11:01:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:01:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:01:287 APS-DATA.request id: 126, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:11:01:289    asdu (length: 2): 2301
17:11:01:313 APS-DATA.confirm id: 126, status: 0x00 SUCCESS
17:11:01:314 APS-DATA.confirm request id: 126 -> confirmed, timeout 70391695
17:11:01:367 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:11:01:368    asdu: 23000301012ed107ffff2e21006bac1afeff14430cfc3b150001ff
17:11:01:368 APS-DATA.indication request id: 126 -> finished
17:11:01:369 APS-DATA.request id: 126 erase from queue
17:11:01:369     * different nwk address 0x0157 / 0x3BFC
17:11:01:370 neigbor 0x0c4314fffe1aac6b is unknown child
17:11:02:096 Idle timer triggered
17:11:02:100 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:02:104 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:03:096 Idle timer triggered
17:11:03:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:03:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:03:595 Daylight now: goldenHour2, status: 180, daylight: 0, dark: 0
17:11:03:612 Master: read param with arg 0x19
17:11:03:679 Device TTL 1468 s flags: 0x7
17:11:04:095 Idle timer triggered
17:11:04:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:04:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:05:096 Idle timer triggered
17:11:05:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:05:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:06:096 Idle timer triggered
17:11:06:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:06:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:07:096 Idle timer triggered
17:11:07:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:07:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:08:096 Idle timer triggered
17:11:08:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:08:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:09:095 Idle timer triggered
17:11:09:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:09:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:10:096 Idle timer triggered
17:11:10:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:10:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:11:096 Idle timer triggered
17:11:11:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:11:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:12:096 Idle timer triggered
17:11:12:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:12:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:13:096 Idle timer triggered
17:11:13:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:13:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:13:596 Daylight now: goldenHour2, status: 180, daylight: 0, dark: 0
17:11:14:096 Idle timer triggered
17:11:14:099 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:14:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:15:096 Idle timer triggered
17:11:15:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:15:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:16:096 Idle timer triggered
17:11:16:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:16:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:16:648 APS-DATA.request id: 190, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:11:16:650    asdu (length: 2): 2402
17:11:16:674 APS-DATA.confirm id: 190, status: 0x00 SUCCESS
17:11:16:675 APS-DATA.confirm request id: 190 -> confirmed, timeout 70407056
17:11:16:727 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:11:16:728    asdu: 24000302012ed107ffff2e2100c69064feff65112c3b92150001ff
17:11:16:729 APS-DATA.indication request id: 190 -> finished
17:11:16:730 APS-DATA.request id: 190 erase from queue
17:11:16:730 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:11:16:731     * different nwk address 0xFFD8 / 0x923B
17:11:16:731 neigbor 0x2c1165fffe6490c6 is unknown child
17:11:16:803 Websocket 127.0.0.1:36986 send message: {"attr":{"id":"1","lastannounced":null,"lastseen":"2022-02-04T16:11Z","manufacturername":"dresden elektronik","modelid":"ConBee II","name":"Configuration tool 1","swversion":"0x26720700","type":"Configuration tool","uniqueid":"00:21:2e:ff:ff:07:d1:2e-01"},"e":"changed","id":"1","r":"lights","t":"event","uniqueid":"00:21:2e:ff:ff:07:d1:2e-01"} (ret = 344)
17:11:17:096 Idle timer triggered
17:11:17:099 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:17:101 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:18:096 Idle timer triggered
17:11:18:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:18:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:19:096 Idle timer triggered
17:11:19:100 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:19:102 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:20:096 Idle timer triggered
17:11:20:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:20:101 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:21:096 Idle timer triggered
17:11:21:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:21:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:21:596 GW firmware version: 0x26720700
17:11:21:598 GW firmware version is up to date: 0x26720700
17:11:22:096 Idle timer triggered
17:11:22:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:22:097 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:23:096 Idle timer triggered
17:11:23:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:23:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:23:598 Daylight now: goldenHour2, status: 180, daylight: 0, dark: 0
17:11:24:095 Idle timer triggered
17:11:24:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:24:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:25:096 Idle timer triggered
17:11:25:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:25:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:26:096 Idle timer triggered
17:11:26:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:26:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:27:096 Idle timer triggered
17:11:27:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:27:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:28:096 Idle timer triggered
17:11:28:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:28:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:29:096 Idle timer triggered
17:11:29:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:29:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:30:095 Idle timer triggered
17:11:30:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:30:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:31:096 Idle timer triggered
17:11:31:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:31:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:32:096 Idle timer triggered
17:11:32:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:32:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:33:096 Idle timer triggered
17:11:33:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:33:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:33:448 APS-DATA.request id: 3, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:11:33:449    asdu (length: 2): 2500
17:11:33:472 APS-DATA.confirm id: 3, status: 0x00 SUCCESS
17:11:33:473 APS-DATA.confirm request id: 3 -> confirmed, timeout 70423854
17:11:33:525 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:11:33:526    asdu: 25000300012ed107ffff2e2100407128feff15cd0452e1120001ff
17:11:33:527 APS-DATA.indication request id: 3 -> finished
17:11:33:528 APS-DATA.request id: 3 erase from queue
17:11:33:596 Daylight now: goldenHour2, status: 180, daylight: 0, dark: 0
17:11:34:096 Idle timer triggered
17:11:34:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:34:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:35:095 Idle timer triggered
17:11:35:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:35:097 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:36:096 Idle timer triggered
17:11:36:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:36:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:37:096 Idle timer triggered
17:11:37:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:37:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:38:096 Idle timer triggered
17:11:38:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:38:101 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:39:096 Idle timer triggered
17:11:39:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:39:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:40:096 APS-DATA.request id: 31, addrmode: 0x02, addr: 0xfffc, profile: 0x0000, cluster: 0x0036, ep: 0x00 -> 0x00 queue: 0 len: 3 tx.options 0x00
17:11:40:097    asdu (length: 3): 174101
17:11:40:098 send permit join, duration: 65
17:11:40:099 APS-DATA.request id: 32, addrmode: 0x02, addr: 0xfffc, profile: 0xA1E0, cluster: 0x0021, ep: 0xF2 -> 0xF2 queue: 1 len: 6 tx.options 0x00
17:11:40:100    asdu (length: 6): 191c020b2800
17:11:40:101 Idle timer triggered
17:11:40:102 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:40:102 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:40:804 APS-DATA.confirm id: 31, status: 0x00 SUCCESS
17:11:40:815 aps request id: 31 finished, erase from queue
17:11:40:822 APS-DATA.confirm id: 32, status: 0x00 SUCCESS
17:11:40:888 aps request id: 32 finished, erase from queue
17:11:41:096 Idle timer triggered
17:11:41:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:41:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:42:096 Idle timer triggered
17:11:42:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:42:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:43:096 Idle timer triggered
17:11:43:099 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:43:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:43:596 Daylight now: goldenHour2, status: 180, daylight: 0, dark: 0
17:11:43:996 sensor 2 (TRADFRI motion sensor): disable presence
17:11:44:006 Websocket 127.0.0.1:36986 send message: {"e":"changed","id":"2","r":"sensors","state":{"dark":true,"lastupdated":"2022-02-04T16:11:43.998","presence":false},"t":"event","uniqueid":"04:cd:15:ff:fe:28:71:40-01-0006"} (ret = 174)
17:11:44:096 Idle timer triggered
17:11:44:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:44:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:44:195 Set sensor check interval to 1000 milliseconds
17:11:45:095 Idle timer triggered
17:11:45:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:45:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:46:096 Idle timer triggered
17:11:46:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:46:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:47:096 Idle timer triggered
17:11:47:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:47:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:48:096 Idle timer triggered
17:11:48:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:48:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:48:808 APS-DATA.request id: 68, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:11:48:810    asdu (length: 2): 2601
17:11:48:833 APS-DATA.confirm id: 68, status: 0x00 SUCCESS
17:11:48:835 APS-DATA.confirm request id: 68 -> confirmed, timeout 70439216
17:11:48:890 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:11:48:891    asdu: 2600010100
17:11:48:891 APS-DATA.indication request id: 68 -> finished
17:11:48:892 APS-DATA.request id: 68 erase from queue

Vanaf 17:11:16:648 schakel ik de lampen wederom uit nadat ze langzaamaan in en uit faden.

[Mimiix]

jja2000 schreef op vrijdag 4 februari 2022 @ 17:14:
[...]


Poging 2 (Ik gebruikte de HASS vnc viewer, nu dus TigerVNC):

code:

17:09:22:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:22:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:22:448 APS-DATA.request id: 225, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:09:22:450    asdu (length: 2): 1d00
17:09:22:464 APS-DATA.confirm id: 225, status: 0x00 SUCCESS
17:09:22:465 APS-DATA.confirm request id: 225 -> confirmed, timeout 70292856
17:09:22:469 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:09:22:470    asdu: 1d000100012ed107ffff2e2100407128feff15cd0452e1120001ff
17:09:22:471 APS-DATA.indication request id: 225 -> finished
17:09:22:472 APS-DATA.request id: 225 erase from queue
17:09:22:472 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:09:22:720 API error 1, /PHuXirAnrXI2euYOFmVBUmvOTv4CHEqdOWbueYJ_WbU/api/config, unauthorized user
17:09:23:096 Idle timer triggered
17:09:23:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:23:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:23:596 Daylight now: goldenHour2, status: 180, daylight: 0, dark: 0
17:09:24:096 Idle timer triggered
17:09:24:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:24:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:25:096 Idle timer triggered
17:09:25:099 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:25:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:26:096 Idle timer triggered
17:09:26:099 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:26:102 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:27:096 Idle timer triggered
17:09:27:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:27:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:28:114 Idle timer triggered
17:09:28:117 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:28:118 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:29:139 Idle timer triggered
17:09:29:145 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:29:147 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:30:136 API error 1, /PHuXirAnrXI2euYOFmVBUmvOTv4CHEqdOWbueYJ_WbU/api/config, unauthorized user
17:09:30:143 Idle timer triggered
17:09:30:145 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:30:149 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:31:096 Idle timer triggered
17:09:31:108 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:31:109 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:32:096 Idle timer triggered
17:09:32:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:32:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:33:096 Idle timer triggered
17:09:33:103 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:33:104 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:33:596 Daylight now: goldenHour2, status: 180, daylight: 0, dark: 0
17:09:34:096 Idle timer triggered
17:09:34:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:34:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:35:104 Idle timer triggered
17:09:35:107 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:35:108 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:36:096 Idle timer triggered
17:09:36:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:36:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:37:096 Idle timer triggered
17:09:37:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:37:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:37:225 API error 1, /PHuXirAnrXI2euYOFmVBUmvOTv4CHEqdOWbueYJ_WbU/api/config, unauthorized user
17:09:38:096 Idle timer triggered
17:09:38:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:38:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:38:960 APS-DATA.request id: 37, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:09:38:962    asdu (length: 2): 1e00
17:09:38:988 APS-DATA.confirm id: 37, status: 0x00 SUCCESS
17:09:38:990 APS-DATA.confirm request id: 37 -> confirmed, timeout 70309368
17:09:39:040 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:09:39:041    asdu: 1e000100012ed107ffff2e2100407128feff15cd0452e1120001ff
17:09:39:042 APS-DATA.indication request id: 37 -> finished
17:09:39:042 APS-DATA.request id: 37 erase from queue
17:09:39:043 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:09:39:106 Idle timer triggered
17:09:39:108 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:39:109 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:40:096 Idle timer triggered
17:09:40:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:40:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:41:096 Idle timer triggered
17:09:41:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:41:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:42:096 Idle timer triggered
17:09:42:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:42:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:43:095 Idle timer triggered
17:09:43:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:43:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:43:595 Daylight now: goldenHour2, status: 180, daylight: 0, dark: 0
17:09:44:096 Idle timer triggered
17:09:44:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:44:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:44:328 API error 1, /PHuXirAnrXI2euYOFmVBUmvOTv4CHEqdOWbueYJ_WbU/api/config, unauthorized user
17:09:45:096 Idle timer triggered
17:09:45:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:45:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:46:096 Idle timer triggered
17:09:46:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:46:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:47:096 APS-DATA.request id: 71, addrmode: 0x02, addr: 0xfffc, profile: 0x0000, cluster: 0x0036, ep: 0x00 -> 0x00 queue: 0 len: 3 tx.options 0x00
17:09:47:097    asdu (length: 3): 143201
17:09:47:098 send permit join, duration: 50
17:09:47:099 APS-DATA.request id: 72, addrmode: 0x02, addr: 0xfffc, profile: 0xA1E0, cluster: 0x0021, ep: 0xF2 -> 0xF2 queue: 1 len: 6 tx.options 0x00
17:09:47:100    asdu (length: 6): 191a020b2800
17:09:47:101 Idle timer triggered
17:09:47:101 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:47:102 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:47:807 APS-DATA.confirm id: 71, status: 0x00 SUCCESS
17:09:47:817 APS-DATA.confirm id: 72, status: 0x00 SUCCESS
17:09:47:839 aps request id: 71 finished, erase from queue
17:09:47:920 aps request id: 72 finished, erase from queue
17:09:48:096 sql exec SELECT conf FROM zbconf ORDER BY rowid desc limit 1
17:09:48:098 Idle timer triggered
17:09:48:100 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:48:101 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:49:096 Idle timer triggered
17:09:49:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:49:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:50:096 Idle timer triggered
17:09:50:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:50:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:51:096 Idle timer triggered
17:09:51:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:51:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:51:440 API error 1, /PHuXirAnrXI2euYOFmVBUmvOTv4CHEqdOWbueYJ_WbU/api/config, unauthorized user
17:09:52:096 Idle timer triggered
17:09:52:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:52:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:53:096 Idle timer triggered
17:09:53:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:53:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:53:596 Daylight now: goldenHour2, status: 180, daylight: 0, dark: 0
17:09:54:096 Idle timer triggered
17:09:54:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:54:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:55:096 Idle timer triggered
17:09:55:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:55:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:55:760 APS-DATA.request id: 108, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:09:55:762    asdu (length: 2): 1f00
17:09:55:786 APS-DATA.confirm id: 108, status: 0x00 SUCCESS
17:09:55:788 APS-DATA.confirm request id: 108 -> confirmed, timeout 70326167
17:09:55:850 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:09:55:851    asdu: 1f000100012ed107ffff2e2100407128feff15cd0452e1120001ff
17:09:55:852 APS-DATA.indication request id: 108 -> finished
17:09:55:852 APS-DATA.request id: 108 erase from queue
17:09:55:853 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:09:56:095 Idle timer triggered
17:09:56:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:56:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:57:096 Idle timer triggered
17:09:57:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:57:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:58:095 Idle timer triggered
17:09:58:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:58:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:09:58:540 API error 1, /PHuXirAnrXI2euYOFmVBUmvOTv4CHEqdOWbueYJ_WbU/api/config, unauthorized user
17:09:59:095 Idle timer triggered
17:09:59:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:09:59:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:00:096 Idle timer triggered
17:10:00:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:00:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:01:096 Idle timer triggered
17:10:01:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:01:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:02:095 Idle timer triggered
17:10:02:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:02:097 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:03:096 Idle timer triggered
17:10:03:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:03:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:03:596 Daylight now: goldenHour2, status: 180, daylight: 0, dark: 0
17:10:03:616 Master: read param with arg 0x19
17:10:03:643 Device TTL 1529 s flags: 0x7
17:10:04:096 Idle timer triggered
17:10:04:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:04:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:05:096 Idle timer triggered
17:10:05:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:05:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:05:196 sensor 2 (TRADFRI motion sensor): disable presence
17:10:05:396 Set sensor check interval to 1000 milliseconds
17:10:05:647 API error 1, /PHuXirAnrXI2euYOFmVBUmvOTv4CHEqdOWbueYJ_WbU/api/config, unauthorized user
17:10:06:096 Idle timer triggered
17:10:06:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:06:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:07:100 Idle timer triggered
17:10:07:102 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:07:103 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:08:096 Idle timer triggered
17:10:08:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:08:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:09:096 Idle timer triggered
17:10:09:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:09:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:09:452 created username: 7BB98E41FA, devicetype: Phoscon#B1664x937
17:10:10:096 Idle timer triggered
17:10:10:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:10:097 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:10:627 New websocket 127.0.0.1:36936 (state: 3) 
17:10:11:096 Idle timer triggered
17:10:11:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:11:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:12:096 Idle timer triggered
17:10:12:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:12:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:12:560 APS-DATA.request id: 177, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:10:12:562    asdu (length: 2): 2000
17:10:12:586 APS-DATA.confirm id: 177, status: 0x00 SUCCESS
17:10:12:588 APS-DATA.confirm request id: 177 -> confirmed, timeout 70342968
17:10:12:639 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:10:12:640    asdu: 20000100012ed107ffff2e2100407128feff15cd0452e1120001ff
17:10:12:641 APS-DATA.indication request id: 177 -> finished
17:10:12:641 APS-DATA.request id: 177 erase from queue
17:10:12:642 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:10:13:096 Idle timer triggered
17:10:13:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:13:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:13:595 Daylight now: goldenHour2, status: 180, daylight: 0, dark: 0
17:10:14:096 Idle timer triggered
17:10:14:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:14:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:15:095 Idle timer triggered
17:10:15:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:15:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:16:096 Idle timer triggered
17:10:16:099 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:16:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:17:096 Idle timer triggered
17:10:17:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:17:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:18:096 Idle timer triggered
17:10:18:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:18:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:19:096 Idle timer triggered
17:10:19:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:19:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:20:096 Idle timer triggered
17:10:20:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:20:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:21:095 Idle timer triggered
17:10:21:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:21:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:22:096 Idle timer triggered
17:10:22:099 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:22:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:23:096 Idle timer triggered
17:10:23:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:23:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:23:596 Daylight now: goldenHour2, status: 180, daylight: 0, dark: 0
17:10:23:609 Websocket disconnected 127.0.0.1:36936, state: 0, close-code: 1000, reason: 
17:10:24:096 Idle timer triggered
17:10:24:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:24:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:24:712 New websocket 127.0.0.1:36986 (state: 3) 
17:10:25:096 Idle timer triggered
17:10:25:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:25:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:26:096 Idle timer triggered
17:10:26:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:26:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:27:096 Idle timer triggered
17:10:27:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:27:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:28:096 Idle timer triggered
17:10:28:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:28:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:29:096 Idle timer triggered
17:10:29:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:29:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:29:128 APS-DATA.request id: 246, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:10:29:129    asdu (length: 2): 2100
17:10:29:173 APS-DATA.confirm id: 246, status: 0x00 SUCCESS
17:10:29:174 APS-DATA.confirm request id: 246 -> confirmed, timeout 70359535
17:10:29:220 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:10:29:221    asdu: 21000100012ed107ffff2e2100407128feff15cd0452e1120001ff
17:10:29:222 APS-DATA.indication request id: 246 -> finished
17:10:29:223 APS-DATA.request id: 246 erase from queue
17:10:29:224 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:10:30:096 Idle timer triggered
17:10:30:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:30:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:31:095 Idle timer triggered
17:10:31:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:31:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:32:096 Idle timer triggered
17:10:32:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:32:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:33:096 Idle timer triggered
17:10:33:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:33:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:33:596 Daylight now: goldenHour2, status: 180, daylight: 0, dark: 0
17:10:34:096 Idle timer triggered
17:10:34:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:34:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:35:096 Idle timer triggered
17:10:35:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:35:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:36:096 Idle timer triggered
17:10:36:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:36:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:37:096 APS-DATA.request id: 23, addrmode: 0x02, addr: 0xfffc, profile: 0x0000, cluster: 0x0036, ep: 0x00 -> 0x00 queue: 0 len: 3 tx.options 0x00
17:10:37:098    asdu (length: 3): 150001
17:10:37:100 send permit join, duration: 0
17:10:37:101 Idle timer triggered
17:10:37:103 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:37:104 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:37:784 APS-DATA.confirm id: 23, status: 0x00 SUCCESS
17:10:37:848 aps request id: 23 finished, erase from queue
17:10:37:874 Search sensors done
17:10:38:096 Idle timer triggered
17:10:38:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:38:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:39:096 APS-DATA.request id: 32, addrmode: 0x02, addr: 0xfffc, profile: 0x0000, cluster: 0x0036, ep: 0x00 -> 0x00 queue: 0 len: 3 tx.options 0x00
17:10:39:097    asdu (length: 3): 164101
17:10:39:099 send permit join, duration: 65
17:10:39:100 APS-DATA.request id: 33, addrmode: 0x02, addr: 0xfffc, profile: 0xA1E0, cluster: 0x0021, ep: 0xF2 -> 0xF2 queue: 1 len: 6 tx.options 0x00
17:10:39:101    asdu (length: 6): 191b020b2800
17:10:39:102 Idle timer triggered
17:10:39:103 Force read attributes for ZHAPresence SensorNode TRÅDFRI Motion sensor
17:10:39:104 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:39:105 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:39:812 APS-DATA.confirm id: 32, status: 0x00 SUCCESS
17:10:39:823 APS-DATA.confirm id: 33, status: 0x00 SUCCESS
17:10:39:848 aps request id: 32 finished, erase from queue
17:10:39:928 aps request id: 33 finished, erase from queue
17:10:40:096 Wait 3s till query finished
17:10:41:096 Wait 2s till query finished
17:10:42:096 Wait 1s till query finished
17:10:43:096 Wait 0s till query finished
17:10:43:596 Daylight now: goldenHour2, status: 180, daylight: 0, dark: 0
17:10:43:986 APS-DATA.indication srcAddr: 0xe152, srcEp: 0x01 dstAddrMode: 1, profile: 0x0104, cluster: 0x0006, lqi: 255, rssi: -49
17:10:43:988    asdu: 0154420008070000
17:10:43:989 APS-DATA.indication from child 0xE152
17:10:43:991 [INFO] - Button 1002 - TRADFRI motion sensor, broadcast to: 0x0002, endpoint: 0x01, cluster: ONOFF (0x0006), action: On with timed off, payload: 0008070000, zclSeq: 84
17:10:43:993 Force binding of attribute reporting for sensor TRÅDFRI Motion sensor
17:10:44:017 Websocket 127.0.0.1:36986 send message: {"config":{"alert":"none","battery":74,"delay":180,"duration":60,"group":"2","on":true,"reachable":true},"e":"changed","id":"2","r":"sensors","t":"event","uniqueid":"04:cd:15:ff:fe:28:71:40-01-0006"} (ret = 199)
17:10:44:019 Websocket 127.0.0.1:36986 send message: {"e":"changed","id":"2","r":"sensors","state":{"dark":true,"lastupdated":"2022-02-04T16:10:43.993","presence":true},"t":"event","uniqueid":"04:cd:15:ff:fe:28:71:40-01-0006"} (ret = 173)
17:10:44:021 Websocket 127.0.0.1:36986 send message: {"attr":{"id":"2","lastannounced":"2022-02-03T20:42:51Z","lastseen":"2022-02-04T16:10Z","manufacturername":"IKEA of Sweden","modelid":"TRADFRI motion sensor","name":"TRÅDFRI Motion sensor","swversion":"2.0.022","type":"ZHAPresence","uniqueid":"04:cd:15:ff:fe:28:71:40-01-0006"},"e":"changed","id":"2","r":"sensors","t":"event","uniqueid":"04:cd:15:ff:fe:28:71:40-01-0006"} (ret = 373)
17:10:44:096 Idle timer triggered
17:10:44:097 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:44:595 Set sensor check interval to 100 milliseconds
17:10:45:096 Idle timer triggered
17:10:45:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:45:928 APS-DATA.request id: 63, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:10:45:929    asdu (length: 2): 2200
17:10:45:955 APS-DATA.confirm id: 63, status: 0x00 SUCCESS
17:10:45:956 APS-DATA.confirm request id: 63 -> confirmed, timeout 70376335
17:10:46:019 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:10:46:020    asdu: 22000300012ed107ffff2e2100407128feff15cd0452e1120001ff
17:10:46:021 APS-DATA.indication request id: 63 -> finished
17:10:46:022 APS-DATA.request id: 63 erase from queue
17:10:46:098 Idle timer triggered
17:10:46:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:47:096 Idle timer triggered
17:10:47:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:48:096 Idle timer triggered
17:10:48:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:49:096 sql exec SELECT conf FROM zbconf ORDER BY rowid desc limit 1
17:10:49:098 Idle timer triggered
17:10:49:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:50:096 Idle timer triggered
17:10:50:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:51:096 Idle timer triggered
17:10:51:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:52:096 Idle timer triggered
17:10:52:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:53:096 Idle timer triggered
17:10:53:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:53:598 Daylight now: goldenHour2, status: 180, daylight: 0, dark: 0
17:10:54:096 Idle timer triggered
17:10:54:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:54:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:55:096 Idle timer triggered
17:10:55:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:55:097 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:56:095 Idle timer triggered
17:10:56:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:56:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:57:096 Idle timer triggered
17:10:57:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:57:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:58:096 Idle timer triggered
17:10:58:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:58:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:10:59:096 Idle timer triggered
17:10:59:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:10:59:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:00:096 Idle timer triggered
17:11:00:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:00:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:01:095 Idle timer triggered
17:11:01:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:01:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:01:287 APS-DATA.request id: 126, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:11:01:289    asdu (length: 2): 2301
17:11:01:313 APS-DATA.confirm id: 126, status: 0x00 SUCCESS
17:11:01:314 APS-DATA.confirm request id: 126 -> confirmed, timeout 70391695
17:11:01:367 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:11:01:368    asdu: 23000301012ed107ffff2e21006bac1afeff14430cfc3b150001ff
17:11:01:368 APS-DATA.indication request id: 126 -> finished
17:11:01:369 APS-DATA.request id: 126 erase from queue
17:11:01:369     * different nwk address 0x0157 / 0x3BFC
17:11:01:370 neigbor 0x0c4314fffe1aac6b is unknown child
17:11:02:096 Idle timer triggered
17:11:02:100 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:02:104 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:03:096 Idle timer triggered
17:11:03:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:03:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:03:595 Daylight now: goldenHour2, status: 180, daylight: 0, dark: 0
17:11:03:612 Master: read param with arg 0x19
17:11:03:679 Device TTL 1468 s flags: 0x7
17:11:04:095 Idle timer triggered
17:11:04:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:04:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:05:096 Idle timer triggered
17:11:05:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:05:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:06:096 Idle timer triggered
17:11:06:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:06:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:07:096 Idle timer triggered
17:11:07:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:07:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:08:096 Idle timer triggered
17:11:08:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:08:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:09:095 Idle timer triggered
17:11:09:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:09:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:10:096 Idle timer triggered
17:11:10:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:10:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:11:096 Idle timer triggered
17:11:11:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:11:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:12:096 Idle timer triggered
17:11:12:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:12:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:13:096 Idle timer triggered
17:11:13:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:13:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:13:596 Daylight now: goldenHour2, status: 180, daylight: 0, dark: 0
17:11:14:096 Idle timer triggered
17:11:14:099 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:14:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:15:096 Idle timer triggered
17:11:15:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:15:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:16:096 Idle timer triggered
17:11:16:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:16:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:16:648 APS-DATA.request id: 190, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:11:16:650    asdu (length: 2): 2402
17:11:16:674 APS-DATA.confirm id: 190, status: 0x00 SUCCESS
17:11:16:675 APS-DATA.confirm request id: 190 -> confirmed, timeout 70407056
17:11:16:727 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:11:16:728    asdu: 24000302012ed107ffff2e2100c69064feff65112c3b92150001ff
17:11:16:729 APS-DATA.indication request id: 190 -> finished
17:11:16:730 APS-DATA.request id: 190 erase from queue
17:11:16:730 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:11:16:731     * different nwk address 0xFFD8 / 0x923B
17:11:16:731 neigbor 0x2c1165fffe6490c6 is unknown child
17:11:16:803 Websocket 127.0.0.1:36986 send message: {"attr":{"id":"1","lastannounced":null,"lastseen":"2022-02-04T16:11Z","manufacturername":"dresden elektronik","modelid":"ConBee II","name":"Configuration tool 1","swversion":"0x26720700","type":"Configuration tool","uniqueid":"00:21:2e:ff:ff:07:d1:2e-01"},"e":"changed","id":"1","r":"lights","t":"event","uniqueid":"00:21:2e:ff:ff:07:d1:2e-01"} (ret = 344)
17:11:17:096 Idle timer triggered
17:11:17:099 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:17:101 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:18:096 Idle timer triggered
17:11:18:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:18:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:19:096 Idle timer triggered
17:11:19:100 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:19:102 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:20:096 Idle timer triggered
17:11:20:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:20:101 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:21:096 Idle timer triggered
17:11:21:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:21:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:21:596 GW firmware version: 0x26720700
17:11:21:598 GW firmware version is up to date: 0x26720700
17:11:22:096 Idle timer triggered
17:11:22:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:22:097 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:23:096 Idle timer triggered
17:11:23:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:23:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:23:598 Daylight now: goldenHour2, status: 180, daylight: 0, dark: 0
17:11:24:095 Idle timer triggered
17:11:24:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:24:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:25:096 Idle timer triggered
17:11:25:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:25:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:26:096 Idle timer triggered
17:11:26:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:26:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:27:096 Idle timer triggered
17:11:27:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:27:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:28:096 Idle timer triggered
17:11:28:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:28:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:29:096 Idle timer triggered
17:11:29:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:29:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:30:095 Idle timer triggered
17:11:30:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:30:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:31:096 Idle timer triggered
17:11:31:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:31:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:32:096 Idle timer triggered
17:11:32:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:32:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:33:096 Idle timer triggered
17:11:33:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:33:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:33:448 APS-DATA.request id: 3, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:11:33:449    asdu (length: 2): 2500
17:11:33:472 APS-DATA.confirm id: 3, status: 0x00 SUCCESS
17:11:33:473 APS-DATA.confirm request id: 3 -> confirmed, timeout 70423854
17:11:33:525 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:11:33:526    asdu: 25000300012ed107ffff2e2100407128feff15cd0452e1120001ff
17:11:33:527 APS-DATA.indication request id: 3 -> finished
17:11:33:528 APS-DATA.request id: 3 erase from queue
17:11:33:596 Daylight now: goldenHour2, status: 180, daylight: 0, dark: 0
17:11:34:096 Idle timer triggered
17:11:34:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:34:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:35:095 Idle timer triggered
17:11:35:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:35:097 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:36:096 Idle timer triggered
17:11:36:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:36:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:37:096 Idle timer triggered
17:11:37:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:37:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:38:096 Idle timer triggered
17:11:38:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:38:101 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:39:096 Idle timer triggered
17:11:39:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:39:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:40:096 APS-DATA.request id: 31, addrmode: 0x02, addr: 0xfffc, profile: 0x0000, cluster: 0x0036, ep: 0x00 -> 0x00 queue: 0 len: 3 tx.options 0x00
17:11:40:097    asdu (length: 3): 174101
17:11:40:098 send permit join, duration: 65
17:11:40:099 APS-DATA.request id: 32, addrmode: 0x02, addr: 0xfffc, profile: 0xA1E0, cluster: 0x0021, ep: 0xF2 -> 0xF2 queue: 1 len: 6 tx.options 0x00
17:11:40:100    asdu (length: 6): 191c020b2800
17:11:40:101 Idle timer triggered
17:11:40:102 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:40:102 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:40:804 APS-DATA.confirm id: 31, status: 0x00 SUCCESS
17:11:40:815 aps request id: 31 finished, erase from queue
17:11:40:822 APS-DATA.confirm id: 32, status: 0x00 SUCCESS
17:11:40:888 aps request id: 32 finished, erase from queue
17:11:41:096 Idle timer triggered
17:11:41:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:41:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:42:096 Idle timer triggered
17:11:42:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:42:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:43:096 Idle timer triggered
17:11:43:099 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:43:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:43:596 Daylight now: goldenHour2, status: 180, daylight: 0, dark: 0
17:11:43:996 sensor 2 (TRADFRI motion sensor): disable presence
17:11:44:006 Websocket 127.0.0.1:36986 send message: {"e":"changed","id":"2","r":"sensors","state":{"dark":true,"lastupdated":"2022-02-04T16:11:43.998","presence":false},"t":"event","uniqueid":"04:cd:15:ff:fe:28:71:40-01-0006"} (ret = 174)
17:11:44:096 Idle timer triggered
17:11:44:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:44:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:44:195 Set sensor check interval to 1000 milliseconds
17:11:45:095 Idle timer triggered
17:11:45:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:45:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:46:096 Idle timer triggered
17:11:46:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:46:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:47:096 Idle timer triggered
17:11:47:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:47:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:48:096 Idle timer triggered
17:11:48:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:11:48:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:11:48:808 APS-DATA.request id: 68, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:11:48:810    asdu (length: 2): 2601
17:11:48:833 APS-DATA.confirm id: 68, status: 0x00 SUCCESS
17:11:48:835 APS-DATA.confirm request id: 68 -> confirmed, timeout 70439216
17:11:48:890 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:11:48:891    asdu: 2600010100
17:11:48:891 APS-DATA.indication request id: 68 -> finished
17:11:48:892 APS-DATA.request id: 68 erase from queue

Vanaf 17:11:16:648 schakel ik de lampen wederom uit nadat ze langzaamaan in en uit faden.

Ik zie geen permit join in de logs.
Zoekt phoscon wel naar devices?

[jja2000]

Mimiix schreef op vrijdag 4 februari 2022 @ 17:17:
[...]


Ik zie geen permit join in de logs.
Zoekt phoscon wel naar devices?

Jazeker! Ik vond het nogal moeilijk spotten dus waarschijnlijk heb ik hem per ongeluk niet meegekopieerd.
Hier zit de permit join wel bij bovenaan:

code:

17:22:37:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:22:37:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:22:38:095 APS-DATA.request id: 210, addrmode: 0x02, addr: 0xfffc, profile: 0x0000, cluster: 0x0036, ep: 0x00 -> 0x00 queue: 0 len: 3 tx.options 0x00
17:22:38:097    asdu (length: 3): 244101
17:22:38:099 send permit join, duration: 65
17:22:38:100 APS-DATA.request id: 211, addrmode: 0x02, addr: 0xfffc, profile: 0xA1E0, cluster: 0x0021, ep: 0xF2 -> 0xF2 queue: 1 len: 6 tx.options 0x00
17:22:38:101    asdu (length: 6): 1927020b2800
17:22:38:103 Idle timer triggered
17:22:38:104 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:22:38:105 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:22:38:783 APS-DATA.confirm id: 210, status: 0x00 SUCCESS
17:22:38:790 APS-DATA.confirm id: 211, status: 0x00 SUCCESS
17:22:38:856 aps request id: 210 finished, erase from queue
17:22:38:936 aps request id: 211 finished, erase from queue
17:22:39:095 Idle timer triggered
17:22:39:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:22:39:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:22:40:096 Idle timer triggered
17:22:40:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:22:40:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:22:41:096 Idle timer triggered
17:22:41:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:22:41:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:22:42:096 Idle timer triggered
17:22:42:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:22:42:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:22:43:096 Idle timer triggered
17:22:43:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:22:43:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:22:43:175 APS-DATA.request id: 233, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:22:43:177    asdu (length: 2): 4d00
17:22:43:190 APS-DATA.confirm id: 233, status: 0x00 SUCCESS
17:22:43:192 APS-DATA.confirm request id: 233 -> confirmed, timeout 71093583
17:22:43:199 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:22:43:200    asdu: 4d000100012ed107ffff2e2100407128feff15cd0452e1120001ff
17:22:43:201 APS-DATA.indication request id: 233 -> finished
17:22:43:202 APS-DATA.request id: 233 erase from queue
17:22:43:203 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:22:43:596 Daylight now: goldenHour2, status: 180, daylight: 0, dark: 0
17:22:44:096 Idle timer triggered
17:22:44:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:22:44:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:22:45:096 Idle timer triggered
17:22:45:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:22:45:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:22:46:095 Idle timer triggered
17:22:46:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:22:46:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:22:46:115 APS-DATA.indication srcAddr: 0xe152, srcEp: 0x01 dstAddrMode: 1, profile: 0x0104, cluster: 0x0006, lqi: 255, rssi: -47
17:22:46:116    asdu: 015a420008070000
17:22:46:117 APS-DATA.indication from child 0xE152
17:22:46:118 [INFO] - Button 1002 - TRADFRI motion sensor, broadcast to: 0x0002, endpoint: 0x01, cluster: ONOFF (0x0006), action: On with timed off, payload: 0008070000, zclSeq: 90
17:22:46:119 Force binding of attribute reporting for sensor TRÅDFRI Motion sensor
17:22:46:122 Websocket 127.0.0.1:36986 send message: {"config":{"alert":"none","battery":74,"delay":180,"duration":60,"group":"2","on":true,"reachable":true},"e":"changed","id":"2","r":"sensors","t":"event","uniqueid":"04:cd:15:ff:fe:28:71:40-01-0006"} (ret = 199)
17:22:46:125 Websocket 127.0.0.1:36986 send message: {"e":"changed","id":"2","r":"sensors","state":{"dark":true,"lastupdated":"2022-02-04T16:22:46.119","presence":true},"t":"event","uniqueid":"04:cd:15:ff:fe:28:71:40-01-0006"} (ret = 173)
17:22:46:127 Websocket 127.0.0.1:36986 send message: {"attr":{"id":"2","lastannounced":"2022-02-03T20:42:51Z","lastseen":"2022-02-04T16:22Z","manufacturername":"IKEA of Sweden","modelid":"TRADFRI motion sensor","name":"TRÅDFRI Motion sensor","swversion":"2.0.022","type":"ZHAPresence","uniqueid":"04:cd:15:ff:fe:28:71:40-01-0006"},"e":"changed","id":"2","r":"sensors","t":"event","uniqueid":"04:cd:15:ff:fe:28:71:40-01-0006"} (ret = 373)
17:22:47:096 Set sensor check interval to 100 milliseconds
17:22:47:098 Idle timer triggered
17:22:47:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:22:48:096 Idle timer triggered
17:22:48:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:22:49:096 Idle timer triggered
17:22:49:098 Force read attributes for ZHAPresence SensorNode TRÅDFRI Motion sensor
17:22:49:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:22:50:096 Wait 3s till query finished
17:22:51:096 Wait 2s till query finished
17:22:52:096 Wait 1s till query finished
17:22:53:096 Idle timer triggered
17:22:53:097 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:22:53:596 Daylight now: goldenHour2, status: 180, daylight: 0, dark: 0
17:22:54:096 Idle timer triggered
17:22:54:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:22:55:095 Idle timer triggered
17:22:55:097 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:22:56:095 Idle timer triggered
17:22:56:097 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:22:57:096 Idle timer triggered
17:22:57:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:22:57:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:22:58:096 Idle timer triggered
17:22:58:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:22:58:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:22:59:096 Idle timer triggered
17:22:59:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:22:59:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:22:59:976 APS-DATA.request id: 47, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:22:59:978    asdu (length: 2): 4e00
17:22:59:993 APS-DATA.confirm id: 47, status: 0x00 SUCCESS
17:22:59:994 APS-DATA.confirm request id: 47 -> confirmed, timeout 71110384
17:23:00:001 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:23:00:002    asdu: 4e000100012ed107ffff2e2100407128feff15cd0452e1120001ff
17:23:00:003 APS-DATA.indication request id: 47 -> finished
17:23:00:004 APS-DATA.request id: 47 erase from queue
17:23:00:004 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:23:00:096 Idle timer triggered
17:23:00:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:00:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:01:096 Idle timer triggered
17:23:01:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:01:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:02:095 Idle timer triggered
17:23:02:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:02:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:03:096 Idle timer triggered
17:23:03:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:03:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:03:595 Daylight now: goldenHour2, status: 180, daylight: 0, dark: 0
17:23:03:607 Master: read param with arg 0x19
17:23:03:636 Device TTL 745 s flags: 0x7
17:23:04:096 Idle timer triggered
17:23:04:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:04:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:05:096 sql exec SELECT conf FROM zbconf ORDER BY rowid desc limit 1
17:23:05:097 Idle timer triggered
17:23:05:099 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:05:101 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:06:096 Idle timer triggered
17:23:06:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:06:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:07:096 Idle timer triggered
17:23:07:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:07:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:08:096 Idle timer triggered
17:23:08:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:08:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:09:096 Idle timer triggered
17:23:09:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:09:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:10:096 Idle timer triggered
17:23:10:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:10:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:11:096 Idle timer triggered
17:23:11:099 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:11:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:12:096 Idle timer triggered
17:23:12:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:12:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:13:096 Idle timer triggered
17:23:13:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:13:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:13:596 Daylight now: goldenHour2, status: 180, daylight: 0, dark: 0
17:23:14:095 Idle timer triggered
17:23:14:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:14:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:15:096 Idle timer triggered
17:23:15:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:15:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:16:095 Idle timer triggered
17:23:16:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:16:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:16:776 APS-DATA.request id: 116, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:23:16:778    asdu (length: 2): 4f00
17:23:16:797 APS-DATA.confirm id: 116, status: 0x00 SUCCESS
17:23:16:798 APS-DATA.confirm request id: 116 -> confirmed, timeout 71127184
17:23:16:818 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:23:16:819    asdu: 4f000300012ed107ffff2e2100407128feff15cd0452e1120001ff
17:23:16:819 APS-DATA.indication request id: 116 -> finished
17:23:16:820 APS-DATA.request id: 116 erase from queue
17:23:17:096 Idle timer triggered
17:23:17:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:17:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:18:095 Idle timer triggered
17:23:18:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:18:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:19:096 Idle timer triggered
17:23:19:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:19:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:20:096 Idle timer triggered
17:23:20:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:20:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:21:096 Idle timer triggered
17:23:21:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:21:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:21:595 GW firmware version: 0x26720700
17:23:21:597 GW firmware version is up to date: 0x26720700
17:23:22:095 Idle timer triggered
17:23:22:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:22:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:23:096 Idle timer triggered
17:23:23:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:23:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:23:596 Daylight now: goldenHour2, status: 180, daylight: 0, dark: 0
17:23:24:096 Idle timer triggered
17:23:24:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:24:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:25:096 Idle timer triggered
17:23:25:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:25:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:26:095 Idle timer triggered
17:23:26:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:26:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:27:096 Idle timer triggered
17:23:27:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:27:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:28:096 Idle timer triggered
17:23:28:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:28:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:29:096 Idle timer triggered
17:23:29:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:29:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:30:096 Idle timer triggered
17:23:30:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:30:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:31:096 Idle timer triggered
17:23:31:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:31:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:32:096 Idle timer triggered
17:23:32:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:32:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:32:136 APS-DATA.request id: 180, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:23:32:137    asdu (length: 2): 5001
17:23:32:152 APS-DATA.confirm id: 180, status: 0x00 SUCCESS
17:23:32:153 APS-DATA.confirm request id: 180 -> confirmed, timeout 71142542
17:23:32:171 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:23:32:172    asdu: 50000301012ed107ffff2e2100c69064feff65112c9caf150001ff
17:23:32:172 APS-DATA.indication request id: 180 -> finished
17:23:32:173 APS-DATA.request id: 180 erase from queue
17:23:32:174     * different nwk address 0xFFD8 / 0xAF9C
17:23:32:174 neigbor 0x2c1165fffe6490c6 is unknown child
17:23:33:096 Idle timer triggered
17:23:33:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:33:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:33:596 Daylight now: goldenHour2, status: 180, daylight: 0, dark: 0
17:23:34:095 Idle timer triggered
17:23:34:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:34:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:35:096 Idle timer triggered
17:23:35:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:35:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:36:097 Idle timer triggered
17:23:36:100 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:36:102 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:37:096 Idle timer triggered
17:23:37:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:37:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:38:096 Idle timer triggered
17:23:38:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:38:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:39:096 APS-DATA.request id: 209, addrmode: 0x02, addr: 0xfffc, profile: 0x0000, cluster: 0x0036, ep: 0x00 -> 0x00 queue: 0 len: 3 tx.options 0x00
17:23:39:098    asdu (length: 3): 254101
17:23:39:099 send permit join, duration: 65
17:23:39:100 APS-DATA.request id: 210, addrmode: 0x02, addr: 0xfffc, profile: 0xA1E0, cluster: 0x0021, ep: 0xF2 -> 0xF2 queue: 1 len: 6 tx.options 0x00
17:23:39:102    asdu (length: 6): 1928020b2800
17:23:39:104 Idle timer triggered
17:23:39:105 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:39:106 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:39:791 APS-DATA.confirm id: 209, status: 0x00 SUCCESS
17:23:39:801 APS-DATA.confirm id: 210, status: 0x00 SUCCESS
17:23:39:818 aps request id: 209 finished, erase from queue
17:23:39:895 aps request id: 210 finished, erase from queue
17:23:40:096 Idle timer triggered
17:23:40:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:40:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:41:095 Idle timer triggered
17:23:41:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:41:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:42:096 Idle timer triggered
17:23:42:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:42:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:43:096 Idle timer triggered
17:23:43:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:43:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:43:596 Daylight now: goldenHour2, status: 180, daylight: 0, dark: 0
17:23:44:096 Idle timer triggered
17:23:44:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:44:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:45:096 Idle timer triggered
17:23:45:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:45:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:46:096 Idle timer triggered
17:23:46:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:46:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:46:196 sensor 2 (TRADFRI motion sensor): disable presence
17:23:46:203 Websocket 127.0.0.1:36986 send message: {"e":"changed","id":"2","r":"sensors","state":{"dark":true,"lastupdated":"2022-02-04T16:23:46.198","presence":false},"t":"event","uniqueid":"04:cd:15:ff:fe:28:71:40-01-0006"} (ret = 174)
17:23:46:395 Set sensor check interval to 1000 milliseconds
17:23:47:096 Idle timer triggered
17:23:47:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:47:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:47:496 APS-DATA.request id: 245, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:23:47:498    asdu (length: 2): 5102
17:23:47:516 APS-DATA.confirm id: 245, status: 0x00 SUCCESS
17:23:47:517 APS-DATA.confirm request id: 245 -> confirmed, timeout 71157904
17:23:47:542 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:23:47:543    asdu: 51000302012ed107ffff2e21006bac1afeff14430c2f0a150001ff
17:23:47:544 APS-DATA.indication request id: 245 -> finished
17:23:47:544 APS-DATA.request id: 245 erase from queue
17:23:47:545 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:23:47:545     * different nwk address 0x0157 / 0x0A2F
17:23:47:546 neigbor 0x0c4314fffe1aac6b is unknown child
17:23:47:555 Websocket 127.0.0.1:36986 send message: {"attr":{"id":"1","lastannounced":null,"lastseen":"2022-02-04T16:23Z","manufacturername":"dresden elektronik","modelid":"ConBee II","name":"Configuration tool 1","swversion":"0x26720700","type":"Configuration tool","uniqueid":"00:21:2e:ff:ff:07:d1:2e-01"},"e":"changed","id":"1","r":"lights","t":"event","uniqueid":"00:21:2e:ff:ff:07:d1:2e-01"} (ret = 344)
17:23:48:096 Idle timer triggered
17:23:48:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:48:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:49:095 Idle timer triggered
17:23:49:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:49:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:50:096 Idle timer triggered
17:23:50:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:50:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:51:096 Idle timer triggered
17:23:51:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:51:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:52:096 Idle timer triggered
17:23:52:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:52:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:53:096 Idle timer triggered
17:23:53:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:53:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:53:596 Daylight now: goldenHour2, status: 180, daylight: 0, dark: 0
17:23:54:096 Idle timer triggered
17:23:54:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:54:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:55:096 Idle timer triggered
17:23:55:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:55:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:56:096 Idle timer triggered
17:23:56:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:56:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:57:097 Idle timer triggered
17:23:57:099 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:57:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:58:096 Idle timer triggered
17:23:58:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:58:097 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:23:59:096 Idle timer triggered
17:23:59:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:23:59:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:24:00:096 Idle timer triggered
17:24:00:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:24:00:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:24:01:096 Idle timer triggered
17:24:01:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:24:01:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:24:02:096 Idle timer triggered
17:24:02:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:24:02:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:24:03:096 Idle timer triggered
17:24:03:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:24:03:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:24:03:596 Daylight now: goldenHour2, status: 180, daylight: 0, dark: 0
17:24:03:612 Master: read param with arg 0x19
17:24:03:664 Device TTL 684 s flags: 0x7
17:24:04:096 Idle timer triggered
17:24:04:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:24:04:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:24:04:296 APS-DATA.request id: 58, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:24:04:299    asdu (length: 2): 5200
17:24:04:316 APS-DATA.confirm id: 58, status: 0x00 SUCCESS
17:24:04:318 APS-DATA.confirm request id: 58 -> confirmed, timeout 71174706
17:24:04:335 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:24:04:336    asdu: 52000200012ed107ffff2e2100407128feff15cd0452e1120001ff
17:24:04:337 APS-DATA.indication request id: 58 -> finished
17:24:04:337 APS-DATA.request id: 58 erase from queue
17:24:05:096 Idle timer triggered
17:24:05:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:24:05:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:24:06:096 sql exec SELECT conf FROM zbconf ORDER BY rowid desc limit 1
17:24:06:098 Idle timer triggered
17:24:06:100 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:24:06:101 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:24:07:096 Idle timer triggered
17:24:07:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:24:07:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:24:08:096 Idle timer triggered
17:24:08:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:24:08:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:24:09:096 Idle timer triggered
17:24:09:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:24:09:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:24:10:096 Idle timer triggered
17:24:10:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:24:10:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:24:11:096 Idle timer triggered
17:24:11:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:24:11:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:24:12:096 Idle timer triggered
17:24:12:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:24:12:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:24:13:096 Idle timer triggered
17:24:13:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:24:13:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:24:13:596 Daylight now: goldenHour2, status: 180, daylight: 0, dark: 0
17:24:14:096 Idle timer triggered
17:24:14:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:24:14:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:24:15:096 Idle timer triggered
17:24:15:099 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:24:15:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:24:16:096 Idle timer triggered
17:24:16:099 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:24:16:101 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:24:17:096 Idle timer triggered
17:24:17:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:24:17:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:24:18:096 Idle timer triggered
17:24:18:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:24:18:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:24:19:096 Idle timer triggered
17:24:19:099 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:24:19:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:24:19:661 APS-DATA.request id: 122, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:24:19:663    asdu (length: 2): 5301
17:24:19:676 APS-DATA.confirm id: 122, status: 0x00 SUCCESS
17:24:19:677 APS-DATA.confirm request id: 122 -> confirmed, timeout 71190068
17:24:19:694 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:24:19:695    asdu: 5300010100
17:24:19:696 APS-DATA.indication request id: 122 -> finished
17:24:19:696 APS-DATA.request id: 122 erase from queue
17:24:19:697 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:24:20:096 Idle timer triggered
17:24:20:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:24:20:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:24:21:096 Idle timer triggered
17:24:21:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:24:21:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:24:22:096 Idle timer triggered
17:24:22:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:24:22:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:24:23:096 Idle timer triggered
17:24:23:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:24:23:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:24:23:598 Daylight now: goldenHour2, status: 180, daylight: 0, dark: 0
17:24:24:096 Idle timer triggered
17:24:24:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:24:24:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:24:25:096 Idle timer triggered
17:24:25:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:24:25:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:24:26:095 Idle timer triggered
17:24:26:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:24:26:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:24:27:096 Idle timer triggered
17:24:27:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:24:27:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:24:28:116 Idle timer triggered
17:24:28:117 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:24:28:118 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:24:29:128 Idle timer triggered
17:24:29:129 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:24:29:129 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:24:30:098 Idle timer triggered
17:24:30:100 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:24:30:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:24:31:106 Idle timer triggered
17:24:31:107 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:24:31:108 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:24:32:135 Idle timer triggered
17:24:32:136 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:24:32:137 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:24:33:096 Idle timer triggered
17:24:33:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:24:33:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:24:33:596 Daylight now: goldenHour2, status: 180, daylight: 0, dark: 0
17:24:34:095 Idle timer triggered
17:24:34:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:24:34:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:24:35:096 Idle timer triggered
17:24:35:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:24:35:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:24:36:098 Idle timer triggered
17:24:36:099 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:24:36:100 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:24:36:456 APS-DATA.request id: 191, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:24:36:457    asdu (length: 2): 5400
17:24:36:470 APS-DATA.confirm id: 191, status: 0x00 SUCCESS
17:24:36:472 APS-DATA.confirm request id: 191 -> confirmed, timeout 71206863
17:24:36:478 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:24:36:480    asdu: 54000100012ed107ffff2e2100407128feff15cd0452e1120001ff
17:24:36:481 APS-DATA.indication request id: 191 -> finished
17:24:36:482 APS-DATA.request id: 191 erase from queue
17:24:36:482 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:24:37:101 Idle timer triggered
17:24:37:103 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:24:37:104 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:24:38:096 Idle timer triggered
17:24:38:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:24:38:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:24:39:096 Idle timer triggered
17:24:39:097 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:24:39:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:24:40:096 APS-DATA.request id: 207, addrmode: 0x02, addr: 0xfffc, profile: 0x0000, cluster: 0x0036, ep: 0x00 -> 0x00 queue: 0 len: 3 tx.options 0x00
17:24:40:098    asdu (length: 3): 264101
17:24:40:100 send permit join, duration: 65
17:24:40:101 APS-DATA.request id: 208, addrmode: 0x02, addr: 0xfffc, profile: 0xA1E0, cluster: 0x0021, ep: 0xF2 -> 0xF2 queue: 1 len: 6 tx.options 0x00
17:24:40:102    asdu (length: 6): 1929020b2800
17:24:40:103 Idle timer triggered
17:24:40:104 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:24:40:105 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:24:40:785 APS-DATA.confirm id: 207, status: 0x00 SUCCESS
17:24:40:795 APS-DATA.confirm id: 208, status: 0x00 SUCCESS
17:24:40:856 aps request id: 207 finished, erase from queue
17:24:40:939 aps request id: 208 finished, erase from queue
17:24:41:096 Idle timer triggered
17:24:41:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:24:41:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:24:42:100 Idle timer triggered
17:24:42:101 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:24:42:102 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:24:43:096 Idle timer triggered
17:24:43:098 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
17:24:43:099 Force binding of attribute reporting for node TRÅDFRI Motion sensor
17:24:43:595 Daylight now: goldenHour2, status: 180, daylight: 0, dark: 0
17:24:43:833 APS-DATA.indication srcAddr: 0xe152, srcEp: 0x01 dstAddrMode: 1, profile: 0x0104, cluster: 0x0006, lqi: 255, rssi: -50
17:24:43:835    asdu: 015b420008070000
17:24:43:836 APS-DATA.indication from child 0xE152
17:24:43:838 [INFO] - Button 1002 - TRADFRI motion sensor, broadcast to: 0x0002, endpoint: 0x01, cluster: ONOFF (0x0006), action: On with timed off, payload: 0008070000, zclSeq: 91
17:24:43:840 Force binding of attribute reporting for sensor TRÅDFRI Motion sensor
17:24:43:855 Websocket 127.0.0.1:36986 send message: {"config":{"alert":"none","battery":74,"delay":180,"duration":60,"group":"2","on":true,"reachable":true},"e":"changed","id":"2","r":"sensors","t":"event","uniqueid":"04:cd:15:ff:fe:28:71:40-01-0006"} (ret = 199)
17:24:43:859 Websocket 127.0.0.1:36986 send message: {"e":"changed","id":"2","r":"sensors","state":{"dark":true,"lastupdated":"2022-02-04T16:24:43.840","presence":true},"t":"event","uniqueid":"04:cd:15:ff:fe:28:71:40-01-0006"} (ret = 173)
17:24:43:862 Websocket 127.0.0.1:36986 send message: {"attr":{"id":"2","lastannounced":"2022-02-03T20:42:51Z","lastseen":"2022-02-04T16:24Z","manufacturername":"IKEA of Sweden","modelid":"TRADFRI motion sensor","name":"TRÅDFRI Motion sensor","swversion":"2.0.022","type":"ZHAPresence","uniqueid":"04:cd:15:ff:fe:28:71:40-01-0006"},"e":"changed","id":"2","r":"sensors","t":"event","uniqueid":"04:cd:15:ff:fe:28:71:40-01-0006"} (ret = 373)
17:24:44:096 Idle timer triggered
17:24:44:098 Force binding of attribute reporting for node TRÅDFRI Motion sensor

[The Druid]

Mimiix schreef op vrijdag 4 februari 2022 @ 13:37:
[...]


Hoi,

Zou je wat deCONZ logs kunnen delen? Deze zijn van de addon namelijk en niet echt relevant. Zie topic warning voor hoe en wat.

Dank voor je hulp, bijgaand een logje.

Update van log met alle lampen in pairing mode:

code:

17:40:21:403    asdu (length: 2): 3800
17:40:21:415 APS-DATA.confirm id: 119, status: 0x00 SUCCESS
17:40:21:415 APS-DATA.confirm request id: 119 -> confirmed, timeout 16162125
17:40:21:424 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 17, rssi: 21
17:40:21:425    asdu: 38000100013cec07ffff2e210084b103feff72025c2769250101ff
17:40:21:425 APS-DATA.indication request id: 119 -> finished
17:40:21:425 APS-DATA.request id: 119 erase from queue
17:40:21:425 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:40:21:884 CTRL skip creating node 0x5C0272FFFE03B184 while permit join is disabled
17:40:23:803 APS-DATA.request id: 131, addrmode: 0x03, addr: 0x00212effff07ec3c, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:40:23:804    asdu (length: 2): 3900
17:40:23:815 APS-DATA.confirm id: 131, status: 0x00 SUCCESS
17:40:23:816 APS-DATA.confirm request id: 131 -> confirmed, timeout 16164526
17:40:23:825 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 69, rssi: 1
17:40:23:825    asdu: 39000100013cec07ffff2e210084b103feff72025c2769250101ff
17:40:23:826 APS-DATA.indication request id: 131 -> finished
17:40:23:826 APS-DATA.request id: 131 erase from queue
17:40:23:826 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:40:24:283 CTRL skip creating node 0x5C0272FFFE03B184 while permit join is disabled
17:40:26:203 APS-DATA.request id: 142, addrmode: 0x03, addr: 0x00212effff07ec3c, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:40:26:203    asdu (length: 2): 3a00
17:40:26:217 APS-DATA.confirm id: 142, status: 0x00 SUCCESS
17:40:26:221 APS-DATA.confirm request id: 142 -> confirmed, timeout 16166925
17:40:26:259 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 17, rssi: 21
17:40:26:260    asdu: 3a000100013cec07ffff2e210084b103feff72025c2769250101ff
17:40:26:260 APS-DATA.indication request id: 142 -> finished
17:40:26:260 APS-DATA.request id: 142 erase from queue
17:40:26:260 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:40:26:295 Daylight now: sunsetEnd, status: 200, daylight: 0, dark: 0
17:40:26:684 CTRL skip creating node 0x5C0272FFFE03B184 while permit join is disabled
17:40:28:603 APS-DATA.request id: 154, addrmode: 0x03, addr: 0x00212effff07ec3c, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:40:28:603    asdu (length: 2): 3b00
17:40:28:622 APS-DATA.confirm id: 154, status: 0x00 SUCCESS
17:40:28:622 APS-DATA.confirm request id: 154 -> confirmed, timeout 16169325
17:40:28:650 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 17, rssi: 21
17:40:28:650    asdu: 3b000100013cec07ffff2e210084b103feff72025c2769250101ff
17:40:28:653 APS-DATA.indication request id: 154 -> finished
17:40:28:653 APS-DATA.request id: 154 erase from queue
17:40:28:653 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:40:29:085 CTRL skip creating node 0x5C0272FFFE03B184 while permit join is disabled
17:40:30:715 New websocket 127.0.0.1:35862 (state: 3) 
17:40:31:003 APS-DATA.request id: 165, addrmode: 0x03, addr: 0x00212effff07ec3c, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:40:31:004    asdu (length: 2): 3c00
17:40:31:016 APS-DATA.confirm id: 165, status: 0x00 SUCCESS
17:40:31:016 APS-DATA.confirm request id: 165 -> confirmed, timeout 16171726
17:40:31:047 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 17, rssi: 21
17:40:31:048    asdu: 3c000100013cec07ffff2e210084b103feff72025c2769250101ff
17:40:31:048 APS-DATA.indication request id: 165 -> finished
17:40:31:048 APS-DATA.request id: 165 erase from queue
17:40:31:049 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:40:31:279 GW firmware version: 0x26580700
17:40:31:279 GW firmware version shall be updated to: 0x26660700
17:40:31:484 CTRL skip creating node 0x5C0272FFFE03B184 while permit join is disabled
17:40:33:402 APS-DATA.request id: 177, addrmode: 0x03, addr: 0x00212effff07ec3c, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:40:33:403    asdu (length: 2): 3d00
17:40:33:415 APS-DATA.confirm id: 177, status: 0x00 SUCCESS
17:40:33:415 APS-DATA.confirm request id: 177 -> confirmed, timeout 16174125
17:40:33:424 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 17, rssi: 21
17:40:33:424    asdu: 3d000100013cec07ffff2e210084b103feff72025c2769250101ff
17:40:33:425 APS-DATA.indication request id: 177 -> finished
17:40:33:425 APS-DATA.request id: 177 erase from queue
17:40:33:425 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:40:33:883 CTRL skip creating node 0x5C0272FFFE03B184 while permit join is disabled
17:40:33:970 Websocket disconnected 127.0.0.1:35862, state: 0, close-code: 1000, reason: 
17:40:34:779 Idle timer triggered
17:40:35:230 New websocket 127.0.0.1:35876 (state: 3) 
17:40:35:803 APS-DATA.request id: 189, addrmode: 0x03, addr: 0x00212effff07ec3c, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:40:35:803    asdu (length: 2): 3e00
17:40:35:815 APS-DATA.confirm id: 189, status: 0x00 SUCCESS
17:40:35:816 APS-DATA.confirm request id: 189 -> confirmed, timeout 16176525
17:40:35:830 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 17, rssi: 21
17:40:35:830    asdu: 3e000100013cec07ffff2e210084b103feff72025c2769250101ff
17:40:35:831 APS-DATA.indication request id: 189 -> finished
17:40:35:831 APS-DATA.request id: 189 erase from queue
17:40:35:832 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:40:36:282 Daylight now: sunsetEnd, status: 200, daylight: 0, dark: 0
17:40:36:287 CTRL skip creating node 0x5C0272FFFE03B184 while permit join is disabled
17:40:38:202 APS-DATA.request id: 200, addrmode: 0x03, addr: 0x00212effff07ec3c, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:40:38:203    asdu (length: 2): 3f00
17:40:38:217 APS-DATA.confirm id: 200, status: 0x00 SUCCESS
17:40:38:221 APS-DATA.confirm request id: 200 -> confirmed, timeout 16178925
17:40:38:259 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 69, rssi: 1
17:40:38:259    asdu: 3f000100013cec07ffff2e210084b103feff72025c2769250101ff
17:40:38:260 APS-DATA.indication request id: 200 -> finished
17:40:38:260 APS-DATA.request id: 200 erase from queue
17:40:38:261 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:40:38:684 CTRL skip creating node 0x5C0272FFFE03B184 while permit join is disabled
17:40:40:603 APS-DATA.request id: 212, addrmode: 0x03, addr: 0x00212effff07ec3c, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:40:40:604    asdu (length: 2): 4000
17:40:40:617 APS-DATA.confirm id: 212, status: 0x00 SUCCESS
17:40:40:618 APS-DATA.confirm request id: 212 -> confirmed, timeout 16181326
17:40:40:650 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 17, rssi: 21
17:40:40:653    asdu: 40000100013cec07ffff2e210084b103feff72025c2769250101ff
17:40:40:654 APS-DATA.indication request id: 212 -> finished
17:40:40:654 APS-DATA.request id: 212 erase from queue
17:40:40:655 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:40:40:779 APS-DATA.request id: 214, addrmode: 0x02, addr: 0xfffc, profile: 0x0000, cluster: 0x0036, ep: 0x00 -> 0x00 queue: 0 len: 3 tx.options 0x00
17:40:40:780    asdu (length: 3): 004101
17:40:40:780 send permit join, duration: 65
17:40:40:780 APS-DATA.request id: 215, addrmode: 0x02, addr: 0xfffc, profile: 0xA1E0, cluster: 0x0021, ep: 0xF2 -> 0xF2 queue: 1 len: 6 tx.options 0x00
17:40:40:781    asdu (length: 6): 1901020b2800
17:40:40:899 APS-DATA.confirm id: 215, status: 0xE1 
17:40:40:937 APS-DATA.confirm id: 214, status: 0xE1 
17:40:41:084 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 2, node: 0x6927
17:40:41:084 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 1, node: 0x6927
17:40:41:085 new node - ext: 0x5c0272fffe03b184, nwk: 0x6927
17:40:43:003 APS-DATA.request id: 225, addrmode: 0x03, addr: 0x5c0272fffe03b184, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:40:43:003    asdu (length: 2): 4100
17:40:43:109 APS-DATA.confirm id: 225, status: 0xE1 
17:40:43:110 unhandled APS-DATA.confirm id: 225 status 0xE1
17:40:45:402 APS-DATA.request id: 236, addrmode: 0x03, addr: 0x00212effff07ec3c, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:40:45:403    asdu (length: 2): 4200
17:40:45:414 APS-DATA.confirm id: 236, status: 0x00 SUCCESS
17:40:45:415 APS-DATA.confirm request id: 236 -> confirmed, timeout 16186125
17:40:45:426 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 17, rssi: 21
17:40:45:427    asdu: 42000100013cec07ffff2e210084b103feff72025c2769250101ff
17:40:45:427 APS-DATA.indication request id: 236 -> finished
17:40:45:428 APS-DATA.request id: 236 erase from queue
17:40:45:428 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:40:45:429 skip create link for 0x0000 (lqi: 255) - 0x6927 (lqi: 0)
17:40:46:279 Daylight now: sunsetEnd, status: 200, daylight: 0, dark: 0
17:40:48:283 APS-DATA.request id: 250, addrmode: 0x03, addr: 0x00212effff07ec3c, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:40:48:283    asdu (length: 2): 4300
17:40:48:303 APS-DATA.confirm id: 250, status: 0x00 SUCCESS
17:40:48:304 APS-DATA.confirm request id: 250 -> confirmed, timeout 16189005
17:40:48:343 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 17, rssi: 21
17:40:48:345    asdu: 43000100013cec07ffff2e210084b103feff72025c2769250101ff
17:40:48:345 APS-DATA.indication request id: 250 -> finished
17:40:48:346 APS-DATA.request id: 250 erase from queue
17:40:48:346 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:40:48:346 skip create link for 0x0000 (lqi: 255) - 0x6927 (lqi: 0)
17:40:51:163 APS-DATA.request id: 7, addrmode: 0x03, addr: 0x00212effff07ec3c, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:40:51:164    asdu (length: 2): 4400
17:40:51:175 APS-DATA.confirm id: 7, status: 0x00 SUCCESS
17:40:51:175 APS-DATA.confirm request id: 7 -> confirmed, timeout 16191886
17:40:51:185 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 17, rssi: 21
17:40:51:186    asdu: 44000100013cec07ffff2e210084b103feff72025c2769250101ff
17:40:51:186 APS-DATA.indication request id: 7 -> finished
17:40:51:186 APS-DATA.request id: 7 erase from queue
17:40:51:186 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:40:51:187 skip create link for 0x0000 (lqi: 255) - 0x6927 (lqi: 0)
17:40:51:280 CTRL db store gui node 5c:02:72:ff:fe:03:b1:84
17:40:51:850 saved node state in 0 ms
17:40:51:850 sync() in 0 ms
17:40:52:779 Skip idle timer callback, too early: elapsed 915 msec
17:40:54:098 APS-DATA.request id: 20, addrmode: 0x03, addr: 0x00212effff07ec3c, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:40:54:099    asdu (length: 2): 4500
17:40:54:114 APS-DATA.confirm id: 20, status: 0x00 SUCCESS
17:40:54:118 APS-DATA.confirm request id: 20 -> confirmed, timeout 16194821
17:40:54:145 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 69, rssi: 1
17:40:54:147    asdu: 45000100013cec07ffff2e210084b103feff72025c2769250101ff
17:40:54:148 APS-DATA.indication request id: 20 -> finished
17:40:54:148 APS-DATA.request id: 20 erase from queue
17:40:54:148 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:40:54:149 skip create link for 0x0000 (lqi: 255) - 0x6927 (lqi: 0)
17:40:56:279 Daylight now: sunsetEnd, status: 200, daylight: 0, dark: 0
17:40:56:979 APS-DATA.request id: 33, addrmode: 0x03, addr: 0x00212effff07ec3c, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:40:56:979    asdu (length: 2): 4600
17:40:56:997 APS-DATA.confirm id: 33, status: 0x00 SUCCESS
17:40:56:998 APS-DATA.confirm request id: 33 -> confirmed, timeout 16197701
17:40:57:023 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 17, rssi: 21
17:40:57:024    asdu: 46000100013cec07ffff2e210084b103feff72025c2769250101ff
17:40:57:024 APS-DATA.indication request id: 33 -> finished
17:40:57:024 APS-DATA.request id: 33 erase from queue
17:40:57:024 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:40:57:025 skip create link for 0x0000 (lqi: 255) - 0x6927 (lqi: 0)

Update

Ik zie in de deconz app het volgende, dus blijkbaar is er iets gevonden. Maar Connect het daarna niet. Zucht



Alles ligt in de kelder naast de stick dus range kan geen issued zijn.

[ Voor 32% gewijzigd door The Druid op 04-02-2022 18:34 ]

[Mimiix]

Ik zie geen apparaten opkomen. Het lijkt erop alsof de lamp niet in pairing mode staat.


Heb je deconz al herstart? Dat helpt heel soms ook.

[jja2000]

Mimiix schreef op vrijdag 4 februari 2022 @ 17:42:
Ik zie geen apparaten opkomen. Het lijkt erop alsof de lamp niet in pairing mode staat.


Heb je deconz al herstart? Dat helpt heel soms ook.

Staan ze als het goed is wel iedere keer dat ik het reset. Maar zoals ik zei in mijn eerste post, ze zijn wel te zien in deCONZ. Hier de logs bij het pairen na een restart:

code:

17:47:00:321 DEV no DDF for 0x04CD15FFFE287140, modelId: TRADFRI motion sensor
17:47:00:322 DEV create on-the-fly DDF for 0x04CD15FFFE287140
17:47:00:376 dlg action: Read binding table
17:47:00:646 Announced to internet https://phoscon.de/discover
17:47:00:647 discovery server date: Fri, 04 Feb 2022 16:47:00 GMT
17:47:00:648     local time seems to be ok
17:47:01:145 COM: /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2471167-if00 / serialno: DE2471167, ConBee II
17:47:01:269 Skip idle timer callback, too early: elapsed 944 msec
17:47:02:596 DEV Tick.Init: booted after 8000 seconds
17:47:02:650 Device firmware version 0x26720700 ConBee II
17:47:02:671 unlocked max nodes: 512
17:47:02:763 Device protocol version: 0x010E
17:47:02:862 Current channel 15
17:47:02:883 CTRL ANT_CTRL 0x03
17:47:02:885 CTRL ZDP_RESPONSE handler 0x0001
17:47:02:919 Device protocol version: 0x010E
17:47:03:020 CTRL ANT_CTRL 0x03
17:47:03:022 CTRL ZDP_RESPONSE handler 0x0001
17:47:03:168 Skip idle timer callback, too early: elapsed 949 msec
17:47:10:597 GW update firmware found: /usr/share/deCONZ/firmware/deCONZ_ConBeeII_0x26660700.bin.GCF
17:47:10:597 GW firmware version is up to date: 0x26720700
17:47:32:340 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:47:34:596 Daylight now: sunsetEnd, status: 200, daylight: 0, dark: 1
17:47:35:207 APS-DATA.request id: 170, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:47:35:208    asdu (length: 2): 1000
17:47:35:223 APS-DATA.confirm id: 170, status: 0x00 SUCCESS
17:47:35:223 APS-DATA.confirm request id: 170 -> confirmed, timeout 72585613
17:47:35:231 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:47:35:231    asdu: 10000100012ed107ffff2e2100407128feff15cd0452e1120001ff
17:47:35:232 APS-DATA.indication request id: 170 -> finished
17:47:35:232 APS-DATA.request id: 170 erase from queue
17:47:35:233 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:47:38:088 APS-DATA.request id: 183, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:47:38:089    asdu (length: 2): 1100
17:47:38:105 APS-DATA.confirm id: 183, status: 0x00 SUCCESS
17:47:38:106 APS-DATA.confirm request id: 183 -> confirmed, timeout 72588494
17:47:38:111 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:47:38:112    asdu: 11000100012ed107ffff2e2100407128feff15cd0452e1120001ff
17:47:38:112 APS-DATA.indication request id: 183 -> finished
17:47:38:112 APS-DATA.request id: 183 erase from queue
17:47:38:113 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:47:40:968 APS-DATA.request id: 197, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:47:40:969    asdu (length: 2): 1200
17:47:40:990 APS-DATA.confirm id: 197, status: 0x00 SUCCESS
17:47:40:991 APS-DATA.confirm request id: 197 -> confirmed, timeout 72591375
17:47:41:029 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:47:41:030    asdu: 12000100012ed107ffff2e2100407128feff15cd0452e1120001ff
17:47:41:030 APS-DATA.indication request id: 197 -> finished
17:47:41:031 APS-DATA.request id: 197 erase from queue
17:47:41:031 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:47:43:602 New websocket 127.0.0.1:47196 (state: 3) 
17:47:43:848 APS-DATA.request id: 211, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:47:43:849    asdu (length: 2): 1300
17:47:43:867 APS-DATA.confirm id: 211, status: 0x00 SUCCESS
17:47:43:868 APS-DATA.confirm request id: 211 -> confirmed, timeout 72594254
17:47:43:909 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:47:43:909    asdu: 13000100012ed107ffff2e2100407128feff15cd0452e1120001ff
17:47:43:910 APS-DATA.indication request id: 211 -> finished
17:47:43:910 APS-DATA.request id: 211 erase from queue
17:47:43:910 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:47:44:596 Daylight now: sunsetEnd, status: 200, daylight: 0, dark: 1
17:47:46:727 APS-DATA.request id: 224, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:47:46:729    asdu (length: 2): 1400
17:47:46:747 APS-DATA.confirm id: 224, status: 0x00 SUCCESS
17:47:46:748 APS-DATA.confirm request id: 224 -> confirmed, timeout 72597134
17:47:46:789 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:47:46:790    asdu: 14000100012ed107ffff2e2100407128feff15cd0452e1120001ff
17:47:46:790 APS-DATA.indication request id: 224 -> finished
17:47:46:790 APS-DATA.request id: 224 erase from queue
17:47:46:791 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:47:48:264 Websocket disconnected 127.0.0.1:47196, state: 0, close-code: 1000, reason: 
17:47:49:348 New websocket 127.0.0.1:47228 (state: 3) 
17:47:49:607 APS-DATA.request id: 238, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:47:49:608    asdu (length: 2): 1500
17:47:49:626 APS-DATA.confirm id: 238, status: 0x00 SUCCESS
17:47:49:626 APS-DATA.confirm request id: 238 -> confirmed, timeout 72600014
17:47:49:671 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:47:49:671    asdu: 15000100012ed107ffff2e2100407128feff15cd0452e1120001ff
17:47:49:672 APS-DATA.indication request id: 238 -> finished
17:47:49:672 APS-DATA.request id: 238 erase from queue
17:47:49:672 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:47:52:488 APS-DATA.request id: 251, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:47:52:489    asdu (length: 2): 1600
17:47:52:509 APS-DATA.confirm id: 251, status: 0x00 SUCCESS
17:47:52:510 APS-DATA.confirm request id: 251 -> confirmed, timeout 72602894
17:47:52:549 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:47:52:550    asdu: 16000100012ed107ffff2e2100407128feff15cd0452e1120001ff
17:47:52:550 APS-DATA.indication request id: 251 -> finished
17:47:52:550 APS-DATA.request id: 251 erase from queue
17:47:52:550 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:47:54:595 Daylight now: sunsetEnd, status: 200, daylight: 0, dark: 1
17:47:54:615 Master: read param with arg 0x19
17:47:54:673 Device TTL 5882 s flags: 0x7
17:47:55:096 APS-DATA.request id: 7, addrmode: 0x02, addr: 0xfffc, profile: 0x0000, cluster: 0x0036, ep: 0x00 -> 0x00 queue: 0 len: 3 tx.options 0x00
17:47:55:097    asdu (length: 3): 004101
17:47:55:098 send permit join, duration: 65
17:47:55:099 APS-DATA.request id: 8, addrmode: 0x02, addr: 0xfffc, profile: 0xA1E0, cluster: 0x0021, ep: 0xF2 -> 0xF2 queue: 1 len: 6 tx.options 0x00
17:47:55:100    asdu (length: 6): 1901020b2800
17:47:55:368 APS-DATA.request id: 11, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 2 len: 2 tx.options 0x00
17:47:55:368    asdu (length: 2): 1700
17:47:55:385 APS-DATA.confirm id: 11, status: 0x00 SUCCESS
17:47:55:386 APS-DATA.confirm request id: 11 -> confirmed, timeout 72605773
17:47:55:430 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:47:55:431    asdu: 17000100012ed107ffff2e2100407128feff15cd0452e1120001ff
17:47:55:431 APS-DATA.indication request id: 11 -> finished
17:47:55:432 APS-DATA.request id: 11 erase from queue
17:47:55:432 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:47:55:782 APS-DATA.confirm id: 7, status: 0x00 SUCCESS
17:47:55:790 APS-DATA.confirm id: 8, status: 0x00 SUCCESS
17:47:55:848 aps request id: 7 finished, erase from queue
17:47:55:928 aps request id: 8 finished, erase from queue
17:47:56:096 Idle timer triggered
17:47:58:248 APS-DATA.request id: 24, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:47:58:249    asdu (length: 2): 1800
17:47:58:269 APS-DATA.confirm id: 24, status: 0x00 SUCCESS
17:47:58:270 APS-DATA.confirm request id: 24 -> confirmed, timeout 72608655
17:47:58:307 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:47:58:307    asdu: 18000100012ed107ffff2e2100407128feff15cd0452e1120001ff
17:47:58:308 APS-DATA.indication request id: 24 -> finished
17:47:58:308 APS-DATA.request id: 24 erase from queue
17:47:58:308 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:48:01:128 APS-DATA.request id: 38, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:48:01:129    asdu (length: 2): 1900
17:48:01:147 APS-DATA.confirm id: 38, status: 0x00 SUCCESS
17:48:01:148 APS-DATA.confirm request id: 38 -> confirmed, timeout 72611535
17:48:01:189 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:48:01:190    asdu: 19000100012ed107ffff2e2100407128feff15cd0452e1120001ff
17:48:01:190 APS-DATA.indication request id: 38 -> finished
17:48:01:191 APS-DATA.request id: 38 erase from queue
17:48:01:191 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:48:04:008 APS-DATA.request id: 51, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:48:04:009    asdu (length: 2): 1a00
17:48:04:028 APS-DATA.confirm id: 51, status: 0x00 SUCCESS
17:48:04:028 APS-DATA.confirm request id: 51 -> confirmed, timeout 72614415
17:48:04:071 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:48:04:071    asdu: 1a000300012ed107ffff2e2100407128feff15cd0452e1120001ff
17:48:04:072 APS-DATA.indication request id: 51 -> finished
17:48:04:072 APS-DATA.request id: 51 erase from queue
17:48:04:596 Daylight now: sunsetEnd, status: 200, daylight: 0, dark: 1
17:48:06:407 APS-DATA.request id: 63, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:48:06:408    asdu (length: 2): 1b01
17:48:06:428 APS-DATA.confirm id: 63, status: 0x00 SUCCESS
17:48:06:429 APS-DATA.confirm request id: 63 -> confirmed, timeout 72616813
17:48:06:469 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:48:06:469    asdu: 1b000301012ed107ffff2e21006bac1afeff14430ca74d150001ff
17:48:06:470 APS-DATA.indication request id: 63 -> finished
17:48:06:470 APS-DATA.request id: 63 erase from queue
17:48:06:471 neigbor 0x0c4314fffe1aac6b is unknown child
17:48:06:890 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 2, node: 0x4DA7
17:48:06:890 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 1, node: 0x4DA7
17:48:06:891 new node - ext: 0x0c4314fffe1aac6b, nwk: 0x4DA7
17:48:08:808 APS-DATA.request id: 74, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:48:08:809    asdu (length: 2): 1c02
17:48:08:826 APS-DATA.confirm id: 74, status: 0x00 SUCCESS
17:48:08:827 APS-DATA.confirm request id: 74 -> confirmed, timeout 72619214
17:48:08:871 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:48:08:872    asdu: 1c000302012ed107ffff2e2100c69064feff65112ce13f150001ff
17:48:08:873 APS-DATA.indication request id: 74 -> finished
17:48:08:873 APS-DATA.request id: 74 erase from queue
17:48:08:874 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:48:08:874 neigbor 0x2c1165fffe6490c6 is unknown child
17:48:08:921 Websocket 127.0.0.1:47228 send message: {"attr":{"id":"1","lastannounced":null,"lastseen":"2022-02-04T16:48Z","manufacturername":"dresden elektronik","modelid":"ConBee II","name":"Configuration tool 1","swversion":"0x26720700","type":"Configuration tool","uniqueid":"00:21:2e:ff:ff:07:d1:2e-01"},"e":"changed","id":"1","r":"lights","t":"event","uniqueid":"00:21:2e:ff:ff:07:d1:2e-01"} (ret = 344)
17:48:09:292 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 2, node: 0x3FE1
17:48:09:293 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 1, node: 0x3FE1
17:48:09:294 new node - ext: 0x2c1165fffe6490c6, nwk: 0x3FE1
17:48:11:688 APS-DATA.request id: 88, addrmode: 0x03, addr: 0x0c4314fffe1aac6b, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:48:11:689    asdu (length: 2): 1d00
17:48:14:595 Daylight now: sunsetEnd, status: 200, daylight: 0, dark: 1
17:48:19:598 CTRL db store gui node 00:21:2e:ff:ff:07:d1:2e
17:48:19:601 CTRL db store gui node 04:cd:15:ff:fe:28:71:40
17:48:19:602 CTRL db store gui node 0c:43:14:ff:fe:1a:ac:6b
17:48:19:603 CTRL db store gui node 2c:11:65:ff:fe:64:90:c6
17:48:19:618 saved node state in 0 ms
17:48:19:618 sync() in 0 ms
17:48:21:787 APS-DATA.confirm id: 88, status: 0xD0 
17:48:22:248 APS-DATA.request id: 131, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:48:22:249    asdu (length: 2): 1e00
17:48:22:268 APS-DATA.confirm id: 131, status: 0x00 SUCCESS
17:48:22:269 APS-DATA.confirm request id: 131 -> confirmed, timeout 72632654
17:48:22:312 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:48:22:313    asdu: 1e000300012ed107ffff2e2100407128feff15cd0452e1120001ff
17:48:22:313 APS-DATA.indication request id: 131 -> finished
17:48:22:313 APS-DATA.request id: 131 erase from queue
17:48:24:596 Daylight now: sunsetEnd, status: 200, daylight: 0, dark: 1
17:48:24:648 APS-DATA.request id: 143, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:48:24:649    asdu (length: 2): 1f01
17:48:24:665 APS-DATA.confirm id: 143, status: 0x00 SUCCESS
17:48:24:666 APS-DATA.confirm request id: 143 -> confirmed, timeout 72635054
17:48:24:701 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:48:24:702    asdu: 1f000301012ed107ffff2e21006bac1afeff14430ca74d150001ff
17:48:24:702 APS-DATA.indication request id: 143 -> finished
17:48:24:702 APS-DATA.request id: 143 erase from queue
17:48:24:703 skip create link for 0x0000 (lqi: 255) - 0x4DA7 (lqi: 0)
17:48:26:096 sql exec SELECT conf FROM zbconf ORDER BY rowid desc limit 1
17:48:26:098 Wait 3s till query finished
17:48:26:771 APS-DATA.indication srcAddr: 0xe152, srcEp: 0x01 dstAddrMode: 1, profile: 0x0104, cluster: 0x0006, lqi: 255, rssi: -49
17:48:26:771    asdu: 0164420008070000
17:48:26:772 APS-DATA.indication from child 0xE152
17:48:26:772 [INFO] - Button 1002 - TRADFRI motion sensor, broadcast to: 0x0002, endpoint: 0x01, cluster: ONOFF (0x0006), action: On with timed off, payload: 0008070000, zclSeq: 100
17:48:26:773 0x04CD15FFFE287140 (TRADFRI motion sensor) create binding for attribute reporting of cluster 0x0001 on endpoint 0x01
17:48:26:773 queue binding task for 0x04CD15FFFE287140, cluster 0x0001
17:48:26:774 Force binding of attribute reporting for sensor TRÅDFRI Motion sensor
17:48:26:787 Websocket 127.0.0.1:47228 send message: {"config":{"alert":"none","battery":74,"delay":180,"duration":60,"group":"2","on":true,"reachable":true},"e":"changed","id":"2","r":"sensors","t":"event","uniqueid":"04:cd:15:ff:fe:28:71:40-01-0006"} (ret = 199)
17:48:26:789 Websocket 127.0.0.1:47228 send message: {"e":"changed","id":"2","r":"sensors","state":{"dark":true,"lastupdated":"2022-02-04T16:48:26.773","presence":true},"t":"event","uniqueid":"04:cd:15:ff:fe:28:71:40-01-0006"} (ret = 173)
17:48:26:790 Websocket 127.0.0.1:47228 send message: {"attr":{"id":"2","lastannounced":"2022-02-03T20:42:51Z","lastseen":"2022-02-04T16:48Z","manufacturername":"IKEA of Sweden","modelid":"TRADFRI motion sensor","name":"TRÅDFRI Motion sensor","swversion":"2.0.022","type":"ZHAPresence","uniqueid":"04:cd:15:ff:fe:28:71:40-01-0006"},"e":"changed","id":"2","r":"sensors","t":"event","uniqueid":"04:cd:15:ff:fe:28:71:40-01-0006"} (ret = 373)
17:48:26:792 APS-DATA.request id: 154, addrmode: 0x03, addr: 0x04cd15fffe287140, profile: 0x0000, cluster: 0x0021, ep: 0x00 -> 0x00 queue: 0 len: 22 tx.options 0x04
17:48:26:793    asdu (length: 22): 38407128feff15cd04010100032ed107ffff2e210001
17:48:27:048 APS-DATA.request id: 156, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 1 len: 2 tx.options 0x00
17:48:27:049    asdu (length: 2): 2002
17:48:27:067 APS-DATA.confirm id: 156, status: 0x00 SUCCESS
17:48:27:068 APS-DATA.confirm request id: 156 -> confirmed, timeout 72637454
17:48:27:110 Set sensor check interval to 100 milliseconds
17:48:27:111 Wait 2s till query finished
17:48:27:116 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:48:27:116    asdu: 20000302012ed107ffff2e2100c69064feff65112ce13f150001ff
17:48:27:117 APS-DATA.indication request id: 156 -> finished
17:48:27:117 APS-DATA.request id: 156 erase from queue
17:48:27:117 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:48:27:118 skip create link for 0x0000 (lqi: 255) - 0x3FE1 (lqi: 0)
17:48:27:834 APS-DATA.confirm id: 154, status: 0x00 SUCCESS
17:48:27:835 APS-DATA.confirm request id: 154 -> confirmed, timeout 72637199
17:48:28:096 Wait 1s till query finished
17:48:28:844 APS-DATA.indication srcAddr: 0xe152, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8021, lqi: 255, rssi: -49
17:48:28:845    asdu: 3800
17:48:28:846 APS-DATA.indication request id: 154 -> finished
17:48:28:846 APS-DATA.indication from child 0xE152
17:48:28:847 APS-DATA.request id: 154 erase from queue
17:48:28:848 Bind response success for 0x04cd15fffe287140 ep: 0x01 cluster: 0x0001
17:48:28:848 0x04CD15FFFE287140: added ZCL value 0x01/0x0001/0x0021
17:48:28:849 configure reporting rq seq 2 for 0x04CD15FFFE287140, attribute 0x0001/0x0021
17:48:28:850 APS-DATA.request id: 166, addrmode: 0x03, addr: 0x04cd15fffe287140, profile: 0x0104, cluster: 0x0001, ep: 0x01 -> 0x01 queue: 0 len: 12 tx.options 0x04
17:48:28:851    asdu (length: 12): 100206002100202c018c0a01
17:48:29:096 Wait 1s till query finished
17:48:29:899 APS-DATA.confirm id: 166, status: 0x00 SUCCESS
17:48:29:900 APS-DATA.confirm request id: 166 -> erase from queue
17:48:30:003 aps request id: 166 finished, erase from queue
17:48:30:096 Wait 0s till query finished
17:48:30:408 APS-DATA.request id: 174, addrmode: 0x03, addr: 0x2c1165fffe6490c6, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:48:30:408    asdu (length: 2): 2100
17:48:31:015 APS-DATA.indication srcAddr: 0xe152, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0001, lqi: 255, rssi: -49
17:48:31:016    asdu: 08020700
17:48:31:016 APS-DATA.indication from child 0xE152
17:48:31:017 ZCL configure reporting rsp seq: 2 0x04CD15FFFE287140 for ep: 0x01 cluster: 0x0001 attr: 0x0021 status: 0x00
17:48:31:017 APS-DATA.request id: 178, addrmode: 0x02, addr: 0xe152, profile: 0x0104, cluster: 0x0001, ep: 0x01 -> 0x01 queue: 1 len: 5 tx.options 0x04
17:48:31:018    asdu (length: 5): 10020b0700
17:48:31:039 APS-DATA.confirm id: 178, status: 0x00 SUCCESS
17:48:31:040 APS-DATA.confirm request id: 178 -> erase from queue
17:48:31:078 aps request id: 178 finished, erase from queue
17:48:31:096 Idle timer triggered
17:48:34:596 Daylight now: sunsetEnd, status: 200, daylight: 0, dark: 1
17:48:40:498 APS-DATA.confirm id: 174, status: 0xD0 
17:48:40:968 APS-DATA.request id: 219, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:48:40:969    asdu (length: 2): 2200
17:48:40:983 APS-DATA.confirm id: 219, status: 0x00 SUCCESS
17:48:40:984 APS-DATA.confirm request id: 219 -> confirmed, timeout 72651374
17:48:41:022 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:48:41:023    asdu: 22000300012ed107ffff2e2100407128feff15cd0452e1120001ff
17:48:41:023 APS-DATA.indication request id: 219 -> finished
17:48:41:024 APS-DATA.request id: 219 erase from queue
17:48:43:368 APS-DATA.request id: 231, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:48:43:369    asdu (length: 2): 2301
17:48:43:387 APS-DATA.confirm id: 231, status: 0x00 SUCCESS
17:48:43:388 APS-DATA.confirm request id: 231 -> confirmed, timeout 72653775
17:48:43:425 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:48:43:425    asdu: 23000301012ed107ffff2e21006bac1afeff14430ca74d150001ff
17:48:43:426 APS-DATA.indication request id: 231 -> finished
17:48:43:426 APS-DATA.request id: 231 erase from queue
17:48:43:426 skip create link for 0x0000 (lqi: 255) - 0x4DA7 (lqi: 0)
17:48:44:595 Daylight now: sunsetEnd, status: 200, daylight: 0, dark: 1
17:48:45:768 APS-DATA.request id: 242, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:48:45:769    asdu (length: 2): 2402
17:48:45:788 APS-DATA.confirm id: 242, status: 0x00 SUCCESS
17:48:45:789 APS-DATA.confirm request id: 242 -> confirmed, timeout 72656175
17:48:45:829 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:48:45:830    asdu: 24000302012ed107ffff2e2100c69064feff65112ce13f150001ff
17:48:45:830 APS-DATA.indication request id: 242 -> finished
17:48:45:831 APS-DATA.request id: 242 erase from queue
17:48:45:831 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:48:45:831 skip create link for 0x0000 (lqi: 255) - 0x3FE1 (lqi: 0)
17:48:49:607 APS-DATA.request id: 4, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:48:49:608    asdu (length: 2): 2500
17:48:49:625 APS-DATA.confirm id: 4, status: 0x00 SUCCESS
17:48:49:628 APS-DATA.confirm request id: 4 -> confirmed, timeout 72660013
17:48:49:668 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:48:49:668    asdu: 25000300012ed107ffff2e2100407128feff15cd0452e1120001ff
17:48:49:668 APS-DATA.indication request id: 4 -> finished
17:48:49:669 APS-DATA.request id: 4 erase from queue
17:48:52:007 APS-DATA.request id: 15, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:48:52:008    asdu (length: 2): 2601
17:48:52:028 APS-DATA.confirm id: 15, status: 0x00 SUCCESS
17:48:52:029 APS-DATA.confirm request id: 15 -> confirmed, timeout 72662414
17:48:52:068 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:48:52:068    asdu: 26000301012ed107ffff2e21006bac1afeff14430ca74d150001ff
17:48:52:069 APS-DATA.indication request id: 15 -> finished
17:48:52:069 APS-DATA.request id: 15 erase from queue
17:48:52:069 skip create link for 0x0000 (lqi: 255) - 0x4DA7 (lqi: 0)
17:48:54:407 APS-DATA.request id: 27, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:48:54:409    asdu (length: 2): 2702
17:48:54:427 APS-DATA.confirm id: 27, status: 0x00 SUCCESS
17:48:54:428 APS-DATA.confirm request id: 27 -> confirmed, timeout 72664814
17:48:54:471 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:48:54:472    asdu: 27000302012ed107ffff2e2100c69064feff65112ce13f150001ff
17:48:54:472 APS-DATA.indication request id: 27 -> finished
17:48:54:473 APS-DATA.request id: 27 erase from queue
17:48:54:473 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:48:54:473 skip create link for 0x0000 (lqi: 255) - 0x3FE1 (lqi: 0)
17:48:54:596 Daylight now: sunsetEnd, status: 200, daylight: 0, dark: 1
17:48:54:612 Master: read param with arg 0x19
17:48:54:674 Device TTL 5822 s flags: 0x7
17:48:55:896 APS-DATA.request id: 30, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0033, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:48:55:897    asdu (length: 2): 3700
17:48:55:916 APS-DATA.confirm id: 30, status: 0x00 SUCCESS
17:48:55:917 APS-DATA.confirm request id: 30 -> confirmed, timeout 72666302
17:48:55:959 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8033, lqi: 221, rssi: 30
17:48:55:960    asdu: 3700000000
17:48:55:961 APS-DATA.indication request id: 30 -> finished
17:48:55:961 APS-DATA.request id: 30 erase from queue
17:48:55:961 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 9, node: 0x0000
17:48:56:096 APS-DATA.request id: 37, addrmode: 0x02, addr: 0xfffc, profile: 0x0000, cluster: 0x0036, ep: 0x00 -> 0x00 queue: 0 len: 3 tx.options 0x00
17:48:56:097    asdu (length: 3): 014101
17:48:56:097 send permit join, duration: 65
17:48:56:097 APS-DATA.request id: 38, addrmode: 0x02, addr: 0xfffc, profile: 0xA1E0, cluster: 0x0021, ep: 0xF2 -> 0xF2 queue: 1 len: 6 tx.options 0x00
17:48:56:098    asdu (length: 6): 1903020b2800
17:48:56:771 APS-DATA.confirm id: 37, status: 0x00 SUCCESS
17:48:56:782 APS-DATA.confirm id: 38, status: 0x00 SUCCESS
17:48:56:826 aps request id: 37 finished, erase from queue
17:48:56:888 aps request id: 38 finished, erase from queue
17:48:58:248 APS-DATA.request id: 48, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:48:58:249    asdu (length: 2): 2800
17:48:58:267 APS-DATA.confirm id: 48, status: 0x00 SUCCESS
17:48:58:268 APS-DATA.confirm request id: 48 -> confirmed, timeout 72668654
17:48:58:307 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:48:58:307    asdu: 28000300012ed107ffff2e2100407128feff15cd0452e1120001ff
17:48:58:308 APS-DATA.indication request id: 48 -> finished
17:48:58:308 APS-DATA.request id: 48 erase from queue
17:49:00:648 APS-DATA.request id: 60, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:49:00:649    asdu (length: 2): 2901
17:49:00:667 APS-DATA.confirm id: 60, status: 0x00 SUCCESS
17:49:00:668 APS-DATA.confirm request id: 60 -> confirmed, timeout 72671054
17:49:00:707 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:49:00:708    asdu: 2900010100
17:49:00:708 APS-DATA.indication request id: 60 -> finished
17:49:00:708 APS-DATA.request id: 60 erase from queue
17:49:00:709 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:49:01:096 Idle timer triggered
17:49:04:488 APS-DATA.request id: 77, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:49:04:489    asdu (length: 2): 2a00
17:49:04:508 APS-DATA.confirm id: 77, status: 0x00 SUCCESS
17:49:04:509 APS-DATA.confirm request id: 77 -> confirmed, timeout 72674895
17:49:04:547 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:49:04:548    asdu: 2a000300012ed107ffff2e2100407128feff15cd0452e1120001ff
17:49:04:548 APS-DATA.indication request id: 77 -> finished
17:49:04:549 APS-DATA.request id: 77 erase from queue
17:49:04:596 Daylight now: sunsetEnd, status: 200, daylight: 0, dark: 1
17:49:06:888 APS-DATA.request id: 89, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:49:06:889    asdu (length: 2): 2b01
17:49:06:909 APS-DATA.confirm id: 89, status: 0x00 SUCCESS
17:49:06:910 APS-DATA.confirm request id: 89 -> confirmed, timeout 72677294
17:49:06:949 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:49:06:950    asdu: 2b000301012ed107ffff2e2100c69064feff65112ca2d8150001ff
17:49:06:950 APS-DATA.indication request id: 89 -> finished
17:49:06:950 APS-DATA.request id: 89 erase from queue
17:49:06:951     * different nwk address 0x3FE1 / 0xD8A2
17:49:06:951 neigbor 0x2c1165fffe6490c6 is unknown child
17:49:09:288 APS-DATA.request id: 100, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:49:09:289    asdu (length: 2): 2c02
17:49:09:309 APS-DATA.confirm id: 100, status: 0x00 SUCCESS
17:49:09:310 APS-DATA.confirm request id: 100 -> confirmed, timeout 72679695
17:49:09:351 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:49:09:352    asdu: 2c000302012ed107ffff2e21006bac1afeff14430c57e9150001ff
17:49:09:352 APS-DATA.indication request id: 100 -> finished
17:49:09:353 APS-DATA.request id: 100 erase from queue
17:49:09:353 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:49:09:353     * different nwk address 0x4DA7 / 0xE957
17:49:09:353 neigbor 0x0c4314fffe1aac6b is unknown child
17:49:09:366 Websocket 127.0.0.1:47228 send message: {"attr":{"id":"1","lastannounced":null,"lastseen":"2022-02-04T16:49Z","manufacturername":"dresden elektronik","modelid":"ConBee II","name":"Configuration tool 1","swversion":"0x26720700","type":"Configuration tool","uniqueid":"00:21:2e:ff:ff:07:d1:2e-01"},"e":"changed","id":"1","r":"lights","t":"event","uniqueid":"00:21:2e:ff:ff:07:d1:2e-01"} (ret = 344)
17:49:13:128 APS-DATA.request id: 118, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:49:13:129    asdu (length: 2): 2d00
17:49:13:151 APS-DATA.confirm id: 118, status: 0x00 SUCCESS
17:49:13:152 APS-DATA.confirm request id: 118 -> confirmed, timeout 72683535
17:49:13:191 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:49:13:191    asdu: 2d000300012ed107ffff2e2100407128feff15cd0452e1120001ff
17:49:13:192 APS-DATA.indication request id: 118 -> finished
17:49:13:192 APS-DATA.request id: 118 erase from queue
17:49:14:596 Daylight now: sunsetEnd, status: 200, daylight: 0, dark: 1
17:49:15:528 APS-DATA.request id: 129, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:49:15:529    asdu (length: 2): 2e01
17:49:15:545 APS-DATA.confirm id: 129, status: 0x00 SUCCESS
17:49:15:546 APS-DATA.confirm request id: 129 -> confirmed, timeout 72685934
17:49:15:588 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:49:15:589    asdu: 2e000301012ed107ffff2e2100c69064feff65112ca2d8150001ff
17:49:15:589 APS-DATA.indication request id: 129 -> finished
17:49:15:589 APS-DATA.request id: 129 erase from queue
17:49:15:590     * different nwk address 0x3FE1 / 0xD8A2
17:49:15:590 neigbor 0x2c1165fffe6490c6 is unknown child
17:49:17:928 APS-DATA.request id: 141, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:49:17:929    asdu (length: 2): 2f02
17:49:17:949 APS-DATA.confirm id: 141, status: 0x00 SUCCESS
17:49:17:950 APS-DATA.confirm request id: 141 -> confirmed, timeout 72688334
17:49:17:986 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:49:17:987    asdu: 2f000302012ed107ffff2e21006bac1afeff14430c57e9150001ff
17:49:17:988 APS-DATA.indication request id: 141 -> finished
17:49:17:988 APS-DATA.request id: 141 erase from queue
17:49:17:988 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:49:17:988     * different nwk address 0x4DA7 / 0xE957
17:49:17:989 neigbor 0x0c4314fffe1aac6b is unknown child
17:49:22:408 node 00C4314FFFE1AAC6B leave wait state
17:49:24:597 Daylight now: sunsetEnd, status: 200, daylight: 0, dark: 1
17:49:26:795 sensor 2 (TRADFRI motion sensor): disable presence
17:49:26:804 Websocket 127.0.0.1:47228 send message: {"e":"changed","id":"2","r":"sensors","state":{"dark":true,"lastupdated":"2022-02-04T16:49:26.796","presence":false},"t":"event","uniqueid":"04:cd:15:ff:fe:28:71:40-01-0006"} (ret = 174)
17:49:26:996 Set sensor check interval to 1000 milliseconds
17:49:31:096 sql exec SELECT conf FROM zbconf ORDER BY rowid desc limit 1
17:49:31:097 Idle timer triggered
17:49:31:097 Force read attributes for ZHAPresence SensorNode TRÅDFRI Motion sensor
17:49:32:096 Wait 1s till query finished
17:49:33:096 Idle timer triggered
17:49:33:288 APS-DATA.request id: 204, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:49:33:289    asdu (length: 2): 3000
17:49:33:306 APS-DATA.confirm id: 204, status: 0x00 SUCCESS
17:49:33:307 APS-DATA.confirm request id: 204 -> confirmed, timeout 72703694
17:49:33:347 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:49:33:348    asdu: 30000300012ed107ffff2e2100407128feff15cd0452e1120001ff
17:49:33:348 APS-DATA.indication request id: 204 -> finished
17:49:33:349 APS-DATA.request id: 204 erase from queue
17:49:34:596 Daylight now: sunsetEnd, status: 200, daylight: 0, dark: 1
17:49:41:207 node 02C1165FFFE6490C6 leave wait state
17:49:44:596 Daylight now: sunsetEnd, status: 200, daylight: 0, dark: 1
17:49:48:648 APS-DATA.request id: 12, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:49:48:649    asdu (length: 2): 3101
17:49:48:668 APS-DATA.confirm id: 12, status: 0x00 SUCCESS
17:49:48:669 APS-DATA.confirm request id: 12 -> confirmed, timeout 72719054
17:49:48:711 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:49:48:712    asdu: 31000301012ed107ffff2e2100c69064feff65112ca2d8150001ff
17:49:48:712 APS-DATA.indication request id: 12 -> finished
17:49:48:713 APS-DATA.request id: 12 erase from queue
17:49:48:713     * different nwk address 0x3FE1 / 0xD8A2
17:49:48:713 neigbor 0x2c1165fffe6490c6 is unknown child
17:49:54:596 Daylight now: sunsetEnd, status: 200, daylight: 0, dark: 1
17:49:54:631 Master: read param with arg 0x19
17:49:54:654 Device TTL 5761 s flags: 0x7
17:49:57:096 binding/unbinding timeout srcAddr: 0x04CD15FFFE287140, retry
17:49:57:098 APS-DATA.request id: 47, addrmode: 0x02, addr: 0xfffc, profile: 0x0000, cluster: 0x0036, ep: 0x00 -> 0x00 queue: 0 len: 3 tx.options 0x00
17:49:57:098    asdu (length: 3): 024101
17:49:57:099 send permit join, duration: 65
17:49:57:100 APS-DATA.request id: 48, addrmode: 0x02, addr: 0xfffc, profile: 0xA1E0, cluster: 0x0021, ep: 0xF2 -> 0xF2 queue: 1 len: 6 tx.options 0x00
17:49:57:101    asdu (length: 6): 1904020b2800
17:49:57:776 APS-DATA.confirm id: 47, status: 0x00 SUCCESS
17:49:57:784 APS-DATA.confirm id: 48, status: 0x00 SUCCESS
17:49:57:848 aps request id: 47 finished, erase from queue
17:49:57:928 aps request id: 48 finished, erase from queue
17:49:58:096 APS-DATA.request id: 53, addrmode: 0x03, addr: 0x04cd15fffe287140, profile: 0x0000, cluster: 0x0021, ep: 0x00 -> 0x00 queue: 0 len: 22 tx.options 0x04
17:49:58:097    asdu (length: 22): 2b407128feff15cd04010100032ed107ffff2e210001
17:50:03:095 Idle timer triggered
17:50:04:008 APS-DATA.request id: 78, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 1 len: 2 tx.options 0x00
17:50:04:010    asdu (length: 2): 3202
17:50:04:027 APS-DATA.confirm id: 78, status: 0x00 SUCCESS
17:50:04:028 APS-DATA.confirm request id: 78 -> confirmed, timeout 72734415
17:50:04:070 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:50:04:070    asdu: 3200010200
17:50:04:071 APS-DATA.indication request id: 78 -> finished
17:50:04:071 APS-DATA.request id: 78 erase from queue
17:50:04:071 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:50:04:596 Daylight now: sunsetEnd, status: 200, daylight: 0, dark: 1
17:50:05:748 APS-DATA.confirm id: 53, status: 0xF0 TRANSACTION_EXPIRED
17:50:05:749 APS-DATA.confirm id: 53 status: transaction expired
17:50:14:597 Daylight now: sunsetEnd, status: 200, daylight: 0, dark: 1
17:50:20:808 APS-DATA.request id: 147, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:50:20:809    asdu (length: 2): 3300
17:50:20:828 APS-DATA.confirm id: 147, status: 0x00 SUCCESS
17:50:20:829 APS-DATA.confirm request id: 147 -> confirmed, timeout 72751215
17:50:20:868 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:50:20:868    asdu: 33000100012ed107ffff2e2100407128feff15cd0452e1120001ff
17:50:20:869 APS-DATA.indication request id: 147 -> finished
17:50:20:869 APS-DATA.request id: 147 erase from queue
17:50:20:869 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:50:20:878 Websocket 127.0.0.1:47228 send message: {"attr":{"id":"1","lastannounced":null,"lastseen":"2022-02-04T16:50Z","manufacturername":"dresden elektronik","modelid":"ConBee II","name":"Configuration tool 1","swversion":"0x26720700","type":"Configuration tool","uniqueid":"00:21:2e:ff:ff:07:d1:2e-01"},"e":"changed","id":"1","r":"lights","t":"event","uniqueid":"00:21:2e:ff:ff:07:d1:2e-01"} (ret = 344)
17:50:24:596 Daylight now: sunsetEnd, status: 200, daylight: 0, dark: 1

Ik zag de 0xF0 error verschijnen tegen het einde, maar dit was al nadat ik de lampen eenmaal uit en aan heb gezet.

[The Druid]

Mimiix schreef op vrijdag 4 februari 2022 @ 17:42:
Ik zie geen apparaten opkomen. Het lijkt erop alsof de lamp niet in pairing mode staat.


Heb je deconz al herstart? Dat helpt heel soms ook.

Inmiddels zie ik in de Deconz app dat er twee apparaten zij gevonden maar ze lijken niet gelinkt met mijn Conbee 2.

code:

11:22:11:058 dlg action: Read binding table
11:22:11:481 COM: /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2478093-if00 / serialno: DE2478093, ConBee II
11:22:12:274 Announced to internet https://phoscon.de/discover
11:22:12:394 DEV Tick.Init: booted after 8000 seconds
11:22:12:806 Skip idle timer callback, too early: elapsed 713 msec
11:22:13:778 Device firmware version 0x26720700 ConBee II
11:22:13:785 Device firmware version 0x26720700 ConBee II
11:22:13:793 unlocked max nodes: 512
11:22:13:891 Device protocol version: 0x010E
11:22:14:027 Current channel 11
11:22:14:042 CTRL got nwk update id 1
11:22:14:050 CTRL ANT_CTRL 0x03
11:22:14:053 CTRL ZDP_RESPONSE handler 0x0000
11:22:14:053 CTRL reconfigure ZDP_RESPONSE handler 0x0001
11:22:14:087 Device protocol version: 0x010E
11:22:14:186 CTRL ANT_CTRL 0x03
11:22:14:201 CTRL ZDP_RESPONSE handler 0x0000
11:22:14:201 CTRL reconfigure ZDP_RESPONSE handler 0x0001
11:22:22:312 GW update firmware found: /usr/share/deCONZ/firmware/deCONZ_ConBeeII_0x26660700.bin.GCF
11:22:22:312 GW firmware version is up to date: 0x26720700
11:23:03:339 Device TTL 3336 s flags: 0x7
11:23:47:189 New websocket 127.0.0.1:33068 (state: 3) 
11:23:52:779 Websocket disconnected 127.0.0.1:33068, state: 0, close-code: 1000, reason: 
11:23:54:145 New websocket 127.0.0.1:33102 (state: 3) 
11:23:59:806 send permit join, duration: 65
11:24:00:935 new node - ext: 0x5c0272fffe03b184, nwk: 0x10DF
11:24:03:335 new node - ext: 0x60a423fffeef5cbb, nwk: 0x8B7F
11:24:03:341 Device TTL 3276 s flags: 0x7
11:24:13:307 saved node state in 0 ms
11:24:13:307 sync() in 0 ms
11:25:00:806 send permit join, duration: 65
11:25:03:339 Device TTL 3216 s flags: 0x7
11:26:01:806 send permit join, duration: 57
11:26:03:338 Device TTL 3156 s flags: 0x7
11:26:22:306 GW firmware version is up to date: 0x26720700
11:26:54:806 send permit join, duration: 0
11:26:55:301 Search sensors done
11:27:03:338 Device TTL 3096 s flags: 0x7
11:28:03:339 Device TTL 3036 s flags: 0x7
11:29:03:340 Device TTL 2976 s flags: 0x7
11:30:03:339 Device TTL 2916 s flags: 0x7
11:30:22:306 GW firmware version is up to date: 0x26720700
11:30:56:283 Websocket disconnected 127.0.0.1:33102, state: 0, close-code: 1000, reason: 
11:31:03:339 Device TTL 2856 s flags: 0x7
11:31:23:714 saved node state in 0 ms
11:31:23:714 sync() in 0 ms
11:32:03:339 Device TTL 2796 s flags: 0x7
11:32:48:852 Toggle LQI 1
11:32:50:740 Toggle neighbor links: 0
11:32:51:524 Toggle neighbor links: 1
11:32:53:679 saved node state in 0 ms
11:32:53:680 sync() in 0 ms
11:33:02:806 Skip idle timer callback, too early: elapsed 879 msec
11:33:03:343 Device TTL 2736 s flags: 0x7
11:33:14:305 Daylight now: goldenHour1, status: 160, daylight: 1, dark: 0
11:33:22:863 APS-DATA.request id: 214, addrmode: 0x03, addr: 0x00212effff07ec3c, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
11:33:22:864    asdu (length: 2): a800
11:33:22:892 APS-DATA.confirm id: 214, status: 0x00 SUCCESS
11:33:22:893 APS-DATA.confirm request id: 214 -> confirmed, timeout 827559
11:33:22:931 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 240, rssi: 1
11:33:22:932    asdu: a8000200013cec07ffff2e210084b103feff72025cdf10250101ff
11:33:22:932 APS-DATA.indication request id: 214 -> finished
11:33:22:933 APS-DATA.request id: 214 erase from queue
11:33:22:933 APS-DATA.request id: 216, addrmode: 0x03, addr: 0x00212effff07ec3c, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
11:33:22:933    asdu (length: 2): a901
11:33:22:935 skip create link for 0x0000 (lqi: 255) - 0x10DF (lqi: 0)
11:33:22:952 APS-DATA.confirm id: 216, status: 0x00 SUCCESS
11:33:22:953 APS-DATA.confirm request id: 216 -> confirmed, timeout 827630
11:33:22:983 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 240, rssi: 1
11:33:22:983    asdu: a9000201013cec07ffff2e2100bb5ceffeff23a4607f8b250101ff
11:33:22:984 APS-DATA.indication request id: 216 -> finished
11:33:22:984 APS-DATA.request id: 216 erase from queue
11:33:22:985 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
11:33:22:987 skip create link for 0x0000 (lqi: 255) - 0x8B7F (lqi: 0)
11:33:24:307 Daylight now: goldenHour1, status: 160, daylight: 1, dark: 0
11:33:34:306 Daylight now: goldenHour1, status: 160, daylight: 1, dark: 0
11:33:34:806 Idle timer triggered
11:33:39:152 APS-DATA.request id: 27, addrmode: 0x03, addr: 0x00212effff07ec3c, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
11:33:39:152    asdu (length: 2): aa00
11:33:39:175 APS-DATA.confirm id: 27, status: 0x00 SUCCESS
11:33:39:175 APS-DATA.confirm request id: 27 -> confirmed, timeout 843847
11:33:39:206 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 240, rssi: 1
11:33:39:206    asdu: aa000200013cec07ffff2e210084b103feff72025cdf10250101ff
11:33:39:206 APS-DATA.indication request id: 27 -> finished
11:33:39:207 APS-DATA.request id: 27 erase from queue
11:33:39:207 APS-DATA.request id: 29, addrmode: 0x03, addr: 0x00212effff07ec3c, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
11:33:39:207    asdu (length: 2): ab01
11:33:39:207 skip create link for 0x0000 (lqi: 255) - 0x10DF (lqi: 0)
11:33:39:223 APS-DATA.confirm id: 29, status: 0x00 SUCCESS
11:33:39:223 APS-DATA.confirm request id: 29 -> confirmed, timeout 843902
11:33:39:244 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 240, rssi: 1
11:33:39:245    asdu: ab000201013cec07ffff2e2100bb5ceffeff23a4607f8b250101ff
11:33:39:245 APS-DATA.indication request id: 29 -> finished
11:33:39:245 APS-DATA.request id: 29 erase from queue
11:33:39:250 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
11:33:39:251 skip create link for 0x0000 (lqi: 255) - 0x8B7F (lqi: 0)
11:33:44:307 Daylight now: goldenHour1, status: 160, daylight: 1, dark: 0
11:33:54:310 Daylight now: goldenHour1, status: 160, daylight: 1, dark: 0
11:33:55:470 APS-DATA.request id: 96, addrmode: 0x03, addr: 0x00212effff07ec3c, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
11:33:55:471    asdu (length: 2): ac00
11:33:55:487 APS-DATA.confirm id: 96, status: 0x00 SUCCESS
11:33:55:488 APS-DATA.confirm request id: 96 -> confirmed, timeout 860166
11:33:55:525 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
11:33:55:526    asdu: ac000200013cec07ffff2e210084b103feff72025cdf10250101ff
11:33:55:526 APS-DATA.indication request id: 96 -> finished
11:33:55:526 APS-DATA.request id: 96 erase from queue
11:33:55:527 APS-DATA.request id: 98, addrmode: 0x03, addr: 0x00212effff07ec3c, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
11:33:55:527    asdu (length: 2): ad01
11:33:55:527 skip create link for 0x0000 (lqi: 255) - 0x10DF (lqi: 0)
11:33:55:542 APS-DATA.confirm id: 98, status: 0x00 SUCCESS
11:33:55:543 APS-DATA.confirm request id: 98 -> confirmed, timeout 860222
11:33:55:571 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
11:33:55:571    asdu: ad000201013cec07ffff2e2100bb5ceffeff23a4607f8b250101ff
11:33:55:574 APS-DATA.indication request id: 98 -> finished
11:33:55:574 APS-DATA.request id: 98 erase from queue
11:33:55:575 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
11:33:55:575 skip create link for 0x0000 (lqi: 255) - 0x8B7F (lqi: 0)
11:34:03:319 Master: read param with arg 0x19
11:34:03:352 Device TTL 2676 s flags: 0x7
11:34:04:306 Daylight now: goldenHour1, status: 160, daylight: 1, dark: 0
11:34:04:806 sql exec SELECT conf FROM zbconf ORDER BY rowid desc limit 1
11:34:04:807 Idle timer triggered
11:34:06:306 DB save zll database items 0x00000001
11:34:06:306 DB sql exec REPLACE INTO nodes (id, state, mac, name, groups, endpoint, modelid, manufacturername, swbuildid, ritems) VALUES ('1', 'normal', '00:21:2e:ff:ff:07:ec:3c-01', 'Configuration tool 1', '65520', '1', 'ConBee II', 'dresden elektronik', '0x26720700', '{"attr/id":"1","attr/lastannounced":null,"attr/lastseen":"2022-02-05T10:33Z","attr/manufacturername":"dresden elektronik","attr/modelid":"ConBee II","attr/name":"Configuration tool 1","attr/swversion":"0x26720700","attr/type":"Configuration tool","attr/uniqueid":"00:21:2e:ff:ff:07:ec:3c-01","state/reachable":true}')
11:34:06:682 DB saved in 376 ms
11:34:11:645 APS-DATA.request id: 165, addrmode: 0x03, addr: 0x00212effff07ec3c, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
11:34:11:646    asdu (length: 2): ae00
11:34:11:665 APS-DATA.confirm id: 165, status: 0x00 SUCCESS
11:34:11:666 APS-DATA.confirm request id: 165 -> confirmed, timeout 876341
11:34:11:673 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
11:34:11:673    asdu: ae000200013cec07ffff2e210084b103feff72025cdf10250101ff
11:34:11:673 APS-DATA.indication request id: 165 -> finished
11:34:11:674 APS-DATA.request id: 165 erase from queue
11:34:11:675 APS-DATA.request id: 167, addrmode: 0x03, addr: 0x00212effff07ec3c, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
11:34:11:676    asdu (length: 2): af01
11:34:11:676 skip create link for 0x0000 (lqi: 255) - 0x10DF (lqi: 0)
11:34:11:696 APS-DATA.confirm id: 167, status: 0x00 SUCCESS
11:34:11:697 APS-DATA.confirm request id: 167 -> confirmed, timeout 876370
11:34:11:710 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
11:34:11:710    asdu: af000201013cec07ffff2e2100bb5ceffeff23a4607f8b250101ff
11:34:11:711 APS-DATA.indication request id: 167 -> finished
11:34:11:711 APS-DATA.request id: 167 erase from queue
11:34:11:711 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
11:34:11:712 skip create link for 0x0000 (lqi: 255) - 0x8B7F (lqi: 0)
11:34:14:305 Daylight now: goldenHour1, status: 160, daylight: 1, dark: 0
11:34:22:306 GW firmware version: 0x26720700
11:34:22:307 GW firmware version is up to date: 0x26720700
11:34:24:305 Daylight now: goldenHour1, status: 160, daylight: 1, dark: 0
11:34:27:966 APS-DATA.request id: 234, addrmode: 0x03, addr: 0x00212effff07ec3c, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
11:34:27:966    asdu (length: 2): b000
11:34:27:980 APS-DATA.confirm id: 234, status: 0x00 SUCCESS
11:34:27:981 APS-DATA.confirm request id: 234 -> confirmed, timeout 892661
11:34:27:996 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
11:34:27:996    asdu: b0000200013cec07ffff2e210084b103feff72025cdf10250101ff
11:34:27:997 APS-DATA.indication request id: 234 -> finished
11:34:27:997 APS-DATA.request id: 234 erase from queue
11:34:27:997 APS-DATA.request id: 236, addrmode: 0x03, addr: 0x00212effff07ec3c, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
11:34:27:998    asdu (length: 2): b101
11:34:27:998 skip create link for 0x0000 (lqi: 255) - 0x10DF (lqi: 0)
11:34:28:060 APS-DATA.confirm id: 236, status: 0x00 SUCCESS
11:34:28:061 APS-DATA.confirm request id: 236 -> confirmed, timeout 892693
11:34:28:099 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
11:34:28:099    asdu: b1000201013cec07ffff2e2100bb5ceffeff23a4607f8b250101ff
11:34:28:100 APS-DATA.indication request id: 236 -> finished
11:34:28:100 APS-DATA.request id: 236 erase from queue
11:34:28:100 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
11:34:28:101 skip create link for 0x0000 (lqi: 255) - 0x8B7F (lqi: 0)
11:34:34:307 Daylight now: goldenHour1, status: 160, daylight: 1, dark: 0
11:34:34:806 Idle timer triggered

Update: Opgelost door mijn USB harddisk eruit te trekken

[ Voor 99% gewijzigd door The Druid op 06-02-2022 09:46 ]

[tjanssen]

Goede avond allemaal. Ik draai Deconz (2.13.04) met een Conbee 2 onder Home Assistant, met firmware versie 26580700. Er staat een update klaar naar versie 26660700. Nu kan ik updaten wat ik wil, krijg de melding dat de update klaar is, maar toch blijft deze steken op versie 26580700. In de log vind ik dit terug:

code:

18:37:55:695 GCFFlasher V3_17 (c) dresden elektronik ingenieurtechnik gmbh
Reboot device  (ConBee II)
deCONZ firmware version 26580700
failed reset 20275
Reboot device  (ConBee II)
deCONZ firmware version 26580700
failed reset 19775
Reboot device  (ConBee II)
deCONZ firmware version 26580700
failed reset 19374
Reboot device  (ConBee II)
deCONZ firmware version 26580700
failed reset 19331
retry, failed
2408: Error: uart reset failed, check retry

18:37:55:696 GW firmware update exit code 3

Wanneer ik bij release notes kijk, dan vind ik versie 26660700 niet eens terug? Verder lijkt versie 26660700 ook alweer verschrikkelijk oud? Hoe krijg ik de laatste firmware op de stick? En maakt het uit dat de firmware nieuwer is dan de Deconz versie?

[Koepert]

Vraagje.. ik heb vannacht een vrij lange stroomuitval gehad. Nu is alles wel weer up..

Echter zie ik dat HomeAssistent mijn Sonoff MotionSensor wel ziet, maar geen beweging registreert.

Kijk ik via VNC naar mn deconz map, zie ik ook dat er vanaf deze sensor geen enkel lijntje loopt naar een andere node (controller, of anders), dus ik denk dat er dan dus ook geen signaal doorkomt..

Is dat iets dat normaliter vanzelf rechttrekt? Of kan ik beter de sensor opnieuw koppelen?

[Peet3kabo]

Koepert schreef op zondag 6 februari 2022 @ 09:17:
Vraagje.. ik heb vannacht een vrij lange stroomuitval gehad. Nu is alles wel weer up..

Echter zie ik dat HomeAssistent mijn Sonoff MotionSensor wel ziet, maar geen beweging registreert.

Kijk ik via VNC naar mn deconz map, zie ik ook dat er vanaf deze sensor geen enkel lijntje loopt naar een andere node (controller, of anders), dus ik denk dat er dan dus ook geen signaal doorkomt..

Is dat iets dat normaliter vanzelf rechttrekt? Of kan ik beter de sensor opnieuw koppelen?

ik zie via VNC ook niet altijd een lijntje lopen vanaf alle aangesloten apparaten, dus zou mij daar niet te druk om maken.
Misschien de sensor eens activeren met de knop of resetten?
Helpt bij mij wel eens om hem opnieuw aan een router te koppelen, en dat was dan in de uitprobeer/installeer fase of verplaatsen van het aangesloten apparaat. Nu draait alles wel stabiel en kijk ik er eigenlijk niet echt naar.
Ik zie bijvoorbeeld van een raam/deur sensor en een lamp geen lijntje lopen maar ze werken wel gewoon

[Osiris]

De lijntjes in deCONZ willen nogal eens spontaan verdwijnen, maar als je de node dan een beetje versleept, dan is 'ie d'r spontaan weer. Is een GUI-probleempje, niet een probleem met de verbinding an sich.

(Tenzij die bug ondertussen al gefixt is.)

[Mimiix]

jja2000 schreef op vrijdag 4 februari 2022 @ 17:51:
[...]


Staan ze als het goed is wel iedere keer dat ik het reset. Maar zoals ik zei in mijn eerste post, ze zijn wel te zien in deCONZ. Hier de logs bij het pairen na een restart:

code:

17:47:00:321 DEV no DDF for 0x04CD15FFFE287140, modelId: TRADFRI motion sensor
17:47:00:322 DEV create on-the-fly DDF for 0x04CD15FFFE287140
17:47:00:376 dlg action: Read binding table
17:47:00:646 Announced to internet https://phoscon.de/discover
17:47:00:647 discovery server date: Fri, 04 Feb 2022 16:47:00 GMT
17:47:00:648     local time seems to be ok
17:47:01:145 COM: /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2471167-if00 / serialno: DE2471167, ConBee II
17:47:01:269 Skip idle timer callback, too early: elapsed 944 msec
17:47:02:596 DEV Tick.Init: booted after 8000 seconds
17:47:02:650 Device firmware version 0x26720700 ConBee II
17:47:02:671 unlocked max nodes: 512
17:47:02:763 Device protocol version: 0x010E
17:47:02:862 Current channel 15
17:47:02:883 CTRL ANT_CTRL 0x03
17:47:02:885 CTRL ZDP_RESPONSE handler 0x0001
17:47:02:919 Device protocol version: 0x010E
17:47:03:020 CTRL ANT_CTRL 0x03
17:47:03:022 CTRL ZDP_RESPONSE handler 0x0001
17:47:03:168 Skip idle timer callback, too early: elapsed 949 msec
17:47:10:597 GW update firmware found: /usr/share/deCONZ/firmware/deCONZ_ConBeeII_0x26660700.bin.GCF
17:47:10:597 GW firmware version is up to date: 0x26720700
17:47:32:340 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:47:34:596 Daylight now: sunsetEnd, status: 200, daylight: 0, dark: 1
17:47:35:207 APS-DATA.request id: 170, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:47:35:208    asdu (length: 2): 1000
17:47:35:223 APS-DATA.confirm id: 170, status: 0x00 SUCCESS
17:47:35:223 APS-DATA.confirm request id: 170 -> confirmed, timeout 72585613
17:47:35:231 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:47:35:231    asdu: 10000100012ed107ffff2e2100407128feff15cd0452e1120001ff
17:47:35:232 APS-DATA.indication request id: 170 -> finished
17:47:35:232 APS-DATA.request id: 170 erase from queue
17:47:35:233 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:47:38:088 APS-DATA.request id: 183, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:47:38:089    asdu (length: 2): 1100
17:47:38:105 APS-DATA.confirm id: 183, status: 0x00 SUCCESS
17:47:38:106 APS-DATA.confirm request id: 183 -> confirmed, timeout 72588494
17:47:38:111 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:47:38:112    asdu: 11000100012ed107ffff2e2100407128feff15cd0452e1120001ff
17:47:38:112 APS-DATA.indication request id: 183 -> finished
17:47:38:112 APS-DATA.request id: 183 erase from queue
17:47:38:113 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:47:40:968 APS-DATA.request id: 197, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:47:40:969    asdu (length: 2): 1200
17:47:40:990 APS-DATA.confirm id: 197, status: 0x00 SUCCESS
17:47:40:991 APS-DATA.confirm request id: 197 -> confirmed, timeout 72591375
17:47:41:029 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:47:41:030    asdu: 12000100012ed107ffff2e2100407128feff15cd0452e1120001ff
17:47:41:030 APS-DATA.indication request id: 197 -> finished
17:47:41:031 APS-DATA.request id: 197 erase from queue
17:47:41:031 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:47:43:602 New websocket 127.0.0.1:47196 (state: 3) 
17:47:43:848 APS-DATA.request id: 211, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:47:43:849    asdu (length: 2): 1300
17:47:43:867 APS-DATA.confirm id: 211, status: 0x00 SUCCESS
17:47:43:868 APS-DATA.confirm request id: 211 -> confirmed, timeout 72594254
17:47:43:909 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:47:43:909    asdu: 13000100012ed107ffff2e2100407128feff15cd0452e1120001ff
17:47:43:910 APS-DATA.indication request id: 211 -> finished
17:47:43:910 APS-DATA.request id: 211 erase from queue
17:47:43:910 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:47:44:596 Daylight now: sunsetEnd, status: 200, daylight: 0, dark: 1
17:47:46:727 APS-DATA.request id: 224, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:47:46:729    asdu (length: 2): 1400
17:47:46:747 APS-DATA.confirm id: 224, status: 0x00 SUCCESS
17:47:46:748 APS-DATA.confirm request id: 224 -> confirmed, timeout 72597134
17:47:46:789 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:47:46:790    asdu: 14000100012ed107ffff2e2100407128feff15cd0452e1120001ff
17:47:46:790 APS-DATA.indication request id: 224 -> finished
17:47:46:790 APS-DATA.request id: 224 erase from queue
17:47:46:791 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:47:48:264 Websocket disconnected 127.0.0.1:47196, state: 0, close-code: 1000, reason: 
17:47:49:348 New websocket 127.0.0.1:47228 (state: 3) 
17:47:49:607 APS-DATA.request id: 238, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:47:49:608    asdu (length: 2): 1500
17:47:49:626 APS-DATA.confirm id: 238, status: 0x00 SUCCESS
17:47:49:626 APS-DATA.confirm request id: 238 -> confirmed, timeout 72600014
17:47:49:671 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:47:49:671    asdu: 15000100012ed107ffff2e2100407128feff15cd0452e1120001ff
17:47:49:672 APS-DATA.indication request id: 238 -> finished
17:47:49:672 APS-DATA.request id: 238 erase from queue
17:47:49:672 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:47:52:488 APS-DATA.request id: 251, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:47:52:489    asdu (length: 2): 1600
17:47:52:509 APS-DATA.confirm id: 251, status: 0x00 SUCCESS
17:47:52:510 APS-DATA.confirm request id: 251 -> confirmed, timeout 72602894
17:47:52:549 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:47:52:550    asdu: 16000100012ed107ffff2e2100407128feff15cd0452e1120001ff
17:47:52:550 APS-DATA.indication request id: 251 -> finished
17:47:52:550 APS-DATA.request id: 251 erase from queue
17:47:52:550 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:47:54:595 Daylight now: sunsetEnd, status: 200, daylight: 0, dark: 1
17:47:54:615 Master: read param with arg 0x19
17:47:54:673 Device TTL 5882 s flags: 0x7
17:47:55:096 APS-DATA.request id: 7, addrmode: 0x02, addr: 0xfffc, profile: 0x0000, cluster: 0x0036, ep: 0x00 -> 0x00 queue: 0 len: 3 tx.options 0x00
17:47:55:097    asdu (length: 3): 004101
17:47:55:098 send permit join, duration: 65
17:47:55:099 APS-DATA.request id: 8, addrmode: 0x02, addr: 0xfffc, profile: 0xA1E0, cluster: 0x0021, ep: 0xF2 -> 0xF2 queue: 1 len: 6 tx.options 0x00
17:47:55:100    asdu (length: 6): 1901020b2800
17:47:55:368 APS-DATA.request id: 11, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 2 len: 2 tx.options 0x00
17:47:55:368    asdu (length: 2): 1700
17:47:55:385 APS-DATA.confirm id: 11, status: 0x00 SUCCESS
17:47:55:386 APS-DATA.confirm request id: 11 -> confirmed, timeout 72605773
17:47:55:430 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:47:55:431    asdu: 17000100012ed107ffff2e2100407128feff15cd0452e1120001ff
17:47:55:431 APS-DATA.indication request id: 11 -> finished
17:47:55:432 APS-DATA.request id: 11 erase from queue
17:47:55:432 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:47:55:782 APS-DATA.confirm id: 7, status: 0x00 SUCCESS
17:47:55:790 APS-DATA.confirm id: 8, status: 0x00 SUCCESS
17:47:55:848 aps request id: 7 finished, erase from queue
17:47:55:928 aps request id: 8 finished, erase from queue
17:47:56:096 Idle timer triggered
17:47:58:248 APS-DATA.request id: 24, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:47:58:249    asdu (length: 2): 1800
17:47:58:269 APS-DATA.confirm id: 24, status: 0x00 SUCCESS
17:47:58:270 APS-DATA.confirm request id: 24 -> confirmed, timeout 72608655
17:47:58:307 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:47:58:307    asdu: 18000100012ed107ffff2e2100407128feff15cd0452e1120001ff
17:47:58:308 APS-DATA.indication request id: 24 -> finished
17:47:58:308 APS-DATA.request id: 24 erase from queue
17:47:58:308 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:48:01:128 APS-DATA.request id: 38, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:48:01:129    asdu (length: 2): 1900
17:48:01:147 APS-DATA.confirm id: 38, status: 0x00 SUCCESS
17:48:01:148 APS-DATA.confirm request id: 38 -> confirmed, timeout 72611535
17:48:01:189 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:48:01:190    asdu: 19000100012ed107ffff2e2100407128feff15cd0452e1120001ff
17:48:01:190 APS-DATA.indication request id: 38 -> finished
17:48:01:191 APS-DATA.request id: 38 erase from queue
17:48:01:191 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:48:04:008 APS-DATA.request id: 51, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:48:04:009    asdu (length: 2): 1a00
17:48:04:028 APS-DATA.confirm id: 51, status: 0x00 SUCCESS
17:48:04:028 APS-DATA.confirm request id: 51 -> confirmed, timeout 72614415
17:48:04:071 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:48:04:071    asdu: 1a000300012ed107ffff2e2100407128feff15cd0452e1120001ff
17:48:04:072 APS-DATA.indication request id: 51 -> finished
17:48:04:072 APS-DATA.request id: 51 erase from queue
17:48:04:596 Daylight now: sunsetEnd, status: 200, daylight: 0, dark: 1
17:48:06:407 APS-DATA.request id: 63, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:48:06:408    asdu (length: 2): 1b01
17:48:06:428 APS-DATA.confirm id: 63, status: 0x00 SUCCESS
17:48:06:429 APS-DATA.confirm request id: 63 -> confirmed, timeout 72616813
17:48:06:469 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:48:06:469    asdu: 1b000301012ed107ffff2e21006bac1afeff14430ca74d150001ff
17:48:06:470 APS-DATA.indication request id: 63 -> finished
17:48:06:470 APS-DATA.request id: 63 erase from queue
17:48:06:471 neigbor 0x0c4314fffe1aac6b is unknown child
17:48:06:890 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 2, node: 0x4DA7
17:48:06:890 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 1, node: 0x4DA7
17:48:06:891 new node - ext: 0x0c4314fffe1aac6b, nwk: 0x4DA7
17:48:08:808 APS-DATA.request id: 74, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:48:08:809    asdu (length: 2): 1c02
17:48:08:826 APS-DATA.confirm id: 74, status: 0x00 SUCCESS
17:48:08:827 APS-DATA.confirm request id: 74 -> confirmed, timeout 72619214
17:48:08:871 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:48:08:872    asdu: 1c000302012ed107ffff2e2100c69064feff65112ce13f150001ff
17:48:08:873 APS-DATA.indication request id: 74 -> finished
17:48:08:873 APS-DATA.request id: 74 erase from queue
17:48:08:874 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:48:08:874 neigbor 0x2c1165fffe6490c6 is unknown child
17:48:08:921 Websocket 127.0.0.1:47228 send message: {"attr":{"id":"1","lastannounced":null,"lastseen":"2022-02-04T16:48Z","manufacturername":"dresden elektronik","modelid":"ConBee II","name":"Configuration tool 1","swversion":"0x26720700","type":"Configuration tool","uniqueid":"00:21:2e:ff:ff:07:d1:2e-01"},"e":"changed","id":"1","r":"lights","t":"event","uniqueid":"00:21:2e:ff:ff:07:d1:2e-01"} (ret = 344)
17:48:09:292 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 2, node: 0x3FE1
17:48:09:293 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 1, node: 0x3FE1
17:48:09:294 new node - ext: 0x2c1165fffe6490c6, nwk: 0x3FE1
17:48:11:688 APS-DATA.request id: 88, addrmode: 0x03, addr: 0x0c4314fffe1aac6b, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:48:11:689    asdu (length: 2): 1d00
17:48:14:595 Daylight now: sunsetEnd, status: 200, daylight: 0, dark: 1
17:48:19:598 CTRL db store gui node 00:21:2e:ff:ff:07:d1:2e
17:48:19:601 CTRL db store gui node 04:cd:15:ff:fe:28:71:40
17:48:19:602 CTRL db store gui node 0c:43:14:ff:fe:1a:ac:6b
17:48:19:603 CTRL db store gui node 2c:11:65:ff:fe:64:90:c6
17:48:19:618 saved node state in 0 ms
17:48:19:618 sync() in 0 ms
17:48:21:787 APS-DATA.confirm id: 88, status: 0xD0 
17:48:22:248 APS-DATA.request id: 131, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:48:22:249    asdu (length: 2): 1e00
17:48:22:268 APS-DATA.confirm id: 131, status: 0x00 SUCCESS
17:48:22:269 APS-DATA.confirm request id: 131 -> confirmed, timeout 72632654
17:48:22:312 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:48:22:313    asdu: 1e000300012ed107ffff2e2100407128feff15cd0452e1120001ff
17:48:22:313 APS-DATA.indication request id: 131 -> finished
17:48:22:313 APS-DATA.request id: 131 erase from queue
17:48:24:596 Daylight now: sunsetEnd, status: 200, daylight: 0, dark: 1
17:48:24:648 APS-DATA.request id: 143, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:48:24:649    asdu (length: 2): 1f01
17:48:24:665 APS-DATA.confirm id: 143, status: 0x00 SUCCESS
17:48:24:666 APS-DATA.confirm request id: 143 -> confirmed, timeout 72635054
17:48:24:701 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:48:24:702    asdu: 1f000301012ed107ffff2e21006bac1afeff14430ca74d150001ff
17:48:24:702 APS-DATA.indication request id: 143 -> finished
17:48:24:702 APS-DATA.request id: 143 erase from queue
17:48:24:703 skip create link for 0x0000 (lqi: 255) - 0x4DA7 (lqi: 0)
17:48:26:096 sql exec SELECT conf FROM zbconf ORDER BY rowid desc limit 1
17:48:26:098 Wait 3s till query finished
17:48:26:771 APS-DATA.indication srcAddr: 0xe152, srcEp: 0x01 dstAddrMode: 1, profile: 0x0104, cluster: 0x0006, lqi: 255, rssi: -49
17:48:26:771    asdu: 0164420008070000
17:48:26:772 APS-DATA.indication from child 0xE152
17:48:26:772 [INFO] - Button 1002 - TRADFRI motion sensor, broadcast to: 0x0002, endpoint: 0x01, cluster: ONOFF (0x0006), action: On with timed off, payload: 0008070000, zclSeq: 100
17:48:26:773 0x04CD15FFFE287140 (TRADFRI motion sensor) create binding for attribute reporting of cluster 0x0001 on endpoint 0x01
17:48:26:773 queue binding task for 0x04CD15FFFE287140, cluster 0x0001
17:48:26:774 Force binding of attribute reporting for sensor TRÅDFRI Motion sensor
17:48:26:787 Websocket 127.0.0.1:47228 send message: {"config":{"alert":"none","battery":74,"delay":180,"duration":60,"group":"2","on":true,"reachable":true},"e":"changed","id":"2","r":"sensors","t":"event","uniqueid":"04:cd:15:ff:fe:28:71:40-01-0006"} (ret = 199)
17:48:26:789 Websocket 127.0.0.1:47228 send message: {"e":"changed","id":"2","r":"sensors","state":{"dark":true,"lastupdated":"2022-02-04T16:48:26.773","presence":true},"t":"event","uniqueid":"04:cd:15:ff:fe:28:71:40-01-0006"} (ret = 173)
17:48:26:790 Websocket 127.0.0.1:47228 send message: {"attr":{"id":"2","lastannounced":"2022-02-03T20:42:51Z","lastseen":"2022-02-04T16:48Z","manufacturername":"IKEA of Sweden","modelid":"TRADFRI motion sensor","name":"TRÅDFRI Motion sensor","swversion":"2.0.022","type":"ZHAPresence","uniqueid":"04:cd:15:ff:fe:28:71:40-01-0006"},"e":"changed","id":"2","r":"sensors","t":"event","uniqueid":"04:cd:15:ff:fe:28:71:40-01-0006"} (ret = 373)
17:48:26:792 APS-DATA.request id: 154, addrmode: 0x03, addr: 0x04cd15fffe287140, profile: 0x0000, cluster: 0x0021, ep: 0x00 -> 0x00 queue: 0 len: 22 tx.options 0x04
17:48:26:793    asdu (length: 22): 38407128feff15cd04010100032ed107ffff2e210001
17:48:27:048 APS-DATA.request id: 156, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 1 len: 2 tx.options 0x00
17:48:27:049    asdu (length: 2): 2002
17:48:27:067 APS-DATA.confirm id: 156, status: 0x00 SUCCESS
17:48:27:068 APS-DATA.confirm request id: 156 -> confirmed, timeout 72637454
17:48:27:110 Set sensor check interval to 100 milliseconds
17:48:27:111 Wait 2s till query finished
17:48:27:116 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:48:27:116    asdu: 20000302012ed107ffff2e2100c69064feff65112ce13f150001ff
17:48:27:117 APS-DATA.indication request id: 156 -> finished
17:48:27:117 APS-DATA.request id: 156 erase from queue
17:48:27:117 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:48:27:118 skip create link for 0x0000 (lqi: 255) - 0x3FE1 (lqi: 0)
17:48:27:834 APS-DATA.confirm id: 154, status: 0x00 SUCCESS
17:48:27:835 APS-DATA.confirm request id: 154 -> confirmed, timeout 72637199
17:48:28:096 Wait 1s till query finished
17:48:28:844 APS-DATA.indication srcAddr: 0xe152, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8021, lqi: 255, rssi: -49
17:48:28:845    asdu: 3800
17:48:28:846 APS-DATA.indication request id: 154 -> finished
17:48:28:846 APS-DATA.indication from child 0xE152
17:48:28:847 APS-DATA.request id: 154 erase from queue
17:48:28:848 Bind response success for 0x04cd15fffe287140 ep: 0x01 cluster: 0x0001
17:48:28:848 0x04CD15FFFE287140: added ZCL value 0x01/0x0001/0x0021
17:48:28:849 configure reporting rq seq 2 for 0x04CD15FFFE287140, attribute 0x0001/0x0021
17:48:28:850 APS-DATA.request id: 166, addrmode: 0x03, addr: 0x04cd15fffe287140, profile: 0x0104, cluster: 0x0001, ep: 0x01 -> 0x01 queue: 0 len: 12 tx.options 0x04
17:48:28:851    asdu (length: 12): 100206002100202c018c0a01
17:48:29:096 Wait 1s till query finished
17:48:29:899 APS-DATA.confirm id: 166, status: 0x00 SUCCESS
17:48:29:900 APS-DATA.confirm request id: 166 -> erase from queue
17:48:30:003 aps request id: 166 finished, erase from queue
17:48:30:096 Wait 0s till query finished
17:48:30:408 APS-DATA.request id: 174, addrmode: 0x03, addr: 0x2c1165fffe6490c6, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:48:30:408    asdu (length: 2): 2100
17:48:31:015 APS-DATA.indication srcAddr: 0xe152, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0001, lqi: 255, rssi: -49
17:48:31:016    asdu: 08020700
17:48:31:016 APS-DATA.indication from child 0xE152
17:48:31:017 ZCL configure reporting rsp seq: 2 0x04CD15FFFE287140 for ep: 0x01 cluster: 0x0001 attr: 0x0021 status: 0x00
17:48:31:017 APS-DATA.request id: 178, addrmode: 0x02, addr: 0xe152, profile: 0x0104, cluster: 0x0001, ep: 0x01 -> 0x01 queue: 1 len: 5 tx.options 0x04
17:48:31:018    asdu (length: 5): 10020b0700
17:48:31:039 APS-DATA.confirm id: 178, status: 0x00 SUCCESS
17:48:31:040 APS-DATA.confirm request id: 178 -> erase from queue
17:48:31:078 aps request id: 178 finished, erase from queue
17:48:31:096 Idle timer triggered
17:48:34:596 Daylight now: sunsetEnd, status: 200, daylight: 0, dark: 1
17:48:40:498 APS-DATA.confirm id: 174, status: 0xD0 
17:48:40:968 APS-DATA.request id: 219, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:48:40:969    asdu (length: 2): 2200
17:48:40:983 APS-DATA.confirm id: 219, status: 0x00 SUCCESS
17:48:40:984 APS-DATA.confirm request id: 219 -> confirmed, timeout 72651374
17:48:41:022 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:48:41:023    asdu: 22000300012ed107ffff2e2100407128feff15cd0452e1120001ff
17:48:41:023 APS-DATA.indication request id: 219 -> finished
17:48:41:024 APS-DATA.request id: 219 erase from queue
17:48:43:368 APS-DATA.request id: 231, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:48:43:369    asdu (length: 2): 2301
17:48:43:387 APS-DATA.confirm id: 231, status: 0x00 SUCCESS
17:48:43:388 APS-DATA.confirm request id: 231 -> confirmed, timeout 72653775
17:48:43:425 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:48:43:425    asdu: 23000301012ed107ffff2e21006bac1afeff14430ca74d150001ff
17:48:43:426 APS-DATA.indication request id: 231 -> finished
17:48:43:426 APS-DATA.request id: 231 erase from queue
17:48:43:426 skip create link for 0x0000 (lqi: 255) - 0x4DA7 (lqi: 0)
17:48:44:595 Daylight now: sunsetEnd, status: 200, daylight: 0, dark: 1
17:48:45:768 APS-DATA.request id: 242, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:48:45:769    asdu (length: 2): 2402
17:48:45:788 APS-DATA.confirm id: 242, status: 0x00 SUCCESS
17:48:45:789 APS-DATA.confirm request id: 242 -> confirmed, timeout 72656175
17:48:45:829 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:48:45:830    asdu: 24000302012ed107ffff2e2100c69064feff65112ce13f150001ff
17:48:45:830 APS-DATA.indication request id: 242 -> finished
17:48:45:831 APS-DATA.request id: 242 erase from queue
17:48:45:831 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:48:45:831 skip create link for 0x0000 (lqi: 255) - 0x3FE1 (lqi: 0)
17:48:49:607 APS-DATA.request id: 4, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:48:49:608    asdu (length: 2): 2500
17:48:49:625 APS-DATA.confirm id: 4, status: 0x00 SUCCESS
17:48:49:628 APS-DATA.confirm request id: 4 -> confirmed, timeout 72660013
17:48:49:668 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:48:49:668    asdu: 25000300012ed107ffff2e2100407128feff15cd0452e1120001ff
17:48:49:668 APS-DATA.indication request id: 4 -> finished
17:48:49:669 APS-DATA.request id: 4 erase from queue
17:48:52:007 APS-DATA.request id: 15, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:48:52:008    asdu (length: 2): 2601
17:48:52:028 APS-DATA.confirm id: 15, status: 0x00 SUCCESS
17:48:52:029 APS-DATA.confirm request id: 15 -> confirmed, timeout 72662414
17:48:52:068 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:48:52:068    asdu: 26000301012ed107ffff2e21006bac1afeff14430ca74d150001ff
17:48:52:069 APS-DATA.indication request id: 15 -> finished
17:48:52:069 APS-DATA.request id: 15 erase from queue
17:48:52:069 skip create link for 0x0000 (lqi: 255) - 0x4DA7 (lqi: 0)
17:48:54:407 APS-DATA.request id: 27, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:48:54:409    asdu (length: 2): 2702
17:48:54:427 APS-DATA.confirm id: 27, status: 0x00 SUCCESS
17:48:54:428 APS-DATA.confirm request id: 27 -> confirmed, timeout 72664814
17:48:54:471 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:48:54:472    asdu: 27000302012ed107ffff2e2100c69064feff65112ce13f150001ff
17:48:54:472 APS-DATA.indication request id: 27 -> finished
17:48:54:473 APS-DATA.request id: 27 erase from queue
17:48:54:473 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:48:54:473 skip create link for 0x0000 (lqi: 255) - 0x3FE1 (lqi: 0)
17:48:54:596 Daylight now: sunsetEnd, status: 200, daylight: 0, dark: 1
17:48:54:612 Master: read param with arg 0x19
17:48:54:674 Device TTL 5822 s flags: 0x7
17:48:55:896 APS-DATA.request id: 30, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0033, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:48:55:897    asdu (length: 2): 3700
17:48:55:916 APS-DATA.confirm id: 30, status: 0x00 SUCCESS
17:48:55:917 APS-DATA.confirm request id: 30 -> confirmed, timeout 72666302
17:48:55:959 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8033, lqi: 221, rssi: 30
17:48:55:960    asdu: 3700000000
17:48:55:961 APS-DATA.indication request id: 30 -> finished
17:48:55:961 APS-DATA.request id: 30 erase from queue
17:48:55:961 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 9, node: 0x0000
17:48:56:096 APS-DATA.request id: 37, addrmode: 0x02, addr: 0xfffc, profile: 0x0000, cluster: 0x0036, ep: 0x00 -> 0x00 queue: 0 len: 3 tx.options 0x00
17:48:56:097    asdu (length: 3): 014101
17:48:56:097 send permit join, duration: 65
17:48:56:097 APS-DATA.request id: 38, addrmode: 0x02, addr: 0xfffc, profile: 0xA1E0, cluster: 0x0021, ep: 0xF2 -> 0xF2 queue: 1 len: 6 tx.options 0x00
17:48:56:098    asdu (length: 6): 1903020b2800
17:48:56:771 APS-DATA.confirm id: 37, status: 0x00 SUCCESS
17:48:56:782 APS-DATA.confirm id: 38, status: 0x00 SUCCESS
17:48:56:826 aps request id: 37 finished, erase from queue
17:48:56:888 aps request id: 38 finished, erase from queue
17:48:58:248 APS-DATA.request id: 48, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:48:58:249    asdu (length: 2): 2800
17:48:58:267 APS-DATA.confirm id: 48, status: 0x00 SUCCESS
17:48:58:268 APS-DATA.confirm request id: 48 -> confirmed, timeout 72668654
17:48:58:307 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:48:58:307    asdu: 28000300012ed107ffff2e2100407128feff15cd0452e1120001ff
17:48:58:308 APS-DATA.indication request id: 48 -> finished
17:48:58:308 APS-DATA.request id: 48 erase from queue
17:49:00:648 APS-DATA.request id: 60, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:49:00:649    asdu (length: 2): 2901
17:49:00:667 APS-DATA.confirm id: 60, status: 0x00 SUCCESS
17:49:00:668 APS-DATA.confirm request id: 60 -> confirmed, timeout 72671054
17:49:00:707 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:49:00:708    asdu: 2900010100
17:49:00:708 APS-DATA.indication request id: 60 -> finished
17:49:00:708 APS-DATA.request id: 60 erase from queue
17:49:00:709 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:49:01:096 Idle timer triggered
17:49:04:488 APS-DATA.request id: 77, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:49:04:489    asdu (length: 2): 2a00
17:49:04:508 APS-DATA.confirm id: 77, status: 0x00 SUCCESS
17:49:04:509 APS-DATA.confirm request id: 77 -> confirmed, timeout 72674895
17:49:04:547 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:49:04:548    asdu: 2a000300012ed107ffff2e2100407128feff15cd0452e1120001ff
17:49:04:548 APS-DATA.indication request id: 77 -> finished
17:49:04:549 APS-DATA.request id: 77 erase from queue
17:49:04:596 Daylight now: sunsetEnd, status: 200, daylight: 0, dark: 1
17:49:06:888 APS-DATA.request id: 89, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:49:06:889    asdu (length: 2): 2b01
17:49:06:909 APS-DATA.confirm id: 89, status: 0x00 SUCCESS
17:49:06:910 APS-DATA.confirm request id: 89 -> confirmed, timeout 72677294
17:49:06:949 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:49:06:950    asdu: 2b000301012ed107ffff2e2100c69064feff65112ca2d8150001ff
17:49:06:950 APS-DATA.indication request id: 89 -> finished
17:49:06:950 APS-DATA.request id: 89 erase from queue
17:49:06:951     * different nwk address 0x3FE1 / 0xD8A2
17:49:06:951 neigbor 0x2c1165fffe6490c6 is unknown child
17:49:09:288 APS-DATA.request id: 100, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:49:09:289    asdu (length: 2): 2c02
17:49:09:309 APS-DATA.confirm id: 100, status: 0x00 SUCCESS
17:49:09:310 APS-DATA.confirm request id: 100 -> confirmed, timeout 72679695
17:49:09:351 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:49:09:352    asdu: 2c000302012ed107ffff2e21006bac1afeff14430c57e9150001ff
17:49:09:352 APS-DATA.indication request id: 100 -> finished
17:49:09:353 APS-DATA.request id: 100 erase from queue
17:49:09:353 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:49:09:353     * different nwk address 0x4DA7 / 0xE957
17:49:09:353 neigbor 0x0c4314fffe1aac6b is unknown child
17:49:09:366 Websocket 127.0.0.1:47228 send message: {"attr":{"id":"1","lastannounced":null,"lastseen":"2022-02-04T16:49Z","manufacturername":"dresden elektronik","modelid":"ConBee II","name":"Configuration tool 1","swversion":"0x26720700","type":"Configuration tool","uniqueid":"00:21:2e:ff:ff:07:d1:2e-01"},"e":"changed","id":"1","r":"lights","t":"event","uniqueid":"00:21:2e:ff:ff:07:d1:2e-01"} (ret = 344)
17:49:13:128 APS-DATA.request id: 118, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:49:13:129    asdu (length: 2): 2d00
17:49:13:151 APS-DATA.confirm id: 118, status: 0x00 SUCCESS
17:49:13:152 APS-DATA.confirm request id: 118 -> confirmed, timeout 72683535
17:49:13:191 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:49:13:191    asdu: 2d000300012ed107ffff2e2100407128feff15cd0452e1120001ff
17:49:13:192 APS-DATA.indication request id: 118 -> finished
17:49:13:192 APS-DATA.request id: 118 erase from queue
17:49:14:596 Daylight now: sunsetEnd, status: 200, daylight: 0, dark: 1
17:49:15:528 APS-DATA.request id: 129, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:49:15:529    asdu (length: 2): 2e01
17:49:15:545 APS-DATA.confirm id: 129, status: 0x00 SUCCESS
17:49:15:546 APS-DATA.confirm request id: 129 -> confirmed, timeout 72685934
17:49:15:588 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:49:15:589    asdu: 2e000301012ed107ffff2e2100c69064feff65112ca2d8150001ff
17:49:15:589 APS-DATA.indication request id: 129 -> finished
17:49:15:589 APS-DATA.request id: 129 erase from queue
17:49:15:590     * different nwk address 0x3FE1 / 0xD8A2
17:49:15:590 neigbor 0x2c1165fffe6490c6 is unknown child
17:49:17:928 APS-DATA.request id: 141, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:49:17:929    asdu (length: 2): 2f02
17:49:17:949 APS-DATA.confirm id: 141, status: 0x00 SUCCESS
17:49:17:950 APS-DATA.confirm request id: 141 -> confirmed, timeout 72688334
17:49:17:986 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:49:17:987    asdu: 2f000302012ed107ffff2e21006bac1afeff14430c57e9150001ff
17:49:17:988 APS-DATA.indication request id: 141 -> finished
17:49:17:988 APS-DATA.request id: 141 erase from queue
17:49:17:988 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:49:17:988     * different nwk address 0x4DA7 / 0xE957
17:49:17:989 neigbor 0x0c4314fffe1aac6b is unknown child
17:49:22:408 node 00C4314FFFE1AAC6B leave wait state
17:49:24:597 Daylight now: sunsetEnd, status: 200, daylight: 0, dark: 1
17:49:26:795 sensor 2 (TRADFRI motion sensor): disable presence
17:49:26:804 Websocket 127.0.0.1:47228 send message: {"e":"changed","id":"2","r":"sensors","state":{"dark":true,"lastupdated":"2022-02-04T16:49:26.796","presence":false},"t":"event","uniqueid":"04:cd:15:ff:fe:28:71:40-01-0006"} (ret = 174)
17:49:26:996 Set sensor check interval to 1000 milliseconds
17:49:31:096 sql exec SELECT conf FROM zbconf ORDER BY rowid desc limit 1
17:49:31:097 Idle timer triggered
17:49:31:097 Force read attributes for ZHAPresence SensorNode TRÅDFRI Motion sensor
17:49:32:096 Wait 1s till query finished
17:49:33:096 Idle timer triggered
17:49:33:288 APS-DATA.request id: 204, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:49:33:289    asdu (length: 2): 3000
17:49:33:306 APS-DATA.confirm id: 204, status: 0x00 SUCCESS
17:49:33:307 APS-DATA.confirm request id: 204 -> confirmed, timeout 72703694
17:49:33:347 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:49:33:348    asdu: 30000300012ed107ffff2e2100407128feff15cd0452e1120001ff
17:49:33:348 APS-DATA.indication request id: 204 -> finished
17:49:33:349 APS-DATA.request id: 204 erase from queue
17:49:34:596 Daylight now: sunsetEnd, status: 200, daylight: 0, dark: 1
17:49:41:207 node 02C1165FFFE6490C6 leave wait state
17:49:44:596 Daylight now: sunsetEnd, status: 200, daylight: 0, dark: 1
17:49:48:648 APS-DATA.request id: 12, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:49:48:649    asdu (length: 2): 3101
17:49:48:668 APS-DATA.confirm id: 12, status: 0x00 SUCCESS
17:49:48:669 APS-DATA.confirm request id: 12 -> confirmed, timeout 72719054
17:49:48:711 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:49:48:712    asdu: 31000301012ed107ffff2e2100c69064feff65112ca2d8150001ff
17:49:48:712 APS-DATA.indication request id: 12 -> finished
17:49:48:713 APS-DATA.request id: 12 erase from queue
17:49:48:713     * different nwk address 0x3FE1 / 0xD8A2
17:49:48:713 neigbor 0x2c1165fffe6490c6 is unknown child
17:49:54:596 Daylight now: sunsetEnd, status: 200, daylight: 0, dark: 1
17:49:54:631 Master: read param with arg 0x19
17:49:54:654 Device TTL 5761 s flags: 0x7
17:49:57:096 binding/unbinding timeout srcAddr: 0x04CD15FFFE287140, retry
17:49:57:098 APS-DATA.request id: 47, addrmode: 0x02, addr: 0xfffc, profile: 0x0000, cluster: 0x0036, ep: 0x00 -> 0x00 queue: 0 len: 3 tx.options 0x00
17:49:57:098    asdu (length: 3): 024101
17:49:57:099 send permit join, duration: 65
17:49:57:100 APS-DATA.request id: 48, addrmode: 0x02, addr: 0xfffc, profile: 0xA1E0, cluster: 0x0021, ep: 0xF2 -> 0xF2 queue: 1 len: 6 tx.options 0x00
17:49:57:101    asdu (length: 6): 1904020b2800
17:49:57:776 APS-DATA.confirm id: 47, status: 0x00 SUCCESS
17:49:57:784 APS-DATA.confirm id: 48, status: 0x00 SUCCESS
17:49:57:848 aps request id: 47 finished, erase from queue
17:49:57:928 aps request id: 48 finished, erase from queue
17:49:58:096 APS-DATA.request id: 53, addrmode: 0x03, addr: 0x04cd15fffe287140, profile: 0x0000, cluster: 0x0021, ep: 0x00 -> 0x00 queue: 0 len: 22 tx.options 0x04
17:49:58:097    asdu (length: 22): 2b407128feff15cd04010100032ed107ffff2e210001
17:50:03:095 Idle timer triggered
17:50:04:008 APS-DATA.request id: 78, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 1 len: 2 tx.options 0x00
17:50:04:010    asdu (length: 2): 3202
17:50:04:027 APS-DATA.confirm id: 78, status: 0x00 SUCCESS
17:50:04:028 APS-DATA.confirm request id: 78 -> confirmed, timeout 72734415
17:50:04:070 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:50:04:070    asdu: 3200010200
17:50:04:071 APS-DATA.indication request id: 78 -> finished
17:50:04:071 APS-DATA.request id: 78 erase from queue
17:50:04:071 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:50:04:596 Daylight now: sunsetEnd, status: 200, daylight: 0, dark: 1
17:50:05:748 APS-DATA.confirm id: 53, status: 0xF0 TRANSACTION_EXPIRED
17:50:05:749 APS-DATA.confirm id: 53 status: transaction expired
17:50:14:597 Daylight now: sunsetEnd, status: 200, daylight: 0, dark: 1
17:50:20:808 APS-DATA.request id: 147, addrmode: 0x03, addr: 0x00212effff07d12e, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:50:20:809    asdu (length: 2): 3300
17:50:20:828 APS-DATA.confirm id: 147, status: 0x00 SUCCESS
17:50:20:829 APS-DATA.confirm request id: 147 -> confirmed, timeout 72751215
17:50:20:868 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
17:50:20:868    asdu: 33000100012ed107ffff2e2100407128feff15cd0452e1120001ff
17:50:20:869 APS-DATA.indication request id: 147 -> finished
17:50:20:869 APS-DATA.request id: 147 erase from queue
17:50:20:869 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
17:50:20:878 Websocket 127.0.0.1:47228 send message: {"attr":{"id":"1","lastannounced":null,"lastseen":"2022-02-04T16:50Z","manufacturername":"dresden elektronik","modelid":"ConBee II","name":"Configuration tool 1","swversion":"0x26720700","type":"Configuration tool","uniqueid":"00:21:2e:ff:ff:07:d1:2e-01"},"e":"changed","id":"1","r":"lights","t":"event","uniqueid":"00:21:2e:ff:ff:07:d1:2e-01"} (ret = 344)
17:50:24:596 Daylight now: sunsetEnd, status: 200, daylight: 0, dark: 1

Ik zag de 0xF0 error verschijnen tegen het einde, maar dit was al nadat ik de lampen eenmaal uit en aan heb gezet.

ER is iets te zien geweest in deconz, kan dat kloppen?

Doe je er meerdere tegelijk? Anders even eentje per keer doen.

[Mimiix]

tjanssen schreef op zaterdag 5 februari 2022 @ 18:53:
Goede avond allemaal. Ik draai Deconz (2.13.04) met een Conbee 2 onder Home Assistant, met firmware versie 26580700. Er staat een update klaar naar versie 26660700. Nu kan ik updaten wat ik wil, krijg de melding dat de update klaar is, maar toch blijft deze steken op versie 26580700. In de log vind ik dit terug:

code:

18:37:55:695 GCFFlasher V3_17 (c) dresden elektronik ingenieurtechnik gmbh
Reboot device  (ConBee II)
deCONZ firmware version 26580700
failed reset 20275
Reboot device  (ConBee II)
deCONZ firmware version 26580700
failed reset 19775
Reboot device  (ConBee II)
deCONZ firmware version 26580700
failed reset 19374
Reboot device  (ConBee II)
deCONZ firmware version 26580700
failed reset 19331
retry, failed
2408: Error: uart reset failed, check retry

18:37:55:696 GW firmware update exit code 3

Wanneer ik bij release notes kijk, dan vind ik versie 26660700 niet eens terug? Verder lijkt versie 26660700 ook alweer verschrikkelijk oud? Hoe krijg ik de laatste firmware op de stick? En maakt het uit dat de firmware nieuwer is dan de Deconz versie?

Ik zou nooit via de addon updaten. Die sloopt meer dan je lief is.

Firmware versies vind je hier: https://github.com/dresde...n/wiki/Firmware-Changelog

Ik zou deze gebruiken als guide: https://github.com/dresde...ki/Update-deCONZ-manually

[glaswerk]

Mimiix schreef op maandag 7 februari 2022 @ 08:34:
[...]

Ik zou deze gebruiken als guide: https://github.com/dresde...ki/Update-deCONZ-manually

Ik denk 'hee, firmware...', en heb maar even gecheckt. Draai deconz-headless (2.13.04) up Ubuntu 20.04, geen VM of docker o.i.d. Phoscon vertelt me dat ik nog op een firmware van 2jr geleden zit. Klopt het dat de firmware niet automatisch door deconz of Phoscon bijgewerkt wordt, en dat dit altijd handmatig moet zoals beschreven in de guide?

[Mimiix]

glaswerk schreef op maandag 7 februari 2022 @ 08:47:
[...]


Ik denk 'hee, firmware...', en heb maar even gecheckt. Draai deconz-headless (2.13.04) up Ubuntu 20.04, geen VM of docker o.i.d. Phoscon vertelt me dat ik nog op een firmware van 2jr geleden zit. Klopt het dat de firmware niet automatisch door deconz of Phoscon bijgewerkt wordt, en dat dit altijd handmatig moet zoals beschreven in de guide?

Dat klopt.

[JBS]

Mimiix schreef op donderdag 28 oktober 2021 @ 13:27:
[...]


Helaas, gaat niet. Volgens Ebaauw werkt dat niet.
https://github.com/dresde...z-rest-plugin/issues/4566

en de comment: https://github.com/dresde...66#issuecomment-797513311

Interessante ontwikkelingen bij Z2M: https://github.com/Koenkk...0#issuecomment-1030935496

[Mimiix]

JBS schreef op maandag 7 februari 2022 @ 09:17:
[...]
Interessante ontwikkelingen bij Z2M: https://github.com/Koenkk...0#issuecomment-1030935496

Kwam ook al voorbij inderdaad.

Erik had er al op gereageerd. Zou best tof zijn als dit inderdaad werkt!

[jja2000]

Mimiix schreef op maandag 7 februari 2022 @ 08:33:
[...]


ER is iets te zien geweest in deconz, kan dat kloppen?

Klopt, was te zien in een screenshot van eerder:

Mimiix schreef op maandag 7 februari 2022 @ 08:33:
Doe je er meerdere tegelijk? Anders even eentje per keer doen.

Ja, ik heb het met 1 geprobeerd en ik liep tegen hetzelfde probleem aan.

[Mimiix]

jja2000 schreef op maandag 7 februari 2022 @ 12:35:
[...]


Klopt, was te zien in een screenshot van eerder:
[Afbeelding]


[...]


Ja, ik heb het met 1 geprobeerd en ik liep tegen hetzelfde probleem aan.

Hij paired ze niet goed. Te zien aan het 2e bolletje. Hij announced niet goed, zal iets in de ikea fw zijn.


Enige wat helpt is hem verwijderen in deCONZ (rechter muis, delete (geloof ik)), daarna restarten en pairen.

[Koepert]

Wat kan ik t beste doen, na n update vn HA *en HA OS als mijn phoscon APP het lijkt te doen, maar de acties niet doorkomen:

code:

pydeconz.errors.BridgeBusy

En mn VNC connectie geen verbinding met de dongle lijkt te hebben:

[Mimiix]

Koepert schreef op maandag 7 februari 2022 @ 12:58:
Wat kan ik t beste doen, na n update vn HA *en HA OS als mijn phoscon APP het lijkt te doen, maar de acties niet doorkomen:

code:

pydeconz.errors.BridgeBusy

En mn VNC connectie geen verbinding met de dongle lijkt te hebben:


[Afbeelding]

Heb je toevallig al deCONZ draaien?

Hij kan de stick niet "locken". Dit zie je meestal:
- Deconz draait al headless
- Z2m/ZHA draait al
- Een tweede deCONZ is gestart
- Door interference kan ie het netwerk niet starten.
- Er is te weinig stroom voor de stick op je apparaat.

[Koepert]

Mimiix schreef op maandag 7 februari 2022 @ 13:02:
[...]


Heb je toevallig al deCONZ draaien?

Hij kan de stick niet "locken". Dit zie je meestal:
- Deconz draait al headless
- Z2m/ZHA draait al
- Een tweede deCONZ is gestart
- Door interference kan ie het netwerk niet starten.
- Er is te weinig stroom voor de stick op je apparaat.

- Geen losse Deconz (alleen de phoscon app dus getest), verder ergens draaien
- Geen Z2m of ZHA actief
- K heb 1 stick, en dus 1 instance van DECONZ
- Zou kunnen, staat sinds kort een 2e appliance in dezelfde meterkast (host)..
- Zou kunnen, lijkt me sterk heeft altijd gewerkt in dezelfde config

[Mimiix]

Koepert schreef op maandag 7 februari 2022 @ 13:05:
[...]


- Geen losse Deconz (alleen de phoscon app dus getest), verder ergens draaien
- Geen Z2m of ZHA actief
- K heb 1 stick, en dus 1 instance van DECONZ
- Zou kunnen, staat sinds kort een 2e appliance in dezelfde meterkast (host)..
- Zou kunnen, lijkt me sterk heeft altijd gewerkt in dezelfde config

Heb je wat logs?

[Koepert]

Mimiix schreef op maandag 7 februari 2022 @ 13:20:
[...]


Heb je wat logs?

code:

13:18:26:919 device state timeout ignored in state 2
13:18:27:080 device state timeout ignored in state 2
13:18:27:187 try to reconnect to network try=5
13:18:27:240 device state timeout (handled)
13:18:27:320 void zmMaster::handleStateIdle(zmMaster::MasterEvent) not connected goto OFF state
13:18:27:320 device state timeout ignored in state 1


13:21:27:111 void zmMaster::handleStateIdle(zmMaster::MasterEvent) not connected goto OFF state
13:21:27:111 device state timeout ignored in state 1
13:21:30:187 failed to reconnect to network try=8
13:21:35:187 failed to reconnect to network try=9
13:21:40:187 failed to reconnect to network try=10

Heb inmiddels. HA herstart, de addon herstart, de usb Incl kabel wat verlegd, de stick eruit en erin gehad..

[Mimiix]

Koepert schreef op maandag 7 februari 2022 @ 13:22:
[...]

code:

13:18:26:919 device state timeout ignored in state 2
13:18:27:080 device state timeout ignored in state 2
13:18:27:187 try to reconnect to network try=5
13:18:27:240 device state timeout (handled)
13:18:27:320 void zmMaster::handleStateIdle(zmMaster::MasterEvent) not connected goto OFF state
13:18:27:320 device state timeout ignored in state 1


13:21:27:111 void zmMaster::handleStateIdle(zmMaster::MasterEvent) not connected goto OFF state
13:21:27:111 device state timeout ignored in state 1
13:21:30:187 failed to reconnect to network try=8
13:21:35:187 failed to reconnect to network try=9
13:21:40:187 failed to reconnect to network try=10

Heb inmiddels. HA herstart, de addon herstart, de usb Incl kabel wat verlegd, de stick eruit en erin gehad..

Heb je wat langere logs?
Er zou iets met "reason"erin moeten staan.

[Koepert]

Mimiix schreef op maandag 7 februari 2022 @ 13:25:
[...]


Heb je wat langere logs?
Er zou iets met "reason"erin moeten staan.

Nee. Geen reason iig. Zie ook in de addon config dat ik geen log opties ‘aangezet’ heb..
Dit gaat n leuke worden 😞

::// Log met alles op 1..

code:

13:41:53:247 SensorNode 37 set node 0x00158d0004018950
13:41:53:247 SensorNode 11 set node 0x00158d00032cb017
13:41:53:248 DB SELECT manufacturername FROM nodes WHERE mac LIKE '58:8e:81:ff:fe:d0:c8:bb%' COLLATE NOCASE: _TZ3000_g5xawfcq
13:41:53:249 LightNode 14: Droger added
13:41:53:249 SensorNode 26 set node 0x588e81fffed0c8bb
13:41:53:249 SensorNode 33 set node 0x588e81fffed0c8bb
13:41:53:311 SensorNode 27 set node 0x00158d0005489ce6
13:41:53:311 SensorNode 28 set node 0x00158d0005489ce6
13:41:53:312 SensorNode 29 set node 0x00158d0005489ce6
13:41:53:312 LightNode 7: Hue Keuken 2 added
13:41:53:313 DB SELECT manufacturername FROM nodes WHERE mac LIKE '84:2e:14:ff:fe:e1:a9:0a%' COLLATE NOCASE: Heiman
13:41:53:313 LightNode 5: Schakelaar added
13:41:53:313 SensorNode 2 set node 0x842e14fffee1a90a
13:41:53:313 SensorNode 3 set node 0x842e14fffee1a90a
13:41:53:377 SensorNode 14 set node 0x00124b00222e92a4
13:41:53:377 SensorNode 13 set node 0x00124b00222e92a4
13:41:53:378 SensorNode 18 set node 0x00158d0004017930
13:41:53:379 LightNode 11: Hue TV 1 added
13:41:53:452 DEV no DDF for 0x60A423FFFE620A6D, modelId: TS0121
13:41:53:452 DEV create on-the-fly DDF for 0x60A423FFFE620A6D
13:41:53:453 DEV found DDF for 0x00158D00032CB017, path: /usr/share/deCONZ/devices/xiaomi/aq1_vibration_sensor.json
13:41:53:453 DEV no DDF for 0x00158D0003A4AEC6, modelId: lumi.sensor_magnet.aq2
13:41:53:453 DEV create on-the-fly DDF for 0x00158D0003A4AEC6
13:41:53:453 DEV no DDF for 0x00158D0005728BA5, modelId: lumi.sensor_motion.aq2
13:41:53:453 DEV create on-the-fly DDF for 0x00158D0005728BA5
13:41:53:453 DEV found DDF for 0x00158D0003A352A6, path: 
13:41:53:453 DEV no DDF for 0x00158D0004017930, modelId: lumi.remote.b1acn01
13:41:53:453 DEV create on-the-fly DDF for 0x00158D0004017930
13:41:53:453 DEV found DDF for 0x00158D0004018950, path: 
13:41:53:453 DEV no DDF for 0x00124B001F8AAAB5, modelId: WB01
13:41:53:454 DEV create on-the-fly DDF for 0x00124B001F8AAAB5
13:41:53:454 DEV no DDF for 0x00158D0005489CE6, modelId: lumi.weather
13:41:53:454 DEV create on-the-fly DDF for 0x00158D0005489CE6
13:41:53:454 DEV found DDF for 0x00158D000320D532, path: 
13:41:53:454 DEV found DDF for 0x00158D000578A961, path: 
13:41:53:466 dlg action: Read binding table
13:41:53:481 DEV found DDF for 0x00158D000483198D, path: /usr/share/deCONZ/devices/xiaomi/aq1_vibration_sensor.json
13:41:53:481 DEV found DDF for 0x04CF8CDF3C7B337C, path: /usr/share/deCONZ/devices/xiaomi/xiaomi_gzcgq01lm_light_sensor.json
13:41:53:482 DEV found DDF for 0x04CF8CDF3C7B5298, path: /usr/share/deCONZ/devices/xiaomi/xiaomi_gzcgq01lm_light_sensor.json
13:41:53:482 DEV no DDF for 0x00124B002214DD35, modelId: MS01
13:41:53:482 DEV create on-the-fly DDF for 0x00124B002214DD35
13:41:53:482 DEV found DDF for 0x00158D000522503F, path: 
13:41:53:482 DEV no DDF for 0x00124B00222E92A4, modelId: TH01
13:41:53:482 DEV create on-the-fly DDF for 0x00124B00222E92A4
13:41:53:482 DEV found DDF for 0x588E81FFFED0C8BB, path: 
13:41:53:482 DEV found DDF for 0x60A423FFFE6206AA, path: 
13:41:53:482 DEV found DDF for 0x588E81FFFEFF607C, path: 
13:41:53:482 DEV found DDF for 0x842E14FFFEE1A90A, path: 
13:41:53:483 DEV no DDF for 0x0017880108CFFF22, modelId: LTG002
13:41:53:483 DEV create on-the-fly DDF for 0x0017880108CFFF22
13:41:53:483 DEV found DDF for 0x00178801084642CB, path: 
13:41:53:483 DEV found DDF for 0x0017880108C6159E, path: 
13:41:53:483 DEV found DDF for 0x0017880108D01A9F, path: 
13:41:53:483 DEV found DDF for 0x0017880108CFFEEC, path: 
13:41:53:483 DEV found DDF for 0x00178801084E9F9A, path: 
13:41:53:483 DEV no DDF for 0x14B457FFFE466DD9, modelId: TRADFRI bulb E27 WW clear 250lm
13:41:53:483 DEV create on-the-fly DDF for 0x14B457FFFE466DD9
13:41:53:483 DEV found DDF for 0x0017880108CFFD1B, path: 
13:41:53:483 DEV found DDF for 0x0017880108C63A3C, path: 
13:41:53:483 DEV no DDF for 0x00124B00226133C6, modelId: GL-C-009
13:41:53:483 DEV create on-the-fly DDF for 0x00124B00226133C6
13:41:53:484 DEV found DDF for 0x0017880108D0198F, path: 
13:41:53:484 DEV found DDF for 0x0017880108CFFF5C, path: 
13:41:53:493 New websocket 172.30.32.1:45980 (state: 3) 
13:41:54:398 COM: /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2149136-if00 / serialno: DE2149136, ConBee II
13:41:56:127 device state timeout ignored in state 2
13:41:56:162 GW update firmware found: /usr/share/deCONZ/firmware/deCONZ_ConBeeII_0x26660700.bin.GCF
13:41:56:287 device state timeout ignored in state 2
13:41:56:313 Announced to internet https://phoscon.de/discover
13:41:56:447 device state timeout ignored in state 2
13:41:56:608 device state timeout ignored in state 2
13:41:56:767 device state timeout ignored in state 2
13:41:56:927 device state timeout ignored in state 2
13:41:57:088 device state timeout ignored in state 2
13:41:57:247 device state timeout ignored in state 2
13:41:57:408 device state timeout ignored in state 2
13:41:57:567 device state timeout ignored in state 2
13:41:57:728 device state timeout ignored in state 2
13:41:57:887 device state timeout (handled)
13:41:57:967 void zmMaster::handleStateIdle(zmMaster::MasterEvent) not connected goto OFF state
13:41:57:967 device state timeout ignored in state 1
13:41:59:187 DEV Tick.Init: booted after 8000 seconds
[13:42:01] INFO: Successfully send discovery information to Home Assistant.
13:42:12:204 COM: /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2149136-if00 / serialno: DE2149136, ConBee II
13:42:12:687 start reconnect to network
13:42:13:767 device state timeout ignored in state 2
13:42:13:927 device state timeout ignored in state 2
13:42:14:088 device state timeout ignored in state 2
13:42:14:247 device state timeout ignored in state 2
13:42:14:407 device state timeout ignored in state 2
13:42:14:568 device state timeout ignored in state 2
13:42:14:727 device state timeout ignored in state 2
13:42:14:887 device state timeout ignored in state 2
13:42:15:048 device state timeout ignored in state 2
13:42:15:207 device state timeout ignored in state 2
13:42:15:367 device state timeout ignored in state 2
13:42:15:528 device state timeout (handled)
13:42:15:608 void zmMaster::handleStateIdle(zmMaster::MasterEvent) not connected goto OFF state
13:42:15:608 device state timeout ignored in state 1
13:42:17:937 failed to reconnect to network try=1

@Mimiix Zojuist de stick in mn Windows laptop (met DeConz) gestoken.. Die wil ook niet connecten.. mag ik dan concluderen dat de stick dood is?

[ Voor 92% gewijzigd door Koepert op 07-02-2022 16:11 ]

[Mimiix]

Koepert schreef op maandag 7 februari 2022 @ 13:32:
[...]


Nee. Geen reason iig. Zie ook in de addon config dat ik geen log opties ‘aangezet’ heb..
Dit gaat n leuke worden 😞

::// Log met alles op 1..

code:

13:41:53:247 SensorNode 37 set node 0x00158d0004018950
13:41:53:247 SensorNode 11 set node 0x00158d00032cb017
13:41:53:248 DB SELECT manufacturername FROM nodes WHERE mac LIKE '58:8e:81:ff:fe:d0:c8:bb%' COLLATE NOCASE: _TZ3000_g5xawfcq
13:41:53:249 LightNode 14: Droger added
13:41:53:249 SensorNode 26 set node 0x588e81fffed0c8bb
13:41:53:249 SensorNode 33 set node 0x588e81fffed0c8bb
13:41:53:311 SensorNode 27 set node 0x00158d0005489ce6
13:41:53:311 SensorNode 28 set node 0x00158d0005489ce6
13:41:53:312 SensorNode 29 set node 0x00158d0005489ce6
13:41:53:312 LightNode 7: Hue Keuken 2 added
13:41:53:313 DB SELECT manufacturername FROM nodes WHERE mac LIKE '84:2e:14:ff:fe:e1:a9:0a%' COLLATE NOCASE: Heiman
13:41:53:313 LightNode 5: Schakelaar added
13:41:53:313 SensorNode 2 set node 0x842e14fffee1a90a
13:41:53:313 SensorNode 3 set node 0x842e14fffee1a90a
13:41:53:377 SensorNode 14 set node 0x00124b00222e92a4
13:41:53:377 SensorNode 13 set node 0x00124b00222e92a4
13:41:53:378 SensorNode 18 set node 0x00158d0004017930
13:41:53:379 LightNode 11: Hue TV 1 added
13:41:53:452 DEV no DDF for 0x60A423FFFE620A6D, modelId: TS0121
13:41:53:452 DEV create on-the-fly DDF for 0x60A423FFFE620A6D
13:41:53:453 DEV found DDF for 0x00158D00032CB017, path: /usr/share/deCONZ/devices/xiaomi/aq1_vibration_sensor.json
13:41:53:453 DEV no DDF for 0x00158D0003A4AEC6, modelId: lumi.sensor_magnet.aq2
13:41:53:453 DEV create on-the-fly DDF for 0x00158D0003A4AEC6
13:41:53:453 DEV no DDF for 0x00158D0005728BA5, modelId: lumi.sensor_motion.aq2
13:41:53:453 DEV create on-the-fly DDF for 0x00158D0005728BA5
13:41:53:453 DEV found DDF for 0x00158D0003A352A6, path: 
13:41:53:453 DEV no DDF for 0x00158D0004017930, modelId: lumi.remote.b1acn01
13:41:53:453 DEV create on-the-fly DDF for 0x00158D0004017930
13:41:53:453 DEV found DDF for 0x00158D0004018950, path: 
13:41:53:453 DEV no DDF for 0x00124B001F8AAAB5, modelId: WB01
13:41:53:454 DEV create on-the-fly DDF for 0x00124B001F8AAAB5
13:41:53:454 DEV no DDF for 0x00158D0005489CE6, modelId: lumi.weather
13:41:53:454 DEV create on-the-fly DDF for 0x00158D0005489CE6
13:41:53:454 DEV found DDF for 0x00158D000320D532, path: 
13:41:53:454 DEV found DDF for 0x00158D000578A961, path: 
13:41:53:466 dlg action: Read binding table
13:41:53:481 DEV found DDF for 0x00158D000483198D, path: /usr/share/deCONZ/devices/xiaomi/aq1_vibration_sensor.json
13:41:53:481 DEV found DDF for 0x04CF8CDF3C7B337C, path: /usr/share/deCONZ/devices/xiaomi/xiaomi_gzcgq01lm_light_sensor.json
13:41:53:482 DEV found DDF for 0x04CF8CDF3C7B5298, path: /usr/share/deCONZ/devices/xiaomi/xiaomi_gzcgq01lm_light_sensor.json
13:41:53:482 DEV no DDF for 0x00124B002214DD35, modelId: MS01
13:41:53:482 DEV create on-the-fly DDF for 0x00124B002214DD35
13:41:53:482 DEV found DDF for 0x00158D000522503F, path: 
13:41:53:482 DEV no DDF for 0x00124B00222E92A4, modelId: TH01
13:41:53:482 DEV create on-the-fly DDF for 0x00124B00222E92A4
13:41:53:482 DEV found DDF for 0x588E81FFFED0C8BB, path: 
13:41:53:482 DEV found DDF for 0x60A423FFFE6206AA, path: 
13:41:53:482 DEV found DDF for 0x588E81FFFEFF607C, path: 
13:41:53:482 DEV found DDF for 0x842E14FFFEE1A90A, path: 
13:41:53:483 DEV no DDF for 0x0017880108CFFF22, modelId: LTG002
13:41:53:483 DEV create on-the-fly DDF for 0x0017880108CFFF22
13:41:53:483 DEV found DDF for 0x00178801084642CB, path: 
13:41:53:483 DEV found DDF for 0x0017880108C6159E, path: 
13:41:53:483 DEV found DDF for 0x0017880108D01A9F, path: 
13:41:53:483 DEV found DDF for 0x0017880108CFFEEC, path: 
13:41:53:483 DEV found DDF for 0x00178801084E9F9A, path: 
13:41:53:483 DEV no DDF for 0x14B457FFFE466DD9, modelId: TRADFRI bulb E27 WW clear 250lm
13:41:53:483 DEV create on-the-fly DDF for 0x14B457FFFE466DD9
13:41:53:483 DEV found DDF for 0x0017880108CFFD1B, path: 
13:41:53:483 DEV found DDF for 0x0017880108C63A3C, path: 
13:41:53:483 DEV no DDF for 0x00124B00226133C6, modelId: GL-C-009
13:41:53:483 DEV create on-the-fly DDF for 0x00124B00226133C6
13:41:53:484 DEV found DDF for 0x0017880108D0198F, path: 
13:41:53:484 DEV found DDF for 0x0017880108CFFF5C, path: 
13:41:53:493 New websocket 172.30.32.1:45980 (state: 3) 
13:41:54:398 COM: /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2149136-if00 / serialno: DE2149136, ConBee II
13:41:56:127 device state timeout ignored in state 2
13:41:56:162 GW update firmware found: /usr/share/deCONZ/firmware/deCONZ_ConBeeII_0x26660700.bin.GCF
13:41:56:287 device state timeout ignored in state 2
13:41:56:313 Announced to internet https://phoscon.de/discover
13:41:56:447 device state timeout ignored in state 2
13:41:56:608 device state timeout ignored in state 2
13:41:56:767 device state timeout ignored in state 2
13:41:56:927 device state timeout ignored in state 2
13:41:57:088 device state timeout ignored in state 2
13:41:57:247 device state timeout ignored in state 2
13:41:57:408 device state timeout ignored in state 2
13:41:57:567 device state timeout ignored in state 2
13:41:57:728 device state timeout ignored in state 2
13:41:57:887 device state timeout (handled)
13:41:57:967 void zmMaster::handleStateIdle(zmMaster::MasterEvent) not connected goto OFF state
13:41:57:967 device state timeout ignored in state 1
13:41:59:187 DEV Tick.Init: booted after 8000 seconds
[13:42:01] INFO: Successfully send discovery information to Home Assistant.
13:42:12:204 COM: /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2149136-if00 / serialno: DE2149136, ConBee II
13:42:12:687 start reconnect to network
13:42:13:767 device state timeout ignored in state 2
13:42:13:927 device state timeout ignored in state 2
13:42:14:088 device state timeout ignored in state 2
13:42:14:247 device state timeout ignored in state 2
13:42:14:407 device state timeout ignored in state 2
13:42:14:568 device state timeout ignored in state 2
13:42:14:727 device state timeout ignored in state 2
13:42:14:887 device state timeout ignored in state 2
13:42:15:048 device state timeout ignored in state 2
13:42:15:207 device state timeout ignored in state 2
13:42:15:367 device state timeout ignored in state 2
13:42:15:528 device state timeout (handled)
13:42:15:608 void zmMaster::handleStateIdle(zmMaster::MasterEvent) not connected goto OFF state
13:42:15:608 device state timeout ignored in state 1
13:42:17:937 failed to reconnect to network try=1

@Mimiix Zojuist de stick in mn Windows laptop (met DeConz) gestoken.. Die wil ook niet connecten.. mag ik dan concluderen dat de stick dood is?

Ik wil alles op 2

Heb je op "firmware update" gedrukt in de addon?

[Koepert]

Mimiix schreef op maandag 7 februari 2022 @ 15:28:
[...]


Ik wil alles op 2

Heb je op "firmware update" gedrukt in de addon?

Nope

en 2:

code:

5:30:56:216 DB pushZdpDescriptorDb()
15:30:56:216 Tuya debug 7 : Missing manufacture name for 0x00124b00222e92a4
15:30:56:216 sql exec SELECT manufacturername FROM nodes WHERE mac LIKE '00:12:4b:00:22:2e:92:a4%' COLLATE NOCASE
15:30:56:216 SensorNode 14 set node 0x00124b00222e92a4
15:30:56:216 SensorNode 13 set node 0x00124b00222e92a4
15:30:56:216 DB pushZdpDescriptorDb()
15:30:56:217 DB save zll database items 0x00000800
15:30:56:217 DB sql exec UPDATE devices SET nwk = 61789 WHERE mac = '00:12:4b:00:22:2e:92:a4';INSERT INTO devices (mac,nwk,timestamp) SELECT '00:12:4b:00:22:2e:92:a4', 61789, strftime('%s','now') WHERE (SELECT changes() = 0);
15:30:56:217 DB saved in 0 ms
15:30:56:217 Tuya debug 7 : Missing manufacture name for 0x00124b00222e92a4
15:30:56:217 sql exec SELECT manufacturername FROM nodes WHERE mac LIKE '00:12:4b:00:22:2e:92:a4%' COLLATE NOCASE
15:30:56:217 DB pushZdpDescriptorDb()
15:30:56:217 SensorNode 18 set node 0x00158d0004017930
15:30:56:217 DB pushZdpDescriptorDb()
15:30:56:217 DB save zll database items 0x00000800
15:30:56:217 DB sql exec UPDATE devices SET nwk = 62634 WHERE mac = '00:15:8d:00:04:01:79:30';INSERT INTO devices (mac,nwk,timestamp) SELECT '00:15:8d:00:04:01:79:30', 62634, strftime('%s','now') WHERE (SELECT changes() = 0);
15:30:56:217 DB saved in 0 ms
15:30:56:217 DB pushZdpDescriptorDb()
15:30:56:218 sql exec SELECT * FROM nodes WHERE mac='00:17:88:01:08:cf:ff:5c-0b' COLLATE NOCASE AND state != 'deleted'
15:30:56:218 LightNode 11: Hue TV 1 added
15:30:56:218 DB pushZdpDescriptorDb()
15:30:56:218 DB save zll database items 0x00000800
15:30:56:218 DB sql exec UPDATE devices SET nwk = 64931 WHERE mac = '00:17:88:01:08:cf:ff:5c';INSERT INTO devices (mac,nwk,timestamp) SELECT '00:17:88:01:08:cf:ff:5c', 64931, strftime('%s','now') WHERE (SELECT changes() = 0);
15:30:56:218 DB saved in 0 ms
15:30:56:218 DB pushZdpDescriptorDb()
15:30:56:218 DB pushZdpDescriptorDb()
15:30:56:291 DEV no DDF for 0x60A423FFFE620A6D, modelId: TS0121
15:30:56:292 DEV create on-the-fly DDF for 0x60A423FFFE620A6D
15:30:56:292 DEV found DDF for 0x00158D00032CB017, path: /usr/share/deCONZ/devices/xiaomi/aq1_vibration_sensor.json
15:30:56:292 DEV no DDF for 0x00158D0003A4AEC6, modelId: lumi.sensor_magnet.aq2
15:30:56:292 DEV create on-the-fly DDF for 0x00158D0003A4AEC6
15:30:56:292 DEV no DDF for 0x00158D0005728BA5, modelId: lumi.sensor_motion.aq2
15:30:56:293 DEV create on-the-fly DDF for 0x00158D0005728BA5
15:30:56:293 DEV found DDF for 0x00158D0003A352A6, path: 
15:30:56:293 DEV no DDF for 0x00158D0004017930, modelId: lumi.remote.b1acn01
15:30:56:293 DEV create on-the-fly DDF for 0x00158D0004017930
15:30:56:293 DEV found DDF for 0x00158D0004018950, path: 
15:30:56:293 DEV no DDF for 0x00124B001F8AAAB5, modelId: WB01
15:30:56:293 DEV create on-the-fly DDF for 0x00124B001F8AAAB5
15:30:56:294 DEV no DDF for 0x00158D0005489CE6, modelId: lumi.weather
15:30:56:294 DEV create on-the-fly DDF for 0x00158D0005489CE6
15:30:56:294 DEV found DDF for 0x00158D000320D532, path: 
15:30:56:306 dlg action: Read binding table
15:30:56:322 DEV found DDF for 0x00158D000578A961, path: 
15:30:56:322 DEV found DDF for 0x00158D000483198D, path: /usr/share/deCONZ/devices/xiaomi/aq1_vibration_sensor.json
15:30:56:322 DEV found DDF for 0x04CF8CDF3C7B337C, path: /usr/share/deCONZ/devices/xiaomi/xiaomi_gzcgq01lm_light_sensor.json
15:30:56:323 DEV found DDF for 0x04CF8CDF3C7B5298, path: /usr/share/deCONZ/devices/xiaomi/xiaomi_gzcgq01lm_light_sensor.json
15:30:56:323 DEV no DDF for 0x00124B002214DD35, modelId: MS01
15:30:56:323 DEV create on-the-fly DDF for 0x00124B002214DD35
15:30:56:323 DEV found DDF for 0x00158D000522503F, path: 
15:30:56:323 DEV no DDF for 0x00124B00222E92A4, modelId: TH01
15:30:56:323 DEV create on-the-fly DDF for 0x00124B00222E92A4
15:30:56:323 DEV found DDF for 0x588E81FFFED0C8BB, path: 
15:30:56:323 DEV found DDF for 0x60A423FFFE6206AA, path: 
15:30:56:323 DEV found DDF for 0x588E81FFFEFF607C, path: 
15:30:56:323 DEV found DDF for 0x842E14FFFEE1A90A, path: 
15:30:56:324 DEV no DDF for 0x0017880108CFFF22, modelId: LTG002
15:30:56:324 DEV create on-the-fly DDF for 0x0017880108CFFF22
15:30:56:324 DEV found DDF for 0x00178801084642CB, path: 
15:30:56:324 DEV found DDF for 0x0017880108C6159E, path: 
15:30:56:324 DEV found DDF for 0x0017880108D01A9F, path: 
15:30:56:324 DEV found DDF for 0x0017880108CFFEEC, path: 
15:30:56:324 DEV found DDF for 0x00178801084E9F9A, path: 
15:30:56:324 DEV no DDF for 0x14B457FFFE466DD9, modelId: TRADFRI bulb E27 WW clear 250lm
15:30:56:324 DEV create on-the-fly DDF for 0x14B457FFFE466DD9
15:30:56:324 DEV found DDF for 0x0017880108CFFD1B, path: 
15:30:56:324 DEV found DDF for 0x0017880108C63A3C, path: 
15:30:56:325 DEV no DDF for 0x00124B00226133C6, modelId: GL-C-009
15:30:56:325 DEV create on-the-fly DDF for 0x00124B00226133C6
15:30:56:325 DEV found DDF for 0x0017880108D0198F, path: 
15:30:56:325 DEV found DDF for 0x0017880108CFFF5C, path: 
15:30:57:236 COM: /dev/ttyUSB0 : FT232R USB UART (0x0403/0x6001)
15:30:57:237 COM: /dev/ttyACM0 : ConBee II (0x1CF1/0x0030)
15:30:57:237 COM: /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2149136-if00 / serialno: DE2149136, ConBee II
15:30:57:317 auto connect com /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2149136-if00
15:30:58:484 COM: /dev/ttyUSB0 : FT232R USB UART (0x0403/0x6001)
15:30:58:484 COM: /dev/ttyACM0 : ConBee II (0x1CF1/0x0030)
15:30:58:485 GW firmware update select USB device
15:30:58:485 GW update firmware not found: 
15:30:58:645 Announced to internet https://phoscon.de/discover
15:30:58:893 Serial com connected
15:30:58:973 device state timeout ignored in state 2
15:30:59:137 device state timeout ignored in state 2
15:30:59:296 device state timeout ignored in state 2
15:30:59:457 device state timeout ignored in state 2
15:30:59:616 device state timeout ignored in state 2
15:30:59:776 device state timeout ignored in state 2
15:30:59:937 device state timeout ignored in state 2
15:31:00:097 device state timeout ignored in state 2
15:31:00:257 device state timeout ignored in state 2
15:31:00:416 device state timeout ignored in state 2
15:31:00:577 device state timeout ignored in state 2
15:31:00:737 device state timeout (handled)
15:31:00:737 Serial com disconnected, reason: 1
15:31:00:739 device disconnected reason: 1, device index: 0
15:31:00:816 void zmMaster::handleStateIdle(zmMaster::MasterEvent) not connected goto OFF state
15:31:00:816 device state timeout ignored in state 1
15:31:01:420 wait reconnect 15 seconds
15:31:01:460 DEV Tick.Init: booted after 8000 seconds
15:31:02:460 wait reconnect 14 seconds
15:31:03:461 Daylight now: solarNoon, status: 170, daylight: 1, dark: 0
15:31:03:461 wait reconnect 13 seconds
[15:31:03] INFO: Successfully send discovery information to Home Assistant
15:31:18:800 Serial com disconnected, reason: 1
15:31:18:803 device disconnected reason: 1, device index: 0
15:31:18:881 void zmMaster::handleStateIdle(zmMaster::MasterEvent) not connected goto OFF state
15:31:18:881 device state timeout ignored in state 1
15:31:19:460 wait reconnect 15 seconds
15:31:20:460 failed to reconnect to network try=1
15:31:20:461 wait reconnect 14 seconds
15:31:21:460 wait reconnect 13 seconds
15:31:22:461 wait reconnect 12 seconds
15:31:23:461 Daylight now: solarNoon, status: 170, daylight: 1, dark: 0
15:31:23:461 wait reconnect 11 seconds
15:31:24:461 wait reconnect 10 seconds
15:31:25:460 failed to reconnect to network try=2
15:31:25:461 wait reconnect 9 seconds
15:31:26:461 wait reconnect 8 seconds
15:31:27:460 wait reconnect 7 seconds
15:31:28:460 wait reconnect 6 seconds
15:31:29:460 wait reconnect 5 seconds
15:31:30:460 failed to reconnect to network try=3
15:31:30:460 wait reconnect 4 seconds
15:31:31:461 wait reconnect 3 seconds
15:31:32:461 wait reconnect 2 seconds
15:31:33:460 Daylight now: solarNoon, status: 170, daylight: 1, dark: 0
15:31:33:460 wait reconnect 1 seconds
15:31:33:478 COM: /dev/ttyUSB0 : FT232R USB UART (0x0403/0x6001)
15:31:33:478 COM: /dev/ttyACM0 : ConBee II (0x1CF1/0x0030)
15:31:33:478 COM: /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2149136-if00 / serialno: DE2149136, ConBee II
15:31:33:539 auto connect com /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2149136-if00
15:31:34:461 Skip idle timer callback, too early: elapsed 921 msec
15:31:34:964 Serial com connected
15:31:35:048 device state timeout ignored in state 2
15:31:35:208 device state timeout ignored in state 2
15:31:35:368 device state timeout ignored in state 2
15:31:35:461 try to reconnect to network try=4
15:31:35:528 device state timeout ignored in state 2
15:31:35:689 device state timeout ignored in state 2
15:31:35:848 device state timeout ignored in state 2
15:31:36:008 device state timeout ignored in state 2
15:31:36:169 device state timeout ignored in state 2
15:31:36:329 device state timeout ignored in state 2
15:31:36:488 device state timeout ignored in state 2
15:31:36:648 device state timeout ignored in state 2
15:31:36:808 device state timeout (handled)
15:31:36:808 MASTER kill cmd 0x08 (ERROR)
15:31:36:808 Serial com disconnected, reason: 1
15:31:36:810 device disconnected reason: 1, device index: 0
15:31:36:889 void zmMaster::handleStateIdle(zmMaster::MasterEvent) not connected goto OFF state
15:31:36:889 device state timeout ignored in state 1
15:31:37:460 wait reconnect 15 seconds
15:31:38:461 wait reconnect 14 seconds
15:31:39:461 wait reconnect 13 seconds
15:31:40:461 failed to reconnect to network try=5
15:31:40:461 wait reconnect 12 seconds
15:31:41:461 wait reconnect 11 seconds
15:31:42:460 wait reconnect 10 seconds
15:31:43:460 Daylight now: solarNoon, status: 170, daylight: 1, dark: 0
15:31:43:460 wait reconnect 9 seconds
15:31:44:461 wait reconnect 8 seconds
15:31:45:461 failed to reconnect to network try=6
15:31:45:461 wait reconnect 7 seconds
15:31:46:461 wait reconnect 6 seconds
15:31:47:460 wait reconnect 5 seconds
15:31:48:461 wait reconnect 4 seconds
15:31:49:461 wait reconnect 3 seconds
15:31:50:461 failed to reconnect to network try=7
15:31:50:461 wait reconnect 2 seconds
15:31:51:460 wait reconnect 1 seconds
15:31:51:478 COM: /dev/ttyUSB0 : FT232R USB UART (0x0403/0x6001)
15:31:51:478 COM: /dev/ttyACM0 : ConBee II (0x1CF1/0x0030)
15:31:51:478 COM: /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2149136-if00 / serialno: DE2149136, ConBee II
15:31:51:538 auto connect com /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2149136-if00
15:31:52:460 Skip idle timer callback, too early: elapsed 921 msec
15:31:52:964 Serial com connected
15:31:53:048 device state timeout ignored in state 2
15:31:53:209 device state timeout ignored in state 2
15:31:53:368 device state timeout ignored in state 2
15:31:53:461 Daylight now: solarNoon, status: 170, daylight: 1, dark: 0
15:31:53:529 device state timeout ignored in state 2
15:31:53:688 device state timeout ignored in state 2
15:31:53:849 device state timeout ignored in state 2
15:31:54:008 device state timeout ignored in state 2
15:31:54:168 device state timeout ignored in state 2
15:31:54:329 device state timeout ignored in state 2
15:31:54:488 device state timeout ignored in state 2
15:31:54:648 device state timeout ignored in state 2
15:31:54:809 device state timeout (handled)
15:31:54:809 Serial com disconnected, reason: 1
15:31:54:811 device disconnected reason: 1, device index: 0
15:31:54:889 void zmMaster::handleStateIdle(zmMaster::MasterEvent) not connected goto OFF state
15:31:54:889 device state timeout ignored in state 1
15:31:55:461 DB save zll database items 0x00000084
15:31:55:461 DB sql exec REPLACE INTO auth (apikey, devicetype, createdate, lastusedate, useragent) VALUES ('0D110F80BD', 'Home Assistant', '2020-06-08T18:43:37', '2022-02-07T14:31:03', 'curl/7.58.0')
15:31:55:518 DB saved in 56 ms
15:31:55:518 failed to reconnect to network try=8
15:31:55:518 wait reconnect 15 seconds
15:31:56:461 wait reconnect 14 seconds
15:31:56:461 Skip idle timer callback, too early: elapsed 942 msec
15:31:57:461 wait reconnect 13 seconds
15:31:58:461 wait reconnect 12 seconds
15:31:59:460 wait reconnect 11 seconds

[ Voor 43% gewijzigd door rens-br op 07-02-2022 15:50 . Reden: Quote tags toegevoegd ]

[Mimiix]

Koepert schreef op maandag 7 februari 2022 @ 15:31:
[...]


Nope

en 2:

code:

5:30:56:216 DB pushZdpDescriptorDb()
15:30:56:216 Tuya debug 7 : Missing manufacture name for 0x00124b00222e92a4
15:30:56:216 sql exec SELECT manufacturername FROM nodes WHERE mac LIKE '00:12:4b:00:22:2e:92:a4%' COLLATE NOCASE
15:30:56:216 SensorNode 14 set node 0x00124b00222e92a4
15:30:56:216 SensorNode 13 set node 0x00124b00222e92a4
15:30:56:216 DB pushZdpDescriptorDb()
15:30:56:217 DB save zll database items 0x00000800
15:30:56:217 DB sql exec UPDATE devices SET nwk = 61789 WHERE mac = '00:12:4b:00:22:2e:92:a4';INSERT INTO devices (mac,nwk,timestamp) SELECT '00:12:4b:00:22:2e:92:a4', 61789, strftime('%s','now') WHERE (SELECT changes() = 0);
15:30:56:217 DB saved in 0 ms
15:30:56:217 Tuya debug 7 : Missing manufacture name for 0x00124b00222e92a4
15:30:56:217 sql exec SELECT manufacturername FROM nodes WHERE mac LIKE '00:12:4b:00:22:2e:92:a4%' COLLATE NOCASE
15:30:56:217 DB pushZdpDescriptorDb()
15:30:56:217 SensorNode 18 set node 0x00158d0004017930
15:30:56:217 DB pushZdpDescriptorDb()
15:30:56:217 DB save zll database items 0x00000800
15:30:56:217 DB sql exec UPDATE devices SET nwk = 62634 WHERE mac = '00:15:8d:00:04:01:79:30';INSERT INTO devices (mac,nwk,timestamp) SELECT '00:15:8d:00:04:01:79:30', 62634, strftime('%s','now') WHERE (SELECT changes() = 0);
15:30:56:217 DB saved in 0 ms
15:30:56:217 DB pushZdpDescriptorDb()
15:30:56:218 sql exec SELECT * FROM nodes WHERE mac='00:17:88:01:08:cf:ff:5c-0b' COLLATE NOCASE AND state != 'deleted'
15:30:56:218 LightNode 11: Hue TV 1 added
15:30:56:218 DB pushZdpDescriptorDb()
15:30:56:218 DB save zll database items 0x00000800
15:30:56:218 DB sql exec UPDATE devices SET nwk = 64931 WHERE mac = '00:17:88:01:08:cf:ff:5c';INSERT INTO devices (mac,nwk,timestamp) SELECT '00:17:88:01:08:cf:ff:5c', 64931, strftime('%s','now') WHERE (SELECT changes() = 0);
15:30:56:218 DB saved in 0 ms
15:30:56:218 DB pushZdpDescriptorDb()
15:30:56:218 DB pushZdpDescriptorDb()
15:30:56:291 DEV no DDF for 0x60A423FFFE620A6D, modelId: TS0121
15:30:56:292 DEV create on-the-fly DDF for 0x60A423FFFE620A6D
15:30:56:292 DEV found DDF for 0x00158D00032CB017, path: /usr/share/deCONZ/devices/xiaomi/aq1_vibration_sensor.json
15:30:56:292 DEV no DDF for 0x00158D0003A4AEC6, modelId: lumi.sensor_magnet.aq2
15:30:56:292 DEV create on-the-fly DDF for 0x00158D0003A4AEC6
15:30:56:292 DEV no DDF for 0x00158D0005728BA5, modelId: lumi.sensor_motion.aq2
15:30:56:293 DEV create on-the-fly DDF for 0x00158D0005728BA5
15:30:56:293 DEV found DDF for 0x00158D0003A352A6, path: 
15:30:56:293 DEV no DDF for 0x00158D0004017930, modelId: lumi.remote.b1acn01
15:30:56:293 DEV create on-the-fly DDF for 0x00158D0004017930
15:30:56:293 DEV found DDF for 0x00158D0004018950, path: 
15:30:56:293 DEV no DDF for 0x00124B001F8AAAB5, modelId: WB01
15:30:56:293 DEV create on-the-fly DDF for 0x00124B001F8AAAB5
15:30:56:294 DEV no DDF for 0x00158D0005489CE6, modelId: lumi.weather
15:30:56:294 DEV create on-the-fly DDF for 0x00158D0005489CE6
15:30:56:294 DEV found DDF for 0x00158D000320D532, path: 
15:30:56:306 dlg action: Read binding table
15:30:56:322 DEV found DDF for 0x00158D000578A961, path: 
15:30:56:322 DEV found DDF for 0x00158D000483198D, path: /usr/share/deCONZ/devices/xiaomi/aq1_vibration_sensor.json
15:30:56:322 DEV found DDF for 0x04CF8CDF3C7B337C, path: /usr/share/deCONZ/devices/xiaomi/xiaomi_gzcgq01lm_light_sensor.json
15:30:56:323 DEV found DDF for 0x04CF8CDF3C7B5298, path: /usr/share/deCONZ/devices/xiaomi/xiaomi_gzcgq01lm_light_sensor.json
15:30:56:323 DEV no DDF for 0x00124B002214DD35, modelId: MS01
15:30:56:323 DEV create on-the-fly DDF for 0x00124B002214DD35
15:30:56:323 DEV found DDF for 0x00158D000522503F, path: 
15:30:56:323 DEV no DDF for 0x00124B00222E92A4, modelId: TH01
15:30:56:323 DEV create on-the-fly DDF for 0x00124B00222E92A4
15:30:56:323 DEV found DDF for 0x588E81FFFED0C8BB, path: 
15:30:56:323 DEV found DDF for 0x60A423FFFE6206AA, path: 
15:30:56:323 DEV found DDF for 0x588E81FFFEFF607C, path: 
15:30:56:323 DEV found DDF for 0x842E14FFFEE1A90A, path: 
15:30:56:324 DEV no DDF for 0x0017880108CFFF22, modelId: LTG002
15:30:56:324 DEV create on-the-fly DDF for 0x0017880108CFFF22
15:30:56:324 DEV found DDF for 0x00178801084642CB, path: 
15:30:56:324 DEV found DDF for 0x0017880108C6159E, path: 
15:30:56:324 DEV found DDF for 0x0017880108D01A9F, path: 
15:30:56:324 DEV found DDF for 0x0017880108CFFEEC, path: 
15:30:56:324 DEV found DDF for 0x00178801084E9F9A, path: 
15:30:56:324 DEV no DDF for 0x14B457FFFE466DD9, modelId: TRADFRI bulb E27 WW clear 250lm
15:30:56:324 DEV create on-the-fly DDF for 0x14B457FFFE466DD9
15:30:56:324 DEV found DDF for 0x0017880108CFFD1B, path: 
15:30:56:324 DEV found DDF for 0x0017880108C63A3C, path: 
15:30:56:325 DEV no DDF for 0x00124B00226133C6, modelId: GL-C-009
15:30:56:325 DEV create on-the-fly DDF for 0x00124B00226133C6
15:30:56:325 DEV found DDF for 0x0017880108D0198F, path: 
15:30:56:325 DEV found DDF for 0x0017880108CFFF5C, path: 
15:30:57:236 COM: /dev/ttyUSB0 : FT232R USB UART (0x0403/0x6001)
15:30:57:237 COM: /dev/ttyACM0 : ConBee II (0x1CF1/0x0030)
15:30:57:237 COM: /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2149136-if00 / serialno: DE2149136, ConBee II
15:30:57:317 auto connect com /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2149136-if00
15:30:58:484 COM: /dev/ttyUSB0 : FT232R USB UART (0x0403/0x6001)
15:30:58:484 COM: /dev/ttyACM0 : ConBee II (0x1CF1/0x0030)
15:30:58:485 GW firmware update select USB device
15:30:58:485 GW update firmware not found: 
15:30:58:645 Announced to internet https://phoscon.de/discover
15:30:58:893 Serial com connected
15:30:58:973 device state timeout ignored in state 2
15:30:59:137 device state timeout ignored in state 2
15:30:59:296 device state timeout ignored in state 2
15:30:59:457 device state timeout ignored in state 2
15:30:59:616 device state timeout ignored in state 2
15:30:59:776 device state timeout ignored in state 2
15:30:59:937 device state timeout ignored in state 2
15:31:00:097 device state timeout ignored in state 2
15:31:00:257 device state timeout ignored in state 2
15:31:00:416 device state timeout ignored in state 2
15:31:00:577 device state timeout ignored in state 2
15:31:00:737 device state timeout (handled)
15:31:00:737 Serial com disconnected, reason: 1
15:31:00:739 device disconnected reason: 1, device index: 0
15:31:00:816 void zmMaster::handleStateIdle(zmMaster::MasterEvent) not connected goto OFF state
15:31:00:816 device state timeout ignored in state 1
15:31:01:420 wait reconnect 15 seconds
15:31:01:460 DEV Tick.Init: booted after 8000 seconds
15:31:02:460 wait reconnect 14 seconds
15:31:03:461 Daylight now: solarNoon, status: 170, daylight: 1, dark: 0
15:31:03:461 wait reconnect 13 seconds
[15:31:03] INFO: Successfully send discovery information to Home Assistant
15:31:18:800 Serial com disconnected, reason: 1
15:31:18:803 device disconnected reason: 1, device index: 0
15:31:18:881 void zmMaster::handleStateIdle(zmMaster::MasterEvent) not connected goto OFF state
15:31:18:881 device state timeout ignored in state 1
15:31:19:460 wait reconnect 15 seconds
15:31:20:460 failed to reconnect to network try=1
15:31:20:461 wait reconnect 14 seconds
15:31:21:460 wait reconnect 13 seconds
15:31:22:461 wait reconnect 12 seconds
15:31:23:461 Daylight now: solarNoon, status: 170, daylight: 1, dark: 0
15:31:23:461 wait reconnect 11 seconds
15:31:24:461 wait reconnect 10 seconds
15:31:25:460 failed to reconnect to network try=2
15:31:25:461 wait reconnect 9 seconds
15:31:26:461 wait reconnect 8 seconds
15:31:27:460 wait reconnect 7 seconds
15:31:28:460 wait reconnect 6 seconds
15:31:29:460 wait reconnect 5 seconds
15:31:30:460 failed to reconnect to network try=3
15:31:30:460 wait reconnect 4 seconds
15:31:31:461 wait reconnect 3 seconds
15:31:32:461 wait reconnect 2 seconds
15:31:33:460 Daylight now: solarNoon, status: 170, daylight: 1, dark: 0
15:31:33:460 wait reconnect 1 seconds
15:31:33:478 COM: /dev/ttyUSB0 : FT232R USB UART (0x0403/0x6001)
15:31:33:478 COM: /dev/ttyACM0 : ConBee II (0x1CF1/0x0030)
15:31:33:478 COM: /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2149136-if00 / serialno: DE2149136, ConBee II
15:31:33:539 auto connect com /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2149136-if00
15:31:34:461 Skip idle timer callback, too early: elapsed 921 msec
15:31:34:964 Serial com connected
15:31:35:048 device state timeout ignored in state 2
15:31:35:208 device state timeout ignored in state 2
15:31:35:368 device state timeout ignored in state 2
15:31:35:461 try to reconnect to network try=4
15:31:35:528 device state timeout ignored in state 2
15:31:35:689 device state timeout ignored in state 2
15:31:35:848 device state timeout ignored in state 2
15:31:36:008 device state timeout ignored in state 2
15:31:36:169 device state timeout ignored in state 2
15:31:36:329 device state timeout ignored in state 2
15:31:36:488 device state timeout ignored in state 2
15:31:36:648 device state timeout ignored in state 2
15:31:36:808 device state timeout (handled)
15:31:36:808 MASTER kill cmd 0x08 (ERROR)
15:31:36:808 Serial com disconnected, reason: 1
15:31:36:810 device disconnected reason: 1, device index: 0
15:31:36:889 void zmMaster::handleStateIdle(zmMaster::MasterEvent) not connected goto OFF state
15:31:36:889 device state timeout ignored in state 1
15:31:37:460 wait reconnect 15 seconds
15:31:38:461 wait reconnect 14 seconds
15:31:39:461 wait reconnect 13 seconds
15:31:40:461 failed to reconnect to network try=5
15:31:40:461 wait reconnect 12 seconds
15:31:41:461 wait reconnect 11 seconds
15:31:42:460 wait reconnect 10 seconds
15:31:43:460 Daylight now: solarNoon, status: 170, daylight: 1, dark: 0
15:31:43:460 wait reconnect 9 seconds
15:31:44:461 wait reconnect 8 seconds
15:31:45:461 failed to reconnect to network try=6
15:31:45:461 wait reconnect 7 seconds
15:31:46:461 wait reconnect 6 seconds
15:31:47:460 wait reconnect 5 seconds
15:31:48:461 wait reconnect 4 seconds
15:31:49:461 wait reconnect 3 seconds
15:31:50:461 failed to reconnect to network try=7
15:31:50:461 wait reconnect 2 seconds
15:31:51:460 wait reconnect 1 seconds
15:31:51:478 COM: /dev/ttyUSB0 : FT232R USB UART (0x0403/0x6001)
15:31:51:478 COM: /dev/ttyACM0 : ConBee II (0x1CF1/0x0030)
15:31:51:478 COM: /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2149136-if00 / serialno: DE2149136, ConBee II
15:31:51:538 auto connect com /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2149136-if00
15:31:52:460 Skip idle timer callback, too early: elapsed 921 msec
15:31:52:964 Serial com connected
15:31:53:048 device state timeout ignored in state 2
15:31:53:209 device state timeout ignored in state 2
15:31:53:368 device state timeout ignored in state 2
15:31:53:461 Daylight now: solarNoon, status: 170, daylight: 1, dark: 0
15:31:53:529 device state timeout ignored in state 2
15:31:53:688 device state timeout ignored in state 2
15:31:53:849 device state timeout ignored in state 2
15:31:54:008 device state timeout ignored in state 2
15:31:54:168 device state timeout ignored in state 2
15:31:54:329 device state timeout ignored in state 2
15:31:54:488 device state timeout ignored in state 2
15:31:54:648 device state timeout ignored in state 2
15:31:54:809 device state timeout (handled)
15:31:54:809 Serial com disconnected, reason: 1
15:31:54:811 device disconnected reason: 1, device index: 0
15:31:54:889 void zmMaster::handleStateIdle(zmMaster::MasterEvent) not connected goto OFF state
15:31:54:889 device state timeout ignored in state 1
15:31:55:461 DB save zll database items 0x00000084
15:31:55:461 DB sql exec REPLACE INTO auth (apikey, devicetype, createdate, lastusedate, useragent) VALUES ('0D110F80BD', 'Home Assistant', '2020-06-08T18:43:37', '2022-02-07T14:31:03', 'curl/7.58.0')
15:31:55:518 DB saved in 56 ms
15:31:55:518 failed to reconnect to network try=8
15:31:55:518 wait reconnect 15 seconds
15:31:56:461 wait reconnect 14 seconds
15:31:56:461 Skip idle timer callback, too early: elapsed 942 msec
15:31:57:461 wait reconnect 13 seconds
15:31:58:461 wait reconnect 12 seconds
15:31:59:460 wait reconnect 11 seconds

15:31:00:739 device disconnected reason: 1, device index: 0


Die zien we bij een "normal disconnect" (Als je bijv de stick er zelf uithaalt).

Je zou op de laptop dit kunnen proberen: https://github.com/dresde...ki/Update-deCONZ-manually

Anders lijkt het mij een DOA.

[Koepert]

Mimiix schreef op maandag 7 februari 2022 @ 15:34:
[...]


15:31:00:739 device disconnected reason: 1, device index: 0


Die zien we bij een "normal disconnect" (Als je bijv de stick er zelf uithaalt).

Je zou op de laptop dit kunnen proberen: https://github.com/dresde...ki/Update-deCONZ-manually

Anders lijkt het mij een DOA.

K ga t proberen.. DOA is t sowieso niet. Is al paar jaar in gebruik 😜.


@Mimiix Reflash worked zo t nu lijkt. DeConz addon restart gegeven, lijkt up te komen.

[ Voor 8% gewijzigd door Koepert op 07-02-2022 16:54 ]

[Awesomo4k]

Beste allemaal... Ik heb sinds een tijdje slappe verbindingen in mijn zigbee-netwerk... Nu weet ik niet waar het probleem ligt.

Wat heb ik reeds gedaan:
Firmware update stick - ConbeeII
Software/docker update Deconz software.
Zigbee kanaal veranderd naar 25
Source routing ingeschakeld.

Resultaat is... hetzelfde als daarvoor... Bijna geen groene verbindingen.

Any tips?

[ Voor 12% gewijzigd door Awesomo4k op 07-02-2022 20:49 ]

[iisworks]

Deconz 2.14.1 stable:
https://github.com/dresde...conz-rest-plugin/releases

[Peet3kabo]

Awesomo4k schreef op maandag 7 februari 2022 @ 20:43:
Beste allemaal... Ik heb sinds een tijdje slappe verbindingen in mijn zigbee-netwerk... Nu weet ik niet waar het probleem ligt.

Wat heb ik reeds gedaan:
Firmware update stick - ConbeeII
Software/docker update Deconz software.
Zigbee kanaal veranderd naar 25
Source routing ingeschakeld.

Resultaat is... hetzelfde als daarvoor... Bijna geen groene verbindingen.

Any tips?

[Afbeelding]

Misschien domme vraag, maar is je waarneming slappe verbindingen gebaseerd op het plaatje in deconz omdat er weinig groen is of daadwerkelijk omdat je problemen hebt met apparaten welke verbinding verliezen.
Het plaatje bij mij ziet er niet veel anders uit terwijl het voorheen groener was, maar heb geen problemen met slechte verbinding.
Kan zijn dat er iets is veranderd in deconz na een update maar dat weet ik dan weer niet, ben alleen benieuwd naar het hoe en waaat.

[Awesomo4k]

Peet3kabo schreef op maandag 7 februari 2022 @ 21:34:
[...]


Misschien domme vraag, maar is je waarneming slappe verbindingen gebaseerd op het plaatje in deconz omdat er weinig groen is of daadwerkelijk omdat je problemen hebt met apparaten welke verbinding verliezen.
Het plaatje bij mij ziet er niet veel anders uit terwijl het voorheen groener was, maar heb geen problemen met slechte verbinding.
Kan zijn dat er iets is veranderd in deconz na een update maar dat weet ik dan weer niet, ben alleen benieuwd naar het hoe en waaat.

Het is voornamelijk omdat er weinig groen is(en er eerst wel was)... In theorie werkt alles behalve 1 sensor... die DCed de hele tijd... en ik dacht dat dat misschien hieraan lag...

[Peet3kabo]

Awesomo4k schreef op maandag 7 februari 2022 @ 21:41:
[...]


Het is voornamelijk omdat er weinig groen is(en er eerst wel was)... In theorie werkt alles behalve 1 sensor... die DCed de hele tijd... en ik dacht dat dat misschien hieraan lag...

Duidelijk, ik zie het zelfde idd maar heb verder geen problemen met apparaten welke niet werken.
Ook iets kleiner netwerk.

[Mimiix]

Awesomo4k schreef op maandag 7 februari 2022 @ 21:41:
[...]


Het is voornamelijk omdat er weinig groen is(en er eerst wel was)... In theorie werkt alles behalve 1 sensor... die DCed de hele tijd... en ik dacht dat dat misschien hieraan lag...

De scaling van de lijn kleuren is veranderd. Ze zijn dus altijd zo geweest alleen de threshold ovor kleur veranderingen is anders.

[Peet3kabo]

Mimiix schreef op maandag 7 februari 2022 @ 21:58:
[...]


De scaling van de lijn kleuren is veranderd. Ze zijn dus altijd zo geweest alleen de threshold ovor kleur veranderingen is anders.

Zo'n idee had ik al, komt dat ook omdat hij nu zenden en ontvangen berekend en meende dat het voorheen 1 waarde was?
Bij de sensoren (batterij) welke niet als router fungeren zie ik sneller een groene waarde richting de 250 dan dus

[Mimiix]

Peet3kabo schreef op maandag 7 februari 2022 @ 21:59:
[...]


Zo'n idee had ik al, komt dat ook omdat hij nu zenden en ontvangen berekend en meende dat het voorheen 1 waarde was?
Bij de sensoren (batterij) welke niet als router fungeren zie ik sneller een groene waarde richting de 250 dan dus

Nee. Daar is niets aan veranderd.

[Peet3kabo]

Mimiix schreef op maandag 7 februari 2022 @ 23:21:
[...]


Nee. Daar is niets aan veranderd.

Duidelijk, dan zat mijn beleving en geheugen er daar naast. Maakt ook niks, ik ervaar geen problemen. Het was mij alleen opgevallen, daarom mijn vraag ook aan Awesomo4k of het niet alleen het plaatje was wat anders leek.

[Thijs8472]

iisworks schreef op zondag 30 januari 2022 @ 08:40:
[...]Ik heb 15 van die nieuwe compacte Tuya plugs met oranje randje klaarliggen, geupdated naar laatste .10 Tuya FW die reporting ondersteunt.

Werkt het zetten 'PowerOn OnOff' die nieuwe firmware wel? Ik heb deze pluggen met een oudere firmware (revisie 68) en daar kun je deze waarde niet zetten. Daardoor blijven ze uit als de stroom uitvalt wat mi nog waardelozer is dan polling ipv metering.

[iisworks]

Thijs8472 schreef op dinsdag 8 februari 2022 @ 20:13:
[...]
Werkt het zetten 'PowerOn OnOff' die nieuwe firmware wel? Ik heb deze pluggen met een oudere firmware (revisie 68) en daar kun je deze waarde niet zetten. Daardoor blijven ze uit als de stroom uitvalt wat mi nog waardelozer is dan polling ipv metering.

Klopt, de grootste nadelen zijn opgelost dus m.i. nu de ideale plugs! Het enige wat ik jammer vind is dat ze <3W niet weergeven.

[Koepert]

iisworks schreef op dinsdag 8 februari 2022 @ 21:21:
[...]


Klopt, de grootste nadelen zijn opgelost dus m.i. nu de ideale plugs! Het enige wat ik jammer vind is dat ze <2W niet weergeven.

Welke zijn dat precies? Ik zoek nog vervanging voor m’n blitzwolf shp-13s.

[iisworks]

Koepert schreef op dinsdag 8 februari 2022 @ 21:24:
[...]


Welke zijn dat precies? Ik zoek nog vervanging voor m’n blitzwolf shp-13s.

Deze, ca. €10/stuk:
https://forum.phoscon.de/...1b-or-tz3000-w0qqde0g/819

PS: Ik heb dus nog wel issues met deze plugs in 2.14.1.

[Oesie]

Weet iemand hoe de third party app Hue Essentials kan worden verbonden met deCONZ welke als integratie in Home Assistant draait?

Ik krijg hem niet verbonden op het IP van Home Assistant en ook niet op het IP welke in de integratie van de Phoscon app staat binnen Home Assistant.

[Koepert]

Oesie schreef op donderdag 10 februari 2022 @ 21:54:
Weet iemand hoe de third party app Hue Essentials kan worden verbonden met deCONZ welke als integratie in Home Assistant draait?

Ik krijg hem niet verbonden op het IP van Home Assistant en ook niet op het IP welke in de integratie van de Phoscon app staat binnen Home Assistant.

Toevallig recent nog gedaan. In de phoson app bij gateway authenticate app doen en dan vanuit de hue app zoeken.. t is n beetje gokken qua timing. Eerst op ip, daar failt ie. Dan krijg je optie om user en pw in te voeren. Op dat moment authenticate app. Zoiets was t geloof ik. Was ff ruzie.

[Oesie]

Koepert schreef op donderdag 10 februari 2022 @ 22:12:
[...]


Toevallig recent nog gedaan. In de phoson app bij gateway authenticate app doen en dan vanuit de hue app zoeken.. t is n beetje gokken qua timing. Eerst op ip, daar failt ie. Dan krijg je optie om user en pw in te voeren. Op dat moment authenticate app. Zoiets was t geloof ik. Was ff ruzie.

De app vindt hem bij mij niet automatisch en ook via een manual instelling (IP van Home Assistant en IP van deCONZ gateway geprobeerd) pakt die hem niet (uiteraard na authenticate app te hebben gedaan).

[Mimiix]

Oesie schreef op donderdag 10 februari 2022 @ 22:24:
[...]

De app vindt hem bij mij niet automatisch en ook via een manual instelling (IP van Home Assistant en IP van deCONZ gateway geprobeerd) pakt die hem niet (uiteraard na authenticate app te hebben gedaan).

Heb je de poorten in de addon correct ingesteld?

[Oesie]

Mimiix schreef op donderdag 10 februari 2022 @ 23:00:
[...]


Heb je de poorten in de addon correct ingesteld?

Bedoel je op deze config page (zie screenshot)?
Op de eerste regel heb ik het IP adres van Home Assistant en van Phoscon geprobeerd.

[Mimiix]

Oesie schreef op vrijdag 11 februari 2022 @ 09:19:
[...]

Bedoel je op deze config page (zie screenshot)?
Op de eerste regel heb ik het IP adres van Home Assistant en van Phoscon geprobeerd.

[Afbeelding]

Die poorten daaronder moet je even overnemen van het voorbeeld ernaast.

Dan werkt het.

De HA Addon exposed de poorten nu niet naar je netwerk waardoor je hem niet kan benaderen met de Hue essentials app.

[vanenkelen]

Terugkerend onderwerp in dit topic en nog nooit echt een goed werkende oplossing gevonden, desalniettemin wel een concrete hulpvraag.

Ik blijf worstelen met mijn Xiaomi sensoren (beweging, temperatuur en deur/raam). Ik heb er best veel en inmiddels heb ik het maximale aantal devices aan mijn Conbee2 stick hangen. Dit zorgt er voor dat ik af en toe uitval heb in het netwerk.

Ondanks dat ik behoorlijk wat dimmers en switches heb die normaalgesproken prima als router zouden moeten fungeren willen die Xiaomi's er niet mee verbinden. Heel soms lukt het, maar binnen een aantal weken springen ze weer rechtstreeks naar de Conbee.

De enige routers waarmee ik wel een stabiele en blijvende verbinding lijk te krijgen met de Xiaomi sensoren zijn de Ikea Tradfri signaalversterkers (die USB laders). En laat die nu al heel lang uitverkocht zijn en voorlopig nog niet op voorraad terug komen (iets met chip tekorten). Dus nu is mijn oog gevallen op de Ikea Tradfri plug stekkers die in ieder geval via marktplaats nog redelijk te krijgen zijn. Daarom twee concrete vragen:

- Werken de Ikea Tradfri stekkers ook als router?
- Heeft iemand ervaring hiermee icm met Xiaomi sensoren?

(en #durftevragen: heeft iemand misschien 1 of 2 tradfri signaalversterkers over die ik over kan nemen?)

[Oesie]

Mimiix schreef op vrijdag 11 februari 2022 @ 10:52:
[...]


Die poorten daaronder moet je even overnemen van het voorbeeld ernaast.

Dan werkt het.

De HA Addon exposed de poorten nu niet naar je netwerk waardoor je hem niet kan benaderen met de Hue essentials app.

Door de naam host was ik in de veronderstelling dat daar een host (dus ip adres) moest worden ingevuld. Soms is de oplossing zo simpel

[Mimiix]

vanenkelen schreef op vrijdag 11 februari 2022 @ 12:13:
Terugkerend onderwerp in dit topic en nog nooit echt een goed werkende oplossing gevonden, desalniettemin wel een concrete hulpvraag.

Ik blijf worstelen met mijn Xiaomi sensoren (beweging, temperatuur en deur/raam). Ik heb er best veel en inmiddels heb ik het maximale aantal devices aan mijn Conbee2 stick hangen. Dit zorgt er voor dat ik af en toe uitval heb in het netwerk.

Ondanks dat ik behoorlijk wat dimmers en switches heb die normaalgesproken prima als router zouden moeten fungeren willen die Xiaomi's er niet mee verbinden. Heel soms lukt het, maar binnen een aantal weken springen ze weer rechtstreeks naar de Conbee.

De enige routers waarmee ik wel een stabiele en blijvende verbinding lijk te krijgen met de Xiaomi sensoren zijn de Ikea Tradfri signaalversterkers (die USB laders). En laat die nu al heel lang uitverkocht zijn en voorlopig nog niet op voorraad terug komen (iets met chip tekorten). Dus nu is mijn oog gevallen op de Ikea Tradfri plug stekkers die in ieder geval via marktplaats nog redelijk te krijgen zijn. Daarom twee concrete vragen:

- Werken de Ikea Tradfri stekkers ook als router?
- Heeft iemand ervaring hiermee icm met Xiaomi sensoren?

(en #durftevragen: heeft iemand misschien 1 of 2 tradfri signaalversterkers over die ik over kan nemen?)

Ja.
Nee.

Het gaat erom dat er genoeg routers zijn in het netwerk. De apparaten kiezen zelf wat ze het beste vinden.

Hoeveel routers heb je nu? En hoeveel sensoren?

[vanenkelen]

Mimiix schreef op vrijdag 11 februari 2022 @ 13:15:
[...]


Ja.
Nee.

Het gaat erom dat er genoeg routers zijn in het netwerk. De apparaten kiezen zelf wat ze het beste vinden.

Hoeveel routers heb je nu? En hoeveel sensoren?

Ik heb in totaal 10 routers (2x Ikea signaalversterker, 1x stekkerdimmer, 2x inbouwschakelaar Robbshop en 5x inbouwdimmer Robbshop en nog een ander merk). De conbee2 hangt op de begane grond, de 2 tradfri versterkers op verdieping 1 en 2.

Ik heb 26 sensoren en 6 schakelaars. Vrijwel alle sensoren die op de begane grond hangen willen alleen maar rechtstreeks met de conbee stick verbinden. Het kost extreem veel moeite om ze op één van de routers beneden te verbinden, eigenlijk lukt dat gewoon niet. Het lukt alleen op de tradfri routers en die stekkerdimmer (rood onderstreept in onderstaand plaatje).

Mijn plan was dus om op de begane grond 2 extra tradfri signaalversterkers te plaatsen om zo de load wat te verdelen.

[JBS]

Dat je met een Tradfri motion sensor een Tradfri lamp kunt resetten om te pairen met een Tradfri Hub weet ik, maar werkt zo'n motion sensor ook om een Tradfri lamp te resetten om te pairen met deCONZ? Pairen = pairen zou je zeggen?