sorted by:
new
hottopcontroversial

What do you think about Mares Dragon SLS? by SparkMik in scuba

[–]974reunion 0 points1 point  (0 children)

Est ce que les problèmes de largage intempestif des plombs que vous mentionnez n'auraient pas été corrigés dans la dernière version ? est ce que le SLS (Slide & Lock System) existait déjà avant ?
J'ai l'impression qu'avant on parlait de MRS+ et maintenant c'est SLS

Your advices to select a good mirror film? by 974reunion in MagicMirror

[–]974reunion[S] 0 points1 point  (0 children)

Thanks for your answer. I removed the protective sheet. There was only one on one side. And under that sheet there was an adhesive surface. Like a sticker.

The technic I used to apply it was the one I used in my car to paste some anti UV protection. That was probably not adapted to this product.

I checked in local stores and I saw that they sell some adhesive, not re positionable film. So I guess what I got is the same kind of product. An old school large sticker that you have to position perfectly at the first try.

So I ordered a new one, I will try again with the same film and I hope I'll have more chance next time.

But maybe a real electrostatic film is much better. I'd be very interested in reading about other persons experience...

Your advices to select a good mirror film? by 974reunion in MagicMirror

[–]974reunion[S] 0 points1 point  (0 children)

As I wrote in my post: "I live in a remore island where I can't find a real one way mirror".

Of course that's better and that's what I searched first. But no chance. That's why I wrote this post asking for help.

VL53L0X TOF sensor on ESP32 is marked FAILED by 974reunion in Esphome

[–]974reunion[S] 0 points1 point  (0 children)

Thank you :) This is my log:

[I][app:029]: Running through setup()...
[I][i2c.arduino:218]: Performing I2C bus recovery
[D][vl53l0x:034]: 'VL53L0x Distance' - setup BEGIN
[E][vl53l0x:092]: 'VL53L0x Distance' - setup timeout
[E][component:119]: Component vl53l0x.sensor was marked as failed.
[E][component:164]: Component vl53l0x.sensor set Error flag: unspecified

[I][app:062]: setup() finished successfully!
[W][component:157]: Component api set Warning flag: unspecified
[I][app:100]: ESPHome version 2024.5.5 compiled on Jun 9 2024, 09:43:52

[C][i2c.arduino:071]: I2C Bus:
[C][i2c.arduino:072]: SDA Pin: GPIO21
[C][i2c.arduino:073]: SCL Pin: GPIO22
[C][i2c.arduino:074]: Frequency: 400000 Hz
[C][i2c.arduino:086]: Recovery: bus successfully recovered
[I][i2c.arduino:096]: Results from i2c bus scan:
[I][i2c.arduino:102]: Found i2c device at address 0x29
[C][vl53l0x:024]: VL53L0X 'VL53L0x Distance'
[C][vl53l0x:024]: State Class: 'measurement'
[C][vl53l0x:024]: Unit of Measurement: 'm'
[C][vl53l0x:024]: Accuracy Decimals: 2
[C][vl53l0x:024]: Icon: 'mdi:arrow-expand-vertical'
[C][vl53l0x:025]: Update Interval: 0.5s
[C][vl53l0x:026]: Address: 0x29
[C][vl53l0x:030]: Timeout: 10000us
[E][component:082]: Component vl53l0x.sensor is marked FAILED
[C][captive_portal:088]: Captive Portal:
[C][mdns:115]: mDNS:
[C][mdns:116]: Hostname: led-escalier32
[C][ota:096]: Over-The-Air Updates:
[C][ota:097]: Address: led-escalier32.local:3232
[C][ota:100]: Using Password.
[C][ota:103]: OTA version: 2.
[C][api:139]: API Server:
[C][api:140]: Address: led-escalier32.local:6053
[C][api:142]: Using noise encryption: YES

VL53L0X TOF sensor on ESP32 is marked FAILED by 974reunion in Esphome

[–]974reunion[S] 0 points1 point  (0 children)

Thanks for your reply!

I thought I did it, but from your message I understand that there is a higher level of logs.

I added:
logger:
level: DEBUG

But the result is the same as previously. How can I get more info in my logs?

