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.
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.