rainepretorius / olarm-ha-integration

Integration for Olarm devices created by a BSC(Computer Science and Mathematics) student.
https://raine.pretoriusse.net
BSD 2-Clause "Simplified" License
30 stars 13 forks source link

[Bug]: Unable to serialize to JSON #88

Closed rwoeke closed 11 months ago

rwoeke commented 1 year ago

Contact Details

rwoeke@gmail.com

What happened?

Hi, When Updated to the latest version of Olarm integration everything stopped working. When I try and add the integration I get this error? Am I missing something. Running version 2.2.5

Sample of error on front end image

Version

2.2.5

Relevant log output form Home Assistant

Logger: homeassistant.components.http.view
Source: components/http/view.py:62
Integration: HTTP ([documentation](https://www.home-assistant.io/integrations/http), [issues](https://github.com/home-assistant/core/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+http%22))
First occurred: 17:33:03 (1 occurrences)
Last logged: 17:33:03

Unable to serialize to JSON. Bad data found at $.errors<key: <class 'str'>>=<class 'str'>(<class 'type'>

Downloaded integration debug logs.

Logger: homeassistant.components.http.view
Source: components/http/view.py:62
Integration: HTTP ([documentation](https://www.home-assistant.io/integrations/http), [issues](https://github.com/home-assistant/core/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+http%22))
First occurred: 17:33:03 (1 occurrences)
Last logged: 17:33:03

Unable to serialize to JSON. Bad data found at $.errors<key: <class 'str'>>=<class 'str'>(<class 'type'>
rainepretorius commented 1 year ago

Hi @rwoeke , This seems to be an issue with Home Assistant itself as specified here: homeassistant.components.http.view in the logs. Maybe just try to redownload the integration and check again?

rwoeke commented 1 year ago

Only way I could get it to work is to redownload as 2.2.2 in other words happen when I upgrade olarm integration to latest

image

rainepretorius commented 1 year ago

If you download 2.2.2 and then instal 2.2.5?

rwoeke commented 1 year ago

not sure if thats a trick question, but I re-downloaded version 2.2.2 and installed it as well.

Running on 2.2.2 there is no issue.

image

rainepretorius commented 1 year ago

I tried to see if I could fix it in 2.2.6 released just now?

rwoeke commented 1 year ago

looks like it does the same on 2.2.6

image

rainepretorius commented 1 year ago

Ok. Let me look at the options one. Does it install but not later allow configuring?

rwoeke commented 1 year ago

I had 2.2.2 installed, updated the integration and tried to configure. both ways does not work

Vlerrie commented 1 year ago

Also had issues when I upgraded to 2.2.5. Uninstalled everything and re-installed to 2.2.6 and seems to be working again.

rwoeke commented 1 year ago

Hello

I'm running on 2.2.6 now, but see this in the log pop up many times. Any idea what could be the cause of this. I have two devices, but only the one was selected. (Mon R) is my active one and everything seems to be working, just this error popping up in the logs.

This error originated from a custom integration.

Logger: custom_components.olarm_sensors Source: custom_components/olarm_sensors/olarm_api.py:277 Integration: Olarm Sensors (documentation, issues) First occurred: 07:23:58 (26 occurrences) Last logged: 07:39:59

Olarm sensors error for device (Mon R): list index out of range