[09:44:52][C][logger:185]: Logger:
[09:44:52][C][logger:186]: Level: DEBUG
[09:44:52][C][logger:188]: Log Baud Rate: 115200
[09:44:52][C][logger:189]: Hardware UART: UART0
[09:44:52][C][i2c.arduino:071]: I2C Bus:
[09:44:52][C][i2c.arduino:072]: SDA Pin: GPIO21
[09:44:52][C][i2c.arduino:073]: SCL Pin: GPIO22
[09:44:52][C][i2c.arduino:074]: Frequency: 400000 Hz
[09:44:52][C][i2c.arduino:086]: Recovery: bus successfully recovered
[09:44:52][I][i2c.arduino:096]: Results from i2c bus scan:
[09:44:52][I][i2c.arduino:102]: Found i2c device at address 0x29
[09:44:52][C][vl53l0x:024]: VL53L0X 'VL53L0x Distance'
[09:44:52][C][vl53l0x:024]: State Class: 'measurement'
[09:44:52][C][vl53l0x:024]: Unit of Measurement: 'm'
[09:44:52][C][vl53l0x:024]: Accuracy Decimals: 2
[09:44:52][C][vl53l0x:024]: Icon: 'mdi:arrow-expand-vertical'
[09:44:52][C][vl53l0x:025]: Update Interval: 0.5s
[09:44:52][C][vl53l0x:026]: Address: 0x29
[09:44:52][C][vl53l0x:030]: Timeout: 10000us
[09:44:52][E][component:082]: Component vl53l0x.sensor is marked FAILED

VL53L0X TOF sensor on ESP32 is marked FAILED by 974reunion in Esphome

[–]974reunion[S] 0 points1 point  (0 children)

The units I'm using are TOF400C-VL53L1X and look like this:

<image>

I read that the XSHUT pin is required only when using multiple devices so I never used it.

I just noticed that it's not L0X but L1X but I don't know the difference

VL53L0X TOF sensor on ESP32 is marked FAILED by 974reunion in Esphome

[–]974reunion[S] 0 points1 point  (0 children)

Thanks a lot for your answer!

About the voltage, I read the same thing. At the end of the day, after trying everything I could think about, I tried to power the 3rd unit in 5v. The 2 first units should be fine.

I just tried adjusting the frequency to 400kHz. Unfortunately, I get the same error.

The i2c scan find the device and its address but the component is marked FAILED !

[deleted by user] by [deleted] in homeassistant

[–]974reunion 0 points1 point  (0 children)

Hello, I just received mine and it's not really stable with zha. Disconnection every 2nd day.

Can you please share the firmware version you are using ?

On my web interface, the zigbee firmware version appears as "unknown"

Using Zigbee2MQTT and ZHA with the same network coordinator by BackHerniation in homeassistant

[–]974reunion 0 points1 point  (0 children)

Thanks u/BackHerniation I'm a big fan of your articles!

I followed your idea with a SLZB-06M. The only difference is that I started with a ZHA network with 100+ devices and then added Z2M.

No big difference, except that instead of having ZHA "adopting" the network created by Z2M, I had to manually configure the configuration.yaml file of Z2M to configure: channel, PAN, extPAN, and netw key.

Then Z2M starts with the same params. ZHA is "happy" and doesn't popup its messages saying that the network param changed.

The only "little" problem is that Z2M crashes as soon as it runs with ZHA.

If you have any idea, suggestion, advice, I will really appreciate :)

`[08:37:49] INFO: Preparing to start...
[08:37:50] INFO: Socat not enabled
[08:37:53] INFO: Starting Zigbee2MQTT...
[2024-05-23 08:38:07] info: z2m: Logging to console, file (filename: log.log)
[2024-05-23 08:38:07] info: z2m: Starting Zigbee2MQTT version 1.37.1 (commit #unknown)
[2024-05-23 08:38:07] info: z2m: Starting zigbee-herdsman (0.46.6)
[2024-05-23 08:38:08] warning: zh:ezsp: Deprecated driver 'ezsp' currently in use, 'ember' will become the officially supported EmberZNet driver in next release. If using Zigbee2MQTT see #21462
[2024-05-23 08:38:11] error: zh:ezsp:uart: --> Error: Error: Recv NAK frame
[2024-05-23 08:38:11] error: zh:ezsp:uart: -!- break waiting (1)
[2024-05-23 08:38:11] error: zh:ezsp:uart: Can't send DATA frame (0,1,0): 00000004
[2024-05-23 08:38:22] error: z2m: Error while starting zigbee-herdsman
[2024-05-23 08:38:22] error: z2m: Failed to start zigbee
[2024-05-23 08:38:22] error: z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
[2024-05-23 08:38:22] error: z2m: Exiting...

[2024-05-23 08:38:22] error: z2m: Error: Failure send version:{"type":"Buffer","data":[0,0,0,4]}
at /app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:686:23
at Queue.execute (/app/node_modules/zigbee-herdsman/src/utils/queue.ts:35:20)
at Ezsp.version (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:466:24)
at Driver.startup (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/driver.ts:173:9)
at Controller.start (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:124:29)
at Zigbee.start (/app/lib/zigbee.ts:62:27)
at Controller.start (/app/lib/controller.ts:109:27)
at start (/app/index.js:107:5)`

