New MiLight Lamp gets no connection

---

Hello, I have noticed a very strange reaction of my MiLight lamps today.
I wanted to register a new MiLight lamp to an existing bridge (MiLight Lamp/Bridge, v6) on the third still free zone. Two lamps (two zones) had been registered for several months. I can’t tell since when exactly.
Anyway, I tried different things, I can’t get the new MiLight registered to pimatic. I can easily register this lamp with the remote control. I can also easily register this lamp to the Bridge via Smartphone/App. Everything works. Only with pimatic I cannot switch the lamp. No reaction.
Then I disconnected one of the long working lamps from the bridge. And the new lamp was registered to the zone of the lamp that was working up to now.
With the result, I could not switch both lamps any more over pimatic.
I have no idea what has changed in the meantime. Now I can’t get both lamps connected anymore. Although the connection via SmartPhone/App to the bridge runs without any problems. After all, I can connect, disconnect and control everything via the SmartPhoneApp. So I guess something must have changed between the connection pimatic <->bridge.

I would be very pleased about a help.

@thrusty said in New MiLight Lamp gets no connection:

ith the result, I could not switch both lamps any more over pimatic.

Can you please post the device configuration you have setup for the two lamps?

@mwittig

Lamp 1, allways useble

{
      "ip": "192.168.178.47",
      "zoneId": 2,
      "id": "mi-esszimmer",
      "name": "Mi Esszimmer",
      "class": "MilightWWCWZone",
      "bridgeVersion": "v6",
      "echo": {
        "additionalNames": []
      }

Lamp 2, just out of order

{
      "class": "MilightWWCWZone",
      "id": "milight-wwcw-zone-2",
      "name": "Milight Küche",
      "ip": "192.168.178.47",
      "bridgeVersion": "v6",
      "zoneId": 1,
      "echo": {
        "additionalNames": []
      }

and the new Lamp

 {
      "class": "MilightWWCWZone",
      "id": "kammerlicht",
      "name": "Kammer",
      "ip": "192.168.178.47",
      "bridgeVersion": "v6",
      "zoneId": 4,
      "echo": {
        "additionalNames": []
      }

Is the reason for the misbehaviour possibly the different arrangement of the entries?
I want to use the scheme of the first lamp for the other two.
Then I’ll get back to you.

Last week I rearranged my milight devices and changed their zones. I had no problems. I have one legacy and one v6 bridge.

Paired them with different apps via smartphone because there is no app supporting both bridge versions. Afterwards I added them to pimatic. The only problem I have, there is no color picker for the v6 connected RGB bulbs. So I change the color via smartphone and only switch them on and off via pimatic.

I changed the entries in the config after the example of lamp 1. Unfortunately it did not bring the desired success. No reaction from lamp 2 and lamp 3
I have restarted pimatic with sudo pimatic.js.
Then I got this error message:

Unhandled rejection Error: no response timeout
    at null._onTimeout (/home/pi/pimatic-app/node_modules/pimatic-milight-reloaded/node_modules/node-milight-promise/src/milight-v6-mixin.js:125:26)
    at Timer.listOnTimeout (timers.js:92:15)

Edit:
Unfortunately I just had to find out that now none of the lamps can be switched. Probably has to do with the error message.

I don’t know if it has anything to do with the current problem, but I’ll write a short story.
It all started when I wanted to connect a Tradfri dimmer via the pimatic-RaspBee plugin. That didn’t work. There I noticed that there was an update for pimatic-RaspBee in the meantime. I didn’t want to do the update with the pimatic-GUI, because of the problems with 0.9.43. I had read a lot about it in the forum.
So I tried with sudo npm install pimatic-raspbee@latest the RaspBee update via the console. Unfortunately without success. I got this message for several packages ...was bundled with pimatic@0.9.43, but bundled package wasn't found in unpacked tree.
So I tried to install pimatic update 0.9.43. Unfortunately also without success. Also sudo npm install unfortunately didn’t help.
Then I renamed the pimatic folder and tried a new installation. Step by step as described in @Leader21. Unfortunately also without success. Even during the installation I got the message: ...was bundled with pimatic@0.9.43, but bundled package wasn't found in unpacked tree.
After that I installed 0.9.42 again. Without problems. Then I copied the plugin folder from the renamed pimatic folder into the new installation and copied the config.json into it.
Now my system was running again.
And then came the MiLight problem.

@thrusty Is the new lamp the same model as the other lamps you have, i.e. are you sure it is RGWWW lamps and not one of the bulbs supporting fullColor mode?

Yes, it is the same Lamp. I have it connect with the same Smartphone App (MiLightApp)-Remote and in there the same Remote as the other lamps.

Hi, I’m getting nowhere. I can no longer register MiLight. Somehow nothing works anymore. What can I do?