Just FYI
I have 4 Mikrotik hAPs all connected DtD here in my radio room. One of them, a hAPac Lite, is for use in a go-box and I want to include a small video camera running MotionEye (MEYE) software and attaching via 2G WiFi. I've been doing something similar for years with 2 MEYE cameras with no issue. In this instance however, I got the "is not advertised" error in Aredn. It was briefly advertised and then disappeared from the mesh view. When the link was briefly visable, it pointed to "meye-622f92dd,local.mesh". If I attach my computer directly to the hAP with the camera via Ethernet, that link and/or the cameras IP address will quickly bring up the video. If I attach my computer to any of the other 3 hAPs in the "group", the IP address works but the "meye-622f92dd,local.mesh" brings up the following error message.
“This site can’t be reached
meye-b22f92dd.local.mesh’s server IP address could not be found.”
The camera IP is ping-able from any of the hAPs. There is a nearly identical camera setup on one of the other hAPS in the group that works fine from any location including the wider mesh. That hAP runs an older FW version. After a couple days of trying to figure this out, I reverted the FW on the new, go-box hAP to that of hAP with the working camera. After that, the go-box's camera works fine and is advertised, with no changes in the settings. An added benefit is my iperfspeed and MeshChat reappeared. The working FW version is 3.23.8.0 . These did not work 3.23.12.0 3.24.10.0 3.25.2.0 . I'm a little uncertain about 3.23.12.0 , as usual, I should take better notes.
Lee
kf7yrs
I have 4 Mikrotik hAPs all connected DtD here in my radio room. One of them, a hAPac Lite, is for use in a go-box and I want to include a small video camera running MotionEye (MEYE) software and attaching via 2G WiFi. I've been doing something similar for years with 2 MEYE cameras with no issue. In this instance however, I got the "is not advertised" error in Aredn. It was briefly advertised and then disappeared from the mesh view. When the link was briefly visable, it pointed to "meye-622f92dd,local.mesh". If I attach my computer directly to the hAP with the camera via Ethernet, that link and/or the cameras IP address will quickly bring up the video. If I attach my computer to any of the other 3 hAPs in the "group", the IP address works but the "meye-622f92dd,local.mesh" brings up the following error message.
“This site can’t be reached
meye-b22f92dd.local.mesh’s server IP address could not be found.”
The camera IP is ping-able from any of the hAPs. There is a nearly identical camera setup on one of the other hAPS in the group that works fine from any location including the wider mesh. That hAP runs an older FW version. After a couple days of trying to figure this out, I reverted the FW on the new, go-box hAP to that of hAP with the working camera. After that, the go-box's camera works fine and is advertised, with no changes in the settings. An added benefit is my iperfspeed and MeshChat reappeared. The working FW version is 3.23.8.0 . These did not work 3.23.12.0 3.24.10.0 3.25.2.0 . I'm a little uncertain about 3.23.12.0 , as usual, I should take better notes.
Lee
kf7yrs
File Attachment:
I have the following going on ... I have a remote camera on the network which is cabled to a switch where the DHCP is provided by a node running 3.24.10.0 firmware. That camera is sending RTSP over the larger AREDN network to my home location where I have a server. I found out that while AREDN requires a browser compatible codec to display video, the streaming video encoders built into the cameras tend to be lousy. So I have the camera send RTSP to a Linux server at my home running MotionEye and then MotionEye provides .mp4 out for others to connect to. The hAP that is providing DHCP to my home network which includes the Linux server is just changed to 3.25.2.0 and it's all working fine.
I don't understand your post. You say you have MotionEye installed on the camera itself? I didn't know that was even possible.
So I'm having no particular issue so far with 3.25.2.0 controlling a server running MotionEye. I'm not entirely clear exactly what is what on your site.
Ed
In my office there is a second hAPac Lite running older Aredn FW with an identical camera connected the identical way, and it is easily reached from the larger mesh by either the IP address or the assigned "name". When I switched the "problem hAP " to that older FW. the problem went away and everything works as it should.
I post this because others might have a similar problem and need a solution, albeit, not a great solution. We have about 5 of these identical cameras running 24/7 at various QTHs over the mesh. I'm concerned something might have changed in recent FW that causes this problem and no one has noticed. It is probably not an issue for most setups.
Thanks for reading the post(s) and any response. Again, this is posted to help others, and to report a possible issue with recent FW versions, at least at my house ;-)
Lee
kf7yrs
Orv W6BI
OK, MotionEye is on the Pi. I know nothing about RPi and only use X86 machines. I do know that MotionEye did not like me trying to add a USB camera to the box it was running on, so I only use IP cameras at this time. Others have figured out how to do USB cameras, ok.
But the pictures show some strange ribbon cable from the camera/chip/module thingy to the RPi. What protocol? That is wild ... and I have no idea how to help at all.
Ed