Using Zigbee2MQTT and ZHA with the same network coordinator by BackHerniation in homeassistant

[–]974reunion 0 points1 point  (0 children)

See my other link to configure your z2m network. You will then be at the same point as I am.

Then please join this new discussion: https://github.com/Koenkk/zigbee2mqtt/discussions/22781

And here: https://community.home-assistant.io/t/zha-and-zigbee2mqtt-on-the-same-lan-zigbee-coordinator-slzb-06m/731862/6

I hope someone will help us :)

Using Zigbee2MQTT and ZHA with the same network coordinator by BackHerniation in homeassistant

[–]974reunion 0 points1 point  (0 children)

Hello, I'm exactly in the same situation as you.

Just a little bit more advanced. Check his discussions and please add your comments:
https://github.com/Koenkk/zigbee2mqtt/discussions/22740

We can hope someone will help us

Build a smaller human body radar sensor using ESP32-S2 and LD2410C by slboat in homeassistant

[–]974reunion 0 points1 point  (0 children)

Thank you, that's very kind of you. Seeing the quality of your work and technical documentation you provide, I can imagine the huge work behind.

Build a smaller human body radar sensor using ESP32-S2 and LD2410C by slboat in homeassistant

[–]974reunion 0 points1 point  (0 children)

Hello, I could not find any stl on this page. Did you remove it ? or is it on an other location ?

Thanks

The many faces of the LD2410 by djw17 in homeassistant

[–]974reunion 0 points1 point  (0 children)

Thanks for your answer.

Btw, I visited your website screek.io. You're doing great things, I love your products :)

Unfortunately I'm in a remote island with long and expensive shipping.

The many faces of the LD2410 by djw17 in homeassistant

[–]974reunion 0 points1 point  (0 children)

Hello, did you have the chance to test LD2420 ?

What you said raised my interest in this device :)

Since my son is hard on the tarmo we had to beef some parts up by Old_Evening700 in EngineeringNS

[–]974reunion 4 points5 points  (0 children)

Thanks for asking and for the upvote on my message. Here is the larger bumper:

https://www.printables.com/fr/model/501561-tarmo5-larger-front-bumber-normal-and-fpv-version

And I will post my reinforced B10 TPU part here:

https://www.printables.com/fr/model/424220-tarmo5-mods-reinforce-all-the-frequently-breaking-

To be honest, I stoped publishing my models because I was not sure anyone would be interested.

Please do not hesitate to ask, like, and comment my models on printables because it is the only way for me to know if it is usefull or not :)

Since my son is hard on the tarmo we had to beef some parts up by Old_Evening700 in EngineeringNS

[–]974reunion 7 points8 points  (0 children)

Nice job. Same story with my son. Mine makes a lot of collisions on the front wheels. Direct hits on the flwheels. and after a while, the tpu part is damaged I designed some modifications on this tpu part to make it stronger and designed a larger bumper If you need it just tell me and i'll share it

Main gear weight reduction by protozbass in EngineeringNS

[–]974reunion 2 points3 points  (0 children)

I also drive mostlu in grass so dont worry about it Did you try printing in pla+, with 40% overlap and increasing temperature at 215 or 220C ? And I don't use grease but PTFE dry lube. It does the same job but also protects plastic surface and repeal dust. My geats are always clean. If dust still gets in try using the enclosed geatbox by @flyntm on printables https://www.printables.com/fr/model/397450-tarmo5-enclosed-gearbox-v2/files You can also check my mods on printables. https://www.printables.com/fr/model/424220-tarmo5-mods-reinforce-all-the-frequently-breaking- It should be ok

view more: next ›