Beiträge von biomass

Bit late to reply back, but having the IP come from DHCP results in extra use of the WiFi radio, resulting in more battery usage. Also, when the reception is poor, retransmission(s) because of the TCP/IP protocol can cause battery drain. Are all devices on the same firmware (TRV and Motion on seperate versions of course)? Do the logs of your access points/wifi router show transmission errors for the devices that have poor battery performance?

Turning on the logging also consumes energy, and is not recommended to leave on permanently.

DHCP disabled on all devices?

Thanks! One thing you are probably also aware of; you have a few (two?) versions of these linkpages, as the page you linked is different from the one I linked to. The one that you linked is very nice with all the thumbnail photos!

@Olsche

Danke Olsche

It would be a bit unreasonable to ask you to post to every beginners thread in the forum, but I must say your signature does look familiar

I think it would be nice to change the text for hint number 2 in the English forum post for beginners Beginner's tips for shelly and the forum

and direct people straight to connection diagrams - overview (as an example link to the lexicon). Three reasons why I suggest this: It's a great resource for beginners, and in the English language, I think people would look for 'wiring diagrams'.

The last reason is that it may not be clear to people that their language settings may prevent them from finding the German or English posts, depending on the settings in their profile.

The devil is in the details Good to see it's working for you now.

Zitat von matdjtee

tried resetting the device via flicking the switch 5x times, and I hear the Shelly clicking but it still won't be found via the app.

If that successfully triggered the factory reset, (here 'auf Deutsch') it should advertise itself as a 'new' unsecured WiFi network named 'shelly*'. If you then join that network on your phone or pc, the web interface of the Shelly 1 should be available from http://192.168.33.1

shellerr: I assumed you had a combined router and accesspoint. Your accesspoint should treat all your Shellies equally. Are you sure the Shelly that is not working is also allowed to interact with the other devices on your LAN??

If you want to try and debug the UDP traffic, have you already checked your router for the settings that apply to all your Shellies? I have an outbound NTP only rule for my Shellies for example, with my last setup I noticed I forgot to do *all* the settings for all the devices....

I assume you mean you changed your internet service provider and they have given you a new wireless WiFi router/access point. Apparently in America "Wifi provider" is a normal term?

If you have a mobile phone that can setup a wifi hotspot on your phone with the same SSID (Hotspot name) and password. Then you can connect your desktop or laptop to that Wifi network if you have wireless capability in your pc (almost guaranteed for a laptop). The Shelly should also connect automatically to that network if the password and SSID are correct. Once both are connected, you would have to find the IP of the Shelly. If the Shelly was configured with a fixed/static IP adress, chances are it will not be on the same network subnet as the phones hotspot.

The other option is to reconfigure the SSID and password of your new router. That will mean you have to reconfigure all your other wireless devices too.

If both of these options don't work for you, you should do a factory reset of the Shelly.

What and why did the wifi connection change? The wifi password in your Shelly will only work if your new WiFI SSID and password are the same as the old ones?? If you can revive your old router/AP, changing the settings or doing a factory reset should be easy...

This thread was helpful to me, as i just tried to setup a Shelly 1PM that I purchased a couple of weeks back and the factory firmware was still on firmware 20191219-114622/1047-long-id-for-shelly-devices@d05667c7 from the factory. I had wired up the 1PM with just the live and neutral wires to set up the wifi. All was good for the first five minutes, it showed the webinterface after entering the WPA key within seconds. But then it would not respond to the webpage calls anymore.

Interestingly, the REST API did work intermittently. I tried to /reboot the device but that gave no response, but when added gibberish behind the /reboot command like /rebootasldkfjalsfjijlsadkfjalskdjf..etc, it gave an OK JSON response? Rebooting the router did help to get the webinterface back, but it would not respond after a few minutes again.

After that I tried to update the firmware via the REST api. That turned out not to work because the archive.shelly-forum.com webservers was so heavily loaded that the download timed out on the 1PM. So I downloaded the firmware separately and hosted it locally. After that the firmware update was successful.

I did not enable a static IP on the 1PM, my AVM Fritz!Box 8753 and AVM Fritz!Repeater 3000 were to take care of that. Interestingly, the 1PM signed up to the repeater, which is located on the first floor, instead of the Fritz!Box in the same room.

I saw the same behaviour. If the clock in the Plug S is not set, the energy readings will not work.

If you see "timestamp":0, in a response to http://ip-address/meter/0 in your browser, the energy reading for your device will not work because it's clock is not running.

I just created an Allterco ticket with the below questions:

Zitat

Clock must be set for energy readings, what happens in 2038?

Dear madam/sir,

last month I more than doubled my inventory of Shelly Plug S devices, I added four of them.

I was puzzled that I received power readings for all seven devices, but got only one energy reading from a single device.

Turns out I had given two of the older devices a firmware update without caring for the system time of the devices, and completely blocking the internet access to all of them, after putting them all on the same firmware.

After realizing that the energy counters rely on the unixtimestamp to be set (e.g. not zero); I wondered what will happen in 2038? Will the firmware support running after ending the 32-bit UNIX epoch?

Also, I could not find the requirement to have a current time set directly in the FAQ, but it could be helpful to hint at the overly enthusiastic types who don't bother to set the time?

thanks in advance,

Alles anzeigen

chris897 How often does it connect to the AP (the Unifi in your case Tom)? And for what reason? My Shelly Motion is mounted on the wall, near the ceiling, out of reach for even the tallest person, ladder required.

The past four days looked like this in HA:

So mine is not triggering on the vibration sensor , and the amount of light change is also minimal, since it is not getting any direct sunlight.

Visit the IP address your access point has given to the Shelly Motion like so http://192.168.178.43, verify that the Shelly Cloud connection is enabled, and that the Shelly can reach the internet. If it offers you a firmware update, the internet connection is ok. Then see if you can find it in the Shelly app. PS I don't use the Shelly cloud myself.

Once the device is on the battery, it will hibernate until it detects motion or vibration. You can wake it if you request its management webpage a few times in a row. I did most of my setup while I had the device connected to a charging cable.

FWIW - I enabled the logs on my access points to see how often my Shelly Motion wakes up to get connected. Sort of expected, it only deregisters a few times per day.

This would mean you are getting/adding sensor events faster than the rate at which they can be removed from the buffer (because they have been sent via WifI)? Is the environment vibration-free and do you have a good WiFi connection for the devices?

According to the API for the Motion, the parameter that you see in the generic HTTP API, is not available. Since the Motion is battery operated, I would think that you cannot change that parameter as it would change the energy consumption drastically depending on the user input. The parameter is mostly there for software like Home Assistant to know when the device is offline (e.g. has not come back with an update within 1 hour).

If the 1 hour update period is a given, how often do you see your Motion devices connect to your AP?

You've enabled DHCP. Are you able to assign it a fixed IP or give it a fixed DHCP IP ? Your CoIOT peer is on a slighlty different network than the Shelly motion (10,10,197.x vs 10.10.196.x). If any timeouts results in the Wifi radio of the Motion being on for a long time, that will hurt battery life? How is the connectivity while you have the device on the charger?