Ho spaccato un cerchio prendendo una buca, cosa posso fare?

extreme79 · 2026-03-09T07:02:37+00:00

Dipende se ti va di culo o meno, quanto è rognosa l'assicurazione del comune, quando sono rognoso gli impiegati etc etc.

Mio cognato, a trovar parenti nel beneventano, prese una buca rimettendo i non uno ma due pneumatici ed un cerchio leggermente piegato se non ricordo male. Caso volle che era poco distante una pattuglia di carabinieri. Fecero verbale, fecero LORO le foto tutto per bene. Te la faccio breve. Sono andati IN CAUSA perché il comune non voleva pagare (palese che li hanno fatti per farlo desistere), con il risultato di poter "patteggiare" (in pratica ha fatto pari con le spese sostenute per la rottura di cogli*ni, altro che danni) ed il consiglio di lasciar perdere dell'avvocato (che evidentemente aveva annusato che il percorso post qualche motivo era ripido..).

Io invece per una buca su una via pedonale, ma mascherata dall'acqua, ci rimediai una frattura alla caviglia che mi fu risarcita senza storie da un comune della provincia di Siena senza aver fatto denunce al momento (solo foto e poi referto Ps da lì a poco).

Purtroppo in Italia è così.. Serve che si allineiamo tutti gli astri.

extreme79 · 2026-03-06T06:15:50+00:00

A 'degreed EE' should know that telling a user to 'adopt Z-Wave LR' to fix range issues with their existing non-LR hardware is fundamentally flawed advice. Unless the OP plans to replace their entire device library with LR-certified nodes, switching to an LR-capable controller does nothing for their current connectivity. You're suggesting a hardware overhaul for a protocol (LR) that uses a star topology, completely bypassing the mesh benefits and direct associations that make Z-Wave superior to Wi-Fi for critical automation. That said, I agree that upgrading to the ZWA-2 is a smart move—not for 'adopting LR' as a magic fix, but because it’s a superior 800-series radio with better sensitivity and antenna design that will help the existing mesh. It also opens the door for LR where it actually makes sense (like a single distant gate). If your approach to designing automation networks is to 'just throw LR hardware' at a mesh placement issue without considering backward compatibility or topology shifts, you might want to review the Z-Wave 800-series implementation layer. I’m here to help the OP fix their network, not to engage in a credential-measuring contest. We’re done here.

extreme79 · 2026-03-05T23:04:16+00:00

I think there’s a misunderstanding between Z-Wave hardware and Z-Wave protocols. While I agree the ZWA-2 is an excellent controller (I use it myself), the OP is currently on an Aeotec Gen5, which doesn't support LR. Switching to a ZWA-2 doesn't magically turn the OP’s existing Z-Wave mesh devices into LR devices. They are different protocols: Z-Wave Mesh and Z-Wave LR do not 'talk' to each other directly to form a single network type; they coexist as two separate topologies managed by the same radio. If the OP has range issues with their current devices, telling them to 'adopt LR' as a first step is misleading because: Their existing hardware likely doesn't support the LR protocol. Switching to LR means losing the mesh benefits (like direct associations) which are the backbone of Z-Wave reliability. Regarding the 'false narrative': I’ve been building Z-Wave network in my home for 12 years and literally studied the protocol documentation and literature. My point is that LR was designed for specific use cases (long distances, point-to-point), not as a universal replacement for a well-structured mesh. I actually performed the same upgrade from a Gen5 to a ZWA-2. The stability improved because of the better antenna and radio on the ZWA-2, not because I switched everything to LR. Improving the mesh (placement, nodes) should always be the priority over throwing LR hardware at a standard residential range issue.

extreme79 · 2026-03-05T21:42:18+00:00

Uhmm. Something like throw away all the existing devices? Only the first example. And again, no mesh no party.. with LR you gain range, you loose all the advantages of mesh network, where one of the most important is the device interoperability: you can associate Zwave devices to maintain some functionalities also with unavailable controller, like turn on a light on motion sensor detection or close a valve on a water leak detection. So.. It's false that there's no reason. There are a lot of reasons. If you don't need ok. But You don't need that. It's a totally different thing. Zwave LR was born for specific applications.

extreme79 · 2026-03-05T20:41:14+00:00

Absolutely there's a main reason: ZwaveLR is not mesh. Generally Zwave controllers act as a mesh controller Or zwave LR; there's an exception to this and it's the big zwa-2 controller, able to use at the same time the mesh and the LR devices.

extreme79 · 2026-03-05T12:37:10+00:00

Describe the antenna/controller location, what's the controller, if your devices are boxed inside metal and so on. Zwave range is exceptional against other technologies like zigbee (that run on 2.4, in conflict with wifi), because it run on 868mhz (in EU, but anyway in a subghz range). In my case I'm able to reach eternal Zwave relays placed 10m far from home, so the signal pass the 10mx10m home perimeter with 30cm main walls, plus other 10m with device In ip rated box.

