Home Nasty Local Spectacular

Home Nasty Local Spectacular

This article tagged under:
Hollywood Hills AirBnB

Copyright © 2022 NBCUniversal Media, LLC. All rights reserved

Follow Us

Facebook

Twitter

Instagram

Families in affluent Hollywood Hills are angry people are openly drinking and having sex on a campsite that has opened in their community.
Advertised through the Airbnb website, it is advertised as a "camping retreat," but sits in middle of a multimillion dollar neighborhood. For the cost of $40 per night people get a tent, spectacular views and are within short walking distance of the Hollywood sign.
However people living in the well-heeled locale are unhappy at the way renters are behaving during their stays, with fornication and other undesirable behavior taking place within view of the surrounding mansions.
"People (are) buck naked, people doing sex out in the open. Drinking," resident and father Sanjeeb Kumar said. "(Happening on) our own backyard, it's scary. (We are) scared to come out."
"I think it's really hard when a lot of us have children and we are driving by and the kids see strange things and ask, 'Why is that going on there?'" a fellow neighbor said.
There are also concerns that an uncontrollable fire could be sparked as campers have been seen smoking, even though a sign in front of the property, which is surrounded by dry brush, says it is not allowed.
"We have a major drought situation, that could take the whole hillside and take the houses with it," a resident said.
Get Los Angeles's latest local news on crime, entertainment, weather, schools, COVID, cost of living and more. Here's your go-to source for today's LA news.
Two tents were pitched when NBC4 visited the site Wednesday. The person living in the house next to the campsite called police rather than respond to requests for a comment. According to the campsite listing campers can use the mansion's bathrooms during their stay.
Neighbors are hoping to have the campsite closed down, and are working to have the city check for any possible zoning violations.

When autocomplete results are available use up and down arrows to review and enter to select. Touch device users, explore by touch or with swipe gestures.
Deep forest green with dusky teal and gold...great for a living room, using velvets and brass...can you picture it?

Proudly powered by WordPress | Theme: Spectacular Magazine | By ThemeSpiral.com.
Your source for event, sports, culture, and entertainment news
RALEIGH, NC – North Carolina-raised, Grammy Award-winning, and multi-platinum hip-hop artist J. Cole and his … Read More
NEW YORK, NY – BET has announced three-time GRAMMY® award-winning singer-songwriter and producer Maxwell will receive … Read More
ATLANTA, GA – Atlanta Black Gay Pride, the country’s leading LGBTQ+ annual pride marked its 25th-year … Read More

