Stopped working after upgrade to 2022.12

[grinco]

Upgrading to 2022.12.1 didn't solve it, so I'm assuming it's an issue with integration. After removing the integration, it loads but no devices are discovered.

Relevant message in the logs:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 281, in _async_setup_platform
    await asyncio.shield(task)
  File "/config/custom_components/jq300/binary_sensor.py", line 40, in async_setup_entry
    await account.async_update_sensors_or_timeout()
  File "/config/custom_components/jq300/api.py", line 573, in async_update_sensors_or_timeout
    await self.async_update_sensors()
  File "/config/custom_components/jq300/api.py", line 566, in async_update_sensors
    self._extract_sensors_data(device_id, ts_now, ret["deviceValueVos"])
  File "/config/custom_components/jq300/api.py", line 465, in _extract_sensors_data
    res[sensor_id] = float(sensor["content"])
ValueError: could not convert string to float: ''```


And "Setup of platform jq300 is taking longer than 60 seconds. Startup will proceed without waiting any longer."

[rogodra]

Same problem, with version 2022.12 it stopped working.

[albxox]

same here. not working after 2022.12

[grinco]

Guys, "same here" types of replies are counter productive. We now know that it's not an isolated case and there are more than one person affected by it. Let's keep this thread clean for actual updates or new information related to the issue.

[albxox]

I apologize if my comment caused offense. My intention was simply to provide additional information and suggest that there may be more cases than previously known. I understand that comments here are meant to be constructive feedback and to help prioritize efforts based on the number of affected cases. Please let me know if there is any way I can better communicate in the future to avoid causing offense. Sorry again, Albxox

…

On Fri, Dec 16, 2022, 22:32 grinco ***@***.***> wrote: Guys, "same here" types of replies are counter productive. We now know that it's not an isolated case and there are more than one person affected by it. Let's keep this thread clean for actual updates or new information related to the issue. — Reply to this email directly, view it on GitHub <#126 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIKW6E7XS5QL26CCOFT6WQLWNTGWJANCNFSM6AAAAAASZOKVU4> . You are receiving this because you commented.Message ID: ***@***.***>

[grinco]

I apologize if my comment caused offense. My intention was simply to provide additional information and suggest that there may be more cases than previously known. I understand that comments here are meant to be constructive feedback and to help prioritize efforts based on the number of affected cases. Please let me know if there is any way I can better communicate in the future to avoid causing offense. Sorry again, Albxox
…
On Fri, Dec 16, 2022, 22:32 grinco @.> wrote: Guys, "same here" types of replies are counter productive. We now know that it's not an isolated case and there are more than one person affected by it. Let's keep this thread clean for actual updates or new information related to the issue. — Reply to this email directly, view it on GitHub <#126 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIKW6E7XS5QL26CCOFT6WQLWNTGWJANCNFSM6AAAAAASZOKVU4 . You are receiving this because you commented.Message ID: @.>

That wasn't directed at you personally, and it definitely didn't offend me (and I hope anyone else). It's merely a suggestion to keep the thread clean. I'm sorry if it made you feel bad.

[grinco]

It started working after the last home Assistant update. Closing.

[grinco]

There are some intermittent issues. Haven't been able to consistently use the sensor for a few months - over the course of the last two releases.

Lately it won't even load the integration, as if the network connectivity is blocked to the API:

Logger: homeassistant.components.sensor
Source: helpers/entity_platform.py:261
Integration: Sensor (documentation, issues)
First occurred: January 28, 2023 at 11:44:30 PM (1 occurrences)
Last logged: January 28, 2023 at 11:44:30 PM

Setup of platform jq300 is taking longer than 60 seconds. Startup will proceed without waiting any longer. 

[grinco]

A few other errors like this one:

Error while setting up jq300 platform for binary_sensor
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 289, in _async_setup_platform
    await asyncio.shield(task)
  File "/config/custom_components/jq300/binary_sensor.py", line 40, in async_setup_entry
    await account.async_update_sensors_or_timeout()
  File "/config/custom_components/jq300/api.py", line 573, in async_update_sensors_or_timeout
    await self.async_update_sensors()
  File "/config/custom_components/jq300/api.py", line 566, in async_update_sensors
    self._extract_sensors_data(device_id, ts_now, ret["deviceValueVos"])
  File "/config/custom_components/jq300/api.py", line 465, in _extract_sensors_data
    res[sensor_id] = float(sensor["content"])
ValueError: could not convert string to float: ''

I can connect to both BASE_URL_API and BASE_URL_DEVICE, as well as subscribe to their MQTT service. They probably changed something in the API....

[rogodra]

I have the same problems, the sensors have not worked for a long time.

[remyderuysscher]

Comfirmed

[grinco]

This pull request fixes the issue: #129
For the time being feel free to test the code in this repo: https://github.com/grinco/ha-jq300

[grinco]

Here's a sample API response:

[{'content': '2', 'dptId': 1, 'seq': 1}, 
{'content': None, 'dptId': 1, 'seq': 2}, 
{'content': None, 'dptId': 1, 'seq': 3}, 
{'content': '20', 'dptId': 1, 'seq': 4}, 
{'content': '', 'dptId': 1, 'seq': 5}, 
{'content': '', 'dptId': 1, 'seq': 6}, 
{'content': '', 'dptId': 1, 'seq': 7}, 
{'content': '1.046', 'dptId': 1, 'seq': 8}, 
{'content': '701', 'dptId': 1, 'seq': 9}, 
{'content': '2700', 'dptId': 1, 'seq': 10}]

[grinco]

The problems seem to be with the upstream API. Even their official all doesn't show any data for the last 7 days, and the things like humidity are missing. Probably will be better off when someone reverse engineers the firmware to have local access to the sensor, or re-flash it with esphome....

[remyderuysscher]

No new release?

[rogodra]

This pull request fixes the issue: #129 For the time being feel free to test the code in this repo: https://github.com/grinco/ha-jq300

This modification in my case only causes the CO2 and TVOC sensors to activate, the P2.5 and HCHO sensors continue to not work.

It does not read any new information from the CO2 and TVOC sensors. The JQ300 shows data in its app, but it hasn't worked in HA for 2 months.

[grinco]

@

This pull request fixes the issue: #129 For the time being feel free to test the code in this repo: https://github.com/grinco/ha-jq300

This modification in my case only causes the CO2 and TVOC sensors to activate, the P2.5 and HCHO sensors continue to not work.

It does not read any new information from the CO2 and TVOC sensors. The JQ300 shows data in its app, but it hasn't worked in HA for 2 months.

Do you have any datapoints in the last few days? Check the 7 days history graph. If it's empty - you need to re-pair your sensor. It's not an integration issue, rather the vendor cloud problem. I completely stopped using this rubbish....

[rogodra]

Do you have any datapoints in the last few days? Check the 7 days history graph. If it's empty - you need to re-pair your sensor. It's not an integration issue, rather the vendor cloud problem. I completely stopped using this rubbish....

Thanks, with your issue, removing and re-pair, all the sensors work again.

[grinco]

Do you have any datapoints in the last few days? Check the 7 days history graph. If it's empty - you need to re-pair your sensor. It's not an integration issue, rather the vendor cloud problem. I completely stopped using this rubbish....

Thanks, with your issue, removing and re-pair, all the sensors work again.

Glad that it worked for you. I wish there was a way to provide this feedback to the engineers developing this product....