The adapter sees this device (type 0x4e2a) but does not know how to handle it. I do not know Vortex wifi control AC and this broadlink type number, and therefore broadlink2 lists it as unknown device. The problem is that nobody know which parameters need to be read or sent to the device to make it working. This could be found only if you have a network sniffer and record all packages sent/received by the device. and reverse-engeneer the commands.

Thank you. Since mySENSORS adapter is about to be fixed to allow nodes with number >10, see latest GitHub, I will stick with adapter.

Hi wendy...super, danke. genau sowas habe ich gesucht. Grund, dass es bei mir nicht funktionierte war, dass ich mit dem Passwort mit dem ich registriert war und nicht mir dem aus der Email gearbeitet habe. Jetzt funktioniert es. Vielen Dank!

solved because of a ESXi 6.5 VMXNET3 Adapter Bug.

I solved it by mapping the path for the container. And tried to delete this thread but it wouldn't let me.

Anyone? Please! I have such a great integration with Loxone to be shared, but lack of that data would be just a shame :( [image: 1584800776696-8788d930-fa56-4c38-b355-c9ff8efda1f3-image.png] I have already found that if I manually change value within ioBroker panel (for instance: remaining filter, from 92% to 90%) then the value gets published to MQTT instantly. But they don't get published upon MQTT-client adapter restart, despite setting publish - enabled ("changes only" is not checked). And as those values change very rarely, I would need to wait long tome to get them published for the first time.... Any idea on workaround such as forcing initial publish of all mqtt-client configured values? Update: Seems I've sorted it out (kind of) with adapter author, see link below if interested https://github.com/Pmant/ioBroker.mqtt-client/issues/34

@arteck sagte in Zigbee Errors in Log: @ap2017 this error message is "ok".. one device has a timeout .. and the herdsman send this message... Hi arteck :-) If an error message is "ok", wouldn't it make sense to catch the error, change it to a "warn" and not "error" message and limit to one single log line? If you agree, then I will open a Github issue to consider for future updates.

@Dutchman sagte in How to lower disk writes (for extending life of an sd card): Better than every 30 seconds 🤷‍♂️ Exactly, and the default value can certainly be increased to whatever is needed. I would give Redis a try. Also, @Tomasz-Nowak sagte in How to lower disk writes (for extending life of an sd card): They say good for many objects such has 10000 for performance reasons I would assume this statement in the documentation was just made for the ease of use of ioBroker in general: Without like Redis, typically ioBroker's performance is good if you have way less than 10000+ objects. You are having a different use case (limited disc r/w per period). Not sure how the performance (like CPU and memory usage) of Redis is on a Raspberry, but I guess pretty low.

@erfan-shaigani I can not write a Node-Red tutorial here - but there are a lot of videos. I can recommend this site - to get familiar with Node-RED this page: http://www.steves-internet-guide.com/node-red-overview/ and his starter video: https://www.youtube.com/watch?v=y05vQUIMIxs&feature=youtu.be instead of the mqtt-in node - you can use the "iobroker in" node. So if you have open your node red - drag an "iobroker in" node into the flow area. Configure this node by opening this node - and select your datapoint of your temperature sensor - as you can see in my screen-shot. Then wire for the first time a debug node to the "iobroker in" node and have the debug window open in node-red. Everytime your temperature will change generates a new message, which you can see in the debug window. With this message - containing the temperature you can do what you want. Create your json string, you can use to put it in an other data object, write to a file, a database, put in an http-request and even use the simple api. [image: 1584286872463-io.png]

It was resolved already by turning off "Use aliases"

=== PLEASE READ === Please describe the changes proposed in the pull request and reference the issue, the pull request relates to (if applicable).

Read out device properties optionally via ioBrocker.State or similar. With this you can automatically read and enter the firmware, serial number, manufacturer etc..

@Asgothian Thank you, it works!

@arteck 0.11.5

That's exactly the point. The config is determined by manufacturer and product and that's also what is displayed in the admin screen. But the name of the channel is taken from the valueId label. So: the device is not in the openzwave database but it still reports the name. Fix: report it to openzwave