Beiträge von RobvdB

A new problem just popped up:

Aparently the Relais is overheating. And it isn't even very warm here today.

How am I going to solve that? I have no idea ...

Due to personal circumstances, I had to wait until today to actually install everything.

I have now installed everything according to your diagram, like this:

Everything works, except there is a big problem: every change of one of the physical switches takes almost 30 seconds before it is recognized in Home Assistant!

The wifi signal is perfect. There are only 3 meters between the Shelly and the router, and there is a direct line-of-sight, without obstructions inbetween. Also the Shelly webinterface indicates full signal strength and I see the same if I look in the configuration in the router.

If have many Shellies: Shelly 1, Plus 1, Plus 1PM, 2.5 and all of them react virtually instantly to switch changes. Only this Shelly 1L does not. Obviously 30 seconds is waaaay too long for practical use.

Do you have any information on what could cause this? Or how to solve it?

===============================================================================================

Never mind, I found the solution.

I had enabled CoIoT, but it was still set to mcast.

I replaced mcast with the IP address and port number of the Home assistant server and now everything works perfectly and fast.

Thanks again!

Yes, I think I am beginning to understand. It looked complicated at first, but the longer I look at this new diagram, it seems not too difficult.

The clever part in this diagram I think, is the top wire that starts wth L > br > bl(1) > O. This makes sure that O is always connected to Live. Yet at the same time you run br through Switch 2 and connect it via bl(2) to SW1 so it can also function as a automation switch. Then basically you do the same thing on the Switch 1 side, where you run the wire through Switch 1 to SW2 so you can use that too as a automation switch, creating two individual switches instead of a hotel-switch, but each switch can operate the light bulb individually (through automation). Brilliant!!

