Rasbee pairing Innr lamps fails

Phoscon App General Support
1

Hi,
I habe a Rasberry4 with a rasbee2 onboard.
I have some Hue outdoor lamps connected and everything works fine.

Now I will pair new Innr E29 lamps and after some tries they paired.
On the next day I could controll the lamps with Phoscon and they were grey as they were offline but they were powered and on.

I erased then in Phoscon and tried to pair them again and this will fail.
I resetted the lamp by six times on/off and they blink whenever I power them on.

Any ideas what I can do?

Thanks in advance

Peter

2

Hi Peter,

Can you please share some logs from deconz while pairing?

You can find out how to make logs in #deconz

3

Hi,

so I should try to pair them again and then send the log of thus timeframe?
How can I stop the logging to make a copy of the logged data?
Currently it‘s running …

Best
Peter

4

Just uncheck the boxes :slight_smile:

5

Sorry… :crazy_face:

6

Will try and come back

7

Hi,
here the log outcome.

Peter

18:31:38:328 wait reconnect 5 seconds
18:31:38:412 COM: /dev/ttyAMA0 : (0x0000/0x0000)
18:31:38:414 COM: /dev/ttyS0 : (0x0000/0x0000)
18:31:38:415 dev /dev/ttyS0 (/dev/ttyS0)
18:31:38:441 APS-DATA.request id: 81, addrmode: 0x03, addr: 0x001788010649f4f0, profile: 0x0000, cluster: 0x0033, ep: 0x00 → 0x00 queue: 0 len: 2 tx.options 0x04
18:31:38:443 asdu (length: 2): ac00
18:31:38:661 API error 950, /sensors, Not connected
18:31:38:823 rule event /config/localtime: 18:31:37.824 → 18:31:38.823 (999ms)
18:31:39:169 API error 950, /sensors, Not connected
18:31:39:323 wait reconnect 4 seconds
18:31:39:823 rule event /config/localtime: 18:31:38.823 → 18:31:39.823 (1000ms)
18:31:40:327 wait reconnect 3 seconds
18:31:40:823 rule event /config/localtime: 18:31:39.823 → 18:31:40.823 (1000ms)
18:31:41:323 Daylight now: sunsetStart, status: 190, daylight: 0, dark: 0
18:31:41:324 APS-DATA.request id: 82, addrmode: 0x03, addr: 0x001788010647f678, profile: 0x0104, cluster: 0x0000, ep: 0x01 → 0x02 queue: 0 len: 7 tx.options 0x00
18:31:41:325 asdu (length: 7): 140b10a3003200
18:31:41:326 failed to reconnect to network try=4
18:31:41:326 wait reconnect 2 seconds
18:31:41:823 rule event /config/localtime: 18:31:40.823 → 18:31:41.823 (1000ms)
18:31:42:323 wait reconnect 1 seconds
18:31:42:365 COM: /dev/ttyAMA0 : (0x0000/0x0000)
18:31:42:366 COM: /dev/ttyS0 : (0x0000/0x0000)
18:31:42:367 dev /dev/ttyS0 (/dev/ttyS0)
18:31:42:368 failed open com status: (-3), path: /dev/ttyS0
18:31:42:378 APS-DATA.request id: 83, addrmode: 0x03, addr: 0x001788010647f678, profile: 0x0000, cluster: 0x0033, ep: 0x00 → 0x00 queue: 0 len: 2 tx.options 0x04
18:31:42:379 asdu (length: 2): ad00
18:31:42:823 rule event /config/localtime: 18:31:41.823 → 18:31:42.823 (1000ms)
18:31:43:323 wait reconnect 5 seconds
18:31:43:365 COM: /dev/ttyAMA0 : (0x0000/0x0000)
18:31:43:366 COM: /dev/ttyS0 : (0x0000/0x0000)
18:31:43:367 dev /dev/ttyS0 (/dev/ttyS0)
18:31:43:824 rule event /config/localtime: 18:31:42.823 → 18:31:43.824 (1001ms)
18:31:44:323 wait reconnect 4 seconds
18:31:44:823 rule event /config/localtime: 18:31:43.824 → 18:31:44.823 (999ms)
18:31:45:323 wait reconnect 3 seconds
18:31:45:824 rule event /config/localtime: 18:31:44.823 → 18:31:45.823 (1000ms)
18:31:46:323 failed to reconnect to network try=5
18:31:46:325 wait reconnect 2 seconds
18:31:46:386 COM: /dev/ttyAMA0 : (0x0000/0x0000)
18:31:46:387 COM: /dev/ttyS0 : (0x0000/0x0000)
18:31:46:388 dev /dev/ttyS0 (/dev/ttyS0)
18:31:46:388 GW firmware update select /dev/ttyS0 device
18:31:46:396 GW update firmware not found:
18:31:46:824 rule event /config/localtime: 18:31:45.823 → 18:31:46.824 (1001ms)
18:31:47:323 wait reconnect 1 seconds
18:31:47:365 COM: /dev/ttyAMA0 : (0x0000/0x0000)
18:31:47:366 COM: /dev/ttyS0 : (0x0000/0x0000)
18:31:47:367 dev /dev/ttyS0 (/dev/ttyS0)
18:31:47:368 failed open com status: (-3), path: /dev/ttyS0
18:31:47:823 rule event /config/localtime: 18:31:46.824 → 18:31:47.823 (999ms)
18:31:48:323 wait reconnect 5 seconds
18:31:48:366 COM: /dev/ttyAMA0 : (0x0000/0x0000)
18:31:48:367 COM: /dev/ttyS0 : (0x0000/0x0000)
18:31:48:368 dev /dev/ttyS0 (/dev/ttyS0)
18:31:48:824 rule event /config/localtime: 18:31:47.823 → 18:31:48.823 (1000ms)
18:31:49:323 wait reconnect 4 seconds
18:31:49:823 rule event /config/localtime: 18:31:48.823 → 18:31:49.823 (1000ms)
18:31:50:324 wait reconnect 3 seconds

8

It can’t mount the stick. So it can’t access the network. For some reason it drops out.

How did you install deconz?

9

Hi,

there is no stick. It‘s a rasbee2 onboard on the pins of the rasberry.

I have 7 Hue outdoor lamps attached to deconz and they work without any issue.

Hope this make it clearer.

Peter

10

Hi,

The reconnect means the Raspbee is not connected.

Can you show some longer logs?

Additionally, what debug flags did you use?

11

Hi,

I used the flags you told me.

I will create a longer log with pairing on Friday or Saturday.
Sorry. Currently I‘m very busy.

Peter