Absolute beginners guide to setting up Local Tuya for Home Assistant
Home Assistant is open source home automation that puts local control and privacy first. Powered by a worldwide community of tinkerers and DIY enthusiasts. Perfect to run on a Raspberry Pi or a local server. Available for free at home-assistant.io
I recently dove into HA, having migrated across from the Smartthings ecosystem, and as many others before me, I wanted to remove dependence on the cloud as much as possible, as well as fix the slow response you often get with Tuya devices integrated to HA via the Tuya cloud. In doing this, I found setting up Local Tuya painful, mainly due to the information on how to do it – although readily available, it is disjointed and all over the place. It often assumes you have a certain level of understanding on how all of this hangs together and if you don’t, you end up spending days trying to work it out, which is what I had to do. All the steps involved are captured in many different places, some in git hub, some on YouTube, others in HA discussion boards, but I found no resources describing the process end to end.
This guide assumes you have a Windows PC, a working Home Assistant setup, know how to type, install applications, and follow instructions. This is what worked for me, so I thought I’d note it all down while fresh in my mind, in the hope it saves someone from pulling their hair out.
SET UP UBUNTU VIRTUAL MACHINE IN WINDOWS
On your Windows PC, set up a Virtual machine running Ubuntu.
1.1. Download Ubuntu Desktop image from: https://ubuntu.com/download/desktop
1.2. Download VirtualBox from: https://www.virtualbox.org/wiki/Downloads (click on “Windows hosts”)
1.3. Install Virtual Box and create a Virual Machine using the Ubuntu Image downloaded earlier. It’s a relatively straight forward process, I could work it out just by following the wizard in the app, but if you’re having trouble, here is a guide: https://brb.nci.nih.gov/seqtools/installUbuntu.html
1.4. Once configured, boot up your Ubuntu virtual machine and ensure you’re logged in and can see the desktop.
1.5. Next, you need to install install “npm”
1.5.1.On your Ubuntu VM right click on the Desktop and click “Open in Terminal”
1.5.2.Update your Ubuntu repository first by typing below command in terminal and hit enter:
You will be asked for the user password, type it in and hit enter.
1.5.3.Install Node JS by typing the below command
1.5.4.Install npm (node package manager) by typing the following command:
1.6. Install Tuya command line interface (cli) with below command:
GET THE TUYA API KEY AND LOCAL KEYS FOR TUYA DEVICES
2. Obtain the Tuya Api key and local keys for your devices. Information below is from https://github.com/codetheweb/tuyapi/blob/master/docs/SETUP.md
2.1. Ensure your devices are connected to either Smart Life or Tuya app and working as expected.
2.2. Create a new account on iot.tuya.com and make sure you are logged in. Select United States as your country when signing up. This seems to skip a required verify step.
2.3. Go to Cloud -> Projects in the left nav drawer. If you haven't already, you will need to "purchase" the Trial Plan before you can proceed with this step. You will not have to add any form of payment, and the purchase is of no charge.
2.4. Once in the Projects tab, click "Create". Make sure you select "Smart Home" for the "Industry" field and PaaS for the development method. Select your country of use in the for the location access option, and feel free to skip the services option in the next window.
2.5. After you've created a new project, click into it. The access ID and access key are the values needed in step 2.9.
2.6. Go to Cloud > Projects> "MyProject" > API > "Go to authorize". "Select API" > click subscribe on "Smart Home Devices Management" in the dropdown. Click subscribe again. Click "basic edition" and "buy now" (basic edition is free). Check if the "Smart Home Devices Management" API is listed under Cloud > Projects > "MyProject" > API. If not, click "New Authorization" and select it.
2.7. Go to Cloud -> Project and click the project you created earlier. Then click "Link Device". Click the "Link Devices by App Account" tab.
2.8. Click "Add App Account" and scan the QR code from your smart phone/tablet app by going to the 'Me' tab in the app, and tapping a QR code / Scan button in the upper right.
2.9. Back on your Ubuntu Virtual Box, on the command line, type the below command:
It will prompt you for required information (step 2.5), and will then list out all your device names, IDs, and keys for use with TuyAPI. This is the information you need to set up your devices on Local Tuya.
INSTALL LOCAL TUYA ON HOME ASSISTANT
3. Install Local Tuya on Home Assistant
3.1. Navigate to your Home Assistant UI and open HACS (Home Assistant Community Store) from the left-hand side navigation menu. If you haven’t set up HACS, this is how you do it: https://hacs.xyz/docs/installation/prerequisites/
3.2. Click on “Integrations” and search for “Local Tuya”.
3.3. Click on “Install” on the Local Tuya tile in the search results and let it complete.
4. Connect your devices to Home Assistant using Tuya Local
4.1. In the Home Assistant UI, Click on “Configuration”
4.3. Disable your regular Tuya integration if already connected.
4.4. Click on “+ ADD INTEGRATION” in the bottom right hand side corner.
4.5. Type “LocalTuya” and click on the corresponding result.
4.6. A screen will pop up with a drop-down box called “Discovered Device” when you expand the drop down, you will see all your connected devices and their device IDs. Click the top result and click Submit
4.7. Enter a name for you device and the Local Key from step 2.9 corresponding to the device ID detected. Click Submit.
4.8. “Entity type selection” pop will appear with a Platform drop down box. Expand the drop-down and select the platform. Let’s use “Light” in this example. Click Submit
4.9. The next screen lets you select and set up all the options for your device. In the case of a light you can chose ID, Friendly name, brightness, color etc. This took a bit of trial and error to work out, I had to repeat the process a few times, but when first setting these up I recommend only setting up “ID” – chose the first option in the drop down, and giving it a friendly name, so you can tell what it is when testing. This will give you basic on/off functionality for your light, and once you’ve tested and confirmed this as working, you can go back and try the other settings, like color temperature, brightness, color, etc.
4.11. If the device doesn’t have multiple entities, ensure the appropriate check box is ticked in the next pop up window and click Submit. If the device has other entities, like for example a ceiling fan that has a Fan and a Light entity, uncheck the box and select the correct entity type, then click submit and repeat the process.
4.12. The device should now be added to your Home Assistant and you can do some testing to ensure it works as expected. I created a separate page in my dashboard and added all the Local Tuya entities so I can easily access them for testing.
Just a heads up, HA/Tuya just announced a partnership where Tuya is will be developing their own HA integration that will eventually include local control. https://github.com/tuya/tuya-home-assistant
I’ve found that LocalTuya works for basic devices/switches but when you get into things like energy monitoring it’s horrendously inconsistent.
I’m holding off for this reason, I recently got plugs with energy monitoring and would like to get it into HA.
Btw, I've been using Local Tuya since the beginning for better response times and control of devices and it worked pretty nicely for what it worked on, I couldn't get any sensors and the energy monitoring was really inconsistent. It's great for lights, switches and automating between different manufacturers (Tuya switch turns Yeelight on), while the original integration takes as long as 10 minutes to refresh status.
This week I've been trying Tuya v2 through HACS and it's way better than the current integration. The delay is almost as good as local with not even half the work and more devices are supported , not to mention the power readings can finally be trusted:
In short, the OP made the best guide I've seen for Local Tuya, but if it's too much work for you, check out the Tuya V2 that will eventually become the default in HA and promised Local support: https://github.com/tuya/tuya-home-assistant
Last year I wanted to use it with an air conditioner but found that wasn't supported (though I could control it with the cli). It looks like it still isn't supported sadly.
This would be spectacular. Local control, and large company backing. I will buy into this if it happens.
That's the main reason I haven't used Local Tuya at all, the guides didn't look very straightforward. This post, on the other hand, makes it seem a lot less daunting. I may give it a shot soon. Thanks for posting it!
We're a different breed when 30+ steps is "a lot less daunting"
I'm super new to home assistant and managed to get this working pretty easy
My biggest issue was getting those local Device IDs. The native guide in Git hub essentially says "All methods below require you to install the CLI tool before proceeding. Install it by running npm i u/tuyapi /cli -g".
Where? First I thought that was in HA, that didn't work. Next i thought to try the Ubuntu terminal, so i set up the VM. Then i kept getting error npm not found. So where to now? I found what npm is and how to install it on a completely unrelated Linux website, nothing to do with home automation.
I realise its a lot of steps. Many of them are basic and self explanatory, but help paint the whole picture, which imho is the missing piece for a lot of people trying to embark on this.
The only Tuya device I have is a kettle which I love but I thought it was cheap and nasty, got it from Kmart, which in Australia is known for cheap stuff not quality. What’s the rest of their offer like? Their app looks to have 1000s of products available across a wide range of smart home tech.
Also your underlying premise that guides expect a certain level of base knowledge and understanding are what makes it so difficult sometimes. I am not planning on migrating to HomeAssistant anymore but this guide looks great and have to thank people like yourself that take the time to put something like this together to help someone else avoid the struggle you went through, it’s a great community (most of the time)
The only Tuya device I have is a kettle which I love but I thought it was cheap and nasty, got it from Kmart, which in Australia is known for cheap stuff not quality. What’s the rest of their offer like? Their app looks to have 1000s of products available across a wide range of smart home tech.
I'm also in Australia and while I don't have any Kmart Tuya compatible items, I have around 30 from Bunnings (Arlec light bulbs, Arlec ceiling fan, Deta light fixtures / switches), all of which have given me no trouble in either Smartthings, or now in Home Assistant. Only reason to switch to Local Tuya was to get as much of my home automation working without having access to the internet. Thanks for your feedback too mate, much appreciated.
Nice guide, but it's possible to do it directly on windows. Just install nodejs and then open a windows command prompt (either cmd or powershell), you should have access to npm.
Thanks Yromal, thats great to know! It would have been even better to know 3 days ago, which is the point I was making. Having information like this available in the same place would have saved me so much stuffing around.
The noob that I am, I saw Linux commands, so off I went and install Linux...
A bit of advise as someone who has started this process but couldn't finish it in one go, consider using a password manager to save your local keys so you don't have to keep revisiting iot.tuya.com. I found that process to be rather tedious and did not want to go through it repeatedly, as I knew I would have to due to time limitations. Plus it made copy/paste hella easy for each entry and device identification.
I just saved a document with the key information and everything else you get in the Tuya website. That local key will still be good unless you delete the device from the Tuya app and reinstall - you then have to get another key.
For someone that did this over a period of time, how did you add more devices after the first go? I can't seem to add more a few days later.
For setting up local Tuya, I found Mark Watt Tech's video very helpful. You can almost set up local Tuya at the same pace he does in the video.
There's a good written one here too:
I found Mark's video very good and used it for my first two local Tuya set-ups.

Lingerie Bowl
Erolanta Lingerie
Naked Mary

Home Nasty Local Spectacular

Report Page