-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ERROR: ‘NoneType' object is not subscriptable #26
Comments
I've updated ic3 to 2.0.6c (or d) in the development directory. Waiting to set up stat. Zone doesn't place nice with the iOS app. New zones are not getting pushed to the iOS app so it then doesn't do any enter/exit triggers for the stat. zone. I'm now trying to create one around the home zone but get enter/exit triggers on a 1m zone passive zone for some strange reason. Download the development version. After loading and the devices are located, do a hard reset on the iOS app to load the zones if the stat. zone is not listed on the App Config/Locations for the iOS app. |
I've confirmed that the version I used for testing associated with this issue is the same as the latest: I've also confirmed that the stationary zone is not showing up in my iOS app, so that is likely the cause. I'm a bit weary of doing a hard reset which will delete my mobile_app integration and all of the associated devices. I believe I can just re-add and rename all of the entities again and everything should "just work". |
Working on 2.0.6d now. Ran into some things today and looking at them now. I'll be out running errands tomorrow and will give it a workout. You don't have to do a hard reset on the ios app on HA and delete the integration as you described.. On the iphone, open the app switcher (slide up fro the bottom) and push the ios app off the top of the screen to unload it from the iphone's memory. Then open the ios app again and it will reload the zones, which will include the newly setup stationary zone. |
I believe everything is working as intended. My status does go into a stationary zone, and exit from that zone. The only issue I see that on HA startup, the above error is thrown. |
I've uploaded iCloud3 v2.1 to the iCloud repository development v2.1 directory here. It's a prerelease that changes the Stationary Zone process. See the changelog.md file for more info. Let me know if you download it and have any problems. |
I've installed the new update. Here are my observations:
|
You had a devicename of maximus a while back. Is that the name that is getting the error or is it another one? What does your config parameters look like. The track devices statement changed a little to remove the sensor_name_prefix and add a friendly name. ic3 tries to figure out the friendly name using the devicename. A name on the track devices parameter line will override it. In your situation, it sounds like it isn't figuring out the friendly name from the devicename and none is specified. I'll some checks for that situation. and let you know when it is ready. |
I have just updated a new version of iCloud3 that fixes the Friendly Name problem. It had to do with no first name in the iCloud account record for the device in the non-2fa account and not making the friendly name from the devicename when the tracking method was FmF. It now does not look at the iCloud account contact name but always makes it from the devicename or the name specified on the track_devices parameter line. You should be all set with this new version. |
That did the trick, thanks Gary. I'd be curious how to set the friendly name using configuration parameters? Doesn't look like the docs are updated yet. |
I had been focusing on fmf tracking methods, nor iosapp. I'll look at that tomorrow.
Try `- maximus > maximus` where the maximus after the > is the name. I haven't updated docs yet but they are available [here](https://gcobb321.github.io/icloud3_docs/#/).
I'll let you know when I upload the next version. Be sure to try it with only the `- maximus` to make sure it works.
————————
Gary Cobb
…On Mar 13, 2020, 6:11 PM -0400, manonstreet ***@***.***>, wrote:
That did the trick, thanks Gary.
I'd be curious how to set the friendly name using configuration parameters? Doesn't look like the docs are updated yet.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Both options are now functional. Using just |
That's good that it's working now but what changes did you make to the config to eliminate the error. I'd like to duplicate it here so the problem doesn't happen to others going forward. In the mean time, I'll mess with the iosapp method to see if I spot anything. |
After you pushed the update related to the above comment, it started working without any configuration changes. I noted this with my comment: 'That did the trick'. Sorry if I wasn't clear. In your follow-up comment on how to override the friendly name, you asked me to try with just using Also to note, I do have 2FA enabled on my icloud account. However as far as I can tell, iCloud3 doesn't attempt to login to iCloud as I do not receive a 2FA notification. I prefer it this way, since I am only using the iosapp features and am not keen on disabling 2FA. The point is, since iCloud3 isn't logging in, it wasn't able to grab my first name. I suspect the fix you applied for FmF edge cases is what corrected my problem since you noted that:
Hopefully that clears things up! |
Version .107 is bringing some new errors with the latest build. On start I see the following:
NOTE: I tried reverting iCloud3 to the latest stable version of 2.05; however I still see these errors. |
The first error is occuring getting the radius of the Home zone, which defaults to 100m. Check Developer tools>States to see if there is a zone entity named Home and what the radius and location is. All of the other errors are the result of not setting up the Home zone within iCloud3 correctly. Have you set it up but called it another name? Get the latest development version from the |
This was actually a home assistant issue corrected in .107.1. None of my zones were loading correctly until I performed an update. I have re-redeployed 2.1rc4. All appears to be working. |
I’m using 2.0.6b to test out the new feature where the Stationary zone isn’t created until first use. However on Home Assistant start, iCloud3 throws the following error:
The text was updated successfully, but these errors were encountered: