WiCAN Pro - data is garbled into other values

[mmstano]

Mostly, everything works, but the values for sensors in HA are messed up. I plan on setting up the MQTT method sometime this week to see if the values are sustained that way. The screenshots show WiCAN's web interface testing the correct values, but they are not sustained within the HA integration.

[wambs]

I had a similar issue. The test values were OK, but the MQTT values sent to HA were sometimes wrong causing my automations to go crazy. I fixed this in the wambs forked SW. Sometimes when the PID was sent the response was late, but the next PID was already sent. When the late response came back, it was use as a respo0nse for the second PID, and so on. I fixed this by checking that the response PID ID matched the sending PIDs ID. If there was a mismatch, the response is discarded. https://github.com/wambs/wican-fw/releases Latest version is v1.12, but this was fixed in V1.07

Docs are in https://wambs.github.io/wican-fw/

[mmstano]

@wambs Thank you. So this is more a WiCAN fw issue as opposed to a WiCAN HA integration issue. That's good to know. Does your fork work fine with the HA integration? Or will I need to setup MQTT?

[wambs]

I have not tried the HA webhooks lately. However, when I started work on the wambs fork, I had to patch the WiCAN HA integration. I do recommend you use the MQTT, it works well. There is an Auto discovery for MQTT, this creates the HA entities for you. https://wambs.github.io/wican-fw/web_interface/settings#mqtt-auto-discovery-zero-yaml-setup

[mmstano]

Awesome, thanks again. I'll flash it later this evening and give it a shot.