paf @ paf @jlai.lu

Posts

12

Comments

150

Joined

2 yr. ago

Even if it looks well sealed, it still could be humidity and popping sound usually means wet filament. That being said, you didn't mentioned if it was pla/petg... Guessing it is pla due to the temp you are using but always best to mention it. Have you watched the print ? Did it actually change temp while printing? because between 190 and 220, there is usually more difference than what you have here, especially on the bridge part.

thanks for helping, I'm running a VM with HA OS (proxmox), i just realised that z2m crash when trying to pair those devices and watch dog isn't starting z2m back. I might load a backup when i was using my raspberry with conbee 2 and replace sonoff dongle by conbee 2 to see if same thing is happening which would indicate it has something to do with my proxmox VM

here are the logs when i try to pair:

Zigbee2MQTT:info 2023-11-28 16:13:42: Zigbee2MQTT started! Zigbee2MQTT:info 2023-11-28 16:13:48: Zigbee: allowing new devices to join. Zigbee2MQTT:info 2023-11-28 16:13:48: MQTT publish: topic 'zigbee2mqtt/bridge/response/permit_join', payload '{"data":{"time":254,"value":true},"status":"ok","transaction":"fh35x-1"}' Zigbee2MQTT:info 2023-11-28 16:13:52: Device '0xa4c138d5784acca7' joined Zigbee2MQTT:info 2023-11-28 16:13:52: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0xa4c138d5784acca7","ieee_address":"0xa4c138d5784acca7"},"type":"device_joined"}' Zigbee2MQTT:info 2023-11-28 16:13:52: Starting interview of '0xa4c138d5784acca7' Zigbee2MQTT:info 2023-11-28 16:13:52: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0xa4c138d5784acca7","ieee_address":"0xa4c138d5784acca7","status":"started"},"type":"device_interview"}' Zigbee2MQTT:info 2023-11-28 16:13:53: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0xa4c138d5784acca7","ieee_address":"0xa4c138d5784acca7"},"type":"device_announce"}' Error: Unhandled error. (TypeError: Cannot destructure property 'vendor' of 'data.device.definition' as it is null. at EventEmitter. (/app/data/extension/miboxer-fut089z-controls-exposer.js:151:21) at EventEmitter.emit (node:events:525:35) at EventBus.emitDeviceMessage (/app/lib/eventBus.ts:102:22) at Controller. (/app/lib/zigbee.ts:108:27) at Controller.emit (node:events:513:28) at Controller.selfAndDeviceEmit (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:527:14) at Controller.onZclOrRawData (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:738:18) at ZStackAdapter. (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:144:70) at ZStackAdapter.emit (node:events:513:28) at ZStackAdapter.onZnpRecieved (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:823:30)) at new NodeError (node:internal/errors:387:5) at ZStackAdapter.emit (node:events:502:17) at emitUnhandledRejectionOrErr (node:events:394:10) at processTicksAndRejections (node:internal/process/task_queues:85:21)`

here are the devices that failed to pair: https://www.zigbee2mqtt.io/devices/WSDCGQ11LM.html (i have 3 of those and one is failing to pair)

https://www.zigbee2mqtt.io/devices/TH02Z.html#tuya-th02z (did a mistake as i have 2 of them and none are pairing)

couple more devices that fails since i started thi post: https://www.zigbee2mqtt.io/devices/AB3257001NJ.html#osram-ab3257001nj

https://www.zigbee2mqtt.io/devices/ERS-10TZBVK-AA.html#tuya-ers-10tzbvk-aa

Edit: HA fail to load my backup file, saying it needs a .tar file (but i did point to a .tar file), will do a fresh install and load my backup to see if same is happening

Edit2: issue with backup file was due to firefox, works in chrome

Edit3: using my backup and conbee, everything works fine (at one exception, a zigbee remote which i remember was a pain to setup. remote is paired but not working yet... https://www.zigbee2mqtt.io/devices/FUT089Z.html

i'm pretty sure i have the P version, and i did flash latest firmware for P version, i did a complete Z2M setup as i also swapped my raspberry for a mini pc at the same time but i haven't tried with an usb extender, will try that in a few hours and will update my comment. Is there a way to check visually if i have the P version ? Thanks for your answer

Edit: can confirm i have P version, model: ZBDongle-P Edit2: just tried to pair them again with an usb extender but still same

Unless you can find an alternative firmware that can run docker, I don't see any other options. Wish you luck

Oh! Ok. Maybe you can try this https://community.home-assistant.io/t/installing-home-assistant-on-wd-mycloudex2ultra/530270

You need something like a raspberry or a small computer to run home assistant 24/7 and you also need a zigbee coordinator (to be able to use your ZigBee devices) like sonoff CC2652P or conbee 3 (others are available). Install home assistant, and learn how to manage/customise as you wish.

Home assistant is great but it's not a plug and play solution (that being said, it has already been much simplified over the years and it's not that hard to get started). Settings basics stuff isn't complicated but you will have a learning curve to be able to do more complicated stuff (depending of knowledge you already have)

https://www.home-assistant.io/installation/

I think it is best to first print a temp tower then some retraction test where you would stick with same temperature and variates distance and speed. You can use tools here to make it simple. https://teachingtechyt.github.io/calibration.html

If after that, you still have stringing, best is to test a new spool (or dry your spool) as too much humidity in pla will give you stringing whatever settings you use

Check HA Devs videos called "year of the voice" to know everything you have missed. Also atom echo isn't really a smart speaker, more a micro with a possible always listening mode

(not first hand experience but) Nabu casa is a way to support HA development, having cloud assistant is just a bonus, you also get easy external access and another bonus is that you don't need to setup the different addons to be able to use assist, while it is doable on something like raspberry 4, problem will be latency compare to nabu casa or you will need a more powerful device to be able to run them smooth. If you didn't bother to setup cloud assistant by yourself to avoid fees, chances are you will stick to nabu casa and it is a good thing as you are supporting home assistant development.

Have you tried to press Enter to show bios setup? (Don't have one, but that's what a quick search tell)

Thanks for the head up