hmm… strange… I`ve done everything according the guide but after copied everything on the folders where they should be I have this mqtt error in paperUI . What can be the problem ?
Generic MQTT Thing OFFLINE - BRIDGE_OFFLINE
Generic MQTT Thing
mqtt:topic:dysonApBroker:dysonAp
and this
Generic MQTT Thing OFFLINE - BRIDGE_OFFLINE
Generic MQTT Thing
mqtt:topic:dysonApBroker:dysonAp
I assume it is not only the error message, you also got no values and it is not possible to control the air purifier.
The error states that it is offline, so the first question is if the device can be reached by the openhab server (you could try a ping to check). If the connection is there, the next possibility is the configuration.
Some questions to improve the possibility to help you:
Hi, thanks for your reply.
These are the files which I copied to the matching folders…
When I ping the device it works as it should.
MQTT Binding is 2.4.0 installed and the error what will be displayed sometimes in the paperUI is
“Status: OFFLINE - COMMUNICATION_ERROR Bad user name or password” when i open the binding.
Type of my Dyson is the blue Dyson (Pure Cool Link) and the SSID / PW is from the sticker inside from the fan.
Ok, so we are one step ahead, the communication in general is possible.
Next questions:
Hi Michael,
Where I can see or read out this logs ?
m a new Raspberry Pi User since maybe 1 week approx. What I tested as well if the mosquitoo in the Raspberry working as it should and when Ive done the tests with the 2 various terminals everything looks good. Message is transmitted.Will send you the dysonapbroker.things during lunchtime today when I have access to my Pi at home.
Hi Pipo,
I think I will have some time at lunchbreak to take a look on the file (I assume CET/UTC+1) .
Yes “Swiss” time 
But Im at work actually.. and this evening busy I think. Otherwise, maybe we can plan something next week if you cant find a failure.
But will look shortly at lunchtime on my Pi about the logs and the test message were done just after installing mosquitoo completely. Not to the Dyson itself.
But yesterday I just create a separate MQTT Broker and this was status green. But the Dysonapbroker not.
But anyway… great you can watch at this. 
For me, until recently worked great, now openhab can no longer connect with the broker, with an app or s.PC does not work anymore. I also recalculated the password via the tool, do not help either. it also looks like the dyson password has changed! Although I have disabled the update of the firmware, really bad.
maybe dyson will ruin your device if you want to sell something new!
With the additional information in the issue on github I enhanced the repo for the Dyson438 and tried to implement a minimum set with read out information (Temperature, Humidity and Power state). As first step I would try to get them working and enhance it later to the other parameters and the set command.
Therefore I need support by someone with the device at hand. Please try out the new files and give me some feedback if it works (log outputs etc.).
My 475 does not work anymore, because I no longer have access to the mqtt server. What can I do?
After testing around some parameters on the broker connection yesterday I experienced a loss of connection even after changing back the values.
I had to restart openhab first to get it back working. A plug out, plug in cycle of the air purifier could be a good starting point, too.
If you already tried a restart (and if does not work maybe reboot) and it still does not work, some additional information is needed to narrow down the root cause.
Logging in to the mqtt server works again, I’m just going to uninstall the original app everywhere and close the firewall for the dyson. Thank you for the effort, runs great under openhab 2.4 great work!
I tried the version that was online on Saturday morning. The prepare.py still has the problem that it cuts off the first parts of the serial. In addition I would suggest to set the shee-bang line (#!/usr/bin/python3). Everything else seems OK so far (on the sitemap I got the 3 values power, temp and humidity life from the tower).
For the 455, 469 and 475 it is necessary to cut off the first part of the serial as it is “DYSON-” and not part of the username in MQTT.
As it seems to be not necessary for the 438 I will include an exception for it.
Good point with the first line!
Thank your very much for the feedback! 
I am on Openhab 2.4 (in docker) and get errors as well.
Mine being “OFFLINE - COMMUNICATION_ERROR java.lang.Exception: No MQTT client” on Generic MQTT Thing.
Generic MQTT Thing
mqtt:topic:dysonApBroker:dysonAp
My broker says it is online
MQTT Broker
mqtt:broker:dysonApBroker
I also had to embedded broker installed at one point but it didn’t help and removing it made no difference either.
I can ping my 455 from my computer and using MQTTBox I can subscribe to the status commands that are triggered by my app.
Any ideas?
Thanks
Steve
Progress here, after a openhab restart i have responses, like;
Dyson455_Topic_Status_Current changed from {“msg”:“ENVIRONMENTAL-CURRENT-SENSOR-DATA”,“time”:“2019-02-05T21:10:02.001Z”,“data”:{“tact”:“2906”,“hact”:“0054”,“pact”:“0000”,“vact”:“0001”,“sltm”:“OFF”}} to {“msg”:“CURRENT-STATE”
etc.
The issue is, that the item values aren’t updating.
Any ideas?
Thanks
Steve
Never mind. I didn’t have the JSONPath transformation.
Fixed it and everything is fine now. Now to get my pure cool working as well.
Update.
So I have some 438 progress but I did it manually and it is still work in progress.
There is a caveat:
There is no “Product WiFi Password” as the wifi set-up is done via BLE not Wifi in access-point mode. Just like my 455, my 438 password is 88 characters and looks like some kind of hash, but it isn’t the serial number using the existing hash.
All the 2018 versions are the same.
The username is just the serial number, i.e. “XXX-XX-XXXXXXXX”, same with the stateTopic and commandTopic.
To find your password you need to use wireshark to capture the password that is sent from your phone app to the unit. I power-cycled my 438 and intercepted the traffic to it, the password was then easy to copy out.
I can get the items for my 438 updated, I’ve modified a few as there some big differences, by triggering a CURRENT-STATE command from the MQTTBox app on my computer. Openhab sending the CURRENT-STATE command doesn’t seem to get out of Openhab. Maybe there is an issue trying to run a 455 and a 438 on the system? I have duplicated the bridge & app broker with unique names but its not working right now. I can see the 455 messages using MQTTBox, but nothing for 438 messages.
I will post further updates as I track down any issues.
For newer models, (like TP04/DP04), authentication is enabled by using a Dyson account registered with the device.
That’s what I assumed as well but I’m struggling to understand what the figures mean, as in what scale they’re measured on and how the two figures relate to the graph that’s shown in the Dyson app.
My TP04/438/Pure Cool (2018) is now fully working (almost). Struggling to control the variable oscillation angle, think my commands aren’t in the correct order.
Everything else works though.
If you have one of these new models you either need to get wire shark in-between your phone and the Dyson unit, or, use a method that talks via the cloud.
Obviously the cloud method is at risk of the system changing to only talk to official Dyson apps, but getting wireshark between 2 wifi devices is not the easiest thing. Raspberry Pi is your friend, or a packet capture app if you are on android.