(I still need to read the other stuff so I understand everything fully, but I think I'll get it if I think about it long and hard enough)

You truly are a Godsend! Thank you so much for taking the time to educate me. It is really very much appreciated! I wish I could buy you a beer! 😁

Ok, I admit defeat ... I thought I understood, but now I think I do not ...

It turns out that the situation in the wall is a little bit more complicated than the test setup in the photo I posted yesterday. It turns out it is actually a hotel-switch. That's why I had the 2 black wires I originally saw in switch 2. Those were not wired, 1 to the switch, and the other to the lamp. They both go to switch 1, like this:

There are a few things I do not understand.

The first is the use of the SX terminals on the Shelly 1L. According to the user guide, they provide 5 Volts to switch SW1 and SW2. So SX should go to the switch, and from there the switch should be connected to SW1 or SW2, right? It also specifically says that you should not connect 220 Volts mains there. BUT, in the diagram you posted, and in the test setup I made, I actually put 220 Volts on SW1, as you can see in the photo from yesterday. And the test setup worked! How can that be? Why did the Shelly not get fried?

And my second question is, what is exactly the purpose of reversing the L and O connectors, connecting L to the lamp and O to live mains. I know it works this way, I have seen it work. I just do not understand why it is not connected as it would normally, with L connected to mains and O to the lamp. What is the reason for reversing these connectors?

I hope you have some time for me to answer these questions. It would be very much appreciated!!!

Nope, I'm going to do that now! haha

Plugged the connector in the wall, it didn't produce smoke, so that's a good start.
At first I thought it had not worked, because the blinking red Wifi light does not come one. But I can connect via the web interface, so it must be working ...

Well, what do you know! It works!!!

Going to install the Shelly into the wall now. Wish me luck! 😆

Unfortunately it took until today for the 1L to arrive, but here it is.

If I read the diagram that you sent correctly, then the Shelly 1L should be wired like this:

Is this correct?

I wanted to ask, before I fry the Shelly hahaha

(I hope you can figure out how the wires are connected in this photo)

aaaah, right!! The fact that in my head, I did not connect the lamp, made me feel like I was missing one lead. But your idea of connecting the lamp to a permanently triggered relais, that allows the Shelly to get it's power regardless. Brilliant! Thank you very very much, I am going to try this tomorrow.

Is it possible to use the Shelly 1L without a neutral wire in detached mode?

I have a smart lamp, so it just needs permanent power. The lamp itself will be turned on/off through home automation commands. So, the lamp is not a consumer of the switch!

So, basically, all I want to use the Shelly 1L for is as a device that registers whenever I turn the physical switch, so that I can have my automation turn that into commands for the light.

But is this even possible? Could I use the bypass as a consumer, because the light itself is not a consumer in this setup.

If this is possible, what would the wiring diagram look like? In the wall I just have the brown live wire and the two black wires....

I think we had the same experience there

Not working

Not working

Not working

... hey, it works!

For me the device was auto-discovered after a manual restart. So I am inclined to think that may have been the reason. But I did do other things as well before the reboot, so I can't be 100% sure.

Rektifikation

Nach mehreren Refreshes, Neustarts, Factory-Reset und HA-Reset funktionierte es auf einmal. Ich weiß nicht, welche dieser Aktionen genau dazu geführt hat, dass es jetzt funktioniert, aber ich könnte das Gerät jetzt hinzufügen. Werde weiter testen ob alles funktioniert...

--------------------------------------------------------------

Alles scheint jetzt perfekt zu funktionieren.

Great work guys!!!

Correction!

After several refreshes, reboots, factory reset and HA reset, it suddenly started working. I do not know which of these actions specifically caused it to start working but I could now add the device. Will continue testing now if everything works...

-------------------------------------------------------------------

Everything seems te be working perfectly now.

Great work guys!!!

It does not show up in my Home Assistant using HA's own integration. The problem is still the same as before, just an empy dialog-box but nothing gets added:

Are you sure you are using the native Shelly-integration in Home Assistant? Or are you using a different integration, like ShellyForHASS or MQTT maybe?

Leider...

Der Model-key ist jetzt verfügbar, stimmt, aber das Gerät lasst sich immer noch nicht in Home Assistant hinzugefügen.

In Home Assistant ist es immer noch gleich, nur ein leeres dialog-box und nichts wird hinzugefügt.

It depends on what the problem is he is having. There are 2 problems being discussed here.
The first problem is, not being able to connect the device to the cloud. That problem was resolved last week by a change Allterco made to their servers. This problem did not require a firmware update.

The second problem is that the device does not return its model identification, which results in other problems, like for example not being able to add the device in Home Assistant. This problem is waiting for a firmware update that Allterco promised is coming soon.

Jap, hab das gestern auch gesehen, als ich das change log von 2022.5.5 nachgeschaut habe. Ich habe das auch versucht, aber es gab keine Änderung. Die Warnung wird nicht einmal gezeigt. Soweit ich auf github sehen kann, wurde dieser Mod bereits wieder gezogen.

I guess I'm one of the 'lucky' ones who has 4 from that production station.
Good to know though it can be fixed through a firmware patch.

Ah Toll!!!

Ja, ich habe Geduld, keine Sorge.

Vielen Dank für die Bestätigung!

Ich habe einen Unterschied gefunden zwischen dem funktionierenden Shelly Plus 1PM und einem der 1PMs die nicht funktionieren:

Die +1PM, die funktioniert, bekommt dies zurück von: http://10.0.0.71/shelly

{

"name": "OVR1",

"id": "shellyplus1pm-3c610579a3a1",

"mac": "3C610579A3A1",

"model": "SNSW-001P16EU",

"gen": 2,

"fw_id": "20220330-151110/0.10.1-g8d603a2",

"ver": "0.10.1",

"app": "Plus1PM",

"auth_en": false,

"auth_domain": null

}

Die +1PM, die nicht funktioniert, bekommt dies zurück von: http://10.0.0.50/shelly

{

"name": "OVR2",

"id": "shellyplus1pm-083af201de3d",

"mac": "083AF201DE3D",

"gen": 2,

"fw_id": "20220330-151110/0.10.1-g8d603a2",

"ver": "0.10.1",

"app": "Plus1PM",

"auth_en": false,

"auth_domain": null

}

Obwohl die Firmware-ID und die Firmware-Version identisch sind, ist das Ergebnis anders.

Wie man sieht, liefert die nicht funktionierende +1PM das "modell" nicht zurück: "model": "SNSW-001P16EU"  fehlt.

Wenn die 'offizielle' Shelly-Integration in Home Assistant nach "Model:" sucht, könnte das erklären, warum diese +PM1 nicht funktionieren ...

Aus Neugier habe ich ShellyForHASS installiert und dort alle Geräte hinzugefügt.

Jetzt funktionieren die Shelly Plus 1PMs ohne Problemen!!! Sie werden automatisch erkannt und sofort hinzugefügt.

Ich habe ShellyForHASS wieder deinstalliert, die Konfigurationsdaten entfernt, von vorne angefangen und alle Geräte wieder in der internen Shelly-Integration hinzugefügt. Jetzt ist das Problem wieder da. Alle Shellys die ich habe funktionieren einwandfrei, Shelly 1, Shelly 1PM, Shelly 1L, Shelly 2.5 und die Shelly Plus 1PM die ich im März gekauft habe.

Aber die vier Plus 1PMs, die ich kürzlich gekauft habe, funktionieren NICHT. Aus irgendeinem Grund weigern die mit der internen Shelly-Integration zu sprechen. Da muss es irgendein Kompatibilitätsproblem geben.

Es ist kein Problem des Netzwerks. Es ist ein Problem mit diesen spezifischen +1PMs.

Ich vermute, dass dieses Problem irgendwie mit den Problemen der letzten 2 Wochen zusammenhängen. Etwas hat sich geändert, was die Probleme mit der Cloud-Verbindung verursacht hat. Das Problem wurde nun gelöst, aber dieses Problem bleibt bestehen.