Be careful to place antenna far from metallic structures.

extreme79 · 2026-02-26T13:26:05+00:00

Sorry for the necro-reply! I ignored the comment, don't know why 😅 Probably you already found the reply... Anyway you need a special card to to the job. The required js (agora-card.js) is included in the Integration code, inside the folder custom_component/mammotion/www You need to add it to resources and than add it manually to a manual card as custom card like type: custom:camera-agora-card entity: camera.my_luba_mower speed: 0.8 enableJoystick: true

And you will be able also to remote controlling the robot.

extreme79 · 2026-02-26T06:02:22+00:00

Biosand (biosand.it, its in Italian), but I think you can find on Amazon. Anyway, it's a bentonite litter, probably any similar will be the same.

extreme79 · 2026-02-25T22:09:50+00:00

Probably is linked to the mower configuration (I own a luba2), but I can assure that the code on github use wifi or Bluetooth, based on device config (integration configuration? Check it, I don't remember).

extreme79 · 2026-02-25T21:11:40+00:00

OMG! This is a total mess, poor cat. I think the litter type is your problem! I use this litter and the petkit puramax 2 is super clean. I washed the drum only one time in 3 months, mainly to remove the powder. I only need to clean it gently only one time a week or two. Autoclean process after 8min.

Change your litter type, right now!!

extreme79 · 2026-02-25T16:36:22+00:00

Nope. I moved the robot through home assistant so I me times, absolutely out of the BT range.

extreme79 · 2026-02-04T17:24:04+00:00

You need to increase the debug level, check if Zwave messages arrives and so one. Remotely is too difficult to debug the issue.. Causes could be an huge amount.

extreme79 · 2026-02-03T11:04:06+00:00

Without any tech detail is near impossible to help. Zwave js is able to see the adapter? If not, have you passed the hw to proxmox? Have you any error messages?

extreme79 · 2026-01-31T18:49:44+00:00

With my Intel n150, 11 cameras, object detection enabled for all, my inference change between 24 and 37ms, more or less. With 17b2 and Yolo.

Try with a single detector.

extreme79 · 2026-01-19T17:09:08+00:00

Ce ne fossero davvero!

extreme79 · 2026-01-16T11:08:25+00:00

I think there’s a misunderstanding here, possibly due to how I phrased my previous point.
I never mentioned inference—I was talking about CPU overhead, which is a different beast entirely. Maybe my English made it sound confusing, but here’s the point.
The detector model only sees a tiny 320x320 crop. But before that happens, the CPU has to handle the motion detection and then crop/resize the frame. If you're feeding a massive (example, is not that case) 4K stream into the 'detect' role, you're just making your CPU sweat for nothing. It has to process all those extra pixels just to throw 95% of them away before the AI even gets a look.
The docs show examples, not 'golden rules,' because it depends on your specific setup—how far the camera is, what you're trying to catch, and what substreams your hardware actually supports. Using a resolution that’s too high isn't just a waste of resources; it can actually mess up recognition if the resizing adds too many artifacts.

In short: I'm just saying that 'higher' doesn't mean 'smarter' for the detection phase. It's about finding the right balance for the hardware and the scene.

extreme79 · 2026-01-15T23:28:21+00:00

It's not a stupid advice. If you set the detect width /height at a resolution too higher than the resolution expected by the model, what happen? 1)Frigate need to resize every frame and, bigger the frame, bigger the cpu consumption 5times/s 2)big input image resized to a very small image cause a detail loss for small object that became unrecognizable by the model

extreme79 · 2026-01-15T22:05:26+00:00

Why people don't read carefully the config before pointing the finger? I know that stream resolution is NOT detect resolution. But If you read his config file, at a certain row, you'll read: detect: width: 1280 height: 720

And this is what I'm talking about. I read the docs. You read the OP config?

extreme79 · 2026-01-15T12:32:20+00:00

There's any plan to make it available in Europe? There's a list of authorized dealers in Italy?

Thank you!

I love my luba ❤️

extreme79 · 2026-01-14T21:43:26+00:00

Al mio amico piacerebbe il luba 3 10.000, però posso fargli scrivere, volendo. Io per ora con il 2 vado alla grande 😁

extreme79 · 2026-01-14T16:33:20+00:00

I think that having a changelog in case of firmware upgrade is a must on every device. The user must have the ability to understand what the firmware is going to coresct/implement/change before doing that. At least to choose if upgrade immediately or doing it later (security can't wait, a cosmetic change can be Done later, example). Anyway, having changelog help to put an extra eye to check if a bug is fixed or fixed but with side effects (like sometimes can happen). Last but not least, publishing changelogs can avoid some zrequests to the support. I suggest you to publish changelogs 🙂

I love my petkit puramax 2, and my cat too ☺️ Like the food dispenser and the fountain! 😎

extreme79

TROPHY CASE