The first time you plug in the dongle, it is on an old firmware. After setting your wifi in the dongle, it should update within half an hour with the new firmware. The new firmware enables the api that I use in the code.
I'm trying this out since Fluvius installed a digital meter a few days ago en today my dongle arrived.
It's kinda working...
It gets all the data of the dongle but it doesn't seems to refresh itself.
If I hit 'refresh' (in hubitat devices), it refresh a few times but then stops refreshing.
anything i could do (or not) to make it refresh itself?
to be clear * wifi_strength : 98
Thx for the respond @fanmanrules
I'm looking forward on that update... meanwhile i will try the basic rule hint you gave
I did notice in my device history I saw * commStatus : **error**
maybe also worth mentioning.
Sorry for the newby question, but this device is my first WiFi device I will be adding to my Hubitat.... but can you please give me the basic steps to add the P1 wizard, because for the life of me I cannot figure it out.
Go to your devices pane > New device.
Select "virtual".
Enter the name you want your device to have, and set the driver to the P1 driver.
Save device.
Now goto the divice, and it should have several input fields. You need to enter IP adress, etc.
REMEMBER to switch on the API in the app vor your P1 device, als you will not get data from it.
Thanks, for the info... I had actually figured it out late last night myself using a manual of a diff. WiFi based device. I love the flexibility of the Hubitat and the fact there is no cloud dependency, but documentation can be improved. Luckily the community kicks butt also.... Thanks for developing the driver. When I get around to it, I think it will also be a nice starting point for me to dev something for my WLed system. I am seeing a lot of (conceptual) overlap with your driver.
Figured I might just pop in as I just created a pull request which adds use of the "power" attribute to the driver (conforming to the PowerMeter capability).
when you use the "power" attribute, you can select "PowerMeter" as triggering events (and use the device easily in dashboarding) as opposed to selecting a custom attribute.