Metadata.Odoo MyEdge casting conflicts?

Hello,
I just set up odoo and Metadata.Odoo component in the backend server with all the necessary credentials, but in the terminal it doesn’t seem to be able to recognize the edge device connection to backend and it gave me this error:

2024-06-17T09:46:59,333 [thread-1] INFO  [.debugcycle.DebugCycleExecutor] [Metadata.Odoo] [monitor] Default: Pool: 0/15, Pending: 0, Completed: 0, Active: 0, EdgeConfig: Pool: 0/15, Pending: 0, Completed: 0, Active: 0, Tasks: 
2024-06-17T09:46:59,335 [thread-1] INFO  [.debugcycle.DebugCycleExecutor] [Ui.Websocket] [monitor] Connections: 0, Pool: 0/10, Pending: 0, Completed: 0, Active: 0
2024-06-17T09:46:59,335 [thread-1] INFO  [.debugcycle.DebugCycleExecutor] [Edge.Websocket] [monitor] Connections: 1, Pool: 10/10, Pending: 0, Completed: 617, Active: 0
java.lang.ClassCastException: class io.openems.backend.metadata.dummy.MyEdge cannot be cast to class io.openems.backend.metadata.odoo.MyEdge (io.openems.backend.metadata.dummy.MyEdge is in unnamed module of loader org.apache.felix.framework.BundleWiringImpl$BundleClassLoader @3c025fcd; io.openems.backend.metadata.odoo.MyEdge is in unnamed module of loader org.apache.felix.framework.BundleWiringImpl$BundleClassLoader @5231a31a)
	at io.openems.backend.metadata.odoo.MetadataOdoo.handleEvent(MetadataOdoo.java:357) ~[?:?]
	at org.apache.felix.eventadmin.impl.handler.EventHandlerProxy.sendEvent(EventHandlerProxy.java:432) ~[?:?]
	at org.apache.felix.eventadmin.impl.tasks.HandlerTask.runWithoutDenylistTiming(HandlerTask.java:82) ~[?:?]
	at org.apache.felix.eventadmin.impl.tasks.SyncDeliverTasks.execute(SyncDeliverTasks.java:107) ~[?:?]
	at org.apache.felix.eventadmin.impl.handler.EventAdminImpl.sendEvent(EventAdminImpl.java:155) ~[?:?]
	at org.apache.felix.eventadmin.impl.security.EventAdminSecurityDecorator.sendEvent(EventAdminSecurityDecorator.java:96) ~[?:?]
	at io.openems.common.event.EventBuilder.send(EventBuilder.java:80) ~[?:?]
	at io.openems.backend.common.metadata.Edge.setLastmessage(Edge.java:146) ~[?:?]
	at io.openems.backend.common.metadata.Edge.setLastmessage(Edge.java:134) ~[?:?]
	at io.openems.backend.common.metadata.Edge.setLastmessage(Edge.java:124) ~[?:?]
	at io.openems.backend.edgewebsocket.OnNotification.lambda$0(OnNotification.java:52) ~[?:?]
	at java.util.Optional.ifPresent(Optional.java:178) ~[?:?]
	at io.openems.backend.edgewebsocket.OnNotification.run(OnNotification.java:51) ~[?:?]
	at io.openems.common.websocket.OnNotificationHandler.run(OnNotificationHandler.java:22) ~[?:?]
	at io.openems.common.websocket.AbstractWebsocketServer.lambda$3(AbstractWebsocketServer.java:332) ~[?:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) ~[?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) ~[?:?]
	at java.lang.Thread.run(Thread.java:840) ~[?:?]

How do I fix this?

please try to rename your device. I do not know about the exact conventions, but I can say that “edge0” works.

Regards,
klinki

Hi, I cannot rename my device on odoo. It says “The operation cannot be completed: Name needs to be unique.” Initially I could name the device “edge0” but ] I archived the protocols and device once before and now try to create it again that happens. I’m also still confused as to how you integrate odoo with backend on windows for user authentication so could you perhaps provide me some instructions on setting it up?
If integrating Odoo doesn’t work how do I atleast change the username and password to backend ui webserver on localhost:4200?

Thank you,
Hailey

I am new to the backend topics. As far as I know you can not delete a device totally. You only can archive it. So the name cannot be used for another device.

I am still trying to find “my” way through all this user authentication stuff, too.

If the record in Odoo was only archived, it is still there in the database. Just select Filter → Archived in the Odoo view and you will be able to see all archived devices.
grafik

You can then “un-archive” the record.

Regards,
Stefan