search

blockchainsllc / usn-mvp

Alpha testers program for the Slock App minimum viable product.
GNU General Public License v3.0
11 stars 5 forks source link

Mapping a slock to my Pi Provider does not work #9

Open jganivet opened 6 years ago

jganivet commented 6 years ago

Hello,

I'm trying to connect a slock I created with my Pi Provider linked to a tp-link HS100 Smart Plug

I'm running:

Story details... sorry it will be a bit long Steps:

  1. Follow the wiki to have my Pi connected to the USN => OK
  2. Link Smart Object : TPLink Switch
  3. Enter details => put the wrong host (pi IP adress instead of tplink IP)
  4. Save => Of course it does not work
  5. As it is not possible to modify the config of the Smart Plug, I create another one
  6. Enter correct details => everything is OK my pi recognizes the SmartPlug
  7. Going into swtich details, I can see it is connected and I can check the status as off (which is correct)
  8. Then I want to assign a slock, but first I need to create one
  9. selecting coffeeMachine and entering all required data => slock creation is OK, need to assign a device
  10. Going back to Pi Providers and selecting my smartplug (the good one)
  11. Trying Assign a slock by selecting my coffeeMachine
  12. It's doing things until step 'Pi Provider is mapping the device...' and ends up with error message saying the user is not allowed to update the device as it is currently rented

Hope you will be able to reproduce the issue. I attach all relevant screenshots

One more remark: When creating my coffeeMachine slock I put a price of 2.63 mKETH/min After the mapping fails, going back to my slock, the price has changed to 157.7 mKETH Why is that? Is it linked to the below error?

Regards, Jean-Yves

screenshot_20180403-202801__01 screenshot_20180404-211030 screenshot_20180404-210032 screenshot_20180404-204322 screenshot_20180404-211245 screenshot_20180404-210823

nomoreboredom commented 6 years ago

Hi Jean-Yves,

Thanks a lot for your issue and your detailed explanation.

We will investigate the first problem, the second bug you have mentioned with changing the price is already fixed, but not released yet.

I will check the logs for updating the slock for the account (0x0247DB4Ab9037B8797FE5B4514d593F01250De54) and let you know.