Raspberry π

No, I can't SSH either (using admin). It's occasionally connecting to a time server so must be doing something but I don't know beyond that.

Thanks I'll try all that in a bit.

Just checking... Have you done the wpa_supplicant.conf stuff as part of the set-up?
https://github.com/ccrisan/motioneyeos/wiki/Wifi-Preconfiguration

If it's connecting to a time server I assume WiFi is working ok.

Yep, it's on the network.

Just found a HDMI cable with a weird sized end, sadly it seems it's micro rather than mini. Need to keep hunting.

Did you use balena etcher to write the SD? If not, do. Motioneyeos images can be a bit weird if you use other image writers.

I know it sounds unlikely, I didn't believe it myself.

I tried both these ammemds on just the tweet step using yesterday's 5into15.mp4 but it failed without confirming the video was uploaded so presume it is an error in the video.

I did a new timelapse using the old script to create a new and it worked again (although I had to confirm it could overwrite the mp4 as I hadn't removed it) - also it is upside down & half obscured as I wasn't thinking when setting it up. https://twitter.com/5into15/status/1382727672963461121?s=19

I'll ammend that to add in the response confirmation line as it'll be useful to have as well as the time checks at each step.

I guess the encoding of the video to h264 might be the problem point still?

1 Attachment

Wondering if I might be limited to one video per 24h also due to hammering it in my early tests?

Done using balena etcher. Finally found a cable and everything seems fine. All I'm meant to be doing here is typing 192.168.2.230 in a web browser aren't I?

There are definitely limits on the Twitter API and it could definitely be causing what you are seeing.

https://developer.twitter.com/en/docs/rate-limits

https://developer.twitter.com/en/docs/twitter-api/v1/rate-limits

This might be useful? Ended up there after reading this:
https://stackoverflow.com/questions/7835067/twitter-api-always-saying-400-bad-request

Toooooo sloooooow

All I'm meant to be doing here is typing 192.168.2.230 in a web browser aren't I?

Yup. Are you trying from a LAN cabled machine on a different subnet? If so, try from another wifi device

& @yoshy ta, hadn't found that on previous searches. I'm sure it should be only 1 request per run of the script though?

P.s. Hoping this one works...

1 Attachment

On numbers of requests:

Please note

Users' rate limits are shared across all apps that they have authorized and the Twitter application. For example, if a specific user likes 20 Tweets on the Twitter mobile application and likes 20 Tweets on a third-party application within a 24 hour period of time, the 40 requests would pull out of the same per user rate limit bucket. That means that if this endpoint has a user rate limit of 1,000 requests per 24 hours, then this user would be able to like 960 more Tweets within that 24 hour period of time across all Twitter and third-party apps.

I don't know how relevant this is to you, way out of my depth in Web stuff here! Mersey looking lovely though, fingers crossed for successful upload

Hmm...

You can only post 300 Tweets or Retweets during a 3 hour period.

It shouldn't be that then unless my code is ticking the counter up by a huge number somehow?

It says elsewhere the error would be code 429 not 400 if a rate is exceeded too?

Either way the latest one just worked so that's a result.

https://twitter.com/5into15/status/1382759906827251717?s=19

One other thing might be a consequence of if the wifi connection drops at any point during the process or if my ssh connection becomes disconnected?

As I'm using mobile hotspot whilst out I was careful on todays to keep my phone close to the pi at all times and to look at the progress on juicessh frequently.

Ta. This is 1 user account not browsing searching following messaging or blocking so technically not hammering it at all?

Mersey looking lovely though, fingers crossed for successful upload

It was at it's best. The pi camera didn't handle the light so well but I got a few nice mobile phone pics.

Tried a few different machines and some are definitely on the same subnet.

Sometimes run into issues with things that don't like the multiple APs and SSIDs on the network but haven't had that issue with a pi before.

Check the pi MAC address against other Pi MAC addresses on the network (even on different subnets).

They may not be unique, and router hate that.

You can also check on the pi which ports are open and from another machine where there are open ports on your network.

I'll dig up the commands when I have access to my desktop.

Wasn;t it the case at some point that if you wanted ssh enabled you had to write a .ssh file or somesuch to the SD card after flashing it? Which version of motioneyeos is it? I have never known the http stuff not come up though? What about if you go to http://whateverAddress:8765?

On Raspibian, you need a file called ssh on the boot partition. Not sure abouy motioneyeOS.

The logging up there shows that sshd is up and running though.

There's 512mb file limit too, but I doubt you're hitting that.

I'd be retrying the failed files to see if it's an intermittent error (indicating and issue with the upload process) or constant (indicating an error with the file itself).

Once a file hasn't tweeted I've been unable to get it to tweet later by running the tweet step only (tweet2.py in my earlier screenshot). Maybe this means problem in the file? If the pi->phone hotspot or ssh connection is lost at any point could that cause it? It seems the only possible remaining explanation.

Fwiw: This is the one that didn't tweet yesterday I renamed it lake.mp4 once I'd scp'd it to the pi400 at home.

1 Attachment

• lake.mp4

The same Pi connects when I'm running Volumio. That is connecting to a different SSID though which I guess may be confusing things.

Maybe I'll have motioneye set up on that SSID to see whether that makes a difference.

It's whatever the latest version is for the Pi Zero.