Are you sure I should update my Plug S with 1PM FW Allterco ?
Beiträge von gdslno
-
-
It looks to me like the network stack in Mongoose OS might be more restrictive then others. I had to tweak my DHCP packets (they where larger then normal due to complex network setup) in order for the shellies to accept them. Also, when I had the DNS resolution problem it seems that maybe the shellies might discard complex DNS replies... I don't have any real evidence of the latter, it's just a speculation.
My solution was to configure my DHCP server to issue shelly devices with Googles DNS servers. That fixed it for me.
-
Your DNS server at 10.0.0.2 fails to do DNS resolution for the hostnames, or fails to relay the information to your Shelly.
I had the same problem on a single Shelly Pro 4 PM not too long ago. The fix was to assign google dns servers 8.8.8.8 / 8.8.4.4 to the Shelly.
-
What's the best way to report a bug in the /statistics/relay/consumption API endpoint ?
-
Is there anyway to get the Output names for the Shelly 4 Pro PM from the cloud ?
The output name does not seem to be included in "interface/device/get_all_lists" or in the "Shelly:StatusOnChange" web socket message.
It would be really good if the metadata array in StatusOnChange could contain the Output name too....
-
To save power and to keep from heating up, the Plus H&T only stays on for a few seconds every few minutes. When the device is in deep sleep it will not respond to anything.
You will either need to wake it up repeatedly with the button, or connect it to the cloud and configure it there.
-
Alright. Seems like Allterco might need to improve their API
-
Zitat
Is there another way (mqtt) to go into set mode because having to open the cover each time is cumbersome, especially if the module is connected via USB.
Indeed.
-
That's a bit strange. The documentation at https://shelly-api-docs.shelly.cloud/cloud-control-…l-device-groups claims it should work for lights:
ZitatControl device groups
Control of similar types of devices - Relays, Lights, Cover controls can be done en masse.
-
-
Also I was wondering if there is a way to list devices for a given user via the cloud API.
Yes. https://shelly-api-docs.shelly.cloud/cloud-control-…--owned-devices
You may need to do oAuth before you call the API.
-
Temperature offset that can be set after the circuitry has reached temperature equilibrium.
-
I'd like to request an option to completely disable deep sleep when the device is USB powered.
-
-
On the PRO 4 PM you can go to the status page on the display and see the internal temperature of the device.
Has anyone found a way to get this value by scripting ?
-
It's worth a try to test http://127.0.0.1/relay/3?turn=toggle and http://localhost/relay/3?turn=toggle and see if that helps.
-
Alright. The Full Debug log (that I hadn't noticed until now) shows that DNS query for the target domain fails. It seems the ISP DNS is no longer responding to queries from one of my Shellys. That is very strange, but it is something I can workaround.
I have reconfigured the local DHCP to issue google DNS servers to the Shelly devices and that fixed the problem.
Sorry for taking every ones time.
-
Yes. That's easy to guess, but the KVS value and the Queue persists. It's the HTTP Request itself that fails.
-
Code
Alles anzeigenfunction SendData(data) { data.DeviceName = Name; data.DeviceType = Device; data.DeviceModel = Info.model; let params = { method: "POST", url: CONFIG.DataURL, headers: CONFIG.Auth, content_type: 'application/json', body: JSON.stringify(data) }; Shelly.call("HTTP.Request", params, function (res, error_code, error_msg, ud) { if (!error_code) { if (res.code === 200) { DeleteKVSandQueue(ud.key); print("SendData: Data Sent", JSON.stringify(ud)); } else { print("SendData: HTTP Status code", res.code); } } else { print("SendData: Error", JSON.stringify(error_code), JSON.stringify(error_msg)); } }, data) }
I have two Shelly 4 Pro PM (fw 0.11.3) in the same local network, both connected with ethernet and set up identically. I can access the WebUI on both of them.
One of them has started to produce the error message: SendData: Error -114 "Resource unavailable: HTTP connect error -1!". It even does this on the first HTTP Request after a reboot.
Have I broken something in the device ?
-
I've seen the same thing.
For me it seems to be related to storing objects in the KVS value.
If object properties are access directly the script crashes and clears the KVS store.
This works:
CodeShelly.call ( "KVS.GetMany" { match: 'M_*' }, function (result, error_code, error_msg, ud) { if (result) { for (let KVS in result.items) { let data = result.items[KVS]; data = data.value if ( data.DoW !== DayOfWeek(ud.ts) || data.HoD !== HourOfDay(ud.ts) ) {
This causes the bug to manifest for me:
CodeShelly.call ( "KVS.GetMany" { match: 'M_*' }, function (result, error_code, error_msg, ud) { if (result) { for (let KVS in result.items) { let data = result.items[KVS].value; if ( data.DoW !== DayOfWeek(ud.ts) || data.HoD !== HourOfDay(ud.ts) ) {
It's a bit strange.....