| Author |
|
GadgetGuy
Super User
Joined: June 01 2008
Location: United States
Online Status: Offline
Posts: 942
|
| Posted: December 19 2022 at 14:57 | IP Logged
|
|
|
Dave -
As I recall you have worked on Alexis support for PH.
I'm wondering if that might support this power monitoring device. I have a number of Insteon controlled electronics that only have an IR command to "Toggle Power" and no ON/OFF commands so it is impossible to accurately control as one is never sure of the device power state to begin with.
This little inexpensive unit looks like it would allow one to determine the power state with confidence...
Product web link
Does it seem likely to be handled by PH?
GadgetGuy
__________________
Ken B - Live every day like it's your last. Eventually, you'll get it right!
|
| Back to Top |
|
| |
GadgetGuy
Super User
Joined: June 01 2008
Location: United States
Online Status: Offline
Posts: 942
|
| Posted: January 14 2023 at 10:57 | IP Logged
|
|
|
Dave-
I was hoping you might be able to comment on the question
above.
It is a mess to try and control an electronic appliance
when the only IR cmd is "Toggle Pwr". In fact it is
impossible.
Being able to sense its energy use value would be a
wonderful issue solver!
Woops I just realized I never included a URL to the
product (which I had intended to do) but just posted a
picture of it.
It's info is available at....
Smart-Plug/dp/B08LN3C7WK/ref=sr_1_17?
crid=O6Q91QAAK2PD&keywords=wifi%2Benergy%2Bmonitor%2Bfor%
2Ban%2Bappliance&qid=1671411249&sprefix=wifi%2Benergy%2Bm
onitor%2Bfor%2Ban%2Bappliance%2Caps%2C108&sr=8-
17&th=1">product description link
Edited by GadgetGuy - January 14 2023 at 11:01
__________________
Ken B - Live every day like it's your last. Eventually, you'll get it right!
|
| Back to Top |
|
| |
gg102
Senior Member
Joined: January 29 2013
Location: United States
Online Status: Offline
Posts: 245
|
| Posted: January 31 2023 at 15:23 | IP Logged
|
|
|
GadgetGuy,
Did you ever get your device to work?
I use Shelly devices, similar to the device you identified. I switched from X10 to these devices.
You can get them on Amazon.
https://www.amazon.com/Shelly-Plug-S/dp/B096W3ZZDD
This specific device doesn't dim. They can be controlled and report power usage and so much more. You can even
program a script into them. No hub or controller, just WiFi. I communicate with them using http directly to/from
PH. You can even have the device call a macro in PH if someone presses the button manually.
For example:
ph_geturl1("http://{SHELLY-ADDRESS}/rpc/Switch.GetStatus?id= 0",{SHELLY-METHOD},{SHELLY-TIMEOUT})
or
ph_geturl1("http://{SHELLY-ADDRESS}/relay/0?turn=off",{SH-UR L_METHOD},{SH-URL_TIMEOUT})
They support http and other protocols. If you're interested, let me know, I'll provide much more info.
|
| Back to Top |
|
| |
GadgetGuy
Super User
Joined: June 01 2008
Location: United States
Online Status: Offline
Posts: 942
|
| Posted: January 31 2023 at 15:46 | IP Logged
|
|
|
gg102-
My profound thanks. I have not found a solution so will
look forward to investigating your suggestion.
__________________
Ken B - Live every day like it's your last. Eventually, you'll get it right!
|
| Back to Top |
|
| |
gg102
Senior Member
Joined: January 29 2013
Location: United States
Online Status: Offline
Posts: 245
|
| Posted: January 31 2023 at 16:56 | IP Logged
|
|
|
Here's some random information.
I invite you to get one, then play with it. I'll be happy to offer whatever I know about it.
You can connect to it using WiFi, Bluetooth, MQTT, cloud, or sockets. I use WiFi because it's just easier and the range is great.
WiFi is blazing fast, reliable and you can debug stuff using a browser. (see below)
Here's my HVAC device.
You can talk to the device by using a browser going to its address: 192.168.x.y
You can look at the raw data also:
URL: http://192.168.x.y/rpc/Switch.GetStatus?id=%0
returns:
{"id":0, "source":"http", "output":true, "apower":9.3, "voltage":118.9, "current":0.140, "aenergy":{"total":222566.125,"by_minute":
[136.961,151.442,150.838],"minute_ts":1675205453},"temperature":{"tC":46.1, "tF":115.0}}
Here's an example if information I accumulate or extract:
Here's one way to extract the information. There's a limit to this method because PH only has 10 locals. (I wish it had more like 50 to make this easier) If the field you
want is beyond the 10th field, you need to use a different method. Here's a shot from my lame debugger:
If you want information past 10, you might use something like:
trim(mid(ph_regexdiff(".output", "[...]", ph_flattenjson(ph_geturl1("http://{SH-ADDR_HVAC}/rpc/Switch. GetStatus?id=0",{SH-URL_METHOD},{SH-URL_TIMEOUT}),",",0,0),1 ,0),2,10))
(Simple huh?)
(.output is actually in [local3] in this example, but you get the idea. In this example it would return 'true' )
There's just a ton of information.
I'm sure it seems overwhelming right now, but these are amazing devices.
(Well, there goes the rest of your day...)
|
| Back to Top |
|
| |
gg102
Senior Member
Joined: January 29 2013
Location: United States
Online Status: Offline
Posts: 245
|
| Posted: January 31 2023 at 17:22 | IP Logged
|
|
|
I forgot to say:
If you're anal about WEB devices like me, you can prevent the device from going on the WEB
by setting the device IP gateway to something invalid on your net like: 192.168.0.0 and DNS to the same and the device can't access the
interwebs. Thus it can't spy on your net. If you do, you can't use the cloud interface. Also, it's internal real time clock will
eventually run amuck. You can still run the device on your LAN just fine. That's what I do.
|
| Back to Top |
|
| |
MelanieEisenhau
Newbie
Joined: February 03 2023
Location: United States
Online Status: Offline
Posts: 1
|
| Posted: February 10 2023 at 04:54 | IP Logged
|
|
|
gg102 wrote:
I forgot to say:
If you're anal about WEB devices like me, you can prevent
the device from going on the WEBbby setting the device IP
gateway to something invalid on your net like: 192.168.0.0
and DNS to the same and the device can't access the
interwebs. Thus it can't spy on your net. If you do, you
can't use the cloud interface. Also, it's internal real
time clock will eventually run amuck. You can still and
this is how man moobs work run the device on your LAN just
fine. That's what I do.
|
|
|
You are right but there are some disadvantages in using
IP gateway for device.
Usually gateways on default are installed on the routers
itself. This makes it more difficult for the network
administrators to install/configure them. Apart from this
the cost involved in the implementation process is very
much high.
Configuration of devices through a gateway is made even
more difficult or impossible. There must be special
system administration for this purpose.
to-get-rid-of-gyno-aka-moobs-best-otc-supplements-for-
gynecomastia-news-238274">man moobs
Edited by MelanieEisenhau - February 20 2023 at 04:59
|
| Back to Top |
|
| |
gg102
Senior Member
Joined: January 29 2013
Location: United States
Online Status: Offline
Posts: 245
|
| Posted: February 10 2023 at 10:43 | IP Logged
|
|
|
Hi,
Your discussion is accurate for most IOT devices and new router configurations, but not for these Shelly devices. These are different.
These are "smart" devices. You have to configure them before you can use them.
As you point out, to configure a new router for example, you must go to the manufacturers WEB site to configure it. In my book, this is
spying your device and network. The manufacturer has your WAN address and your configuration. Using this method, however, does NOT
require an understanding of networks and technical configurations. Thus the "average person" can configure and use an IOT device without
having a technical background.
I do not use DHCP on my network. People who do use DHCP would, as you point out, get the default gateway and DNS as configured in their
router. Most routers have the ability to send a DHCP configuration using the MAC address to IOT or other devices using DHCP. If you set a
static DHCP address to a device, you must understand how LANs work. Again, you are correct, to do manual configurations requires semi-
advanced network understanding. Manufacturers now do this so a non-technical person can do limited configurations; enough to get the
device to connect.
These Shelly devices are different. You DO need a semi-technical understanding of your network to do a configuration.
Most programmers who program an IOT device should be able to handle this manual configuration.
Let me explain.
The Shelly devices come with a default Access Point and default WEB server build into every Shelly device. When you boot the device from
a factory reset starting point, that default AP is running.
So to start, it easiest use your smart phone. On your phone, go to "settings" and WiFi, you will see a WiFi network called "Shelly-
something-something". (something-something will the model of the device and the MAC address of the device.) Connect to that open
network. Then open a browser on your phone, and go to the default address '192.168.33.1'. That is the configuration site on the Shelly
device for that Shelly device. From there you can configure the Shelly device and its WiFi. You set the device to use your WiFi network
by selecting your network and setting a device IP address and all those parameters for your LAN. You can give the device a static address
and gateway. At this point, I have the Shelly device check for a firmware update and load if necessary.
After that, I set the gateway address to an invalid address. From this point, the Shelly device can't access the interwebs, only the
network you configured. (It's like setting up an IP camera on your LAN. The device is "smart" so you configure the device for your LAN,
then you can use it on your LAN.) I then turn off the default AP (optional), I turn off Bluetooth (optional) and other things. If I mess
something up, I can always do a "factory reset" and start over.
Once you save those configurations in the device, you can then access the Shelly device on your local network at the IP address you setup.
You can continue to set configurations, setup scripts or whatever.
From that point, you can set your Shelly device configurations, how it responds to inputs, default power on state, timers, sensors,
schedules or whatever. At any time, you can access the device at the LAN address you setup. When you turn off the default AP, the device
is ONLY on your network. No spying.
Shelly has a massively well documented WEB site for all of this technical information.
https://shelly-api-docs.shelly.cloud/gen1/#shelly-family-
overview
Feel free to ask me for more information or visit their site.
|
| Back to Top |
|
| |
TonyNo
Moderator Group
Joined: December 05 2001
Location: United States
Online Status: Offline
Posts: 2889
|
| Posted: February 13 2023 at 22:10 | IP Logged
|
|
|
Funny, they seem to have deleted the GPIO assignments for at least the RGBW2.
|
| Back to Top |
|
| |
gg102
Senior Member
Joined: January 29 2013
Location: United States
Online Status: Offline
Posts: 245
|
| Posted: February 21 2023 at 09:47 | IP Logged
|
|
|
My Frens,
I wanted to update you about the Shelly devices, and specifically this device. I have a lot of these things now, and I have
noticed that their firmware version 12.x has serious problems. Versions 11.x and 13.x are fine, but ANY version 12 is BAD.
They have several sub-versions of 12 and they are ALL bad! Version 12 reports power badly, falls off the WiFi network a lot
and has problems resetting and scripts can crash the device. There are a lot of other issues, but these are the most
severe.
My suggestion is, if you have any version 12.x get rid of it and update to version 13.x.
Version 13.x has a different user interface, and I don't like it, but at least it's stable.
|
| Back to Top |
|
| |
|
|
Active Topics 
Memberlist 
Search 
Help
Register 
Login
PowerHome Messageboard : PowerHome General
Topic: wifi Power Monitor support?
